Certified Professional in Configuration Management Glossary of Terms

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Certified Professional in Configuration Management Glossary of Terms"

Transcription

1 Certified Professional in Configuration Management Glossary of terms used in Configuration Management Issue Association of the International Certified Configuration Manager e.v.

2 Copyright 2007, the authors (René Schaap, Lars Bendix, Anne Mette Jonassen Hass, Karol Frühauf, Olaf Kosel), all rights reserved. The authors are transferring the copyright to the Association of the international Certified Configuration Manager (hereinafter called intccm). The authors, as current copyright holders, and intccm, as the future copyright holder, have agreed to the following conditions of use: 1) Any individual or training company may use this glossary if the authors and the intccm are acknowledged as the source and copyright owners of the syllabus and provided that any advertisement of such a training course may mention the glossary only after submission for official accreditation of the training materials to an intccm-recognized Board; 2) Any individual or group of individuals may use this glossary as the basis for articles, books, or other derivative writings if the authors and the intccm are acknowledged as the source and copyright owners of the glossary; 3) Any intccm-recognized Board may translate this glossary and license the glossary (or its translation) to other parties. Issue Page 1 of 12 July 20 th 2007

3 Revision and Change History Issue / Revision Date Reason for Change intccm Glossary 2006.xx 2006 Internal working issues intccm Glossary /01/2007 Draft for internal review meeting intccm Glossary /04/2007 Draft for final review (workgroup) intccm Glossary /06/2007 Draft for final review (association) intccm Glossary /07/2007 Approved and ready for distribution Change Record Reason for Change Changes as result of internal reviews Chapter / Paragraph / Page Throughout document Issue Page 2 of 12 July 20 th 2007

4 Table of Contents Revision and Change History... 2 Table of Contents... 3 Introduction to this glossary... 4 Purpose of this document... 4 Scope... 4 Arrangement... 4 Normative references... 5 Definitions... 6 Used Abbreviations... 6 A... 6 B... 6 C... 7 D... 8 E... 9 F... 9 I... 9 L... 9 M... 9 P... 9 R S T U V W Appendix A (Informative) Issue Page 3 of 12 July 20 th 2007

5 Introduction to this glossary Purpose of this document Much time and effort is wasted both within and between industry, commerce, government and professional and academic institutions when ambiguities arise as a result of the inability to differentiate adequately between such terms as change control and change management ; configuration management policy and configuration management plan and similar terms which form an interface between various sectors of society. Moreover, the professional or technical use of these terms is often at variance with different meanings attributed to them. Scope This document presents terms and definitions designed to aid communication in configuration management and related disciplines. Arrangement The glossary has been arranged in a single section of definitions ordered alphabetically. Some terms are preferred to other synonymous ones, in which case, the definition of the preferred term appears, with the synonymous ones referring to that. For example change control refers to configuration control. For synonyms, the See indicator is used. See also cross-references are also used. They assist the user to quickly navigate to the right index term. See also cross-references are constructed for relationships such as broader term to a narrower term, and overlapping meaning between two terms. Issue Page 4 of 12 July 20 th 2007

6 Normative references At the time of publication, the edition indicated was valid. All standards are subject to revision, and parties to agreements based upon this Standard are encouraged to investigate the possibility of applying the most recent edition of the standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. IEEE :1990 IEEE 828:2005 IEEE 829:1998 IEEE 1008:1993 IEEE 1044:1993 IEEE 1058:1998 ISO/IEC 10007:2003 EIA-649-A:2004 Standard Glossary of Software Engineering Terminology Standard for Software Configuration Management Plans Standard for Software Test Documentation Standard for Software Unit Testing Standard Classification for Software Anomalies Standard for Software Project Management Plans Quality management systems -- Guidelines for Configuration Management National Consensus Standard for Configuration Management Issue Page 5 of 12 July 20 th 2007

