TABLE OF CONTENTS Modeling the object flow is shown in Table 2.15.
| Reference card: Model domain knowledge. | |
|---|---|
| | Incoming and outgoing data Requirements: General requirements to the system. Use cases [object flow]: Use cases with object flow in flow descriptions. Domain knowledge: Structures of the system's domain terms. |
| Motivation/description Why? The domain objects you are using in the object flow of activities have to be described in order to ensure that all stakeholders reach a uniform understanding and that they are used consistently in the model. What? Model the structures of the domain-relevant terms from the system's view. How? Model the terms and their structures as domain blocks in a block definition diagram. Where? The domain knowledge model reflects the static view of the domain logic; it is well suited for coordination with the principal and as a design basis. | |
| Guiding questions
| |
| SysML elements Block definition diagram, SYSMOD: domain block, association, generalization. |
The domain terms we are dealing with in our project are described in the glossary (Section 2.6). Some terms described there directly concern our system. The system "knows" and uses the terms listed in the glossary. For example, a customer is known to our system. In the use case start car usage, the customer is identified. In the display unit, they...
