Change
Note: There is a newer version of this specification see KBL 2.5.sr1
A Change is a mechanism to keep track of the change history. The set of changes assigned to a Part covers all modification numbers up to the last modification level of the version of the Part.
General Information
Attribute | Value |
---|---|
Owner | 6_Foundation |
Applied Stereotype | |
Base Classifier | |
Is Abstract | false |
Derived Classifiers |
Attributes
Name | Type | Mult. | Description | Owning Classifier |
---|---|---|---|---|
Id | String | 0..1 | The id specifies the identifier by which a certain change can be referenced. Example: reference of a fax, note, etc. |
Change |
Description | String | 0..1 | The description specifies additional information about the change. |
Change |
Change_request | String | 0..1 | The change_request specifies the activity which triggers one ore more changes. Example: change request, AEKO, VV; “Modellpflegepunkt” |
Change |
Change_date | String | 0..1 | The change_date specifies the date the change was performed. |
Change |
Responsible_designer | String | 1 | The responsible_designer specifies the responsible design engineer. |
Change |
Designer_department | String | 1 | The designer_department specifies the department of the responsible design engineer. |
Change |
Approver_name | String | 0..1 | The approver_name specifies the name of the personnel who approved the Part. |
Change |
Approver_department | String | 0..1 | The approver_department specifies the department of the personnel who approved the Part. |
Change |
Incoming Relations
Type | Mult. | Role | Mult. | Description |
---|---|---|---|---|
Part | 1 | Change | 0..* |