Getting Started
Begin by reviewing Section 5 of the Redbook, "Model Driven Systems Development with Rational Products". Also, the
whitepaper "Rational Unified Process for Systems Engineering Part III: Requirements analysis and design". Study the
concept of a viewpoint.
Joint realization consists of the following procedure:
-
Choose the participating viewpoints. The logical viewpoint is mandatory.
-
For each white-box step in realizing a black-box service, you must:
-
-
Specify the logical element that executes it.
-
Model how the additional viewpoints participate. For example, you might include a Distribution viewpoint:
specify hosting locality; if there are two localities, then decompose into two steps.
-
Throughout this process, apply the following joint realization rule: If a given logical element white-box
step requires more than one element of the other viewpoints, divide that step into further steps so that
each step requires exactly one white-box element from each viewpoint.
-
Create interaction diagrams for each viewpoint:
-
-
Architecture Interaction Diagram
-
Maybe a Locality Interaction Diagrams
-
Budget supplementary requirements for performance, accuracy, and so forth, to each step; evaluate/confirm with
interaction diagrams.
Common Pitfalls
There's only one architecture
A logical architecture isn't necessarily the same as a distribution architecture. The logical architecture helps one
reason about the groupings of functionality. The distribution architecture is used to reason about some of the
non-functional requirements and constraints. How a system performs its functions and includes concerns such as quality,
quantity, and timeliness. These are just two different viewpoints that are important, but depending on the application
other viewpoints such as security may need to be used in the analysis.
Consider only functional requirements
A frequent pitfall is to consider only functional requirement during your development activities. A common mistake is
to overlook non-functional requirements, as availability, security, performance. Realization of both functional and
non-functional requirements will ensure the success of your design.
|