7 Definitions Not all terms in the glossary are mentioned directly as terms in the Foundation Level Qualification Scheme; they are added here for completeness because they are related to configuration management discipline. Used Abbreviations CCB CI COTS CM CMMI CSA FCA PCA Configuration Control Board Configuration Item Commercial of-the-shelf Configuration Management Capability Maturity Model Integration Configuration Status Accounting Functional Configuration Audit Physical Configuration Audit A approval: The agreement that an item is complete and suitable for its intended use. [EIA-649] artefact: See product. attributes: See meta-data. audit: An independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual agreements, or other criteria. [IEEE ] An audit of a configuration management system will not examine a work product or set of work products but a process or set of processes. B baseline: A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through a formal change control process. [IEEE ] branch: A separate development line, to e. g. isolate bugfixing of an already delivered release from further development. build: An operational version of a software product incorporating a specified (sub)set of the capabilities that the final product will include. building: Assembling a system or part of a system - sometimes called a build - from components placed under configuration management. build management: Management of the build process in development and testing with an interface to configuration management. Issue Page 6 of 12 July 20 th 2007

8 C CCB: See configuration control board. change: A modification to an existing configuration item (CI) after agreement by the relevant configuration control board (CCB), which leads to a new version of the CI. change control: An activity of configuration management, consisting of the evaluation, co-ordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration and stored in the configuration controlled area. change control board: See configuration control board. change management: Judicious use of means to effect a change, or proposed change, on a product or service [CMMI] change request: A formal request for a change to be implemented in a specific configuration item approved by the CCB and based on a registered event (problem, requirement change, etc.). check in: Storing a configuration item in the configuration controlled area. [AMJ] check out: Copy of a configuration item from the configuration controlled area. [AMJ] commercial off-the-shelf (COTS): Software defined by a market-driven need, commercially available, and whose fitness for use has been demonstrated by a broad spectrum of commercial users. [IEEE ] component: One of the parts that make up a system. A component may be hardware or software and may be subdivided into other components. [IEEE ] configuration: The arrangement of a system or component as defined by the number, nature, and interconnections of its constituent parts. [IEEE ] configuration audit: The process of verifying that all required hardware/software configuration items have been produced, that the current version agrees with specified requirements, that the technical documentation completely and accurately describes the configuration items, and that all change requests have been resolved. [IEEE ]. Standards recognize functional configuration audits (FCA) and physical configuration audits (PCA). configuration change control: An activity of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items. configuration control board (CCB): Person or a group of persons assigned responsibility and authority to make decisions on the configuration. Relevant interested parties within and outside the organization should be represented on the CCB. [ISO 10007] configuration controlled area: An area where the components / CI s are identified and stored in order to be recreated or retrieved unmodified at any time. configuration identification: An activity of configuration management, consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. [IEEE ] Issue Page 7 of 12 July 20 th 2007

9 configuration item (CI): An entity within a configuration that satisfies an end use function and is under configuration change control. An aggregation of hardware, software, or both that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE ]. This should be extended with all types of components to include documents, middleware, etc. configuration management (CM): A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. [IEEE ] configuration management librarian: A person responsible for the establishment of configuration management for selected environments, for the maintenance of each configuration controlled area, its internal integrity, and integrity between areas. configuration management metrics: Definition of what to measure concerning the performance of configuration management, both directly in the form of raw data, and by calculations based on raw data. configuration management plan: A document setting forth the configuration items of a system and the plan for configuration management of each of them, including schedules, procedures, personnel, and equipment to be used. [IEEE 828] configuration management policy: An expression of the overall organisational position towards configuration. It provides guidance and direction for all CM work in the organisation. configuration management system: The collection of procedures, tools, and storage facilities for the performed configuration management. [CMMI] configuration manager: Person responsible for planning, monitoring and controlling the configuration management for at least one specific domain/configuration. configuration status accounting (CSA): See configuration status reporting. configuration status reporting: The process of reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of approved changes. [IEEE ] D deviation: A written authorization, granted prior to the manufacture of an item, to depart from a particular performance or design requirement for a specific number of units or a specific period of time. Note: Unlike an engineering change, a deviation does not require revision of the documentation defining the affected item. [IEEE ] disapproval: Conclusion by the appropriate authority that an item submitted for approval is either incomplete or not suitable for its intended use. [EIA-649] distributed development: Different parts of the development group are located at different geographical sites. Also called multi-site development. Issue Page 8 of 12 July 20 th 2007

