User Tools

Site Tools



Software behaviour is what the user perceives. It's the software's runtime properties. Behaviour is solely implemented by Logic.

Software shows behaviour when triggered. A trigger can be starting the program, clicking on a button in a dialog, a REST call arriving, or the contents in a file changing.

In any case a trigger is processed by executing Logic residing in a function. This function can be located on a Controller or a Dialog.

Triggers are of different kind:

  • Request → Response
    • Command → Status
    • Query → Result
  • Event

Requests are sent to the software in order to cause a certain behaviour; they are intentionally directed at the software by an actor in the environment. Events on the other hand are information about something that happened in the environment which the software is curious about.

Request sources depend on the software for some behaviour, event sources do not; they might even be oblivious to the software's existence.

All triggers carry some data with them which the software takes as input, or they explicitly or implicitly point to data to be used as input (e.g. in memory or in a database).

All triggers cause the execution of Logic to transform the input into output. Output is passed back to the source of requests and/or send elsewhere (e.g. to some memory location, a database, or a printer).

From the point of view of a customer software development primarily is about turning a computer into a machine offering certain behaviour as a reaction to triggers. Software is supposed to show required Functionality and Efficiency.

behaviour.txt · Last modified: 2018/04/22 10:42 by fdadmin