| Description |
1 online resource |
| Contents |
Front cover -- Dedication -- Contents -- Foreword -- References -- Preface -- Who Should Read This Book? -- 1 -- Introduction to Software Configuration Management -- SCM and Process Improvement -- Measurements and Metrics -- Benefits of SCM -- SCM Components -- Configuration Identification -- Configuration Change Control -- Configuration Status Accounting -- Configuration Auditing -- Implementing SCM in the Organization -- Manage the Risks of SCM -- Summary -- References -- 2 -- Project Management in a CM Environment -- Who Writes the Project Plan -- What Goes into the Project Plan -- CM-Based Project Plan Components -- Identification -- Software Scope -- Project Estimates -- Estimation Techniques -- Decomposition Techniques -- Empirical Model -- Risk Management Strategy -- Risk Table -- RMMM Plan for Each Risk -- Schedules -- Resource Table -- Project Resources -- Tracking and Control Mechanisms -- Quality Assurance and Control -- Change Management and Control -- Performance Measurement -- Configuration Status Accounting -- Summary -- References -- 3 -- The DoD CM Process Model -- CM Benefits, Risks, and Cost Impact -- CM Life-Cycle Management and Planning -- Management and Planning -- Configuration Identification -- Configuration Control -- Configuration Status Accounting (CSA) -- Configuration Verification and Audit -- Relation to Systems Engineering Process -- Implementing the CM Process -- Measuring and Evaluating the CM Process -- CM Benefits and Risks by Program Life-Cycle Activity (See Figure 3.5) -- Management and Planning: Concept and Technology Development Phase -- Configuration Identification: Concept and Technology Development Phase -- Configuration Control: Concept and Technology Development Phase -- Configuration Status Accounting: Concept and Technology Development Phase |
|
Management and Planning: System Development and Demonstration Phase -- Configuration Identification: System Development and Demonstration Phase -- Configuration Control: System Development and Demonstration Phase -- Configuration Status Accounting: System Development and Demonstration Phase -- Configuration Audit: System Development and Demonstration Phase -- Management and Planning: Production and Deployment Phase -- Configuration Identification: Production and Deployment Phase -- Configuration Control: Production and Deployment Phase -- Configuration Status Accounting: Production and Deployment Phase -- Configuration Audit: Production and Deployment Phase -- Management and Planning: Operations and Support Phase -- Configuration Identification: Operations and Support Phase -- Configuration Control: Operations and Support Phase -- Configuration Status Accounting: Operations and Support Phase -- Effect Process Improvement and Document Lessons Learned -- Summary -- References -- Resources -- 4 -- Configuration Identification -- How Configuration Identification Works -- Configuration Identification General Activity Guides -- Product Structure -- Configuration Items -- Configuration Item Selection Criteria -- General Guidance -- CI Selection Checklist -- Additional Factors -- Configuration Documentation -- Specification Types Categorized by Object -- System -- Item -- Software -- Process -- Specification Types Categorized by Purpose -- Performance -- Detail -- Design Solution Document Concepts -- Software Documentation List -- Process Implementation: Planning -- System Requirements Analysis and Architectural Design -- Software Requirements Analysis and Design -- Software Architectural and Detailed Design -- Software Integration and Qualification Testing -- As-Built Software Product Definition -- System Operation -- System/Software Maintenance |
|
Configuration Baselines -- Configuration Baseline Concepts -- Document and Item Identification -- Part/Item Identification Numbers (PIN) -- Software Identifiers -- Engineering Release -- Interface Management -- Summary -- References -- 5 -- Configuration Control -- The Process of Configuration Control -- Engineering Change Proposal -- Request for Deviation -- RFD Contents -- Summary -- References -- 6 -- Configuration Status Accounting -- Typical CSA Information over the Acquisition Program Life Cycle -- Concept and Technology Development -- System Development and Demonstration -- Production and Deployment -- Operational Support -- Configuration Status Accounting Process Evaluation Checklist -- Summary -- References -- 7 -- A Practical Approach to Documentation and Configuration Status Accounting -- Configuration Identification -- Product Structure -- Product Identifiers -- Baselines -- Configuration Status Accounting -- The Effective Documentation of Systems -- Methods and Standards -- Generating Documentation the Right Way -- 1. All Documentation Produced prior to the Start of Code Development -- 2. Program Flowcharts -- 3. Use or Business Cases -- 4. Terms of Reference -- 5. Data Dictionary -- 6. Program/Component/Object Documentation -- 7. All Presentation Material -- 8. Test Cases (Appendix E) and Test Plan -- 9. Metrics -- 10. Operations Instructions -- 11. End-User Help Files -- 12. User Documentation -- Maintaining Documentation -- Summary -- References -- 8 -- Configuration Verification and Audit -- Configuration Verification and Audit Concepts and Principles -- Configuration Verification -- Configuration Audit -- Functional Configuration Audit -- Physical Configuration Audit -- Application of Audits during Life Cycle -- Summary -- References -- 9 -- A Practical Approach to Configuration Verification and Audit |
|
Components of a Design and Document Verification Methodology -- Components of a Configuration Audit Methodology -- Components of a Testing Methodology -- Inspections -- Walk-Throughs -- Unit Testing -- Daily Build and Smoke Test -- Integration Testing -- System Testing -- Parallel Testing -- The QA Process -- The Test Plan -- Test Automation -- Summary -- References -- 10 -- Configuration Management and Data Management -- CM-Related Data Management Concepts and Principles -- Document Identification -- Data Status Level Management -- Data and Product Configuration Relationships -- Data Version Control -- Digital Data Transmittal -- Data Access Control -- Summary -- References -- 11 -- Configuration Change Management -- What Is Configuration Change Management? -- The Maintenance Process -- The Product Baseline -- Types of Maintenance -- Corrective Maintenance -- Adaptive Maintenance -- Perfective Maintenance -- Preventive Maintenance -- Maintenance Costs -- A Model for Maintenance -- Configuration Management Steps -- Change Identification -- Evaluation and Coordination -- Change Implementation and Verification -- Handling Variances -- Managing Maintenance Personnel -- Measuring Effectiveness -- Summary -- References -- 12 -- Configuration Management and Software Engineering Standards Reference -- The Standards Bodies -- A Summary of the EIA Standard (EIA-649) -- Configuration Management Planning and Management -- Configuration Identification -- Configuration Change Management -- Configuration Status Accounting -- Configuration Verification and Audit -- Management of Digital Data -- ANSI -- IEEE -- IEEE Software Engineering Standards Summary -- ISO -- ISO Software Engineering Standards Summary -- Summary -- References -- 13 -- Metrics and Configuration Management Reference -- What Metrics Are and Why They Are Important -- Traditional CM Metrics |
|
IEEE Process for Measurement -- Stage 1: Plan Organizational Strategy -- Stage 2: Determine Software Reliability Goals -- Stage 3: Implement Measurement Process -- Stage 4: Select Potential Measures -- Stage 5: Prepare Data Collection and Measurement Plan -- Stage 6: Monitor the Measurements -- Stage 7: Assess Reliability -- Stage 8: Use Software -- Stage 9: Retain Software Measurement Data -- Metrics as a Component of the Process Maturity Framework -- Level 1: Initial Process -- Level 2: Repeatable Process -- Level 3: Defined Process -- Level 4: Managed Process -- Level 5: Optimizing Process -- Steps to Take in Using Metrics -- 1. Fault Density -- 2. Defect Density -- 3. Cumulative Failure Profile -- 4. Fault-Days Number -- 5. Functional or Modular Test Coverage -- 6. Requirements Traceability -- 7. Software Maturity Index -- 8. Number of Conflicting Requirements -- 9. Cyclomatic Complexity -- 10. Design Structure -- 11. Test Coverage -- 12. Data or Information Flow Complexity -- 13. Mean-Time-to-Failure -- 14. Software Documentation and Source Listings -- IT Developer's List of Metrics -- McCabe's Complexity Metric -- Halstead's Effort Metric -- Summary -- References -- 14 -- CM Automation -- Automating CM -- Phase 1: Preparation and Planning -- Phase 2: Process Definition -- Phase 3: Tool Evaluation -- Phase 4: Pilot Project Implementation -- Phase 5: Rollout to Other Projects -- Phase 6: Capture and Communicate Improvements -- A Selection of CM Tools -- Summary -- References -- Appendix A -- Project Plan -- ORSS Software Project Plan -- I. Table of Contents -- 1.0 Goals and Objectives -- 1.1 System Statement of Scope -- 1.2 System Context -- 1.3 Major Constraints -- 2.0 Project Estimates -- 2.1 Historical Data Used for Estimates -- 2.2 Estimation Techniques Applied and Results -- 2.2.1 Process-Based Estimation -- 2.2.2 LOC-Based Estimation |
| Summary |
An effective systems development and design process is far easier to explain than it is to implement. A framework is needed that organizes the life cycle activities that form the process. This framework is Configuration Management (CM). Software Configuration Management discusses the framework from a standards viewpoint, using the original DoD MIL-STD-973 and EIA-649 standards to describe the elements of configuration management within a software engineering perspective. Divided into two parts, the first section is composed of 14 chapters that explain every facet of configuration management related to software engineering. The second section consists of 25 appendices that contain many valuable real world CM templates. The content is extensive and inclusive, covering everything from CM planning to configuration identification, verification, and auditing. Although it is vendor-neutral, it offers a serious discussion of what to look for in a CM tool and lists toolsets for review. This volume is a sourcebook of techniques, templates, and best practices in the field, providing software engineers and systems developers with what they need to run a successful CM program |
| Audience |
Trade Taylor & Francis Group |
| Subject |
Software configuration management.
|
|
Software configuration management
|
| Form |
Electronic book
|
| ISBN |
9780849319761 |
|
0849319765 |
|
9780203496114 |
|
0203496116 |
|
