D R A F T. Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "D R A F T. Resource Ordering and Status System (ROSS) Software Configuration Management Guidelines"

Transcription

1 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 Order Number: GA81 Configuration Management & Control 1

2 1.0 Software Configuration Management Overview Software Configuration Management (SCM) is the effective management of the evolving configuration of a software product or system, and its related documentation. SCM controls and monitors the evolving software products, their technical requirements, and conformance to these requirements. Control over the evolving product s characteristics is maintained by establishing reference points or baselines. The SCM discipline applies technical and administrative direction to each phase of the software lifecycle to: 1. Identify all documents and physical media for each major module 2. Control changes to the software 3. Record and report change processing and implementation status 4. Changes are tracked via SP/CRs (Software Problem/Change Reports), Discrepancy Reports/Notices 1.1 Software Configuration Management - Organization and Responsibility During the performance of this Task Order, the ROSS Program s Software Configuration Management will be established and maintained by the selected members of the ROSS team. Specific responsibilities are identified in the Program Management Plan. 2.0 Configuration Identification All functional and physical characteristics of the ROSS major modules identified in the ROSS Specification Tree and in the Deliverables Mapping Spreadsheet, including the Software Requirements Specification, the RTM, the System Design Document, files and code, will be tracked and updated throughout the ROSS life cycle. All customer-furnished software and vendor-supplied COTS software will be uniquely identified and tracked. 3.0 Flow of Configuration Control Configuration control is the process by which changes to customer-approved baseline items and to internal baseline items are initiated, clarified, evaluated, approved, documented, implemented, and verified. ROSS Configuration control will: 1. Establish a developmental configuration for each module. 2. Maintain current copies of the deliverables. 3. Provide the customer with documentation and code access under configuration control. 4. Control and preparation and dissemination of changes to the master copies of deliverable software and documentation that has been placed under configuration control so that they reflect only the approved changes. 5. Maintain current copies of vendor COTS software media, licensing information, and related documentation. Figure 3.0 depicts the flow of control through the configuration management process. Software changes, enhancements, and problems can originate from any ROSS team member or the customer. These changes are tracked through Software Problem Change Reports, Discrepancy Reports, or Discrepancy Notices. 3.1 Classifications of SCM Changes Changes to software or documentation can be placed into one of three classifications: 1. Class I This type of change alters the operation or physical characteristics of a configured item or customer-approved baseline beyond the scope of intent under the current design requirements. These include: Configuration Management & Control 2

3 a. Compatibility Changes those changes to correct a deficiency that prevents the product from performing within contractual requirements. b. Design Changes those changes resulting from new or modified requirements outside the scope of the existing contract Class I changes require approval by the project and the customer prior to implementation. Ross identified Class 1 Change Prepare Proposed Specification Changes Prepare ECP/SCN Pkg & circulate for Review Approval Yes ECP/SCN Pkg Logged & sent to Contract Admin/submits to Customer No Customer Approval No ROSS notified of disposition Yes Returns to ROSS Contract Admin Conditionally Approved ECPs to CM ROSS Team incorporates changes Approved Proposed changes to CM Approval Yes Specification revised CM updates log & forwards to document release Document release Internal distribution No Submit revision to Customer Figure 3.0 Flow of Configuration Control 2. Class II These types of changes are usually non-technical, affecting ONLY the documentation. Class II changes do not require project or customer approval prior to implementation. Copies of Class II changes must be forwarded to the customer for concurrence of the change classification. 3. Internal Are changes to software or documentation that have not been classified as Class I or Class II changes. Changes released during development testing are treated as Internal Changes unless the change affects the documentation representing the Baseline. Configuration Management & Control 3