10 E event: An occurrence or happening, usually significant to the performance of a function, operation, or task. Registered events can lead to change requests. event lifecycle: The complete cycle from recognizing the event to the end of all actions related to the event. F functional configuration audit (FCA): A formal examination to verify that a configuration item has achieved the functional and performance characteristics specified in its product configuration information. [ISO 10007] I identification: See configuration identification. impact analysis: The assessment of the impact of a requested requirements change to the layers of documentation and components. incident: Any event occurring that requires investigation. [After IEEE 1008] incident management: The process of recognizing, investigating, taking action and disposing of incidents. It involves recording incidents, classifying them and identifying the impact. [After IEEE 1044] incident management tool: A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities. incident report: A document reporting on any event that occured, e.g. during the testing, which requires investigation. [After IEEE 829] L label: A type of meta-data to identify a special version of a configuration item. library: See configuration controlled area M manufacturing area: An area in which the components are created or modified, initiated by a formal change request (except for the first version) and approved by a change decision authority. merging: The consolidation of different development branches. meta-data: Information about configuration items (also called attributes). [AMJ] P phvsical attributes: Quantitative and qualitative expressions of material features, such as composition, dimensions, finishes, form, fit, and their respective tolerances. [After EIA 649] Issue Page 9 of 12 July 20 th 2007

11 physical configuration audit (PCA): a formal examination to verify that a configuration item has achieved the physical characteristics specified in its product configuration information. [ISO10007] priority: An attribute of an incident expressing the urgency of its resolution. Using a defined classification scheme (for example High, Medium, Low) one priority value shall be assigned in the incident report. procedure: A written description of a course of action to be taken to perform a given task. [IEEE ] process: A set of interrelated activities that transform inputs into outputs. [ISO 12207] product: Anything that is used or produced to satisfy a need, for example, facilities, systems, hardware, software, firmware, data, processes, materials, or services. [EIA 649] A product is the result of activities or processes. [ISO 8402] product engineering: the technical processes to define, design, and construct or assemble a product. [IEEE 1002] product configuration information: All information/documents related to requirements for product design, realization,verification, operation and support. [ISO10007] product life cycle: A theory in which products follow a sequence of stages from its conception, through design and manufacture, to service and disposal. R release: The formal notification and distribution of an approved version of a hardware/software system. [IEEE 828] release management: The discipline to manage the release cycles of the product or part of the product; this refers to planning and actual releasing. requirement: A condition or capability that must be met or possessed by a product or product component to satisfy a contract, standard, specification or other formally imposed documents. [IEEE 610] revision: See version. S severity: An attribute of an incident expressing its impact on the function and user. Using a defined classification scheme (for example Critical, Serious, Non Critical) one value shall be assigned in the incident report. software: See IEEE sub-system: A secondary or subordinate system within a larger system. [IEEE ] support processes: Cover the activities, that support product development and maintenance, CM is one of the support processes [CMMI] system: A collection of components organized to accomplish a specific function or set of functions. [IEEE ] Issue Page 10 of 12 July 20 th 2007

12 T tag: See label. traceability: The ability to identify related items in documentation and software, such as requirements with associated tests. U unique identification: Identification that distinguishes a version of a configuration item from any other version of any other configuration item in the context. usage: Any employment or application of a CI (work product, product component or product) without it being changed. For example requirement specification used for review, requirement specification used as basis for test specification, test specification used to perform test, end-user using the system. V version: A version is an initial release or re-release of a configuration item. [IEEE ] version control: A process for keeping different versions in a CI class, without formal control of the changes between versions. A basic activity needed within configuration management. version identifier: Part of the unique identification used to distinguish a changed version of a CI from the previous version of the CI with the same primary identifier. [from EIA-649] W waiver: A written authorization to accept a configuration item or other designated item which, during production or after having been submitted for inspection, is found to depart from specified requirements, but is nevertheless considered suitable for use as is or after rework by an approved method. [IEEE ] work product: Any document, documentation, or other tangible item that results from working on a project function, activity, or task. Examples of work products include the project plan, functional requirements, design documents, source code, test plans, meeting minutes, schedules, budgets, and problem reports. A subset of the work products will form the set of project deliverables. [IEEE 1058] workspace: A workspace represents a configuration controlled area copy and acts as an environment where one can work isolated for a task duration. Issue Page 11 of 12 July 20 th 2007

