Seminar Themes (1 Of 3) IEEE/EIA 12207:1995 Software Life .

IEEE/EIA 12207 - Software Life Cycle Processes12207 - Unit 2 - JWM - 980112207 - Unit 2 - JWM - 9801112207 - Unit 2 - JWM - 98012Unit 2Unit 2 - ISO/IEC 12207IEEE/EIA 12207:1995Software Life Cycle ProcessesNHistoryNNNPrepared by:James W. Moore, moorej@ieee.orgThe MITRE CorporationJanuary 1998NKey conceptsISO/IEC 12207 processes 1998, The MITRE Corporation. Permission is granted to reproduce without modification.12207 - Unit 2 - JWM - 9801 1998, The MITRE Corporation. Permission is granted to reproduce without modification.312207 - Unit 2 - JWM - 9801Purpose of 12207NNPrevious standards .NAcquire, supply, develop, operate, and maintainsoftwareNUndertakes broader scope than previous standardsNNManage, control, and improve the frameworkNNRecognizes that software is part of a system and thata project is part of an enterpriseTo establish a basis for world trade insoftwareN 1998, The MITRE Corporation. Permission is granted to reproduce without modification.512207 - Unit 2 - JWM - 9801NNHistoryKey conceptsISO/IEC 12207 processesNNNN 1998, The MITRE Corporation. Permission is granted to reproduce without modification. 1998, The MITRE Corporation. Permission is granted toreproduce without modification.6Key concept of ISO/IEC 12207:Process/activity/task hierarchyUnit 2 - ISO/IEC 12207N focused on the single contract or project inisolation described a single monolithic process failed to encourage investment in thediscipline and capitalization of processes induced 20-50% added costs indocumentation and formal reviewsAdapted from a slide by Perry DeWeese 1998, The MITRE Corporation. Permission is granted to reproduce without modification.12207 - Unit 2 - JWM - 98014Motivations for 12207To establish a common framework for thelife cycle of softwareNPurpose of 12207History of 12207Processes are subdivided into cohesiveactivitiesActivities are subdivided into tasksYou may think of tasks as being thespecifications for the execution of an activityA task may be a self-declaration of intent, arequirement, a recommendation, or apermissible action 1998, The MITRE Corporation. Permission is granted to reproduce without modification.1

IEEE/EIA 12207 - Software Life Cycle Processes12207 - Unit 2 - JWM - 980112207 - Unit 2 - JWM - 9801712207 - Unit 2 - JWM - 9801Key concept of ISO/IEC 12207:Processes and partiesNIdentification of processes is based on twoprinciples:NNNKey concept of ISO/IEC 12207:Continuing responsibilitiesNModularity: Processes should be cohesive andshould have low coupling to otherResponsibility: Each process should beexecutable by a single partyA particular organization may become the partyresponsible for executing a processNN 1998, The MITRE Corporation. Permission is granted to reproduce without modification.912207 - Unit 2 - JWM - 9801Key concept of ISO/IEC 12207:Categories of processesPrimaryNNNNNNNNProcesses used as “subroutines” by other processesOrganizationalNProcesses inherent to the organization and“instantiated” by the project12207 - Unit 2 - JWM - 9801 1998, The MITRE Corporation. Permission is granted to reproduce without modification.1112207 - Unit 2 - JWM - 9801Key concept of ISO/IEC 12207:Temporal issuesNNEvaluation is not a distinct process or activityEvaluation is treated as an internal, integral taskof many activities in the standardIn general, the evaluations have stated purposesand stated criteriaOther processes may supplement internalevaluations: Verification, Validation, JointReview, Audit, Quality Assurance, ImprovementAlso, a special tailoring process 1998, The MITRE Corporation. Permission is granted to reproduce without modification.N10Key concept of ISO/IEC 12207:Integral evaluationNAcquisition, SupplyDevelopment, Operation, MaintenanceSupportingNThe activities and tasks of a 12207 process arenot steps to be performed12207 does not require that the activities andtasks are to be performed in any particularorderThe activities and tasks of 12207 arecontinuing responsibilities whose execution isassigned for the duration of the process 1998, The MITRE Corporation. Permission is granted to reproduce without modification.12207 - Unit 2 - JWM - 9801N8The standard does not specify a life cyclemodel, e.g. waterfall, spiral, etc.The standard does not place orderingdependencies or time dependencies on thetasks that is the job of the chosen lifecycle model and the project planTasks may be iterated, repeated, recursivelyinvoked, etc 1998, The MITRE Corporation. Permission is granted to reproduce without modification. 1998, The MITRE Corporation. Permission is granted toreproduce without modification.12Key concept of ISO/IEC 12207:Approach to documentationNNNThe standard requires some outputs to bedocumentedThe standard does not prescribe format,media, or content of the documentationThe Documentation Process permits theuser to make these decisions 1998, The MITRE Corporation. Permission is granted to reproduce without modification.2