4 Internal changes do not require project approval, customer approval, or customer concurrence. 3.2 Reporting Documentation The documentation used to report and track changes in the developmental configuration or formal baseline are the Software Problem/Change Report (SP/CR), Discrepancy Notice (DN), Engineering Change Proposal (ECP), and Specification Change Notice (SCN). The Issue Weaver application will be used to input, track, and update SP/CRs and DNs Software Problem/Change Report (SP/CR) The SP/CR is the vehicle used internally to report a known or suspected anomaly in the developmental configuration. If a software problem results in changes to an approved baseline, an SP/CR is prepared with accompanying redlined specification change pages and forwarded to the project officer for disposition. Following project officer approval of SP/CRs, the work to correct the problem and the work on the supporting ECP with SCNs are started. Final approval will be with the acceptance of the ECP and SCNs Discrepancy Notice (DN) The DN form is the vehicle used during Formal Test by for tracking and reporting hardware/software problems that occur during validation testing. If the problem is in software, an SP/CR(s) is filed, the problem is fixed, the software is retested to the extent necessary, and the SP/CR and DN are closed Engineering Change Proposal (ECP) The ECP is used to propose Class I changes to the customer and for the customer to finalize Class II changes. It describes the merits of the proposed change, the desirability of authorizing the required funding, and the available alternatives. It gives the customer the information needed to evaluate changes that have performance, cost and schedule implications. The ECP is approved by the and coordinated through the Project Officer prior to formal submittal Specification Change Notice (SCN). The SCN is used to propose, transmit, and record Class I and Class II changes to base-lined specifications. Changes shall be made upon completion of a review or made as a normal update of the specification. The SCN, which documents the exact changes to the specifications, shall be required as part of an ECP. 4.0 Review Procedures If the base-lined specifications are impacted, the ROSS internal processing of ECPs/SCNs by the Configuration Control Board () is initiated. The reviews the ECP change. If approved, the ECP/SCN is submitted to the customer for review and approval. When the ROSS customer approval is received, approved changes are implemented. If required, deviations and waivers are requested. Upon customer approval of the ECP, the associated SCN with specification change pages (or specification revision) will be processed. The Configuration Management system for major systems is composed of a hierarchy of control boards that can interface with the customer s control boards. These formal control boards are the Configuration Control Board and the Software Configuration Review Board. For this Task Order, the, ERB and SCRB Boards are merged, with the Program Manager acting as the Chair for all three. The ROSS Program Management and Key Lead Personnel will represent the ROSS /SCRB. Weekly board meetings are held each Tuesday for the purpose of reviewing any Class I, Class II or Internal Changes. 4.1 Configuration Control Board () The is the forum through which the impact of changes to the program's technical requirements are evaluated, then transmitted to the implementation team members. The assesses the necessity for, and reviews the proposed changes to, the authenticated baseline. The release (submittal) of specifications and changes to approved baselines requires approval of the. The is composed of senior members of the program and is chaired by the Program Manager. The chairman may request that customer Configuration Management & Control 4

5 representatives, or other contractor/subcontractor representatives support any meeting. Members of the advise the Chairman of the impact of proposed changes in the areas of cost, production, development, reliability, maintainability, training, logistical support, and specifications. Changes are initiated as ECPs or SP/CRs based on classification. The authorizes submittal of only those changes for which a requirement exists. Customer approval is required prior to implementing any change to a controlled baseline. 4.2 Software Configuration Review Board (SCRB) The SCRB interacts and coordinates with the to affect configuration control of internal baselines and provide inputs to formal baselines. The SCRB ensures that the procedures and mechanisms for updating and maintaining the software baseline are adequate and rigidly enforced. The SCRB analyzes SP/CRs generated by the test team or other originators and initiates action as appropriate. The SCRB is chaired by the ROSS Program Manager. The Documentation Management & Control Function records the minutes. Participating members are Software Team members, Test Team representative(s), Software Quality Assurance, Configuration Management, and as needed, participants from other functional disciplines. The SCRB is chartered to implement the resolution of software issues and maintain software baselines. To this end, the SCRB reviews all SP/CRs to determine the technical aspects, identify the need for change, assess the impact of software performance, and determine the ability to provide required technical support to resolve the discrepancy. The objectives of the SCRB are identified below: a. To resolve (or coordinate the resolution of) all issues against baselines of deliverable software. Issues include errors, deficiencies, and interface changes as well as failure to meet quality standards. b. To administer the software SP/CR process. The SCRB is authorized to proceed unilaterally on internal changes. c. To effect such changes to any established software baseline as are detailed by the resolution of SP/CRs. d. To manage changes to software which reside in multiple baselines. e. To establish, review, and approve all software configurations for the software development environment. g. In terms of Software Configuration Management, to: 1. Administer configuration control, consisting of the management of the software SP/CR process, and the capturing of baselines for new software releases. 2. Provide configuration status accounting and SCM metrics. The ROSS SCRB will meet with the on a weekly basis, as determined by the chairman. An SP/CR Status Report, which will serve as the agenda, will be prepared and distributed by the SCRB Recorder in a timely manner to adequately support the functions of the boards. The relationship of the, ERB, and SCRB review boards is shown in Figure 4.0. Configuration Management & Control 5

