The following table lists the products that the IBM® Rational® Rhapsody® for DoDAF Add On includes.
| Architecture Product | View | Product Name | Product Description |
|---|---|---|---|
| All Views | Package | AllViews | This optional stereotyped package allows you to add in AV products and other views and packages, if wanted. |
| AV-1 | All | Overview and Summary Information |
This product is typically a text (Word, FrameMaker, HTML) document. You can add AV‑1documents and launch them by clicking on them. |
| AV-2 | All | Integrated Dictionary |
This is a DoDAF‑generated text product (report). |
| Operational View | Package | This optional stereotyped package is similar to the All View product. It supports all the operational products. | |
| OV-1 | Operational | High-Level Operational Concept Graphic |
This high-level graphical/ textual description of the operational concept allows you to import pictures and other operational elements, such as Operational Nodes, Human Operational Nodes, Operational Activities and the relations among them. |
| OV-2 | Operational | Operational Node Connectivity Description | This product shows the connections and flows among operational nodes and operational activities. If wanted, the behavior of operational nodes and operational activities can be shown by adding OV‑5, OV‑6a, OV‑6b, and OV‑6c diagrams. These diagrams are the primary source of information used by the Rational Rhapsody for DoDAF Add On to create the OV‑3 diagram. |
| OV-3 | Operational | Operational Information Exchange Matrix |
This product shows information exchanged between nodes, and the relevant attributes of that exchange. OV-3 is generated from the information shown in OV‑2 and other operational diagrams. This information is stored as a CSV file and can be added to any product. |
| OV-5 | Operational | Operational Activity Model |
This product details the behavior of operational nodes or more commonly, operational activities. |
| OV-6a | Operational | Operational Rules Model | This product is a textual description of "business rules" for the operation. It is a controlled file. One of three products used to describe the mission objective. |
| OV-6b | Operational | Operational State Transition Description |
This product is a statechart that can be used to depict the behavior of an operational element (node or activity). One of three products used to describe the mission objective. |
| OV-6c | Operational | Operational Event Trace Description | This product is a sequence diagram that captures the behavioral interactions among and between operational elements and (in the Harmony process) captures the operational contracts among them. One of the three products used to describe the mission objective. |
| OV-7 | Operational | Logical Data Model | This product is a class diagram that shows the relations among Informational Elements (data classes). This is similar to entity relationship diagrams, but is more powerful. |
| System View | Package | This optional stereotyped package is similar to other views, but contains system elements. | |
| SV-1 | Systems | Systems Interface Description |
This product is a diagram that contains System nodes, systems, system parts and the connections between them (links). These can be used with or without ports. |
| SV-2 | Systems | Systems Communications Description |
This product is a diagram that shows the connections among systems via the communications systems and networks. |
| SV-3 | Systems | Systems-Systems Matrix | This product is generated from the information in the other system views. SV‑3 assumes that there are links between items stereotyped SystemNode, System, or System Part and represents these in an N2 diagram (system-system matrix). |
| SV-4 | Systems | Systems Functionality Description |
This product represents the connection between System Functions and Operational Activities. The connection is made by drawing a Realize dependency line from the System Function to the Operational activity on the diagram. System Functions are mapped onto the system elements that support them by making System Functions parts of the system elements (that is, System Functions are drawn within the other system elements). System elements can also realize system functions. Note that here, as in almost all the other views, you can use Performance Parameters (bound to their constrained elements via anchors) to add performance data. This is summarized in SV‑7. |
| SV-5 | Systems | Operational Activity to Systems Function Traceability Matrix |
This product is a spreadsheet-like generated view summarizing the relations among system elements (system nodes, systems and system parts), system functions that they support, and the mapping to operational activities. |
| SV-6 | Systems | Systems Data Exchange Matrix | This product shows the information in the flows (information exchanges) between system elements. They might be embedded flows (bound to the links) or they might be flows independent of links. This is a spreadsheet-like generated product. |
| SV-7 | Systems | Systems Performance Parameters Matrix |
This is a generated spreadsheet-like product, showing all the performance parameters and the elements that they constrain. |
| SV-8 | Systems | Systems Evolution Description |
This product is the system evolution description. This is an activity diagram (there is a SystemProject element stereotype to serve as the "base" for this activity diagram). SV‑8 depicts the workflow for system development, object nodes for products released, and performance parameters for things like start and end dates, slack time, and so on. |
| SV-9 | Systems | Systems Technology Forecast |
This product is a text document - a stereotype of a Controlled File. |
| SV-10a, SV-10b, SV-10c |
Systems | Systems Rules Model, Systems State Transition Description, Systems Event Trace Description |
These products are similar to the OV‑6a, OV‑6b, and OV‑6c products, but they are separately identified, even though they are structurally identical. |
| SV-11 | Systems | Physical Schema | This product is similar to the OV‑7 class diagram. This product uses a class diagram to show physical schema (data representation). |