IEEE/EIA 12207 - Software Life Cycle Processes12207 - Unit 2 - JWM - 980112207 - Unit 2 - JWM - 98011312207 - Unit 2 - JWM - 9801Key concept of ISO/IEC 12207:Approach to baseliningNNStandard differentiates between items andconfiguration items (CI). The ConfigurationManagement (CM) process can handle both,but the latter are handled more rigorouslyA baseline is a formally approved versionof a CI. Baselines (as clarified by theIEEE/EIA version) are established by theprimary processes, not by the CM processUnit 2 - ISO/IEC 12207NNNHistoryKey conceptsISO/IEC 12207 processes 1998, The MITRE Corporation. Permission is granted to reproduce without modification.12207 - Unit 2 - JWM - 9801 1998, The MITRE Corporation. Permission is granted to reproduce without modification.1512207 - Unit 2 - JWM - 9801NN16ISO/IEC 12207 processes:Primary processesISO/IEC 12207 y processes are executed by partieswho initiate or perform major roles in thesoftware life cycle:NNAcquisitionSupplyNNN 1998, The MITRE Corporation. Permission is granted to reproduce without modification.12207 - Unit 2 - JWM - 9801 1998, The MITRE Corporation. Permission is granted to reproduce without modification.1712207 - Unit 2 - JWM - 9801ISO/IEC 12207 processes:Supporting processesNA supporting process supports another process asan integral part with a distinct purpose:NDocumentationNValidationNConfiguration ManagementNJoint ReviewNQuality AssuranceNAuditNVerificationNProblem ResolutionBut fundamental responsibility remains integral tothe primary processNOrganizational processes inherently existoutside the scope of the project butinstances of them are employed by theproject:NNN 1998, The MITRE Corporation. Permission is granted to reproduce without modification. 1998, The MITRE Corporation. Permission is granted toreproduce without modification.18ISO/IEC 12207 processes:Organizational ntInfrastructureImprovementTraining 1998, The MITRE Corporation. Permission is granted to reproduce without modification.3

Process HarmonizationGlobal Harmonization ofSystems and SoftwareEngineering ProcessesJames W. Moore, F-IEEE, CSDPMay 2008ISO/IEC JTC 1/SC 7 (software and systems engineering) has alarge collection of standards.nIEEE Software and Systems Engineering Standards Committeehas a large collection of standards.– Some of the key process standards are difficult to use together.– Some of the key process standards were adopted (and slightlymodified) from SC 7.The authors’ affiliation with TheMITRE Corporation is providedfor identification purposes only,and is not intended to convey orimply MITRE’s concurrence with,or support for, the positions,opinions, or viewpointsexpressed by the authors.The MITRE CorporationnnThe goal of process harmonization is to:– Create a single definitive set of processes .– . described in a set of standards that are easy to use together .– . agreed and shared by both organizations.n 20082007 The MITRE Corporation.All rights reservedThis presentation describes progress toward that goal.Names are ImportantMany Standards are NamesWe use names to localize the subject under discussion. Butsometimes confusion results because we use different name spaces.445 Hoes Lane,Piscataway, NJDriver’s viewZip 08855- 1331Postal worker’s viewTract 15, Lot 25,Liber 227, Plat 22Town clerk’s viewThe portion of the 1677 royalgrant of Charles II to Robert C.Smith, bounded by .Title researcher’s viewWould youknow thatthese aredifferentnames forthe samething?Would youknowwithout themap? 2007 The MITRE Corporation.All rights reservedIn a complex,multidimensionaltrade space ofsolutions .Two technically excellent standards are at the center of process harmonization:It defines somecharacteristics that abuyer can count on.Jim Moore, 2004-03 CSEE&T Panel7 Insurer andinsured2008 SSTC –James W. Moore - 4nISO/IEC 15288:2002 gave names to 25 processes in the life cycle of asystem. It is more descriptive than 12207.nISO/IEC 12207:1995 gave names to 17 processes in the life cycle of asoftware product or service. It is more prescriptive than 15288.nThe names are important so that acquirers and suppliers cancommunicate regarding their practices.– (Two amendments re-described the processes for assessment purposes.)– Furthermore, a set of amendments to 12207 (for the process assessment community)compounded the difficulty.– “Oh, when you say ‘implementation’, you include ‘testing’? No, no, no, that’s aseparate thing; our contract doesn’t include that!”A two-step project is underway to “harmonize” the two standards.– The first step – aligning the processes – was completed early in 2008.nThe names are important as a basis for process evaluation andimprovement.nThe names are important to provide a context for implementing improvedpractices. – Our goal.– The second step – integration – will seek a single set of shared software/systemprocesses.In addition, a companion project, 24748, is underway. It will provide a guide to lifecycle management using the two standards. 2007 The MITRE Corporation.All rights reserved Governmentand industry 2007 The MITRE Corporation.All rights reservedA large international user base wants standards that can be used together fordevelopment of systems with software content– However, the standards were difficult to use together.n This enablescommunicationbetween15288 and 12207 Give “Names” to Processes– ISO/IEC 12207:1995, Software life cycle processes, and the substantially identicalIEEE/EIA 12207.0:1997n a standard gives a nameto a bounded region. Buyer andseller– ISO/IEC/IEEE 15288:2002, System life cycle processesn Many softwareengineeringstandards assignnames topractices orcollections ofpractices.A standard is a Name for anotherwise fuzzy concept2008 SSTC –James W. Moore - 3Harmonization of 15288 and 12207n2008 SSTC –James W. Moore - 2 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 5 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 6

