System Model-Time

Zachman Definition

"Processing Structure”

This is the logical (implementation - technology neutral) systems specification of points in time (systems events) and lengths of time (processing cycles).  This model describes the system events that trigger the state to transition from one valid state (point in time) to another and the dynamics of that transition cycle.  This style of model is represented in the notation of an entity life history diagram (from the SSADM methodology that originated in the U.K.) or in the notation of a Harel state chart (in an Object-Oriented approach).  Petri Nets are also used to express at least the relative time (sequence) aspects of time.

Select Perspective

When using the Select Perspective, Harel State Charts and UML Activity Diagrams are used to model states and the Business Events that trigger transition from one to another; UML Activity Diagrams are an extension of the Harel Charts and may be used in many parts of the development lifecycle for different reasons.

Although Select Perspective is primarily concerned with discovering and designing run-time components which, in a distributed environment, are generally stateless, Harel Charts and Activity diagrams are used to indicate user interface flow and model Business Rules for complex business scenarios.

Select Solution Factory

UML requires that State Charts may be constructed for individual objects and that Activity Diagrams may be constructed for Use Cases and class operations; Select Architect also supports constructing Activity Diagrams for classes.

For the Enterprise model, Select Business Solutions recommends that either:

a.  A relevant business concept ie an Order, be created as a class in the Select Architect Enterprise Model and a State  Diagram constructed for it:

or

b.  A relevant Use Case that deals with the concept is chosen and an Activity Diagram drawn for it; Use Cases can be mapped directly to Business Processes from the Business-Time cell:

Back to Top