Filter
Top Products
28 Model Driven Systems Development with Rational Products
Views
Views constitute the intersection of viewpoints and model levels. Views contain
artifacts (that is, objects used to document engineering data) that describe how
the viewpoint’s engineering concern is addressed at a particular model level.
Table 2-3 includes a sample set of view artifacts. In practice, each program
chooses the view artifacts that meet its individual needs. The project’s set of view
artifacts is what the RUP calls the development case, which includes the choice
of artifacts and prescriptive guidance on how to document them, along with
guidelines, templates, and checklists.
The framework might leave the impression that the views contain unrelated
artifacts. In reality, there are many relationships between the artifacts. These
relationships are captured in the MDSD meta model.
6
Table 2-3 RUP SE architecture framework (cells shows sample model views)
Transformation methods
MDSD includes novel, related artifacts for transformation methods between
model levels. The generation of these artifacts and their relationships requires
new techniques. These techniques are described next.
6
See footnote 7 on page 5
Model
levels
Model viewpoints
Worker Logical Information Distribution Process Geometric
Context Role
definition,
activity
modeling
Use case
diagram
specification
Enterprise
data view
Domain-
dependent
views
Domain-
dependent
views
Analysis Partitioning
of system
Product logical
decomposition
Product data
conceptual
schema
Product
locality view
Product
process
view
Layouts
Design Operator
instructions
Software
component
design
Product data
schema
ECM
(electronic
control
media)
design
Timing
diagrams
MCAD
(mechanical
computer-
assisted
design)
Implemen-
tation
Hardware and software configuration