![]() |
![]() |
![]() |
|
![]() |
|||
| CM 4.3: Interface Coordination |
KM4.3 - Schnittstellen koordinieren
Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| CM2 | being proc./ accepted |
All | Configuration Identification Document (CID) | - | - | |||
| SD2, SD4-SW, External (1) |
being proc./ submitted |
All | Interface Overview | - | - | |||
| SD2, SD4-SW, External (1) |
being proc./ submitted |
All | Interface Description | - | - | |||
| - | - | All | Report Documents: Protocol , Progress Report, Final Project Report, Case Report, Memo, Internal Message, Invitation |
Project Members | - | |||
+ "Chapter" are extra columns from the original printed version of GD 250
Handling
In the case of serious and uncoordinated changes, meetings have to be organized with the corresponding developers or (especially in larger projects) working group sessions for clarification of the facts and for mutual agreements.
The actual processing of the interfaces does not take place in submodel CM, but in SD. The objective of CM is the information and agreement of people concerned.
Explanation
Roles
| Role | Participation | ||
|---|---|---|---|
| CM Representative | responsible
| CM Administrator |
cooperating
| |
Tools Requirements
External Norms
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |