Orthgonality, Software Engineering, Agilist

What Have I learned about Orthogonality, Software Engineering, and being an Agilist?

Some possible Definitions:

1. Software Engineering: composed of analytical drawings and supportive documentation (Narratives) showing an existing or proposed application system from several perspectives
   1. Event Model – a graphic showing events coming from their sources (External people or other modules/applications) and which internal or in-scope process is expected to respond to each event
      1. It is also expected that there be a date-driven Process responsible for creating or delivering Events specific to key dates that are needed to drive the application
         e,.g.: If an application must take specific action at the end of particular time periods. Then, this Date-Driven Process can notify the application when “End Of Cycle” dates occur, such as the end of the week, Month, Quarter, Year, or Decade.
   2. Process Model – a graphic showing how each in-scope process responds to its input and generates output to other processes or external recipients. Often, data files/objects are also represented visually on the Process Model.
   3. Data Model – a graphic showing each in-scope data entity or collection of data and the relationships between each Entity. Relationships are usually documented in the following format:
      1. One (to many) data row(s) in an entity {MUST or CAN} be related to One or More rows in another entity
      2. A Recursive relationship is where one or more data rows {MUST or CAN} be related to One or More rows in the SAME entity
   4. State Model – a graphic showing how a Process will change the State of an output data row based on the process’ logical rules and actions
2. Orthogonality: a validation effort to reconcile any one Model to each of the other Models, showing how each Model represents the same in-scope behaviors or capabilities of the overall application under investigation. When all Models are shown to represent the same and only the same set of capabilities, are these Models considered to be “Orthogonal”.
3. Agilist: A member of any Project Team who has expert knowledge of the techniques and processes of the Agile Methodology or Manifesto. The Agilist provides consulting assistance to their project team to perform and apply the Agile techniques in an appropriate manner and times throughout the execution of their projects.