1. Configuration Control of Architecture Models
Dr. Ron Carson
John Herrold
Michael Crow
The Boeing Company

2. Discussion Topics
1. How are models used in your organization today?
2. How are they managed/controlled today?
3. What are the problems in model management today?
4. What do you think are the solutions to the problem?

3. Underlying Objectives
Establish purposes of configuration control of models in architecting (use cases)
Establish measures of effectiveness of configuration control of models in architecting
Quality attributes of configuration control
Configuration control completeness
Defects in configuration control

4. Elements and Features of Models
Objects
Relationships
Vertical – parent/child
Horizontal – e.g., functionsrequirements
Configuration control of
Control by self or by parent or owner?
Control by self, “owner”, “defining”, “complying” object?
Event or time-sequenced configuration control
Functional/Logical: Parentchild (left-side-of-V)
Physical: Childparent (right-side-of-V)
A sibling Parent (same or different type)
Child of a different parent

5. Model Management Use Cases – 1
Develop architecture (left side of V)
“Freeze” requirements, functions, logical architecture elements, interfaces at specified levels prior to going to next-lower level
“Design review” sequence
Synchronize at each level (horizontal integration)
Allow lower-level items to be changed until baselined
Enables sequential, tiered architecting
Measures:
Number of functional and logical objects under control
Number of relationships under control
% objects appropriately under control (maturity check)
% relationships appropriately under control
Sibling
Sibling
Child
Child
Child
Child
Child
Child

6. Model Management Use Cases – 2
Maintain configuration control of design (right side of V)
Manage functions, logical elements, at higher levels
Manage effects of changes at lower levels
E.g., Part substitutions
Measures
Number and % of physical objects under configuration control (by level)
Sibling
Sibling
Child
Child
Child
Child
Child
Child

7. Model Management Use Cases – 3
Maintain multiple versions concurrently
Establish controlled object
Establish controlled, alternative objects
Establish compatibility of multiple objects
Measures
Number of available versions of any object (1,*)
Accuracy of version assignment to configuration or “baseline”
Consistency of version assignments to baseline across all objects
Sibling
Sibling
Child
Alt.
Child
Child
Child
Child
Child

8. Satisfying Objectives
Establish purposes of configuration control of models in architecting (use cases)
Are there more use cases to consider?
Establish measures of effectiveness of configuration control of models in architecting
Quality attributes of configuration control
Configuration control completeness
Are we controlling the right things at the right times?
Levels
Links and relationships
Children / parents
Defect management
Uncontrolled, or prematurely controlled
Incompletely controlled (see completeness)
“Size” – number of versions for any object
Related artifacts