6 C CLASS 1 CHANGE APPROVAL CLASS II CHANGE CONCURRENCE PREPARE/SUBMIT ECP DATA SPR/CR ERB CONTRACTORS CHANGE AUTHORITY ECP APPROVAL DEVIATIONS WAIVERS SCRB SPR/CR TECHNICAL CONTROL OF S/W BASELINE REVIEW/APPROVE INTERNAL BASELINE CHANGES IDENTIFY AND ESTABLISH SYSTEM REQUIREMENTS FUNCTIONAL BASELINE ALLOCATED BASELINE C Customer Configuration Control Board Configuration Control Board (chaired by the ROSS Program Manager) ERB Engineering Review Board (combined w/ross ) SCRB Software Configuration Review Board (chaired by the ROSS Program Manager) Figure 4.0 Example Control Board Interaction The ROSS is a merged board having the responsibilities of the, ERB and SCRB combined activities. Weekly meetings are held to review submitted changes for approval. In addition, more frequent meetings are held by the Chair (Program Manager) on an as-needed basis to review requested changes and identified problems in order to maintain the momentum of the development and testing efforts. These changes are captured in a standard format and maintained as historical data. The merged relationship of the, ERB, and SCRB boards are illustrated in Figure 4.0a. Includes responsibilities of ERB, & SCRB C ROSS Merged Class I Change Approval Class II Change Concurrence Prepare/Submit ECP Data SP/CRs Contractors Change Authority Technical Control of Sw Baseline Review/Approve Internal Baseline Changes Establish ROSS System Requirements and Baselines ECP Approval Deviations Waivers Figure 4.0a ROSS Team / Customer problem identification ROSS Control Board Interaction Configuration Management & Control 6

7 5.0 Configuration Status Accounting Configuration Status Accounting is the means through which control and tracking of discrepancies and change requests affecting major modules are reported to the ROSS Program Manager. The Configuration Status Accounting contains an ECP Status log. Approved ECPs to the product baseline developmental configuration are listed, thus providing a status accounting of ECPs against each major module. Each ECP status log contains at least, the following: a. Control number b. Descriptive title c. Origination data d. Author's name e. Priority f. Status change date g. Comments or action assigned 5.1 Configuration Audits The ROSS Configuration Manager will plan, schedule, co chair the audits, and follow up on any resulting actions of any formal configuration audits. The CM will ensure the customer is advised of the status schedule and agenda of pending audits. Records and summary reports will be maintained for all internal reviews and audits conducted during the various phases of the ROSS Program development life cycle. 6.0 Configuration Management Major Milestones Configuration Milestones will be reached as each iterative software life cycle is reached. Milestones will consist of the following baseline controls: a. Functional Baseline. Periodic customer reviews will establish and authenticate the ROSS Functional Baseline. b. Allocated Baseline. The SRS will establish the Allocated Baseline for each major module. c. Product Baseline. Upon successful completion of the functional and physical configuration audits for each major module, and when authenticated by the customer, a Software Product Specification for each major module will be entered into the Product Baseline and the module s developmental configuration will cease to exist. Configuration Management & Control 7

CONFIGURATION MANAGEMENT PLAN GUIDELINES

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

More information

SOFTWARE CONFIGURATION MANAGEMENT GUIDEBOOK

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

More information

5 FAH-5 H-520 LIFE CYCLE 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

More information

<name of project> Software Project Management Plan

<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

More information

CalMod Design-Build Electrification Services

CalMod Design-Build Electrification Services SECTION 01800 SYSTEMS INTEGRATION AND INTEGRATOR REQUIREMENTS PART 1 GENERAL DESCRIPTION A. This section specifies the system-wide integration requirements for the Caltrain Electrification system, i.e.

More information

074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements

074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality

More information

Change Management Plan (CMP)

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

More information

Configuration Management

Configuration Management 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

More information

ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE

ITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution

More information

NOTICE: This publication is available at: http://www.nws.noaa.gov/directives.

NOTICE: This publication is available at: http://www.nws.noaa.gov/directives. Department of Commerce National Oceanic & Atmospheric Administration National Weather Service NATIONAL WEATHER SERVICE INSTRUCTION 30-1201 OCTOBER 13, 2003 Maintenance, Logistics, & Facilities Configuration

More information

Configuration Management Practices

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

More information

Project Management Guidelines

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.

More information

Space Project Management

Space Project Management EUROPEAN COOPERATION FOR SPACE STANDARDIZATION Space Project Management Configuration Management Secretariat ESA ESTEC Requirements & Standards Division Noordwijk, The Netherlands Published by: Price:

More information