13 Appendix A (Informative) Index of sources; the following non-normative sources were used in constructing this glossary: [AMJ] Anne Mette Jonassen Hass (2003), Configuration Management Principles and Practice, Addison Wesley. [CMMI] Crissis, Konrad, Shrum (2005), CMMI - Guidelines for Process Integration and Product Improvement, Addison Weseley. Issue Page 12 of 12 July 20 th 2007

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

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

Service Support. 2005 Kasse Initiatives, LLC. ITIL Configuration Management - 1. version 2.0

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

More information

CMS Policy for Configuration Management

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

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

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

Medical Device Software - Software Life Cycle Processes

Medical Device Software - Software Life Cycle Processes 1 Medical Device Software - Software Life Cycle Processes IEC 62304 2 Credits John F. Murray Software Compliance Expert U.S. Food and Drug Administration Marcie R. Williams Medical Device Fellow Ph.D.

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

2015. All rights reserved.

2015. All rights reserved. DOCUMENT: Future AAMI/IEC 62304:2006/AMD1, 18-August-2015 Final Draft International Standard for Vote, Amendment 1 to IEC 62304: Medical device software Software life cycle processes. Public Review Draft

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

SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT

SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT Mar 31, 2014 Japan Aerospace Exploration Agency This is an English translation of JERG-2-610. Whenever there is anything ambiguous in this document, the original

More information

Eastern Illinois University EISE Configuration Management Plan

Eastern Illinois University EISE Configuration Management Plan Eastern Illinois University EISE Configuration Management Prepared by: Bill Witsman Version: 10.0 Create Date: April 13, 2005 Approval Date: Last Revision Date: December 17, 2009 CM Analyst: Project Manager:

More information

Software Configuration Management. Addendum zu Kapitel 13

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

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

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

The Configuration Management process area involves the following:

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

More information

SOFTWARE ASSURANCE STANDARD

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

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

CONFIGURATION MANAGEMENT PLAN

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

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

R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM

R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM The American Association for Laboratory Accreditation Document Revised: R214: Specific Requirements: Information Technology Testing Laboratory Accreditation July 13, 2010 Program Page 1 of 26 R214 SPECIFIC

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

F15. Towards a More Mature Test Process. Anne Mette-Hass. P r e s e n t a t i o n

F15. Towards a More Mature Test Process. Anne Mette-Hass. P r e s e n t a t i o n Towards a More Mature Test Process Anne Mette-Hass International Conference On Software Testing, Analysis & Review November 19-23 Stockholm, Sweden P r e s e n t a t i o n F15 Friday 23rd November, 2001

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

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

NATO GUIDANCE ON THE USE OF THE AQAP 2000 SERIES

NATO GUIDANCE ON THE USE OF THE AQAP 2000 SERIES NATO GUIDANCE ON THE USE OF THE AQAP 2000 SERIES (June 2003) I ORIGINAL Page blank II ORIGINAL NORTH ATLANTIC TREATY ORGANIZATION NATO STANDARDISATION AGENCY (NSA) NATO LETTER OF PROMULGATION June 2003

More information

DRAFT REGULATORY GUIDE

