 |
 |
 |
|
 |
|
|
CM 2.3: Product Management |
|
KM2.3 - Produkt verwalten
| From |
Product |
to |
Methods |
Tool Req. |
Ext. Norms |
| Activity |
State |
Chapter |
Title |
Activity |
State |
SD,
QA,
CM,
PM |
(1) |
All |
Product |
CM2.4 |
(1) |
|
SCM02
|
|
+ "Chapter" are extra columns from the original printed version of GD 250
CM administers the product depending on the state.
- If the product is in state "b. proc.", "submitted" or "accepted" CM enters the already initialized product and updates the product attributes.
- If the product does not have any state (protocols, etc.) then the product and the product attributes must be entered.
It must be guaranteed by means of the product management that changed states and products reset to earlier versions can be traced. The product management supervises the entire lifecycle of a product, beginning with the planning of the product concerned, then all states of all existing versions, and up to the completion of the project.
Reusable products (e. g. procedures, programs, specifications) may possibly have to be transmitted to the central CM services as well; they must be administered by CM4.2 - Cataloging of SW/HW Products.
To "administer" a product means: a product is physically stored in the product library; therefore, it is "protected" by the CM. This also includes archivation. In the case of HW products the initialization and administration are realized with the same methods (product identification, product attributes, etc.) as applied for SW products; only the physical storage is outside of the product library, though the place of storage has to be referenced in the product library.
Being defined
Note:
(1) The product may be in state "b. proc.", "submitted" or "accepted", or it may not be in any state at all.
 |
 |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
 |
|