The Harmonization ProblemOverview of approach for HarmonizationSource: ISO/IEC JTC1/SC7 WG7 briefing materialStarting from a diverse set ofstandards with develop a revised set ofstandards with – different terms– a single vocabulary– different process sets– a single process set– different process architectures– a single, uniform architecture– different levels of prescription,and– a shared level of prescription,and– different audiences*– suitability across theaudiencesAgreed andtechnically correctISO/IEC 12207 andguide - can be usedwith confidenceSmallnormativechanges all without needlessly disrupting current organizationalinvestment based on usage of the current set of standards.* Systems versus software and process definition versus process assessment2008 SSTC –James W. Moore - 7 2007 The MITRE Corporation.All rights reserved– A single process set– Different processarchitectures– A single, uniformarchitecture– Different levels ofprescription– A shared level ofprescription– Different audiences– Suitable across theaudiencesMay 2005March 2008 tcomesActivitiesComponentProcessesDifferentname, butthe samelevel ofdetail. tivitiesSamename, butdifferentlevel ofdetail.NotesActivitiesTasksNonNormativeExemplar ListsNotesDifferentform2008 SSTC –James W. Moore - 9Key Terminology and ConceptsnIt is not required to use allarchitecture constructs inany particular document or forany particular process.12207:1995* System versus software and process definition versus process assessment 2007 The MITRE Corporation.All rights reservedFuture2008 SSTC –James W. Moore - 8Tasks all without needlessly disrupting current organizationalinvestment based on usage of the current set of standards.Guides and specificlife cyclemanagementprocess standardsNormative– Different process setsISO/IEC15288:2008 using acommonnomenclature andstructure withISO/IEC 12207PreambleIncreasing Level of Detail– A single vocabularyAgreed andtechnically correctISO/IEC 15288 andguide - can be usedwith confidenceArchitectural Constructs develop a revised setof standards with – Different termsLargernormativechanges 2007 The MITRE Corporation.All rights reservedThe Harmonization Problem – Problems addressed inthe Alignment PhaseStarting with a diverse set ofstandards with ISO/IEC XYZGeneral life cycleprocess setfor systems andsoftwareISO/IEC 12207:2008aligned and using acommonnomenclature andstructure withISO/IEC 152882008 SSTC –James W. Moore - 10 2007 The MITRE Corporation.All rights reservedKey Terminology and Concepts– A part of an organization is an organization if it meets the definition.ProjOrgOrgParty: an organization entering into an agreementnProject: an endeavour with defined start and finish datesundertaken to create a product or service in accordance withspecified resources and requirements [adapted from ISO 9000]ProjProjOrgOrganizations conduct projects todo things, notably to deal withsystems.– An individual can be an organization if s/he meets the definition.nOrganizationOrgOrganization: a person or a group of people and facilities with anarrangement of responsibilities, authorities and relationships[ISO 9000]Anindividualcan be anorganizationOrganizations make agreements toacquire and supply products andservices.OrgOrgAgreeing organizations are called parties. 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 11 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 12