DRAFT REGULATORY GUIDE U.S. NUCLEAR REGULATORY COMMISSION August 2012 OFFICE OF NUCLEAR REGULATORY RESEARCH Division 1 DRAFT REGULATORY GUIDE Contact: K. Sturzebecher (301) 251-7494 DRAFT REGULATORY GUIDE DG-1206 (Proposed Revision

More information

Introduction for Software Configuration Management Training

Introduction for Software Configuration Management Training Introduction for Software Configuration Management Training I thought I knew it all! History of 12207 ISO/IEC 12207 1995: Standard for Information Technology Software Life Cycle Processes IEEE/EIA 12207.0

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

Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?

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

More information

ASTRIUM SPACE TRANSPORTATION GENERIC QUALITY ASSURANCE REQUIREMENTS FOR SUPPLIERS MANAGED BY DIRECT MATERIALS

ASTRIUM SPACE TRANSPORTATION GENERIC QUALITY ASSURANCE REQUIREMENTS FOR SUPPLIERS MANAGED BY DIRECT MATERIALS ASTRIUM SPACE TRANSPORTATION GENERIC QUALITY ASSURANCE REQUIREMENTS FOR SUPPLIERS MANAGED BY DIRECT MATERIALS ISSUE: 02 RELEASE DATE: 02.04.2013 Supplier Organisational Unit: Name: ASTRIUM Space Transportation

More information

QA Procedure Page 1 Appendix A

QA Procedure Page 1 Appendix A *Changes from the previous QASE noted by "yellow" highlight of block Evaluation Summary Company: Prepared By: Section Element Manual Audit OK Objective Evidence 2.1 Objective of Quality Assurance Program

More information

CORPORATE QUALITY MANUAL

CORPORATE QUALITY MANUAL Corporate Quality Manual Preface The following Corporate Quality Manual is written within the framework of ISO 9001:2008 Quality System by the employees of CyberOptics. CyberOptics recognizes the importance

More information

SOFTWARE DEVELOPMENT AND DOCUMENTATION

SOFTWARE DEVELOPMENT AND DOCUMENTATION DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited. NOT MEASUREMENT SENSITIVE MIL-STD-498 5 December 1994 (PDF version) Superseding DOD-STD-2167A 29 February 1988 DOD-STD-7935A

More information

CHAPTER 7 SOFTWARE CONFIGURATION MANAGEMENT

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 scott7@llnl.gov

More information

Software Quality Assurance: VI Standards

Software Quality Assurance: VI Standards Software Quality Assurance: VI Standards Room E 3.165 Tel. 60-3321 Email: hg@upb.de Outline I Introduction II Software Life Cycle III Quality Control IV Infrastructure V Management VI Standards VII Conclusion

More information

System Development Life Cycle Guide

System Development Life Cycle Guide TEXAS DEPARTMENT OF INFORMATION RESOURCES System Development Life Cycle Guide Version 1.1 30 MAY 2008 Version History This and other Framework Extension tools are available on Framework Web site. Release

More information

Project QA and Collaboration Plan for <project name>

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

More information

Quality management systems Guidelines for configuration management

Quality management systems Guidelines for configuration management BRITISH STANDARD Quality management systems Guidelines for configuration management ICS 03.120.10 BS ISO 10007:2003 BS ISO 10007:2003 This British Standard was published under the authority of the Standards

More information

Implementation of ANSI/AAMI/IEC 62304 Medical Device Software Lifecycle Processes.

Implementation of ANSI/AAMI/IEC 62304 Medical Device Software Lifecycle Processes. Implementation of ANSI/AAMI/IEC 62304 Medical Device Software Lifecycle Processes.. www.pharmout.net Page 1 of 15 Version-02 1. Scope 1.1. Purpose This paper reviews the implementation of the ANSI/AAMI/IEC

More information

Preparation Guide. IT Service Management Foundation Bridge based on ISO/IEC 20000

Preparation Guide. IT Service Management Foundation Bridge based on ISO/IEC 20000 Preparation Guide IT Service Management Foundation Bridge based on ISO/IEC 20000 Edition April 2011 Copyright 2011 EXIN All rights reserved. No part of this publication may be published, reproduced, copied

More information

Effective Methods for Software and Systems Integration

Effective Methods for Software and Systems Integration Effective Methods for Software and Systems Integration Boyd L. Summers CRC Press Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487-2742 CRC Press is an imprint of Taylor

More information

PHASE 5: DESIGN PHASE

PHASE 5: DESIGN PHASE PHASE 5: DESIGN PHASE During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed

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

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

Notice of Clarification

Notice of Clarification U. S. ELECTION ASSISTANCE COMMISSION VOTING SYSTEM TESTING AND CERTIFICATION PROGRAM 1225 New York Avenue, NW, Suite 1100 Washington, DC. 20005 Notice of Clarification NOC 09-004: Development and Submission

More information

The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements.

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

More information

Life Cycle Support Information System. Training Guide

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

More information

Configuration Management in Software Development Life Cycle

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

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

Regulatory Guide 1.169 Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants

Regulatory Guide 1.169 Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants Regulatory Guide 1.169Configuration Managemen... Page 1 of 10 September 1997 Regulatory Guide 1.169 Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power

More information

REGULATORY GUIDE 1.170 (Draft was issued as DG-1207, dated August 2012)

REGULATORY GUIDE 1.170 (Draft was issued as DG-1207, dated August 2012) Purpose U.S. NUCLEAR REGULATORY COMMISSION July 2013 Revision 1 REGULATORY GUIDE OFFICE OF NUCLEAR REGULATORY RESEARCH REGULATORY GUIDE 1.170 (Draft was issued as DG-1207, dated August 2012) Technical

More information

General Principles of Software Validation; Final Guidance for Industry and FDA Staff

General Principles of Software Validation; Final Guidance for Industry and FDA Staff General Principles of Software Validation; Final Guidance for Industry and FDA Staff Document issued on: January 11, 2002 This document supersedes the draft document, "General Principles of Software Validation,

More information

U.S. Department of Energy

U.S. Department of Energy 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

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

Procedure for Assessment of System and Software

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

More information

CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN

CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN CENG492 SENIOR DESIGN PROJECT AND SEMINAR II SOFTWARE CONFIGURATION MANAGEMENT PLAN by Group LaPaix Subject on COMPUTERIZED READING SYSTEM FOR BLINDS DEPARTMENT OF COMPUTER ENGINEERING METU ANKARA 28.03.2003

More information

IRCA Briefing note ISO/IEC 20000-1: 2011

IRCA Briefing note ISO/IEC 20000-1: 2011 IRCA Briefing note ISO/IEC 20000-1: 2011 How to apply for and maintain Training Organization Approval and Training Course Certification IRCA 3000 Contents Introduction 3 Summary of the changes within ISO/IEC

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

IEEE ComputerSociety 1 Software and Systems Engineering Vocabulary

IEEE ComputerSociety 1 Software and Systems Engineering Vocabulary IEEE ComputerSociety 1 Software and Systems software. (1) computer programs, procedures and possibly associated documentation and data pertaining to the operation of a computer system (IEEE 828-2012 IEEE

More information

Standard Glossary of Terms Used in Software Testing. Version 3.01

Standard Glossary of Terms Used in Software Testing. Version 3.01 Standard Glossary of Terms Used in Software Testing Version 3.01 Terms Used in the Foundation Level Syllabus International Software Testing Qualifications Board Copyright International Software Testing

More information

Overview of the System Engineering Process. Prepared by

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.

More information

Project Knowledge Areas

Project Knowledge Areas From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.

More information

Software Engineering Compiled By: Roshani Ghimire Page 1

Software Engineering Compiled By: Roshani Ghimire Page 1 Unit 7: Metric for Process and Product 7.1 Software Measurement Measurement is the process by which numbers or symbols are assigned to the attributes of entities in the real world in such a way as to define

More information

A Return on Investment Model for Software Configuration Management

A Return on Investment Model for Software Configuration Management Master s Thesis A Return on Investment Model for Software Configuration Management Lorenzo Borraci Erasmus Department of Computer Science Lund Institute of Technology Lund University, 2005 ISSN 1650-2884

More information

HOW TO CREATE USEFUL SOFTWARE PROCESS DOCUMENTATION ABSTRACT

HOW TO CREATE USEFUL SOFTWARE PROCESS DOCUMENTATION ABSTRACT HOW TO CREATE USEFUL SOFTWARE PROCESS DOCUMENTATION Linda Westfall The Westfall Team lwestfall@westfallteam.com 3000 Custer Road, Suite 270, PMB 383 Plano, TX 75075 ABSTRACT Whether our organization is

More information

What Are Software Developers Facing?

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

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

INTERMEDIATE QUALIFICATION

INTERMEDIATE QUALIFICATION PROFESSIONAL QUALIFICATION SCHEME INTERMEDIATE QUALIFICATION SERVICE CAPABILITY RELEASE, CONTROL AND VALIDATION CERTIFICATE SYLLABUS Page 2 of 23 Contents RELEASE, CONTROL AND VALIDATION CERTIFICATE 4

More information

Tutorial: Towards better managed Grids. IT Service Management best practices based on ITIL

Tutorial: Towards better managed Grids. IT Service Management best practices based on ITIL Tutorial: Towards better managed Grids. IT Service Management best practices based on ITIL EGI Technical Forum 2011, Lyon (France) September 22, 2011 Dr. Thomas Schaaf www.gslm.eu EMERGENCE TECH LTD. The

More information

Commonwealth of Virginia

Commonwealth of Virginia Commonwealth of Virginia Information Technology Resource Management Standard for PROJECT MANAGER SELECTION and TRAINING Virginia Information Technologies Agency Preface Publication Designation Commonwealth

More information

Uncontrolled Document

Uncontrolled Document SOUTHWEST RESEARCH INSTITUTE QUALITY SYSTEM MANUAL July 2015 Revision 5 Quality System Manual Page iii TABLE OF CONTENTS 1.0 PURPOSE... 1 2.0 SCOPE... 1 3.0 TERMS AND DEFINITIONS... 2 4.0 QUALITY MANAGEMENT

More information

Enterprise Content Management and Alfresco

Enterprise Content Management and Alfresco ECM and Alfresco 1 Enterprise Content Management and Alfresco Compiled by Russ Danner Architect, Christian Science Publishing Society dannerr@csps.com Copyright 2006 Licensed under the Mozilla Public License

More information

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

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

More information

PHASE 9: OPERATIONS AND MAINTENANCE PHASE

PHASE 9: OPERATIONS AND MAINTENANCE PHASE PHASE 9: OPERATIONS AND MAINTENANCE PHASE During the Operations and Maintenance Phase, the information system s availability and performance in executing the work for which it was designed is maintained.

More information

Space project management

Space project management ECSS-M-ST-40C Rev. 1 Space project management Configuration and information management ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is

More information

Company Quality Manual Document No. QM Rev 0. 0 John Rickey Initial Release. Controlled Copy Stamp. authorized signature

Company Quality Manual Document No. QM Rev 0. 0 John Rickey Initial Release. Controlled Copy Stamp. authorized signature Far West Technology, Inc. ISO 9001 Quality Manual Document No.: QM Revision: 0 Issue Date: 27 August 1997 Approval Signatures President/CEO Executive Vice President Vice President/CFO Change Record Rev

More information

Standard Glossary of Terms Used in Software Testing. Version 3.01

Standard Glossary of Terms Used in Software Testing. Version 3.01 Standard Glossary of Terms Used in Software Testing Version 3.01 Terms Used in the Expert Level Test Automation - Engineer Syllabus International Software Testing Qualifications Board Copyright International

More information

CONSOLIDATED VERSION IEC 62304. Medical device software Software life cycle processes. colour inside. Edition 1.1 2015-06

CONSOLIDATED VERSION IEC 62304. Medical device software Software life cycle processes. colour inside. Edition 1.1 2015-06 IEC 62304 CONSOLIDATED VERSION Edition 1.1 2015-06 colour inside Medical device software life cycle processes INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 11.040 ISBN 978-2-8322-2765-7 Warning! Make sure

More information

EXIN IT Service Management Foundation based on ISO/IEC 20000

EXIN IT Service Management Foundation based on ISO/IEC 20000 Sample Exam EXIN IT Service Management Foundation Edition October 2013 Copyright 2013 EXIN All rights reserved. No part of this publication may be published, reproduced, copied or stored in a data processing

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

Hong Kong Information Security Group TRAINING AGENDA

Hong Kong Information Security Group TRAINING AGENDA TRAINING AGENDA THE ITIL FOUNDATION CERTIFICATE IN IT SEVICE MANAGEMENT The purpose of the ITIL Foundation certificate in IT Service Management is to certify that the candidate has gained knowledge of

More information

DATA ITEM DESCRIPTION

DATA ITEM DESCRIPTION DATA ITEM DESCRIPTION Form Approved OMB NO.0704-0188 Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions,

More information

5.1 Project Control Overview

5.1 Project Control Overview 5.1 Project Control Overview Project Control is a formal process in project management. In most respects, there is not a lot of room for creativity in the Control Phase of project management. The PMBOK

More information

Test Framework Introduction & Overview of the Test Framework

Test Framework Introduction & Overview of the Test Framework Test Framework Introduction & Overview of the Test Framework Author(s): imbus AG MoReq2 test development team Date: 18/04/2008 Version: 1.0 Status: Customer: Approved Serco Consulting imbus AG v1.0 April

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

U. S. Department of Energy. Document Online Coordination System (DOCS) Systems Configuration Management Plan (SCMP)

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

More information

ALS Configuration Management Plan

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

More information

Quality Management System General

Quality Management System General Audit Date: Quality Management System General Requirement: 4.1 and 4.2.2-QMS General Verify Scope Comments/Evidence/Findings: Verify the Exclusions is applicable and justified How are the processes in

More information

Fundamentals of Measurements

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

More information

ITIL Roles Descriptions

ITIL Roles Descriptions ITIL Roles s Role Process Liaison Incident Analyst Operations Assurance Analyst Infrastructure Solution Architect Problem Manager Problem Owner Change Manager Change Owner CAB Member Release Analyst Test

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

Standard Glossary of Terms Used in Software Testing. Version 3.01

Standard Glossary of Terms Used in Software Testing. Version 3.01 Standard Glossary of Terms Used in Software Testing Version 3.01 Terms Used in the Advanced Level - Test Manager Syllabus International Software Testing Qualifications Board Copyright International Software

More information

ISO/IEC Directives, Part 1 Consolidated ISO Supplement Procedures specific to ISO

ISO/IEC Directives, Part 1 Consolidated ISO Supplement Procedures specific to ISO ISO/IEC Directives, Part 1 Consolidated ISO Supplement Procedures specific to ISO Directives ISO/IEC, Partie 1 Supplément ISO consolidé Procédures spécifiques à l ISO Sixth edition, 2015 [Based on the

More information

TEMPLATE. U.S. Department of Energy. Project Name. Configuration Management Plan. September 2002 U. S. DEPARTMENT OF ENERGY

TEMPLATE. U.S. Department of Energy. Project Name. Configuration Management Plan. September 2002 U. S. DEPARTMENT OF ENERGY U.S. Department of Energy Project Name Configuration Management Plan September 2002 TEMPLATE U. S. DEPARTMENT OF ENERGY Organizational Title 1 Organizational Title 2 Change Control Page The following information

More information

Reviewers of proposed revision to ISO/IEC 19770 1:2006 SAM Processes. Call for feedback on draft of revised 19770 1 Tiered SAM Processes

Reviewers of proposed revision to ISO/IEC 19770 1:2006 SAM Processes. Call for feedback on draft of revised 19770 1 Tiered SAM Processes To: From: Reviewers of proposed revision to ISO/IEC 19770 1:2006 SAM ISO/IEC JTC1 SC7 WG21 Software Date: 30 November 2010 Re: Call for feedback on draft of revised 19770 1 ed SAM On 30 November 2010,

More information

Space product assurance

Space product assurance ECSS-Q-ST-80C Space product assurance Software product assurance ECSS Secretariat ESA-ESTEC Requirements & Standards Division Noordwijk, The Netherlands Foreword This Standard is one of the series of ECSS

More information

Requirements Analysis/Gathering. System Requirements Specification. Software/System Design. Design Specification. Coding. Source Code.

Requirements Analysis/Gathering. System Requirements Specification. Software/System Design. Design Specification. Coding. Source Code. Change Control and Configuration Management IVT 11 th Annual conference April 2010 DISCLAIMER Amgen is not responsible for the written or verbal bl content t of fthi this presentation tti Gisele Fahmi,

More information