| Topics |
Details |
Weights |
| MODELS OF REQUIREMENTS |
| Interpreting Requirements on Requirement Diagrams |
- The concept of "requirement", key relationships including derive, verify, satisfy, refine, trace, containment as well as the Requirement Diagram description, purpose and benefits. |
7% |
| Interpreting System Functionality on Use Case Diagrams |
- Use Case Diagram description, purpose and benefits, use case structure encompassing use case, actor and subject, as well as basic relationships including association, include, extend and generalization. |
7% |
| MODELS OF SYSTEM STRUCTURE |
| Interpreting System Structure on Block Diagrams |
- Package Diagram description, purpose, and benefits, aspects of packages including ownership of elements and defining a namespace, relationships including containment and dependency, and concepts of view and viewpoint. |
7% |
| Interpreting System Structure on Block Diagrams |
- Block definition and description, including definition vs. usage, valuetype (with units), block features including value properties, parts, references and operations. Block Definition Diagram description, purpose, and benefits, compartments,relationships between blocks including specialization and associations (including composite but not shared aggregation), multiplicities. Internal Block Diagram description, purpose, and benefits, enclosing block,flow ports and standard ports, connectors and item flows as well asrepresentation of parts. |
22% |
| Interpreting System Constraints on Block Definition Diagrams and Parametric Diagrams |
- Interpreting constraint blocks on Block Definition Diagrams, Parametric Diagram description, purpose and benefits, constraint properties, parameters and expressions, connecting constraint properties and value properties with binding connectors. |
7% |
| MODELS OF SYSTEM BEHAVIOR |
| Interpreting Flow-Based Behavior on Activity Diagrams |
- Activity Diagram description, purpose, and benefits, I/O flow including object flow, parameters, parameter nodes and pins, control flow including control nodes, activity partitions (swimlanes) and actions including decomposition of activities using call behavior action,send signal action, as well as accept event action. |
13% |
| Interpreting Message-Based Behavior on Sequence Diagrams |
- Sequence Diagram description, purpose and benefits, lifelines, asynchronous and synchronous messages, and interaction references (to elements outside the diagram). |
7% |
| Interpreting Event-Based Behavior on State Machine Diagrams |
- State Machine Diagram description, purpose, and benefits, states and regions including state, regions, initial state and final state, transitions including trigger by time and signal events, guard and action (i.e., effect), as well as behaviors including entry, exit and do. |
10% |
| CROSS-CUTTING CONSTRUCTS |
| Interpreting Allocations Across Multiple Diagram Types; Other Topics |
- Allocation description, purpose and usage, AllocatedFrom and AllocatedTo, representation including callouts, compartments, allocate activity partitions, and tables, special notations for comment, rationale, problem and constraint. Some concepts relating to diagrams: diagram frames, ports, parameters and anchors on diagram frames, diagram header and diagram description as well as stereotype. |
20% |
Posts
0 comments:
Post a Comment