Development, Acquisition, Implementation, and Maintenance of Application Systems

Development, Acquisition, Implementation, and Maintenance of Application Systems Development, Acquisition, Implementation, and Maintenance of Application Systems Part of a series of notes to help Centers review their own Center internal management processes from the point of view of

More information

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

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

More information

8. Master Test Plan (MTP)

8. Master Test Plan (MTP) 8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across

More information

Configuration Management Self Assessment Checklist

Configuration Management Self Assessment Checklist Configuration Management Self Assessment Checklist Introduction: The purpose of this Configuration Management (CM) Self- Assessment Checklist is to ensure that the Organization correctly understands the

More information

Department of Administration Portfolio Management System 1.3 June 30, 2010

Department of Administration Portfolio Management System 1.3 June 30, 2010 E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2

More information

UNCONTROLLED IF PRINTED IN-SERVICE MANAGEMENT OF SOFTWARE FOR AIRBORNE AND RELATED SYSTEMS

UNCONTROLLED IF PRINTED IN-SERVICE MANAGEMENT OF SOFTWARE FOR AIRBORNE AND RELATED SYSTEMS UNCONTROLLED IF PRINTED AAP 7001.054 Sect 2 Chap 17 SECTION 2 CHAPTER 17 IN-SERVICE MANAGEMENT OF SOFTWARE FOR AIRBORNE AND RELATED SYSTEMS INTRODUCTION 1. The in-service maintenance and development of

More information

Certified Professional in Configuration Management Glossary of Terms

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,

More information

Criteria for Flight Project Critical Milestone Reviews

Criteria for Flight Project Critical Milestone Reviews Criteria for Flight Project Critical Milestone Reviews GSFC-STD-1001 Baseline Release February 2005 Approved By: Original signed by Date: 2/19/05 Richard M. Day Director, Independent Technical Authority

More information

NSSC Enterprise Service Desk Configuration Management Database (CMDB) Configuration Management Service Delivery Guide

NSSC Enterprise Service Desk Configuration Management Database (CMDB) Configuration Management Service Delivery Guide National Aeronautics and Space Administration NASA Shared Services Center Stennis Space Center, MS 39529-6000 www.nssc.nasa.gov NASA Shared Services Center Version 1.0 NSSC Enterprise Service Desk Configuration

More information

Software Configuration Management Plan

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.

More information

Appendix H Software Development Plan Template

Appendix H Software Development Plan Template Appendix H Software Development Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms

More information

IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results

IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results Acquire or develop application systems software Controls provide reasonable assurance that application and system software is acquired or developed that effectively supports financial reporting requirements.

More information

CHAPTER 7 Software Configuration Management

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

More information

CLASS SPECIFICATION. Business Intelligence Supervisor

CLASS SPECIFICATION. Business Intelligence Supervisor San Diego Unified Port District Class Code: B843-UE08 CLASS SPECIFICATION FLSA Status: EEOC Job Category: Classified: Union Representation: Exempt Professionals No Unrepresented GENERAL PURPOSE Under general

More information

STAR JPSS Algorithms Integration Team Configuration Management Plan Version 1.2

STAR JPSS Algorithms Integration Team Configuration Management Plan Version 1.2 STAR JPSS Algorithms Integration Team Version 1.2 NOAA Center for Weather and Climate Prediction (NCWCP) NOAA/NESDIS/STAR 5830 University Research Ct College Park, MD 20740 Revisions Version Description

More information

Program Lifecycle Methodology Version 1.7

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

More information

Configuration Management Plan

Configuration Management Plan Project: Version: Prepared by: : Approvals: Submitted By: Project Team Member Review Approvals By: Document Change Log Version Author Description ii Table of Contents 1.0 Scope 1 2.0 Configuration Management

More information

National Information Assurance Certification and Accreditation Process (NIACAP)

National Information Assurance Certification and Accreditation Process (NIACAP) NSTISSI No. 1000 April 2000 National Information Assurance Certification and Accreditation Process (NIACAP) THIS DOCUMENT PROVIDES MINIMUM STANDARDS. FURTHER INFORMATION MAY BE REQUIRED BY YOUR DEPARTMENT

More information

Chapter 5. Choose the answer that mostly suits each of the sentences given:

Chapter 5. Choose the answer that mostly suits each of the sentences given: Chapter 5 Software Configuration Management Choose the answer that mostly suits each of the sentences given: 1. No matter where you are in the system lifecycle, the system will change, and the desire to

More information

SOFTWARE MANAGEMENT PROGRAM. Software Testing Checklist

