| Artifact: Configuration Specification |
|
 |
| A controlled group of elements which represent some state of the design, library or IP Block. |
|
|
Purpose
| Enables a group of items to be identified, referenced and used across different stakeholders. Enables identification and
control of changes, such as from revision (changes) or for variants (with optional or alternative functionality or
performance). |
Relationships
| Roles | Responsible:
| Modified By:
|
| Tasks | Input To:
| Output From:
|
Description
| Main Description |
Configuration occurs in multiple places and at multiple levels of granularity with varying levels of business control.
In addition certain additional control of updates to configurations is needed to allow parallel working within the
constraints of processes and tools. For instance designers may be working concurrently in tools that do not allow work
to be merged and differences resolved easily, this is more typical in electronic design tools and so care but be taken
to provide configuration control schemes. The IBM practices provide such examples.
Within the detailed design management scenario the work flow allow for the correct identification of configurations to
start from, prior definition of the target configuration (place holder) is optional, control of (check out and check in
from) editing and control of referenced configuration during work and identification (marking) of released
configuration.
|
Tailoring
| Representation Options | Represented by identity, state descriptors such as variant configuration parameters, compositional descriptions (includes),
business control parameters (e.g. immutable baseline), business significance indicators (release R, baseline B, latest,
main, milestone M, snapshot date:time ). |
© Copyright IBM Corp. 1987, 2010. All Rights Reserved.
|
|