|


System Model-Function
Zachman Definition
"Application Architecture"
This is a model of the logical (implementation - technology
neutral) "systems" implementation (manual and/or automated) supporting the
Business processes and would express the "human/machine" boundaries. It would likely include the "controls
and mechanisms" as well as the "inputs and outputs" to the logical systems
representations of the systems functions/processes.
Select Perspective
The Select Perspective supports the requirements of this cell by
the products of the Consume/Business Alignment/Define Business
Requirements Stage of the Supply, Manage and
Consume (SMaC)
Service and Component Based Development model.
Specifically, all the requirements of this cell may be met
by UML Use Case specifications and Use Case diagrams but may be
supplemented by User Interface prototypes and 'logical' UML Object
Sequence Diagrams (OSD).
Each
of the Business Processes lowest in the Process Hierarchy diagrams
produced in the Business-Function cell
(known as Elementary Business Processes (EBP) that is/will be supported by
the system is, initially, mapped one-to-one with a Use Case; further
analysis of the resulting Use Cases may result in a
one-to-many,many-to-one or many-to-many mapping.
Select Solution Factory
Use
the Properties Editor for each EBP in Select Architect
to link the EBP with one or more Use
Cases. You can either create Use Cases in the model with
the Associated Items Property tab:

or link to
Use Cases that already exist in the model Dictionary:

Use the
Properties editor for each Use Case to document the Use Case Specification
using the default Specification headings, changing them or adding your
own:

Back to Top
|