SOFTWARE MANAGEMENT PROGRAM. Software Testing Checklist SOFTWARE MANAGEMENT PROGRAM Software Testing Checklist The following checklist is intended to provide system owners, project managers, configuration managers, and other information system development and

More information

<Project Name> Project Implementation Plan

<Project Name> Project Implementation Plan Client Logo Project Implementation Plan Version 0.1 Prepared By: David Bowman Information Management Architect Table of Contents Revision History...4 1. INTRODUCTION...5 1.1. Purpose...5

More information

CHANGES, DEVIATIONS & WAIVERS PROCESSES

CHANGES, DEVIATIONS & WAIVERS PROCESSES PROCEDURE CHANGES, DEVIATIONS & WAIVERS PROCESSES This document is stored electronically. Printed version might not be the latest. SAOCOM PROJECT COMISION NACIONAL DE ACTIVIDADES ESPACIALES BUENOS AIRES

More information

The Software Development Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) Document ID: Version: 2.0 1 / 22 2 TABLE OF CONTENTS INTRODUCTION... 4 THE SDLC WATERFALL... 4 ALLOWED VARIATIONS... 5 OTHER SDLC MODELS... 6 REFERENCES... 7 GENERIC STAGE... 8 KICKOFF PROCESS... 8 INFORMAL

More information

STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840

STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840 MARYLAND STATE BOARD OF ELECTIONS P.O. BOX 6486, ANNAPOLIS, MD 21401-0486 PHONE (410) 269-2840 Bobbie S. Mack, Chairman David J. McManus, Jr., Vice Chairman Rachel T. McGuckian Patrick H. Murray Charles

More information

ORACLE QUALITY ORACLE DATA SHEET KEY FEATURES

ORACLE QUALITY ORACLE DATA SHEET KEY FEATURES ORACLE QUALITY KEY FEATURES Enterprise wide Quality Data Repository In-process Quality Integrated with manufacturing, logistics, maintenance and service modules in the Oracle E-Business Suite. Analysis

More information

Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects

Best Practices Statement Project Management. Best Practices for Managing State Information Technology Projects State of Arkansas Office of Information Technology 124 W. Capitol Ave. Suite 990 Little Rock, AR 72201 501.682.4300 Voice 501.682.4020 Fax http://www.cio.arkansas.gov/techarch Best Practices Statement

More information

PM Planning Configuration Management

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

More information

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997

Project Start Up. Start-Up Check List. Why a Project Check List? What is a Project Check List? Initial Release 1.0 Date: January 1997 Why a Project Check List? A good way to ensure that all start-up tasks are completed prior to actually starting the project is to develop a start-up check list. The check list can be developed and then

More information

Configuration Management ISO 10007

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

More information

Configuration, Change, and Release Management Policies and Procedures Guide

Configuration, Change, and Release Management Policies and Procedures Guide Configuration, Change, and Release Management Policies and Procedures Guide Table of Contents Section 1 Introducing Configuration, Change, and Release Management...5 1.1 Overview of Configuration, Change,

More information

Contract No. E22PS02. PROJECT CONFIGURATION MANAGEMENT PLAN (CMP) for PRELIMINARY ENGINEERING AND DESIGN/BUILD PROCUREMENT

Contract No. E22PS02. PROJECT CONFIGURATION MANAGEMENT PLAN (CMP) for PRELIMINARY ENGINEERING AND DESIGN/BUILD PROCUREMENT Contract No. E22PS02 PROJECT CONFIGURATION MANAGEMENT PLAN (CMP) for PRELIMINARY ENGINEERING AND DESIGN/BUILD PROCUREMENT Revision 0.0 May 18, 2011 Prepared By: Robert E. Cone Engineering Manager Date

More information

Chapter 3, Section 3-2 (B), dated 1/2002 Chapter 3, Section 3-2 (B), dated 7/2008

Chapter 3, Section 3-2 (B), dated 1/2002 Chapter 3, Section 3-2 (B), dated 7/2008 Special Attention of: Transmittal for Handbook No: 3252.1 Chg 1 Issued: 7/20/08 1. This Transmits: Handbook 3252.l Chg 1, Software Configuration Management Policy, Chapter 3, Section 3-2, a change to subsection

More information

Federal Business Opportunities (FedBizOpps.gov) Change Management Plan (CMP)

Federal Business Opportunities (FedBizOpps.gov) Change Management Plan (CMP) GSA OFFICE OF GOVERNMENTWIDE POLICY Federal Business Opportunities (FedBizOpps.gov) Change Management Plan (CMP) Issued on October 18, 2002 by the FedBizOpps Program Management Office in consultation with