Key Terminology and ConceptsKey Terminology and ConceptsActInputsActA system is composed of system elements. Eachelement is implemented and then integrated into thesystem. One invocation of 15288 suffices to create asystem composed of a set of tSysElem SysElemSysnProcess: set of interrelated or interacting activities which transformsinputs into outputs [ISO 9000]nProduct: the result of a process [ISO 9000]nService: performance of activities, work, or duties associated with aproduct2008 SSTC –James W. Moore - 13 2007 The MITRE Corporation.All rights reservedKey Terminology and Concepts SysElemIt is fundamentalto 12207 thatsoftware existsonly in the contextof a system. SWItemSWUnit Intended Relationships of Key System and SoftwareEngineering Life Cycle Process Standards(Andassociatedguide, d15939:MeasurementRevised 15288:Life cycleprocesses forsystems(Andassociatedguide, 19760) SysElem2008 SSTC –James W. Moore - 14Otherstandardsprovidingdetails ofselectedsystemprocessesEvery system has a life cycle which is viewed as composed of stages.(The standards do not require a particular set of stages.)nStages are initiated and terminated by decision gates.nStages may overlap and may be concurrent.nThe purpose of each stage is accomplished by executing processes.nAny process may be useful in any stage.ConceptThis is important.UtilizationDevelopment ProductionSupportRetire-mentnIt is a common error to talk about life cycle stages when one reallymeans processes or vice-versa.nLocating practices with respect to processes provides much greaterprecision. 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 16Related ProjectsPlanned 24748: Guide to Life Cycle ManagementRevised15289:DocumentationSysElemnA typicalset of lifecyclestages2008 SSTC –James W. Moore - 15Revised 12207:Life cycleprocesses forSWSys– Each stage has a purpose and makes a contribution to the life cycle.SWUnit 2007 The MITRE Corporation.All rights reservedOtherstandardsprovidingdetails ofselected SWprocesses Key Terminology12207 uses a hierarchyof items – composed ofcomponents –composed of units.12207 is not invokedrecursively to create thishierarchy.SWSW CompCompSysElem 2007 The MITRE Corporation.All rights reservedSometimes a system element is to beimplemented in software. The 12207standard accepts this as one or moresoftware items.SysSysElemHowever, 15288 states that a systemelement can itself be regarded as asystem. So, 15288 can be invokedrecursively to create a hierarchy ofsystems and their elements.A hierarchy of systems often impliesa hierarchy of projects.Revised 15026:Additionalpractices forhigherassurancesystems 16085:RiskMgmt.n24774 summarizes the agreed conventions for describingprocesses.n15289 summarizes the data products produced by the processesof 15288 and 12207. It exists, but must be revised to deal with the2007 revisions.nThree standards provide additional details on selected life cycleprocesses: 15939, Measurement; 16085, Risk management;16326, Project management.n15026 provides additional practices for the assurance of systemsand software when particular critical properties are required.n24765 is a database of vocabulary that will occasionally bepublished as a conventional printed standard:– Database is publicly available at: http://www.computer.org/sevocabCommon vocabulary. Common process description conventions 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 17 2007 The MITRE Corporation.All rights reserved2008 SSTC –James W. Moore - 18

Example Process: 12207 Stakeholder RequirementsDefinition Process (1 of 2)6.4.1 Stakeholder Requirements Definition ProcessExample Process: 12207 Stakeholder RequirementsDefinition Process (2 of 2)6.4.1.3 Activities and tasksNOTE The Stakeholder Requirements Definition Process in this International Standardis a specialization of the Stakeholder Requirements Definition Process of ISO/IEC15288. Users may consider claiming conformance to the 15288 process rather thanthe process in this standard.The project shall implement the following activities and tasks in accordancewith applicable organization policies and procedures with respect toStakeholder Requirements Definition Process6.4.1.3.1 Stakeholder identification. This activity consists of the following task:6.4.1.1 PurposeThe purpose of the Stakeholder Requirements Definition Process is to definethe requirements for a system that can provide the services needed by usersand other stakeholders in a defined environment. 6.4.1.2 OutcomesAs a result of successful implementation of the Stakeholder RequirementsDefinition Process:6.4.1.3.1.1 The project shall identify the individual stakeholders or stakeholderclasses who have

IEEE/EIA 12207 is a strategic, integrating standard for the IEEE software engineering collection. It provides a unifying approach to life cycle process standardization. It provides a unifying approach to life cycle data standardization. IEEE is now improving the fit. IEEE plans to build upon the standard with future strategic efforts.