| |
| |
| List of Figures | |
| |
| |
| List of Tables | |
| |
| |
| Foreword by Kim Caputo | |
| |
| |
| Foreword by Alistair Cockburn | |
| |
| |
| Preface | |
| |
| |
| Introduction | |
| |
| |
| |
| What isIs Configuration Management? | |
| |
| |
| |
| Definition of Configuration Management Used in This Book | |
| |
| |
| Configuration Management Activities | |
| |
| |
| Metadata | |
| |
| |
| Configuration Management Is Cyclicor Is It? | |
| |
| |
| Quality Assurance Process | |
| |
| |
| Audit | |
| |
| |
| Identification | |
| |
| |
| Inputs | |
| |
| |
| Outputs | |
| |
| |
| Process Descriptions | |
| |
| |
| Unique dentification | |
| |
| |
| Examples | |
| |
| |
| Authorization | |
| |
| |
| Roles | |
| |
| |
| Connection with Other Activities | |
| |
| |
| Storage | |
| |
| |
| Library | |
| |
| |
| Main Processes | |
| |
| |
| Process escriptions | |
| |
| |
| Roles | |
| |
| |
| Connection with Other Activities | |
| |
| |
| Example | |
| |
| |
| Change Control | |
| |
| |
| Inputs | |
| |
| |
| Outputs | |
| |
| |
| Change Control Activities | |
| |
| |
| Usage of Metadata | |
| |
| |
| Consequence Analysis | |
| |
| |
| Roles | |
| |
| |
| Process Descriptions | |
| |
| |
| Connection with Other Activities | |
| |
| |
| Example | |
| |
| |
| Status Reporting | |
| |
| |
| Inputs | |
| |
| |
| Outputs | |
| |
| |
| Process Descriptions | |
| |
| |
| Roles | |
| |
| |
| Connection with Other Activities | |
| |
| |
| False Friends: Version Control and Baselines | |
| |
| |
| Version Control | |
| |
| |
| Baseline | |
| |
| |
| |
| Configuration Management in Maturity ModelsCMM Version 1.1 | |
| |
| |
| CMM Maturity Levels | |
| |
| |
| Definition | |
| |
| |
| Activities | |
| |
| |
| CMMICMMI Process Areas | |
| |
| |
| Definition | |
| |
| |
| Goals | |
| |
| |
| Practice-to-Goal Relationships | |
| |
| |
| Capability and Maturity Levels | |
| |
| |
| Achieving Capability Levels | |
| |
| |
| Level 2 for All Process Areas | |
| |
| |
| Raising the Capability of the Configuration Management Process | |
| |
| |
| ISO 15504 (SPICE) and BOOTSTRAP 3.2 | |
| |
| |
| SPICE Process Model | |
| |
| |
| Definition | |
| |
| |
| Goals | |
| |
| |
| Best Practices | |
| |
| |
| Maturity Levels | |
| |
| |
| Maturity of Configuration Management | |
| |
| |
| |
| Configuration Management in International Standards | |
| |
| |
| Overview of Related Standards | |
| |
| |
| BS6488, DoD, IEEEBS6488DoD Mil-Std-973IEEE-Std-610.12-1990ESA PSS-05-09 | |
| |
| |
| Introduction from the Guide | |
| |
| |
| GAMP | |
| |
| |
| Description from the Guide | |
| |
| |
| ISO 9001:1994, ISO 9000-3, and ISO 9001:2000ISO 9001:1994ISO 9000-3ISO 9001:2000 | |
| |
| |
| |
| Organizations Working with Configuration Management | |
| |
| |
| Institutions and Companies | |
| |
| |
| CM Today Yellow Pages | |
| |
| |
| Institute of Configuration Management | |
| |
| |
| Conferences | |
| |
| |
| Ovum | |
| |
| |
| Software Engineering Institute | |
| |
| |
| Projects | |
| |
| |
| ACMEAdCoMsDaSC | |
| |
| |
| |
| Scoping the Configuration Management TaskLevel of Ambition | |
| |
| |
| Cost/Benefit Analysis | |
| |
| |
| Level of Ambition = Scope + Formalism | |
| |
| |
| Formalism for a Configuration Item | |
| |
| |
| Degrees of Formalism | |
| |
| |
| Earliest and Latest Extremes for Starting Configuration Management | |
| |
| |
| Formalism and Tools | |
| |
| |
| Expansion of Scopefrom Candidate to Item | |
| |
| |
| No Rough Drafts-Please! | |
| |
| |
| Expansion from the Middle | |
| |
| |
| Examples | |
| |
| |
| Calculation of Profitability | |
| |
| |
| Expenses | |
| |
| |
| Savings | |
| |
| |
| Pitfalls in Connection with Scoping | |
| |
| |
| Too Demanding | |
| |
| |
| Wrong | |
| |
| |
| Too Coarse or Too Fine | |
| |
| |
| Too Embracing or Too Exclusive | |
| |
| |
| Too Late or Too Early | |
| |
| |
| How to Treat What Is Kept Outside | |
| |
| |
| Objects to Keep Outside | |
| |
| |
| Identification | |
| |
| |
| Storage | |
| |
| |
| |
| Configuration Management Data | |
| |
| |
| |
| What Can Be Placed under Configuration Management | |
| |
| |
| Physical or Electronic Objects | |
| |
| |
| Configuration Item Class Hierarchy | |
| |
| |
| Physical Objects | |
| |
| |
| Electronic Objects | |
| |
| |
| Types of Objects in Product Perspective | |
| |
| |
| Software | |
| |
| |
| Hardware | |
| |
| |
| Network | |
| |
| |
| Data | |
| |
| |
| Services | |
| |
| |
| Tools | |
| |
| |
| Types of Objects in Project Perspective | |
| |
| |
| Life Cycle Activities | |
| |
| |
| Support Functions | |
| |
| |
| Tools | |
| |
| |
| Types of Objects in Cross-Organizational Perspective | |
| |
| |
| Cross-Organizational Perspective | |
| |
| |
| Administrative Documents | |
| |
| |
| Company Product Assets | |
| |
| |
| Infrastructure | |
| |
| |
| Quality System | |
| |
| |
| Deliveries under Configuration Management | |
| |
| |
| Examples | |
| |
| |
| Project Relationships | |
| |
| |
| Deliveries for Planned Events Like Milestones | |
| |
| |
| Development Model | |
| |
| |
| Milestones | |
| |
| |
| |
| What One Needs to Know about a Configuration Item | |
| |
| |
| Overview of Metadata for a Configuration Item | |
| |
| |
| Data Elements | |
| |
| |
| Metadatabase Medium | |
| |
| |
| Other Data Elements | |
| |
| |
| Metadata for Unique Identification | |
| |
| |
| Belongs To | |
| |
| |
| Name | |
| |
| |
| Version | |
| |
| |
| Status | |
| |
| |
| Date | |
| |
| |
| Storage Location | |
| |
| |
| Storage Medium | |
| |
| |
| Example of States for a Document | |
| |
| |
| Example of States for a Source Code Unit, Including in Build | |
| |
| |
| Metadata for Authorization | |
| |
| |
| Producer | |
| |
| |
| Person Holding Overall Responsibility | |
| |
| |
| Person Responsible for Approval | |
| |
| |
| Ownership | |
| |
| |
| Metadata for Relations to Other Configuration Items | |
| |
| |
| Traces To (and From!)Tracing Registration | |
| |
| |
| Importance of Tracing | |
| |
| |
| Produced With | |
| |
| |
| Derived From | |
| |
| |
| Consists Of Metadata for Distribution | |
| |
| |
| May Be Distributed To | |
| |
| |
| Has Been Distributed To | |
| |
| |
| |
| What One Must Register for a Configuration Item | |
| |
| |
| Item Approval | |
| |
| |
| Quality Approval | |
| |
| |
| Medium | |
| |
| |
| Content Examples Release Request | |
| |
| |
| Medium | |
| |
| |
| Content Stock Control | |
| |
| |
| Examples Event Registration | |
| |
| |
| Life Cycle and Responsibility Conte | |