More information

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute

More information

5 FAM 630 DATA MANAGEMENT POLICY

5 FAM 630 DATA MANAGEMENT POLICY 5 FAM 630 DATA MANAGEMENT POLICY (Office of Origin: IRM/BMP/OCA/GPC) 5 FAM 631 GENERAL POLICIES a. Data management incorporates the full spectrum of activities involved in handling data, including its

More information

Software Project Management Plan (SPMP)

Software Project Management Plan (SPMP) Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.

More information

CDC UNIFIED PROCESS JOB AID

CDC UNIFIED PROCESS JOB AID CDC UNIFIED PROCESS JOB AID Independent Verification & Validation Activities Document Purpose This Job Aid is a brief document listing the items to be noted, checked, remembered, and delivered when completing

More information

Configuration & Build Management

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

More information

THE PROJECT MANAGEMENT KNOWLEDGE AREAS

THE PROJECT MANAGEMENT KNOWLEDGE AREAS THE PROJECT MANAGEMENT KNOWLEDGE AREAS 4. Project Integration Management 5. Project Scope Management 6. Project Time Management 7. Project Cost Management 8. Project Quality Management 9. Project Human

More information

Appendix 2-A. Application and System Development Requirements

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

More information

Example Software Development Process.

Example Software Development Process. Example Software Development Process. The example software development process is shown in Figure A. The boxes represent the software development process kernels. The Software Unit Testing, Software Component

More information

SECURITY THROUGH PROCESS MANAGEMENT

SECURITY THROUGH PROCESS MANAGEMENT SECURITY THROUGH PROCESS MANAGEMENT Jennifer L. Bayuk Price Waterhouse, LLP Headquarters Plaza North Morristown, NJ 07962 jennifer_bayuk@notes.pw.com Overview This paper describes the security management

More information

Software and Hardware Configuration Management

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

More information

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES

ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES 1. ROLE DEFINITIONS ATTACHMENT 3 SPS PROJECT SENIOR PROGRAM MANAGER (SPM) DUTIES & RESPONSIBILITIES The purpose of this section is to distinguish among the roles interacting with the SPM obtained through

More information

Lockheed Martin Tactical Aircraft Systems (LMTAS) Fort Worth, Texas CONFIGURATION MANAGEMENT REQUIREMENTS FOR SUPPLIERS AND SUBCONTRACTORS.

Lockheed Martin Tactical Aircraft Systems (LMTAS) Fort Worth, Texas CONFIGURATION MANAGEMENT REQUIREMENTS FOR SUPPLIERS AND SUBCONTRACTORS. Lockheed Martin Tactical Aircraft Systems (LMTAS) Fort Worth, Texas CONFIGURATION MANAGEMENT REQUIREMENTS FOR SUPPLIERS AND SUBCONTRACTORS Approved: //signed// J. K. Goodman, Manager Configuration Management

More information

ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT

ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT ORACLE PROCESS MANUFACTURING QUALITY MANAGEMENT KEY FEATURES Automated stability study management Lot expiration handling and retesting Potency or variability management Quality holds during receiving

More information

Defense Travel Management Office. Change Management Plan

Defense Travel Management Office. Change Management Plan Defense Travel Management Office Change Management Plan January 2007 Version 2.0 Table of Contents Table of Contents...2 List of Figures...2 List of Appendices...2 Record of Changes...3 Executive Summary...4

More information

SYSTEMS ENGINEERING AND MANAGEMENT FOR SUSTAINABLE DEVELOPMENT - Vol. I - Configuration Management - Brouse, Peggy S.

SYSTEMS ENGINEERING AND MANAGEMENT FOR SUSTAINABLE DEVELOPMENT - Vol. I - Configuration Management - Brouse, Peggy S. CONFIGURATION MANAGEMENT Brouse, Peggy S. Systems Engineering and Operations Research Department, George Mason University, USA Keywords: Audits, baseline, change control board, configuration items, configuration

More information

ISO 20000-1:2005 Requirements Summary

ISO 20000-1:2005 Requirements Summary Contents 3. Requirements for a Management System... 3 3.1 Management Responsibility... 3 3.2 Documentation Requirements... 3 3.3 Competence, Awareness, and Training... 4 4. Planning and Implementing Service

More information

Project Governance Concepts Issues and Constraints. Dick Patterson

