Templates For Software Configuration Management Documents
TemplatesForSoftwareConfiguration ManagementDocumentsDeluxe Version 3.0ISBN Number: 0-9770309-2-xProduced by:Software Engineering Process Technology (SEPT)2725 NW Pine Cone DriveIssaquah, WA. 98027Tel: 425-391-2344E-mail: Stanmagee@smartwire.netWeb Pages: www.12207.com and www.15288.comAuthors: H. Ronald Berlack and John M. Neorr 2007 Software Engineering Process Technology (SEPT).1
TemplatesForSoftwareConfiguration ManagementDocumentsDeluxe Version 3.0ISBN Number: 0-9770309-2-xAbstractThis document contains a set of templates for software configuration management (CM)documents to aid engineers and managers to implement software configuration managementprocesses per the requirements specified in ISO/IEC standard 12207, Software Life CycleProcesses (1995), including Amendment 1:2002 and Amendment 2:2004; and standard 15288,System Life Cycle Processes (2002) as it pertains to software elements. For software CMprocesses and related activities and artifacts, these standards-driven templates provide genericdescriptions and instructions that, as needed, can be tailored to a specific organization’s orproject’s needs. Thirteen templates are provided. They are:Template #Template Name1Software Configuration Management Policy2Software Configuration Management Strategy3Software Configuration Management Organization Charts4Software Configuration Management Plan5Software Configuration Management Process6Software Configuration Identification Procedure7Software Configuration Change Control Procedure8Software Configuration Status Accounting Procedure9Software Configuration Item Check-in and Check-out Procedure10Software Configuration Audits and Reviews Procedure11ASubcontractor Software Configuration Control Procedure11BExternal Interface Configuration Control Procedure12Software Product Release and Delivery ProcedureIn addition to the templates shown above, this document provides five different aids to help tailorthe templates. 2007 Software Engineering Process Technology (SEPT).2
What’s New in Version 3.0Version 2.0 of this document, ably written by Ron Berlack, provided a set of softwareconfiguration management templates to enable software engineers and managers to implementsoftware configuration management processes per the requirements specified in ISO/IECstandard 12207, Software Life Cycle Processes. In Version 3.0, these templates have beenupdated to add the software CM requirements of ISO/IEC standard 15288, System Life CycleProcesses. In addition to revising existing templates, we added three new templates and includednew diagrams throughout the document. We also expanded and improved the document’s text tomake the document more readable and usable.Version 3.0, with its added templates, improved graphics, and expanded text should provebeneficial to you as you begin to implement and execute the very important process of softwareconfiguration management. An itemization of Version 3.0 enhancements appears below.Version 3.0 EnhancementDescriptionDocument updated to insure templates meetISO/IEC 15288 standard as it pertains tosoftware configuration management.Templates can now be used to meet therequirements of both ISO/IEC 12207 andISO/IEC 15288. Strategy documentspecifically added as part of this effort.Added template for software CM strategy.This template not only helps insure a betterCM plan, but also insures compliance with the15288 standard.Added template for a check-in/check-outprocedure.This procedure enables version management ofconfiguration items and uses a CM repositoryto store configuration management data.Added template for product release anddelivery.This template added to insure compliance withspecific requirements in the 12207 standard.Added an introduction to each template.Templates are preceded by introductory text tohelp readers understand the process beingsupported.Added standards cross-reference table.For each 12207 and 15288 CM process clause,this table shows what templates are needed tosatisfy that clause.Added several new diagrams.10 new diagrams have been included in thedocument. They explain the topic area to whicha template applies. These diagrams can be usedfor communicating CM concepts to affectedorganizations and individuals. 2007 Software Engineering Process Technology (SEPT).3
Software Configuration Management Templates - Table of ContentsTable of ContentsWhat’s New in Version 3.0 . 31. Introduction . 61.1About Software Configuration Management . 61.2How to Use This Document . 71.3The Software Domain . 91.4Traceability to 12207 and 15288 . 91.5Product Support . 121.6Warranties and Liability . 122. Software Configuration Management Templates . 132.1Software Configuration Management Policy. 152.2Software Configuration Management Strategy . 202.3Software Configuration Management Organization Charts . 282.4Software Configuration Management Plan . 322.5Software Configuration Management Process. 432.6Software Configuration Identification Procedure . 532.7Software Configuration Change Control Procedure . 592.8Software Configuration Status Accounting Procedure . 652.9Software Configuration Item Check-in and Check-out Procedure . 692.10Software Configuration Audits and Reviews Procedure . 742.11External Interfaces Procedures . 782.12Software Product Release and Delivery Procedure . 863. Software Configuration Management Aids . 913.1Aid 1: Acronyms . 923.2Aid 2: Standards. 973.3Aid 3: Software Change Request Data Elements . 973.4Aid 4: Software Status Accounting Data Elements . 983.5Aid 5: Software Documentation Approval Matrix . 994.About the Authors. 103 2007 Software Engineering Process Technology (SEPT).4
Software Configuration Management Templates – List of FiguresList of FiguresFigure 1: Software CM templates, and aids, and how they relate. . 8Figure 2: CM Policy provides high-level guidance and control. . 15Figure 3: CM Strategy is guided by policy and focuses plans and procedures. . 20Figure 4: Software CM organization within a typical large company. . 29Figure 5: CM organization within a small company. . 30Figure 6: Organization of a typical software CM group. . 30Figure 7: The configuration management process showing all its inputs and outputs. 44Figure 8: Controlled objects and their relationships and attributes. . 45Figure 9: Conceptual hierarchy of CM policies, plans, processes, and procedures. . 46Figure 10: Change control process flow. . 61Figure 11: Check-in/Check-out used by CM processes. . 69Figure 12: The check-in/check-out process. . 71Figure 13: Product release and delivery – the final step. . 86 2007 Software Engineering Process Technology (SEPT).5
Software Configuration Management Templates - Introduction1. IntroductionIn the past decade, the need for establishing effective software configuration managementpolicies and procedures has grown in conjunction with the need for systems that are complex,fast, accurate, secure, and safety-critical. From simple everyday systems that track bankaccounts to the complex systems in airplanes, cars, medical devices, and industrial, or militaryproducts; there is a demand for highly reliable, error-free software that either supports thedevelopment and maintenance of these systems or is an integral part of them.This document provides a set of templates for implementing a software configurationmanagement process the meets the requirements of ISO/IEC standard 12207, Software Life CycleProcesses and ISO/IEC standard 15288, System Life Cycle Processes. These templates are easyto use, self-explanatory, and do not require expensive training or extensive experience.To show how ISO/IEC 12207 and ISO/IEC 15288 standards are met, Section 1.6 provides amapping of standard requirements to the templates that address them.1.1About Software Configuration ManagementThe inclusion of software configuration management as a top-level process in the software lifecycle has proven to be a necessary and cost effective step in producing and delivering qualityproducts on time and within specified time and dollar limitations. Effective configurationmanagement of a system’s software elements is accomplished by:Establishing a policy that requires the implementation of software configurationmanagement.Defining a software configuration management strategy that drives subsequent plans andprocedures.Establishing a scheme for software item identification.Identifying the controlled items and item types that are designed, developed, anddelivered.Agreeing to a baseline configuration.Enabling the development of and changes to that agreed upon baseline.Recording the events of an item’s evolution through status accounting records.It is imperative for companies that build software to have a clear and concise policy on softwareconfiguration management as well as the procedures to implement it. A CM policy should beestablished by executive level management to provide top-level guidance and constraints tolower level plans and procedures. This guidance and constraint helps insure consistency acrosslower level procedures including compliance with key corporate objectives.Because software CM procedures may affect the utilization of resources across companyorganizations, these procedures should be reviewed and approved by an appropriate level ofmanagement in those organizations. These organizations can include Quality Management, 2007 Software Engineering Process Technology (SEPT).6
Software Configuration Management Templates - IntroductionEngineering, Testing, Project Management, and the customer (when applicable). Theresponsibility for defining and executing CM procedures must be clearly assigned down anorganization as well as across it.In large companies or organizations, different groups or projects may have their own unique CMrequirements and resultant policies and procedures. In such cases, each organization must insurethat their unique software CM plan, strategy, and procedures are aligned with higher-level CMdocuments.1.2How to Use This DocumentThis document is designed to aid a person, with some knowledge of software configurationmanagement, implement a sound software CM system. Expertise in software configurationmanagement is not required. This document provides templates and aids for software CM thatcan be applied to manual or automated methods and can be implemented by one or more personsdepending on the scope and complexity of the project or organization. These materials areapplicable to projects of all sizes, and are applicable for all types of products during their lifespan.Figure 1 shows the thirteen software CM templates and five CM aids contained in this documentand how they relate to one another. Note, for example, how higher level documents(organization, strategy, policy, plan) provide the overall guidance and direction for theestablishment of lower level procedures. 2007 Software Engineering Process Technology (SEPT).7
Software Configuration Management Templates - IntroductionImpacts#1SW Configuration MgtPolicyDictatesGuides/Controls#3SW Configuration MgtOrganizationChartsShapes#2SW Configuration MgtStrategyFocusesAppear in#1AcronymsTailors#4SW Configuration MgtPlanAppear inGuide/Control#2StandardsRequirements for#5SW Configuration MgtProcessConsists of#6SW ConfigurationIdentificationProcedureUses#7SW ConfigurationChange ControlProcedure#8SW ConfigurationStatus AccountingProcedureUses#10SW ConfigurationAudits and ReviewsProcedureUses#3SW Change RequestData Elements#4SW Status AccountingData Elements#11A and #11BSubcontractor andExternal InterfaceConfg. Control Procedures#12Product Releaseand DeliveryProcedureUses#5SW DocumentationApproval Matrix#9SW Configuration ItemCheck-in and Check-outProcedureLegend:TemplateAidFigure 1: Software CM templates, and aids, and how they relate.Software CM TemplatesEach subsection of Section 2 (2.1, 2.3, etc) is devoted to one of the thirteen templates shown inFigure 1. Preceding each template, which begins with a title page, is a brief overview of the areabeing addressed by that template. Guidance notations in the templates appear underlined andshould be stripped from the implemented template. Template pages can be distinguished fromother types of pages in this document by the occurrence of the word “Template” in their pageheader. Pages that are not part of a template do not have that word in their header.The template serves as a framework for meeting the unique CM requirements of yourorganization. Thus, you will have to add text that provides the necessary detail to carry out theactivities described in each template. Specific tools, data, and geographic distribution of workproducts and people will all affect the definition of an activity and will necessitate the tailoringof each template. The size and experience of your software staff will also affect the level ofdetail required. You may also have to modify text for specific domains and end-item types(embedded software, government software, classified software, etc). 2007 Software Engineering Process Technology (SEPT).8
Software Configuration Management Templates - IntroductionAlthough specific details to a template may be added to make its resulting procedure useful, donot be afraid to start with minimal text. The important thing is to document your procedures!Once they are documented, you can begin the more important task of executing them along withmeasuring, monitoring, and improving them throughout the system life cycle.Software CM AidsSection 3 of this document provides additional aids for software configuration management.These aids and their relationship to the templates are also shown in Figure 1. These aids providehelp concerning acronyms, standards, CM data records, and document approval. Documentationfound in Section 3 can be incorporated into your CM procedures or simply used as referencematerial.1.3The Software DomainNote again that all of the templates contained in this document are for software policies, plans,procedures, etc. At times, to streamline the text, the word software does not precede the words“configuration management” or the abbreviation “CM.” Nevertheless, it is to be assumed.1.4Traceability to 12207 and 15288The templates in this document satisfy the requirements of ISO/IEC 12207, Software Life CycleProcesses (1995), including Amendment 1:2002 and Amendment 2:2004. These templates alsosatisfy the requirements of ISO/IEC 15288, System Life Cycle Processes (2002) as thoserequirements pertain to software configuration management. To facilitate the use of crossreference tables where only clause numbers are used, each requirements clause number and itsassociated topic is listed in Table 1. Following that table, Table 2 cross-references ISO/IEC12207 and ISO/IEC 15288 clauses to the templates that address them.ISO/IEC 12207, released in 1995, was subsequently amended in 2002 and 2004 by Amendment1 and Amendment 2 respectively. Amendment 1 makes a minor modification to CM clause 6.2,but more importantly provides a process model that enables users to measure the capability,maturity, and conformance of their CM processes and procedures. The Amendment 1 processmodel defines the purpose of configuration management and its required outcome. Released aspart of Amendment 1, it was subsequently updated by Amendment 2 in 2004. Along with otherstandard requirements, CM process outcomes, as updated in Amendment 2, appear in Table 2and are cross-referenced to the templates needed to produce them.Neither ISO/IEC 12207 nor ISO/IEC 15288 specifically requires the development of a CMpolicy, but they refer to the use of a policy to tailor strategies and plans. This is consistent withthe hierarchy of policy, strategy, plan, and procedures shown in Figures 2 and 3 in Sections 2.2and 2.3 respectively. Accordingly, the CM policy template is shown as being required to meetselected standards.For each requirement, an “X” has been placed in the column under the template needed to satisfythat requirement. Because the standards are written at a high level and the procedures are interrelated, each requirement is addressed by multiple templates. Depending on how you adapt yourtemplates, you may need a different set of cross-referenced templates to meet a standard. 2007 Software Engineering Process Technology (SEPT).9
Software Configuration Management Templates - IntroductionTable 1: Standard RequirementsF.2.2 (Configuration Mgt. Process)ISO/IEC 12207ISO/IEC 12207, Amendment 25.4.7 (Configuration Mgt Process)ISO/IEC 152886.2 (Configuration Mgt.Process)StandardClause #Clause Topic6.2.1Process implementation6.2.2Configuration identification6.2.3Configuration control6.2.4Configuration status accounting6.2.5Configuration evaluation6.2.6Release management and deliveryF.2.2Purpose of the configuration management processF.2.2 (1)Outcome: CM StrategyF.2.2 (2)Outcome: Identified, defined, baselined work productsF.2.2 (3)Outcome: Controlled work products changes and releasesF.2.2 (4)Outcome: Modifications and releases available to affectedparties.F.2.2 (5)Outcome: Work product status recorded and reportedF.2.2 (6)Outcome: Work product completeness and consistencyensuredF.2.2 (7)Outcome: Work product storage, handling, deliverycontrolled.5.4.7.1Purpose of the configuration management process5.4.7.2Configuration management process outcomes5.4.
Processes and ISO/IEC standard 15288, System Life Cycle Processes. These templates are easy to use, self-explanatory, and do not require expensive training or extensive experience. To show how ISO/IEC 12207 and ISO/IEC 15288 standards are met, Section 1.6 provides a mapping of
Bruksanvisning för bilstereo . Bruksanvisning for bilstereo . Instrukcja obsługi samochodowego odtwarzacza stereo . Operating Instructions for Car Stereo . 610-104 . SV . Bruksanvisning i original
10 tips och tricks för att lyckas med ert sap-projekt 20 SAPSANYTT 2/2015 De flesta projektledare känner säkert till Cobb’s paradox. Martin Cobb verkade som CIO för sekretariatet för Treasury Board of Canada 1995 då han ställde frågan
service i Norge och Finland drivs inom ramen för ett enskilt företag (NRK. 1 och Yleisradio), fin ns det i Sverige tre: Ett för tv (Sveriges Television , SVT ), ett för radio (Sveriges Radio , SR ) och ett för utbildnings program (Sveriges Utbildningsradio, UR, vilket till följd av sin begränsade storlek inte återfinns bland de 25 största
Hotell För hotell anges de tre klasserna A/B, C och D. Det betyder att den "normala" standarden C är acceptabel men att motiven för en högre standard är starka. Ljudklass C motsvarar de tidigare normkraven för hotell, ljudklass A/B motsvarar kraven för moderna hotell med hög standard och ljudklass D kan användas vid
LÄS NOGGRANT FÖLJANDE VILLKOR FÖR APPLE DEVELOPER PROGRAM LICENCE . Apple Developer Program License Agreement Syfte Du vill använda Apple-mjukvara (enligt definitionen nedan) för att utveckla en eller flera Applikationer (enligt definitionen nedan) för Apple-märkta produkter. . Applikationer som utvecklas för iOS-produkter, Apple .
Cisco 3560 & 3750 NetFlow Configuration Guide Cisco Nexus 7000 NetFlow Configuration Cisco Nexus 1000v NetFlow Configuration Cisco ASR 9000 NetFlow Configuration Appendix. 3 Cisco NetFlow Configuration Cisco IOS NetFlow Configuration Guide Netflow Configuration In configuration mode issue the following to enable NetFlow Export:
Templates & Drilling 1-Cut out all templates, on the INSIDE of the lines shown, and trace or spray glue onto 1/8" hardboard for permanent templates. Cut out, sand the edges smooth, & label all pieces. Trace all templates onto the final stock of pine or ceda
EIOPA Explanatory notes on reporting templates Variation Analysis templates 1.1. EIOPA has received in the last months a number of Q&A addressing the reporting of Variation Analysis templates (S.29.01 to S.29.04). The Q&A received covered most of the templates and put into question how the templates are to be interpreted in many areas.
