-
Notifications
You must be signed in to change notification settings - Fork 1
Fragment Modeler
All features from the "fcm design support" tool were adopted. The respective wiki entry can be found here.
In the construction context, the execution of activities gets planned. In this context activities need estimated durations and are assigned to employees. Therefore we extended the definition of activities and added the possibility to define a duration and a role able to execute the specific activity together with a needed number of people (NoP).
Roles are modeled in the Role Model and instantiated (assigned to resources) in the Resource-Model. One specific role of the Role Model can be set together with a positive NoP (defaults to one, when none given). Setting a NoP without a Role is not possible, thus NoP gets removed when no Role is assigned. The assigned Role is written before the name of the activity. Together with a sperating colon(:) the name moves to a newline. The NoP is written in parentheses after the roll.
The duration doesn't have to be set (default assumption is zero), otherwise it must be a non negative integer and is written in the top-right corner of the activity together with a clock symbol.
Fragments of the example
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)