Project Governance Concepts Issues and Constraints. Dick Patterson Project Governance Concepts Issues and Constraints Dick Patterson dpatterson@intelcheck.caca GOVERNANCE PROJECT Concepts, Issues and Constructs SERVICE Governance What Is It? The Functional Perspective

More information

This is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>.

This is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>. Guide to Preparing the SOFTWARE PROJECT MANAGEMENT PLAN R. Buckley CSc 190 Senior Project Department of Computer Science - College of Engineering and Computer Science California State University, Sacramento

More information

PHASE 3: PLANNING PHASE

PHASE 3: PLANNING PHASE PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning

More information

CMMI for Development Quick Reference

CMMI for Development Quick Reference CAUSAL ANALYSIS AND RESOLUTION SUPPORT (ML5) The purpose of Causal Analysis and Resolution (CAR) is to identify causes of selected outcomes and take action to improve process performance. SG 1 Root causes

More information

Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996

Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996 Quality Assurance Plan A Model DRAFT United States Department of Energy Office of Nonproliferation and National Security Title Page Document Name: Publication Date: Draft, ontract Number: Project Number:

More information

Construction Management Standards of Practice

Construction Management Standards of Practice Construction Management Standards of Practice 2010 Edition Advancing Professional Construction/ Program Management Worldwide. 7926 Jones Branch Drive, Suite 800 McLean, VA 22102-3303 USA 703.356.2622 703.356.6388

More information

<Project Name> Configuration Management Plan

<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

More information

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

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 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,

More information

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

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

More information

AIRLIE LITTLE BOOK OF CONFIGURATION MANAGEMENT

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: spmn@aol.com http://www.spmn.com

More information

WHAT IS CHANGE MANAGEMENT

WHAT IS CHANGE MANAGEMENT WHAT IS CHANGE MANAGEMENT It is a set of activity designed to manage change by identifying the work products that are likely to change reestablishing relationships among them; defining mechanisms for managing

More information

MNLARS Project Audit Checklist

MNLARS Project Audit Checklist Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?

More information

Software Review Job Aid - Supplement #1

Software Review Job Aid - Supplement #1 Software Review Job Aid - Supplement #1 1010011101010011110001101001101101101101000100100010101011100010110 1010011101010011110001101001101101101101000100101110101011100010111 0110100110110110110100010010001010101110001011000100111010100111100

More information

Baseline Change Control Procedure

Baseline Change Control Procedure Earned Value Management System (EVMS) Implementing Procedures Baseline Change Control Procedure EVMS-P-7 Revision 0 - October, 2006 Change Log Earned Value Management System Procedure Change Log Revision

More information

Application of Standard Project Management Processes in Fiber Optic Cable Plant Project Management. Introduction. Alfred Sankara, DigiBridge TelCo

Application of Standard Project Management Processes in Fiber Optic Cable Plant Project Management. Introduction. Alfred Sankara, DigiBridge TelCo Application of Standard Project Management Processes in Fiber Optic Cable Plant Project Management Alfred Sankara, DigiBridge TelCo Introduction The Project Management Institute (PMI) is the world's leading

More information

WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING

WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING June 28, 1999 WILLIAM J. DOWLING VICE PRESIDENT, ENGINEERING Subject: Tray Management System Software Management () As part of an ongoing audit of the Tray Management System, the Office of Inspector General

More information

Configuration Management. CxOne Standard

Configuration Management. CxOne Standard Configuration Management CxOne Standard CxStand_ConfigurationManagement.doc November 4, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 OVERVIEW...

More information

Commercial Software Licensing

Commercial Software Licensing Commercial Software Licensing CHAPTER 11: Software Prepared by DoD ESI January 2013 Chapter Overview The government uses three primary agreement types for services: Fixed Price (FP). T&M (Time and Materials).

More information

Appendix E Program Management Plan Template

Appendix E Program Management Plan Template Appendix E Program Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions

More information

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

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

More information

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 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,

More information

Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201

Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 PURCHASE ORDER ATTACHMENT Q-201A Software Quality Subcontractor Survey Questionnaire INSTRUCTIONS FOR PURCHASE ORDER ATTACHMENT Q-201 1. A qualified employee shall be selected by the Software Quality Manager

More information

I S O I E C 2 7 0 0 2 2 0 1 3 I N F O R M A T I O N S E C U R I T Y A U D I T T O O L

I S O I E C 2 7 0 0 2 2 0 1 3 I N F O R M A T I O N S E C U R I T Y A U D I T T O O L 15.1 ESTABLISH SECURITY AGREEMENTS WITH SUPPLIERS 15.1.1 EXPECT SUPPLIERS TO COMPLY WITH RISK MITIGATION AGREEMENTS Do you clarify the information security risks that exist whenever your suppliers have

