-
Notifications
You must be signed in to change notification settings - Fork 1
Dependency Model
Description: For representing a Goal, the Designer should use a single linear sequence of Objectives. Therefore every Objective should be directly or indirectly connected to every other one. Supported notation elements are: Objectives with labels and transitions in one direction between them.
Example: To give an impression about how a dependency model can look like, please have a look at the figure shown below.
Example_DEP1
References:
Description: Every Goal has a so called Start State that is neither renamable nor deletable. It describes the initial situation and in order to fulfil Guideline DEP1, especially the Start State must also be included into the dependency graph.
Example: To give an impression about how a dependency model can look like, please have a look at the figure shown below.
Example_DEP2
References:
Description: When there is a cycle in the dependency model it is not clear which Objective is the first one to be fulfilled. The Designer should make sure to only create linear sequences of Objectives to obtain clarity of their processing order.
References:
Description: When there is a cycle in the dependency model it is not clear which Objective is the first one to be fulfilled. The Designer should make sure to only create linear sequences of Objectives to obtain clarity of their processing order.
References:
Description: The designer should use meaningful names for each Objective. Objective names should be unique within one Goal.
References:
Background
General Characteristics of fCM (> old wiki)
Example Use Case Construction Process Goal Modeling for-Construction-Modeling
Modeling
Data Modeler
Fragment Modeler
Objective Modeler
Dependency Modeler
Resource Modeler
Role Modeler
General (> old wiki)
Fragment Model
Dependency Model
Objective Model
Consistency (> old wiki)