Configuration Management
|
|
|
- Griffin Parrish
- 9 years ago
- Views:
Transcription
1 Configuration Management Co Al Florence This presenter s affiliation with the MITRE Corporation is provided for identification purposes only and is not intended to convey or imply MITRE s concurrence with or support for the positions, opinions or view points expressed by this presenter.
2 Presentation Contents Introduction Reasons for Configuration Management (CM) CM Concepts Formal CM Formal Baselines and Configuration Items (CIs) Configuration Control Boards (CCBs) Supported with Technical Review Boards (TRBs) Change Control CM Audits and Status Accounting Internal CM Internal Baselines CM of Design, Code, Hardware Items, Test Articles Operation CM During Operation / Maintenance References 2
3 Why CM? CM ensures that the current configuration of items are known throughout their lifecycle CM ensures that changes to the configuration of evolving items are correct, controlled, managed, and documented CM helps manage complexity, interface dependencies, increases security, and recovery from errors 3
4 What is CM? CM is a discipline applying technical and administrative direction and surveillance to: Identifying and documenting the physical, functional, and performance characteristics of items Baselining those characteristics Controlling changes to those characteristic Providing status on those characteristics Conducting audits on those characteristics The CM tasks that produce these results are: Configuration Planning Configuration Identification Configuration Control Configuration Status Accounting Configuration Management Audits 4
5 Application of CM The CM concepts presented in this course can be applied to: Hardware (H/W) Software (S/W) Facilities And their appropriate documentation During Development and Operaton by the Acquirer and Supplier 5
6 Some Levels of CM Enterprise CM Control Changes: Cost Schedule Interfaces Control Changes: Whatever is necessary Supplier CM Development CM Formal CM CI Characteristics Physical Function Performance Internal CM Design Implementation Code Test Process Documentation Acquirer CM Development Formal CM CI Characteristics Physical Function Performance Internal CM Business Cases Business Practices Budgets Operational and Maintenance CM Operational and Maintenance CM 6
7 Presentation Contents Introduction Reasons for Configuration Management (CM) CM Concepts Formal CM Formal Baselines and Configuration Items (CIs) Configuration Control Boards (CCBs) Supported with Technical Review Boards (TRBs) Change Control CM Audits and Status Accounting Internal CM Internal Baselines CM of Design, Code, Hardware Items, Test Articles Operation CM During Operation / Maintenance References 7
8 Configuration Management Overview System Configuration Identification Configuration Item Configuration Control Board (CCB) Baseline Configuration Control Technical Review Board (TRB) Configuration Management Audits Configuration Status Accounting 8
9 Configuration Identification continued Three level of Configuration Identification are established Functional Configuration Identification (FCI) Allocated Configuration Identification (ACI) Physical Configuration Identification (PCI) Conceptual Systems Requirements Hardware Software Facilities Requirements Design Implementation Test Operation FCI ACI PCI Lifecycle Phases 9
10 Functional Configuration Identification Functional Configuration Identification (FCI) The identified system and system items and their physical, functional, and performance characteristics which are documented in a System Specification System PHY 1 PHY 2 PHY 3 System CI Specification Item FUN 1 FUN 2 FUN 3 Physical (PHY) Functional (FUN) PER 1 PER 2 PER 3 Performance (PER) 10
11 Allocated Configuration Identification Allocated Configuration Identification (ACI) Later in development the physical, functional, and performance characteristics of the system are allocated to lower level entities: software, hardware, facilities, and are documented as Allocated Specifications for requirements Software Hardware PHY 1 PHY 3 FUN 1 PER 1 FUN 3 PER 3 Software CI Specification Hardware CI Specification 11
12 Physical Configuration Identification Physical Configuration Identification (PCI) Finally, the products of the developed system: software, hardware, facilities are defined in a series of Product Specifications that describe the as-built system As-built System Product CI Specifications 12
13 Formal Baselines Baselines are established at strategic points in a system lifecycle. Three baselines may be defined Functional Baseline (FBL) Allocated Baseline (ABL) Product Baseline (PBL) Hardware Software Systems Facilities Requirements Requirements Design Implementation Test Operation FCI - CI ACI - CIs PCI - CIs FBL ABLs PBLs Lifecycle Phases 13
14 Configuration Identification and Configuration Items Configuration Identification is an activity that identifies items and their characteristics: physical, functional, and performance Not all items that are identified need be controlled at the same level of rigor Configuration Items are selected for formal change control from items identified Configuration Identification - Software *Operating System *Network Software **Navigation Software CI **Communication Software CI **Test Software CI *Commercial products MAY not be subject to change In operation everything is under CM control **Applications software in development that is subject to change 14
15 Configuration Item Represents the characteristics of a Configuration Item Functional and performance characteristics Physical characteristic 15
16 Baseline vs. Configuration Items The approved and fixed (baselined) configuration of a CI at a specific time in its lifecycle that serves as a reference point for change control CIs are used for visibility Baselines are used for control CI Visibility Baselined CI Control 16
17 Configuration Control The systematic evaluation coordination approval or disapproval, and implementation of changes to the physical, functional, and performance characteristics of a baselined CI Changes are requested with a Change Request (CR) form 17
18 Configuration Control Board (CCB) Establishes baselines for CIs Reviews and approves / disapproves / defers Change Requests to CIs Membership comprised of management, and other stakeholders and supported by the subject matter experts Project Management Systems Engineering Software/Hardware Engineering Test Engineering Quality Assurance Configuration Management Chaired by the program / project manager or designee 18
19 Technical Review Board (TRB) Provides technical and programmatic support to the CCB Conducts impact assessment on CRs to baselined CIs Makes approval / disapproval recommendations to the CCB Membership comprised of program / project personnel and subject matter experts Chaired by a technical manager 19
20 CCB and TRB Hierarchy Acquirer CCB TRB Acquirer (Customer) Supplier Program CCB TRB Supplier (Contractor) Supplier Project CCB TRB Subcontractor CCB TRB 20
21 Configuration Control Configuration Item Less than 3 mph wind Functional and performance characteristic Constraint 3% Grade Physical characteristic Gravel Change Request Need to control the configuration of physical, functional, and performance characteristic If not we might get something really dumb or suffer a catastrophic failure 21
22 CR Example Change Request CR # Date: 12/4/2003 Requestor: ET Class: I II II Problem: A requirement to deploy the probe s parachute does not exist Change: Add the following requirement: The probe s parachute shall be deployed seconds after the heat shield has been jettisoned Impacts: Enter figures for cost and schedule and list affected interfaces or None and attach impact assessments Systems: Hardware: Software: Test: Configuration Management: Quality Assurance: Contracts: Other [Specify]: Approve: TRB Date: Chair: CCB Date: Chair: Disapprove: TRB Date: Chair: CCB Date: Chair: Assignee: Due Date: 22
23 Change Flow Request Change (CR) Supplier or Acquirer Evaluate Change TRB Approve Change CCB Implement Change Owner of item Track Change CM staff and owner of item 23
24 Impact Assessments Impact assessments need to be conducted by all stakeholders: Systems Hardware Software Test Configuration Management Quality Assurance Contracts Others On CI characteristics: Physical Functional Performance Against their interests: Cost Schedule Interface 24
25 Classification of Changes At least two types of changes can be defined: Class I affects the Acquirer s interest in one or more of these factors: Physical characteristics Functional capability Performance External interfaces Cost Schedule Supplier must submit change to the Acquirer for approval before implementation 25
26 Classification of Changes concluded Class II - Does not affect any of the Class I factors, affects changes such as: Spelling or typographical errors Addition of clarifying comments Changes that do not affect external interfaces, change functionality or degrade performance Supplier may implement it without Acquirer s approval but must inform Acquirer of change 26
27 CM Audits Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA) are conducted by Engineering and facilitated by CM and/or Quality Assurance (QA) Other audits conducted by QA and CM may include: Audits of CM Repository that contains CM records, documentation, processes, procedures, artifacts, etc. Audits of Program/Project organizations to ensure CM process is being followed Audits of status of approved CRs PCA can be prolonged Audits to ensure that CIs are consistent with CM records Conceptual Systems Requirements Hardware Software Requirements until after Operational Tests If necessary Design Implementation Test Operation FCA/PCA 27
28 Functional Configuration Audit (FCA) A formal examination of test results of the as-built functional configuration of CIs, prior to acceptance, to verify that the CIs have satisfied their specified requirements This audit is conducted by the Supplier for the Acquirer and attended by Management System Engineering Hardware / Software Engineering Test Engineering QA and CM Contracts of both the Acquirer and Supplier 28
29 Functional Configuration Audit continued Functional Testing Requirements Specifications Requirements Traceability Test Plans Test Scenarios Requirements Specifications Requirements Traceability Test Plans Test Scenarios Test Results Inputs Products Tests Functional Configuration Audit Verify that the CIs have satisfied their specified requirements Supplier Acquirer Test Results Physical Configuration Audit 29
30 Physical Configuration Audit (PCA) A formal examination of the as-built physical configuration of CI products against their design documentation This establishes the Product Baseline This audit is conducted by the Supplier for the Acquirer and attended by Management System Engineering Hardware / Software Engineering Test Engineering QA and CM Contracts of both the Acquirer and Supplier 30
31 Physical Configuration Audit continued Implementation Physical Design Documentation Supplier As-Built Products: Design Documentation Code Hardware Etc. Inputs Physical Configuration Audit Examination of the as-built configuration of CIs against their documentation Supplier Acquirer Outputs Product Baselines 31
32 Configuration Status Accounting (CSA) CSA is performed to gather, correlate, maintain and provide status on controlled products (CIs), and on CM tasks Configuration Identification Specifications CM Planning Configuration Control Configuration Audits Configuration Status Accounting Products (CIs) CM Tasks 32
33 Configuration Status Accounting continued The Configuration Status Accounting (CSA) task gathers, correlates, maintains, and provides status on CM controlled products and CM tasks Provides the means for reporting status on: Configurations FCI ACI PCI Baselines FBL ABL PBL Other CM metrics CM activities CM Audits 33
34 Configuration Status Accounting concluded Supplier Configuration Status Accounting Reports produced by the CM organization Acquirer Monthly Reports Program Management Reviews Management and Staff Milestone Reviews 34
35 Presentation Contents Introduction Reasons for Configuration Management (CM) CM Concepts Formal CM Formal Baselines and Configuration Items (CIs) Configuration Control Boards (CCBs) Supported with Technical Review Boards (TRBs) Change Control CM Audits and Status Accounting Internal CM Internal Baselines CM of Design, Code, Hardware Items, Test Articles Operation CM During Operation / Maintenance References 35
36 Internal CM versus Formal CM Formal CM is concerned with High Level baselines FBL ABL PBL Master Schedules Contractual Items Internal CM is concerned with Design BL Code BL Hardware component BL Test BL COTS BL Etc. 36
37 Internal CM Concerns Documents Database Test procedures Analysis that drive requirements and design Etc. Plans Project plans CM plans QA plans Risk Management plans Test plans Etc. 37
38 Formal CM Under Configuration Control Board (CCB) Configuration Control Board is Chaired by PM Membership composed of management Systems Software Hardware Test CM QA Etc. 38
39 Internal CM Under Technical Review Board (TRB) Chaired by Deputy PM or Lead Systems Engineer Systems Software Hardware Test CM QA Etc. 39
40 Internal CM Concerns continued Internal CM is concerned with Version Control Documents Code Hardware items COTS Data Management Documents Plans Process Documentation Procedures Metrics Action Items Etc. 40
41 Internal CM & Testing Internal CM during testing is concerned with Code changes (TRB) Design changes (TRB) Test case changes (TRB) Requirements changes (Require escalation to CCB) 41
42 Internal Baselines Internal baselines are established at strategic points in a system lifecycle. Three internal baselines may be defined Design Baseline (DBLs) Code/Hardware Components Baseline (C/HCBLs) Test Baseline (TBLs) Hardware Software Systems Facilities Requirements Requirements FCI - CI ACI - CIs Design Implementation Test Operation PCI - CIs FBL ABLs DBLs C/HCBLs TBLs PBLs Lifecycle Phases 42
43 Internal CM During Design Design not yet Baselined Design Team fixes Design Design Defect Design Defect is identified Requirement Defect CCB processes change request (CR) to fix the Requirement & update the baseline 43
44 Internal CM During Coding Design Baselined, Code not Baselined TRB Design Team fixes Design Design Defect Coding/Hardware Defect Identified Requirement Defect Code/Hardware Defect Coding/Hardware Team fixes defect CCB processes CR to fix Requirement & update the baseline 44
45 Internal CM During Testing Design, Code & Test Cases Baselined TRB Code/Hardware Team fixes defect Code/Hardware Defect Testing Defect identified Requirement Defect Test Case Defect TRB fixes Test Case TRB Design Team fixes Design CCB processes CR to fix Requirement & update the baseline 45
46 CM During Operation Operation CM does not differ from CM conducted during development Formal CM Internal CM The players may change A different Operation contractor A different Operation agency Acquisition Agency vs. Operation Agency The Product Baseline has been established 46
47 Presentation Contents Introduction Reasons for Configuration Management (CM) CM Concepts Formal CM Formal Baselines and Configuration Items (CIs) Configuration Control Boards (CCBs) Supported with Technical Review Boards (TRBs) Change Control CM Audits and Status Accounting Internal CM Internal Baselines CM of Design, Code, Hardware Items, Test Articles Operation CM During Operation / Maintenance References 47
48 CM During Operation continued Defects and changes during Operation may require repeat of activities that were conducted during development and reestablishment of baselines as appropriate. Hardware Software Systems Facilities Requirements Design Implementation Test Operation Requirements FCI - CI ACI - CIs PCI - CIs FBL ABLs DBLs CBLs TBLs PBLs Lifecycle Phases 48
49 References/Suggested Reading IEEE Std IEEE Standard for Software Configuration Management Plans IEEE 1042, Guide to Software Configuration Management ANSI/EIA National Consensus Standard for Configuration Management IEEE Standard for Software CM plans MIL-STD-973 Military Standard for Configuration Management (cancelled, but still good reference) CM Today Yellow Pages, Your Source for Daily CM News, CM BoK Configuration Management Body of Knowledge. CMBoK, CM Crossroads, CM Community Forums Capability Maturity Mode Integration (CMMI ), Version 1.3 Software Engineering Institute 49
50 Contact Information Al Florence
CHAPTER 7 Software Configuration Management
CHAPTER 7 Software Configuration Management ACRONYMS CCB CM FCA MTBF PCA SCCB SCI SCM SCMP SCR SCSA SEI/CMMI SQA SRS USNRC INTRODUCTION Configuration Control Board Configuration Management Functional Configuration
The Configuration Management process area involves the following:
CONFIGURATION MANAGEMENT A Support Process Area at Maturity Level 2 Purpose The purpose of is to establish and maintain the integrity of work products using configuration identification, configuration
CONFIGURATION MANAGEMENT PLAN GUIDELINES
I-680 SMART CARPOOL LANE PROJECT SYSTEM ENGINEERING MANAGEMENT PLAN CONFIGURATION MANAGEMENT PLAN GUIDELINE SECTIONS: PLAN GUIDELINES 1. GENERAL 2. ROLES AND RESPONSIBILITIES 3. CONFIGURATION MANAGEMENT
SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK
Office of Safety and Mission Assurance NASA-GB-9503 SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK AUGUST 1995 National Aeronautics and Space Administration Washington, D.C. 20546 PREFACE The growth in cost
Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
CMS Policy for Configuration Management
Chief Information Officer Centers for Medicare & Medicaid Services CMS Policy for Configuration April 2012 Document Number: CMS-CIO-POL-MGT01-01 TABLE OF CONTENTS 1. PURPOSE...1 2. BACKGROUND...1 3. CONFIGURATION
Configuration Management Practices
Safety Critical Software Management Practices Linda Westfall Westfall Team, Inc. International Conference on Software Quality ICSQ 2011 Copyright 1999-2010 Westfall Team, Inc. All Rights Reserved. Management
5 FAH-5 H-520 LIFE CYCLE MANAGEMENT
5 FAH-5 H-520 LIFE CYCLE MANAGEMENT (CT:ITS-5; 02-05-2013) (Office of Origin: (IRM/BMP/SPO/PM) 5 FAH-5 H-521 CONFIGURATION MANAGEMENT REQUIREMENTS Configuration management (CM) is a function deployed throughout
5 FAH-5 H-510 CONFIGURATION MANAGEMENT
5 FAH-5 H-500 CONFIGURATION MANAGEMENT 5 FAH-5 H-510 PROJECT DEVELOPMENT AND CHANGE CONTROL (CT:ITS-4; 06-21-2012) (Office of Origin: IRM/BMP/GRP/GP) (Updated only to revise Office of Origin) 5 FAH-5 H-511
EPA Classification No.: CIO 2123.0-P-01.1 CIO Approval Date: 06/10/2013 CIO Transmittal No.: 13-003 Review Date: 06/10/2016
Issued by the EPA Chief Information Officer, Pursuant to Delegation 1-84, dated June 7, 2005 CONFIGURATION MANAGEMENT PROCEDURE 1 PURPOSE The purpose of this procedure is to describe the process EPA Program
CONFIGURATION MANAGEMENT PLAN
CONFIGURATION MANAGEMENT PLAN Integrated Procurement System U.S. Election Commission i CONFIGURATION MANAGEMENT PLAN TABLE OF CONTENTS Page # 1.0 CONFIGURATION CONTROL...3 1.1 Change Control Board (CCB)...3
<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
Certified Professional in Configuration Management Glossary of Terms
Certified Professional in Configuration Management Glossary of terms used in Configuration Management Issue 2007.07 Association of the International Certified Configuration Manager e.v. Copyright 2007,
Program Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
Software and Hardware Configuration Management
DOWNLOADED AND/OR HARD COPY UNCONTROLLED Verify that this is the correct version before use. AUTHORITY DATE Jeffrey Northey (original signature on file) IMS Manager 07/09/2014 Doug Dorrer (original signature
Reaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
Configuration & Build Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Configuration & Build Management Outline of the Lecture Purpose of Software Configuration Management (SCM) Some Terminology Software Configuration
DEPARTMENT OF DEFENSE INTERIM STANDARD PRACTICE CONFIGURATION MANAGEMENT
NOT MEASUREMENT SENSITIVE MIL-STD-3046(ARMY) 06 March 2013 DEPARTMENT OF DEFENSE INTERIM STANDARD PRACTICE CONFIGURATION MANAGEMENT AMSC 9275 AREA SESS DISTRIBUTION STATEMENT A. Approved for public release;
D R A F T. Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines
TO #GA81 Resource Ordering and Status System (ROSS) D R A F T Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines June 28, 2000 Version 1.1 Contract: GS-35F-4863G Delivery
SOFTWARE ASSURANCE STANDARD
NOT MEASUREMENT SENSITIVE National Aeronautics and NASA-STD-8739.8 w/change 1 Space Administration July 28, 2004 SOFTWARE ASSURANCE STANDARD NASA TECHNICAL STANDARD REPLACES NASA-STD-2201-93 DATED NOVEMBER
APPENDIX 1, CONFIGURATION MANAGEMENT IN THE FEDERAL AVIATION ADMINISTRATION
09/19/07 1800.66 CHG 2 APPENDIX 1, CONFIGURATION MANAGEMENT IN THE FEDERAL AVIATION ADMINISTRATION Page i (and ii) 09/19/07 1800.66 CHG 2 Document Overview Table of Contents Part One - Configuration Management
WROCI Configuration Management Plan (CMP)
WROCI Configuration Management Plan (CMP) Western Range Operations Communications and Information (WROCI) Contract No. F04684-03-C-0050 CDRL A009 Configuration Management Prepared for Department of the
Software Configuration Management
Software Engineering Courses (University of Kansas, Spring 2004) Slide 1 Software Configuration Management Software Configuration: All items that constitute the software while under the development (e.g.,
IEEE 1540 - Software Engineering Risk Management: Measurement-Based Life Cycle Risk Management PSM 2001 Aspen, Colorado
Paul R. Croll Chair, IEEE SESC Computer Sciences Corporation [email protected] IEEE 1540 - Software Engineering Risk : Measurement-Based Life Cycle Risk PSM 2001 Aspen, Colorado Objectives Describe Risk in
<Project Name> Software Quality Assurance (SQA) Plan. <Document Control Number>
Software Quality Assurance (SQA) Plan Date: CHECK THE AT< WEBSITE Address> TO VERIFY THAT THIS IS THE CORRECT VERSION PRIOR TO USE. General Tailoring Guidelines This
U. S. Department of Energy. Document Online Coordination System (DOCS) Systems Configuration Management Plan (SCMP)
U. S. Department of Energy Office of the Executive Secretariat Document Online Coordination System (DOCS) Systems Configuration Management Plan (SCMP) October, 1998 U. S. DEPARTMENT OF ENERGY Assistant
Theme 1 Software Processes. Software Configuration Management
Theme 1 Software Processes Software Configuration Management 1 Roadmap Software Configuration Management Software configuration management goals SCM Activities Configuration Management Plans Configuration
DEPARTMENT OF DEFENSE STANDARD PRACTICE CONFIGURATION MANAGEMENT
NOTE: This draft, dated 21 August 2012, prepared by the U.S. Army ARDEC (AR), has not been approved and is subject to modification. DO NOT USE PRIOR TO APPROVAL. (Project SESS-2012-012.) NOT MEASUREMENT
Software Process Training
Dr. Ernest Wallmüller Wolfgang Höh Rule 8 Configuration Management Qualität & Informatik www.itq.ch Copyright Qualität & Informatik 2005 Software Configuration Management (S) The process of identifying,
IT Baseline Management Policy. Table of Contents
Table of Contents 1. INTRODUCTION... 1 1.1 Purpose... 2 1.2 Scope and Applicability... 2 1.3 Compliance, Enforcement, and Exceptions... 3 1.4 Authority... 3 2. ROLES, RESPONSIBILITIES, AND GOVERNANCE...
Configuration Management in Software Development Life Cycle
13 Configuration Management in Software Development Life Cycle Tejinder Kaur Sanjay Bhatnagar Deepali StudentComputer Application Associate Prof. Computer Assistant Prof. Computer Department, GZS PTU Applications
<Project Name> Configuration Management Plan
Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=infoblue) is included
DATA REQUIREMENTS DESCRIPTION (DRD)
DATA REQUIREMENTS DESCRIPTION (DRD) 1. DPD NO.: XXX ISSUE: Draft 2. DRD NO.: STD/AD 3. DATA TYPE: 2/3 4. DATE REVISED: 5. PAGE: 1/4 6. TITLE: Functional and Physical Configuration Audit (FCA/PCA) Documentation
CMMI Asset Library: Maturity Level 2
CMMI Asset Library: Maturity Level 2 All items listed below are to assist in achieving CMMI Maturity Level 2; they may be purchased by the bundle. David Consulting Group will invoice you for your total
ALS Configuration Management Plan
Westinghouse Non-Proprietary Class 3 ALS Configuration Management Plan 6002-00002-NP Rev. 7 October 26, 2012 APPROVALS Function Author Reviewer Approver Name and Signature Bill Irmen* Operations Manager
Service Support. 2005 Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0
Service Support Configuration Management ITIL Configuration Management - 1 Goals of Configuration Management The goals of Configuration Management are to: Account for all the IT assets and configurations
INTEGRATED SOFTWARE QUALITY MANAGEMENT (ISQM)
Guide for Integrated Software Quality Management (ISQM) GUIDE FOR INTEGRATED SOFTWARE QUALITY MANAGEMENT (ISQM) SEPTEMBER 2012 (Updated July 2014 see next page) American Bureau of Shipping Incorporated
CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT
CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT John A. Scott and David Nisse Lawrence Livermore National Laboratory 7000 East Avenue P.O. Box 808, L-632 Livermore, CA 94550, USA (925) 423-7655 [email protected]
Operational Change Control Best Practices
The PROJECT PERFECT White Paper Collection The Project Perfect White Paper Collection Operational Change Control Best Practices Byron Love, MBA, PMP, CEC, IT Project+, MCDBA Internosis, Inc Executive Summary
PM Planning Configuration Management
: a Project Support Function As stated throughout the Project Planning section, there are fundamental components that are started during the pre-performance stage of the project management life cycle in
Project Management Guidelines
Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.
NODIS Library Program Formulation(7000s) Search
NODIS Library Program Formulation(7000s) Search NASA Procedural Requirements This Document Is Uncontrolled When Printed. Check the NASA Online Directives Information System (NODIS) Library to verify that
Configuration Management
Configuration Management based on the National Consensus Standard for Configuration Management ANSI/EIA-649 Best Practices Industry Best Practices Reference Material ANSI/EIA 649; National Consensus Standard
Software Configuration Management. Addendum zu Kapitel 13
Software Configuration Management Addendum zu Kapitel 13 Outline Purpose of Software Configuration Management (SCM) Motivation: Why software configuration management? Definition: What is software configuration
Project QA and Collaboration Plan for <project name>
Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and
Risk Management. Software SIG. Alfred (Al) Florence. The MITRE. February 26, 2013. MITRE Corporation
Risk Management Software SIG MITRE Corporation February 26, 2013 The MITRE Alfred (Al) Florence MITRE Corporation The MITRE Agenda Introduction Risk Management References Contact Information Al Florence
Software Quality Assurance Plan for the EMD Project
104-EMD-001 ECS Maintenance and Development Project Software Quality Assurance Plan for the EMD Project Revision - October 2003 Raytheon Company Upper Marlboro, Maryland Software Quality Assurance Plan
The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements.
CAPACITY AND AVAILABILITY MANAGEMENT A Project Management Process Area at Maturity Level 3 Purpose The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision
Process and Procedure Definition: A Primer
Process and Procedure Definition: A Mike Bandor Member of the Technical Staff Acquisition Support Program [email protected] Overview What is a process? Definitions Varieties of Processes & Procedures
Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?
Books: Software Configuration Management 1. B. Bruegge and A. H. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns, and Java (Chapter 13) Outline of the Lecture Purpose of Software Configuration
MKS Integrity & CMMI. July, 2007
& CMMI July, 2007 Why the drive for CMMI? Missed commitments Spiralling costs Late delivery to the market Last minute crunches Inadequate management visibility Too many surprises Quality problems Customer
From Chaos to Clarity: Embedding Security into the SDLC
From Chaos to Clarity: Embedding Security into the SDLC Felicia Nicastro Security Testing Services Practice SQS USA Session Description This session will focus on the security testing requirements which
JSP 886 DEFENCE LOGISTIC SUPPORT CHAIN MANUAL VOLUME 7 INTEGRATED LOGISTIC SUPPORT PART 8.12 CONFIGURATION MANAGEMENT
JSP 886 DEFENCE LOGISTIC SUPPORT CHAIN MANUAL VOLUME 7 INTEGRATED LOGISTIC SUPPORT PART 8.12 CONFIGURATION MANAGEMENT THE MASTER VERSION OF JSP 886 IS PUBLISHED ON THE DEFENCE INTRANET. FOR TECHNICAL REASONS,
Realizing CMMI using Enterprise Architect and UML for Process Improvement
Realizing CMMI using Enterprise Architect and UML for Process Improvement Jack Hunnicutt, Anteon Corporation www.anteon.com Ramsay Millar, integrate IT architects LLC www.integrateitarchitects.com Introduction
Change Management Plan (CMP)
Change Management Plan (CMP) i Version/Change Record Revision Date Description ii Table of Contents 1.0 Introduction... 5 1.1 Purpose... 5 1.2 Plan Scope... 5 1.3 Document Overview... 7 1.4 Referenced
Software Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
STSG Methodologies and Support Structure
STSG Methodologies and Support Structure STSG Application Life Cycle Management STSG utilizes comprehensive lifecycle tools that are fully integrated and provide capabilities for most of the roles in its
NATIONAL AIRSPACE CONFIGURATION MANAGEMENT. 1800.8f. May 20, 1991. Chapter 5. Configuration Management for NAS Requirements Determination
NATIONAL AIRSPACE CONFIGURATION MANAGEMENT 1800.8f May 20, 1991 Chapter 1. General Chapter 2. NAS Configuration Management Overview Chapter 3. Configuration Control Boards Chapter 4. Configuration Control
Superseded by T MU AM 04001 PL v2.0
Plan T MU AM 04001 PL TfNSW Configuration Management Plan Important Warning This document is one of a set of standards developed solely and specifically for use on the rail network owned or managed by
Configuration Management ISO 10007
Configuration Management ISO 10007 Introduction Configuration Management Overview: What is Configuration Management? Collection of tools, techniques and experience designed to reduce costs and improve
Appendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
ADVISORY MEMORANDUM REPORT ON DEVELOPMENT OF THE LOAN MONITORING SYSTEM ADVISORY REPORT NUMBER A1-03 FEBRUARY 23, 2001
ADVISORY MEMORANDUM REPORT ON DEVELOPMENT OF THE LOAN MONITORING SYSTEM ADVISORY REPORT NUMBER A1-03 FEBRUARY 23, 2001 This report may contain proprietary information subject to the provisions of 18 USC
SOFTWARE CONFIGURATION MANAGEMENT DOCUMENTATION
SOFTWARE CONFIGURATION MANAGEMENT DOCUMENTATION STEVE J. AYER FRANK S. PATRINOSTRO Edited by JACK A. NELSON Technische Hochschule Darmstadt FACH8EREICH INFORMATIK BIBLIOTHEK Inventar-Nr.:, SachgetH9te:
OPM System Development Life Cycle Policy and Standards. Table of Contents
Table of Contents 1. INTRODUCTION... 4 1.1 Purpose... 4 1.1.1 OPM SDLC Policy... 4 1.1.2 Key Concepts and Principles... 4 1.2 Scope and Applicability... 5 1.3 Compliance, Enforcement and Exceptions...
Engineering Procedure
Engineering Procedure Design Owner: EPD 0014 MANAGING CONFIGURATION CHANGE Manager, Engineering Standards and Configuration Version 2.1 Issued February 2010 Approved Jagath Peiris Authorised Jim Modrouvanos
White Paper. Making the case for PPM
Introduction There are many reasons why organizations decide to implement project portfolio management solutions, but typically it is to help senior management confidently and consistently answer questions
How To Write A Contract For Software Quality Assurance
U.S. Department of Energy Washington, D.C. NOTICE DOE N 203.1 Approved: Expires: 06-02-01 SUBJECT: SOFTWARE QUALITY ASSURANCE 1. OBJECTIVES. To define requirements and responsibilities for software quality
Project Monitoring and Control
Project Monitoring and Control ProPath Office of Information and Technology Table of Contents Project Monitoring and Control Process Maps... 1 Process: Project Monitoring and Control... 10 Project Monitoring
Integrating Quality Assurance into the Software Development Life Cycle
Integrating Quality Assurance into the Software Development Life Cycle Leslie Tierstein, STR LLC Hilary Benoit, W R Systems W R Systems, Ltd. 1 Overview (1) Why bother with QA? QA and the SEI CMM/CMMI
ALS Configuration Management Plan. Nuclear Safety Related
Westinghouse Non-Proprietary Class 3 Advanced Logic System 6002-00002-NP, Rev. 10 Function Author Nuclear Safety Related July 2014 APPROVALS Name and Signature Anthony C. Pagano* Integrated Process Lead,
Overview Presented by: Boyd L. Summers
Overview Presented by: Boyd L. Summers Systems & Software Technology Conference SSTC May 19 th, 2011 1 Report Documentation Page Form Approved OMB No. 0704-0188 Public reporting burden for the collection
AIRLIE LITTLE BOOK OF CONFIGURATION MANAGEMENT
LITTLE BOOK OF CONFIGURATION MANAGEMENT AIRLIE SOFTWARE COUNCIL For additional information please contact the Software Program Managers Network (703) 521-5231 Fax (703) 521-2603 E-Mail: [email protected] http://www.spmn.com
Role Description Vendor Relationship Manager ICT
Role Description Vendor Relationship Manager ICT Classification/Grade/Band Clerk Grade 9/10 ANZSCO Code PCAT Code Date of Approval Primary purpose of the role The Vendor Relationship Manager ICT is responsible
Fundamentals of Measurements
Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role
How To Integrate Software And Systems
September 25, 2014 EFFECTIVE METHODS FOR SOFTWARE AND SYSTEMS INTEGRATION P R E S E N T E D B Y: D R. B O Y D L. S U M M E R S 1 Software Engineer (Quality) Defense and Space The Boeing Company - Seattle,
Department of Energy Quality Managers Software Quality Assurance Subcommittee Reference Document SQAS20.01.00-2000
Department of Energy Quality Managers Software Quality Assurance Subcommittee Reference Document SQAS20.01.00-2000 Software Configuration Management (SCM) A Practical Guide April 25, 2000 United States
A Report on The Capability Maturity Model
A Report on The Capability Maturity Model Hakan Bayraksan hxb07u 29 November 2009 G53QAT Table of Contents Introduction...2 The evolution of CMMI...3 CMM... 3 CMMI... 3 The definition of CMMI... 4 Level
Software and Systems Engineering. Software and Systems Engineering Process Improvement at Oerlikon Aerospace
SYMPOSIUM at Claude Y. Laporte OA - Process Engineering Nicola R. Papiccio OA - Software Engineering AGENDA Introduction Software Engineering Process s Engineering Process Management of of Change Lessons
Configuration Management Plan (CMP) Template
Configuration Management Plan (CMP) Template T2401 Revision: B Effective Date: January 10, 2011 DOWNLOADED AND/OR HARD COPY UNCONTROLLED Verify that this is the correct version before use. APPROVAL SIGNATURES
Life Cycle Support Information System. Training Guide
Life Cycle Support Information System Training Guide This manual is intended for both the end user and the administrator of the LCSIS tool suite. You are free to copy and distribute this manual without
Enterprise Test Management Standards
Enterprise Test Management Standards Version 4.0 09/28/2012 Document Number: FSA_TOADG_STDS_TEST.TMS_001 Document Version Control This section summarizes this document revision history. Each entry includes
WHITE PAPER December, 2008
INTRODUCTION Key to most IT organization s ongoing success is the leadership team s ability to anticipate, plan for, and adapt to change. With ever changing business/mission requirements, customer/user
Draft Document STATE OF MICHIGAN. SACWIS Planning Department of Human Services Strategic Implementation Plan: Project Staffing
STATE OF MICHIGAN SACWIS Planning Department of Human Services Strategic Implementation Plan: Project Staffing Executive Summary The State of Michigan has dedicated integrated team of resources for the
MM Agile: SCRUM + Automotive SPICE. Electronics Infotainment & Telematics
MM Agile: SCRUM + Automotive SPICE Electronics Infotainment & Telematics 20 Novembre, 2010 INDEX Introduction Why MM Agile Approach? How did we align classical and agile approach? How do we implement SCRUM?
Capability Maturity Model Integrated (CMMI)
When the Outcome Matters Capability Maturity Model Integrated (CMMI) Configuration Management Considerations Gerard Dache [email protected] 703-560-9477 Agenda SEI Overview Capability Maturity Models
Overview of the System Engineering Process. Prepared by
Overview of the System Engineering Process Prepared by Ed Ryen, PE Maintenance ITS March 2008 Introduction This document provides a high level look at the Systems Engineering Process for ITS projects.
Technical Baseline Management
Technical Baseline Management September 30, 2003 Pat Hascall LAT System Engineering 1 Technical Baseline Management We are required to manage the configuration of our technical baseline What is configuration
Capability Maturity Model Integration (CMMI SM ) Fundamentals
Capability Maturity Model Integration (CMMI SM ) Fundamentals Capability Maturity Model Integration and CMMI are are service marks of Carnegie Mellon University 2008, GRafP Technologies inc. 1 What is
The ITIL Foundation Examination
The ITIL Foundation Examination Sample Paper B, version 4.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. All answers are to be marked on the answer grid provided. 3. You have
Space project management
ECSS-M-ST-80C Space project management Risk management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS Standards
Procedure for Assessment of System and Software
Doc. No: STQC IT/ Assessment/ 01, Version 1.0 Procedure for Assessment of System and Software May, 2014 STQC - IT Services STQC Directorate, Department of Electronics and Information Technology, Ministry
What Are Software Developers Facing?
Configuration Management Tuotteenhallinta ohjelmistoprojektissa 1. Objectives 2. Problems & Motivation 3. CM Concept 4. Making CM system to work 5. Present CM Standards and Terms 6. CM Benefits and Summary