More information

Organization. Project Name. Project Overview Plan Version # Date

Organization. Project Name. Project Overview Plan Version # Date Project Overview Plan Template Organization Project Name Project Overview Plan Version # Date REVISION HISTORY VERSION # REVISION DATE COMMENT 1 APPROVALS: Authorized Signature DATE 2 Table of Contents

More information

NONCONFORMANCE MANAGEMENT SYSTEM

NONCONFORMANCE MANAGEMENT SYSTEM PROCEDURE NONCONFORMANCE MANAGEMENT SYSTEM This document is stored electronically. Printed version might not be the latest. SAOCOM PROJECT COMISION NACIONAL DE ACTIVIDADES ESPACIALES BUENOS AIRES ARGENTINA

More information

05.0 Application Development

05.0 Application Development Number 5.0 Policy Owner Information Security and Technology Policy Application Development Effective 01/01/2014 Last Revision 12/30/2013 Department of Innovation and Technology 5. Application Development

More information

ABC COMPANY Extended Accounting System (EAS) Project Charter Sample

ABC COMPANY Extended Accounting System (EAS) Project Charter Sample ABC COMPANY Extended Accounting System (EAS) Project Charter Sample Prepared by: Document Details ABC Company IT Canada Inc. Business Services Department Information Technology Project: Extended Accounting

More information

PURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B"

PURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY B PURCHASE ORDER ATTACHMENT Q-202 SOFTWARE QUALITY SUBCONTRACTOR REQUIREMENTS TASK DESCRIPTIONS - PURCHASE CATEGORY "B" 1 SOFTWARE QUALITY PROGRAM. This attachment establishes the software quality requirements

More information

Functional Area 3. Skill Level 301: Applications Systems Analysis and Programming Supervisor (Mercer 1998 Job 011)

Functional Area 3. Skill Level 301: Applications Systems Analysis and Programming Supervisor (Mercer 1998 Job 011) Functional Area 3 Skill Level 301: Applications Systems Analysis and Programming Supervisor (Mercer 1998 Job 011) Description: Supervises activities of all applications systems analysis and programming

More information

The statements in this policy document establish HEALTHeLINK's expectations with respect to incident management.

The statements in this policy document establish HEALTHeLINK's expectations with respect to incident management. 1 Introduction The statements in this policy document establish HEALTHeLINK's expectations with respect to incident management. 2 Policy Statement 2.1 Incident Response Authority 2.1.1 Single Point of

More information

Draft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack

Draft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack Draft Copy Change Management Release Date: March 18, 2012 Prepared by: Thomas Bronack Section Table of Contents 10. CHANGE MANAGEMENT... 5 10.1. INTRODUCTION TO CHANGE MANAGEMENT... 5 10.1.1. PURPOSE OF

More information

This paper was presented at the 1995 CAUSE annual conference. It is part of the proceedings of that conference, "Realizing the Potential of

This paper was presented at the 1995 CAUSE annual conference. It is part of the proceedings of that conference, Realizing the Potential of This paper was presented at the 1995 CAUSE annual conference. It is part of the proceedings of that conference, "Realizing the Potential of Information Resources: Information, Technology, and Services--

More information

SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS)

SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS) SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS) 1.0 SEI Product 1.1 SEI Level 2 Product 1.1.1 SEI Level 2 Process 1.1.1.1 Requirements Management Process 1.1.1.2 Software Project Planning Process

More information

PHASE 8: IMPLEMENTATION PHASE

PHASE 8: IMPLEMENTATION PHASE PHASE 8: IMPLEMENTATION PHASE The Implementation Phase has one key activity: deploying the new system in its target environment. Supporting actions include training end-users and preparing to turn the

More information

Supporting Workflow Overview. CSC532 Fall06

Supporting Workflow Overview. CSC532 Fall06 Supporting Workflow Overview CSC532 Fall06 Objectives: Supporting Workflows Define the supporting workflows Understand how to apply the supporting workflows Understand the activities necessary to configure

More information

Quality Management Plan

Quality Management Plan 6500m HOV Project Stage 1: A-4500 HOV Document Control No.: 0000000 3-November-2009 WOODS HOLE OCEANOGRAPHIC INSTITUTION WOODS HOLE, MA 02543 Document Control Sheet Date Originator Description 07-28-09

More information

Software Process Training

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,

More information