Visualizing The Situation

All-In-1-Glance To Essential Diagrams

Cutimbo

You really just require 6 diagrams. They are

1. User Case 
2. Timing, Swimlane (Sequence)
3. Flow Chart
4. State Machine
5. Block-Component Flow
6. Entity-Relationship

story -> picture -> definitions -> specifications -> design

The architecture is a map, and it’s usefulness and utility is based on how the developers can find themselves chart and navigate themselves (and orchestrate among themselves) the clarity of the tasks of constructing the parts manifest into realization. The decomposition of different components in different scenarios and different states demonstrates what is expected of the functionality to realize the serviceability and/or expected situational operational outcome. It also clearly shows the interaction and integration. It has to serve as both as a map, a plan which points to the reference manuals of building the parts as well as integrating them into a seamless body of work. The visibility must cover Situation, Systems, and Solutions.

In each perspective, there are layers and modules of abstractions depicting SIO (Subjects, Interfaces, Objects). It tells a story of their raison d’etre and their nature (and properties) of existence. Profiling their existence in each perspectives give us a clarity of their expected…