Systems and software engineering — Content of life-cycle

Systems and software engineering — Content of life-cycle information items (documentation)Ingénierie des systèmes et du logiciel — Contenu des articles d’information du cycle de vie (documentation)

INTERNATIONAL STANDARD

ISO/IEC/IEEE

15289

Reference numberISO/IEC/IEEE 15289:2017(E)

Third edition2017-06

© ISO/IEC 2017© IEEE 2017

iTeh STANDARD PREVIEW(standards.iteh.ai)

ISO/IEC/IEEE 15289:2017https://standards.iteh.ai/catalog/standards/sist/8786f085-ccf1-411a-a8b7-

126c0ad72200/iso-iec-ieee-15289-2017

ii © ISO/IEC/IEEE 2017 – All rights reserved

ISO/IEC/IEEE 15289:2017(E)

COPYRIGHT PROTECTED DOCUMENT

© ISO/IEC 2017, Published in Switzerland© IEEE 2017All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at the address below or ISO’s member body in the country of the requester.

ISO copyright office Institute of Electrical and Electronics Engineers, IncCh. de Blandonnet 8 • CP 401 3 Park Avenue, New YorkCH-1214 Vernier, Geneva, Switzerland NY 10016-5997, USATel. +41 22 749 01 11 Fax +41 22 749 09 47 [email protected] [email protected] www.ieee.org



126c0ad72200/iso-iec-ieee-15289-2017


iii©ISO/IEC2017–Allrightsreserved

©IEEE2017–Allrightsreserved

Contents Page

Foreword ......................................................................................................................................................................................... vi

Introduction ................................................................................................................................................................................. vii

1 Scope .................................................................................................................................................................................. 1

2 Normative references ................................................................................................................................................... 3

3 Terms, definitions, and abbreviated terms ........................................................................................................... 33.1 Terms and definitions .................................................................................................................................................. 33.2 Abbreviated terms ......................................................................................................................................................... 6

4 Applicability .................................................................................................................................................................... 64.1 Purpose ............................................................................................................................................................................. 64.2 Intended users of this document ............................................................................................................................... 64.3 Applicability to work efforts ....................................................................................................................................... 74.4 Applicability to information item audiences ......................................................................................................... 7

5 Conformance ................................................................................................................................................................... 75.1 Definition of conformance ........................................................................................................................................... 75.2 Conformance situations ............................................................................................................................................... 85.3 Type of conformance ..................................................................................................................................................... 9

6 Life-cycle data and information items ..................................................................................................................... 96.1 Life-cycle data characteristics .................................................................................................................................... 96.2 Records compared to information items (documents) ...................................................................................... 96.3 Management of life-cycle data (records) ............................................................................................................. 106.4 Management of information items (documents) ............................................................................................... 106.4.1 Developing the documentation plan .................................................................................................................... 106.4.2 Managing and controlling information items .................................................................................................... 11

7 Generic types of information items ....................................................................................................................... 117.1 General ........................................................................................................................................................................... 117.2 Description – generic content .................................................................................................................................. 117.3 Plan – generic content ................................................................................................................................................ 127.4 Policy – generic content ............................................................................................................................................. 147.5 Procedure – generic content .................................................................................................................................... 157.6 Report – generic content ........................................................................................................................................... 167.7 Request – generic content ......................................................................................................................................... 187.8 Specification – generic content ............................................................................................................................... 18

8 Mapping of information items to the life cycle and service management processes ............................. 198.1 Mapping of information items to the system life cycle .................................................................................... 208.2 Mapping of information items to the software life cycle ................................................................................. 258.3 Mapping of information items to the service management processes ....................................................... 32

9 Records ........................................................................................................................................................................... 379.1 Record – generic content ........................................................................................................................................... 379.2 Specific record contents ............................................................................................................................................ 38

10 Specific information item (document) contents ................................................................................................ 4110.1 General ........................................................................................................................................................................... 4110.2 Acceptance plan ........................................................................................................................................................... 4110.3 Acceptance report ....................................................................................................................................................... 4110.4 Acquisition plan ........................................................................................................................................................... 4210.5 Asset management plan ............................................................................................................................................ 4210.6 Audit acknowledgement report .............................................................................................................................. 4210.7 Audit plan ...................................................................................................................................................................... 43



126c0ad72200/iso-iec-ieee-15289-2017


iv©ISO/IEC2017–Allrightsreserved


10.8 Audit procedure ........................................................................................................................................................... 4310.9 Audit report ................................................................................................................................................................... 4310.10 Capacity plan ................................................................................................................................................................. 4310.11 Capacity management procedure ........................................................................................................................... 4410.12 Change request ............................................................................................................................................................. 4410.13 Communication procedure ....................................................................................................................................... 4410.14 Complaint procedure ................................................................................................................................................. 4410.15 Concept of operations ................................................................................................................................................ 4510.16 Configuration management plan and policy ....................................................................................................... 4510.17 Configuration management procedure ................................................................................................................ 4610.18 Configuration status report ...................................................................................................................................... 4710.19 Contract .......................................................................................................................................................................... 4710.20 Customer satisfaction survey ................................................................................................................................... 4810.21 Database design description .................................................................................................................................... 4810.22 Development plan ....................................................................................................................................................... 4910.23 Disposal plan ................................................................................................................................................................. 4910.24 Documentation plan ................................................................................................................................................... 5010.25 Documentation procedure ....................................................................................................................................... 5010.26 Domain engineering plan .......................................................................................................................................... 5010.27 Evaluation report ........................................................................................................................................................ 5010.28 Implementation procedure ...................................................................................................................................... 5110.29 Improvement plan....................................................................................................................................................... 5110.30 Improvement procedure ........................................................................................................................................... 5110.31 Incident management procedure ........................................................................................................................... 5210.32 Incident report ............................................................................................................................................................. 5210.33 Information management plan ............................................................................................................................... 5310.34 Information management procedure .................................................................................................................... 5310.35 Information security plan ......................................................................................................................................... 5310.36 Information security policy ...................................................................................................................................... 5410.37 Information security procedure ............................................................................................................................. 5410.38 Installation plan ........................................................................................................................................................... 5510.39 Installation report ....................................................................................................................................................... 5510.40 Integration and test report ....................................................................................................................................... 5510.41 Integration plan ........................................................................................................................................................... 5510.42 Interface description .................................................................................................................................................. 5610.43 Life-cycle policy and procedure .............................................................................................................................. 5610.44 Maintenance plan ........................................................................................................................................................ 5610.45 Maintenance procedure ............................................................................................................................................ 5710.46 Measurement plan ...................................................................................................................................................... 5710.47 Measurement procedure ........................................................................................................................................... 5710.48 Monitoring and control report ................................................................................................................................ 5710.49 Operational test procedure ...................................................................................................................................... 5810.50 Problem management procedure .......................................................................................................................... 5810.51 Problem report ............................................................................................................................................................ 5810.52 Process assessment procedure ............................................................................................................................... 5910.53 Process improvement report ................................................................................................................................... 5910.54 Product need assessment .......................................................................................................................................... 5910.55 Progress report ............................................................................................................................................................ 6010.56 Project management plan ......................................................................................................................................... 6010.57 Proposal ......................................................................................................................................................................... 6110.58 Qualification test procedure .................................................................................................................................... 6110.59 Qualification test report ............................................................................................................................................ 6210.60 Quality management plan ......................................................................................................................................... 6210.61 Quality management policy and procedure ........................................................................................................ 6210.62 Release plan (and policy) ......................................................................................................................................... 6310.63 Request for proposal (RFP) ...................................................................................................................................... 6410.64 Resource request ......................................................................................................................................................... 6410.65 Reuse plan ..................................................................................................................................................................... 6410.66 Review minutes ............................................................................................................................................................ 6510.67 Risk action request ..................................................................................................................................................... 65



126c0ad72200/iso-iec-ieee-15289-2017


v©ISO/IEC2017–Allrightsreserved


10.68 Risk management policy and plan ......................................................................................................................... 6510.69 Service catalog .............................................................................................................................................................. 6510.70 Service continuity and availability plan ............................................................................................................... 6510.71 Service level agreement (SLA) ................................................................................................................................. 6610.72 Service management plan (and policy) ................................................................................................................ 6710.73 Service plan ................................................................................................................................................................... 6710.74 Service report ............................................................................................................................................................... 6810.75 Software architecture description ......................................................................................................................... 6810.76 Software design description .................................................................................................................................... 6910.77 Software requirements specification .................................................................................................................... 7010.78 Software unit description ......................................................................................................................................... 7110.79 Software unit test procedure ................................................................................................................................... 7110.80 Software unit test report ........................................................................................................................................... 7110.81 Supplier management procedure .......................................................................................................................... 7110.82 Supplier selection procedure .................................................................................................................................. 7210.83 System architecture description ............................................................................................................................. 7210.84 System element description ..................................................................................................................................... 7310.85 System requirements specification ....................................................................................................................... 7310.86 Training documentation ........................................................................................................................................... 7410.87 Training plan ................................................................................................................................................................ 7410.88 User documentation ................................................................................................................................................... 7410.89 User notification .......................................................................................................................................................... 7510.90 Validation plan ............................................................................................................................................................. 7510.91 Validation procedure (validation test specification) ...................................................................................... 7510.92 Validation report ......................................................................................................................................................... 7510.93 Verification plan .......................................................................................................................................................... 7510.94 Verification procedure .............................................................................................................................................. 7710.95 Verification report ...................................................................................................................................................... 77

Annex A(informative) Procedure for identifying information items and their contents .................................. 78

Annex B(informative) Information items and records by source .............................................................................. 80Bibliography ................................................................................................................................................................................ 84List of Tables Table 1 — Mapping of ISO/IEC/IEEE 15288:2015, clauses to information items for each system life-

cycle process ................................................................................................................................................................. 21Table 2 — Mapping of ISO/IEC 12207:2008 (IEEE Std 12207-2008) clauses to information items

for each software life-cycle process ..................................................................................................................... 26Table 3 — Mapping of ISO/IEC 20000-1:2011 (IEEE Std 20000-1:2013) and ISO/IEC 20000-2:2012

(IEEE Std 20000-2:2013) clauses to information items for each service management process ....... 33Table 4 — Record references and contents ....................................................................................................................... 38Table B.1 — Information items by source .......................................................................................................................... 80Table B.2 — Records by source .............................................................................................................................................. 83



126c0ad72200/iso-iec-ieee-15289-2017

vi©ISO/IEC2017–Allrightsreserved



Foreword

ISO(the InternationalOrganization forStandardization)and IEC(the InternationalElectrotechnicalCommission)form the specialized system for worldwide standardization. National bodies that are members of ISO or IECparticipate in the development of International Standards through technical committees established by therespective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborateinfieldsofmutualinterest.Otherinternationalorganizations,governmentalandnon‐governmental,inliaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have establishedajointtechnicalcommittee,ISO/IECJTC1.

IEEEStandardsdocumentsaredevelopedwithintheIEEESocietiesandtheStandardsCoordinatingCommitteesoftheIEEEStandardsAssociation(IEEE‐SA)StandardsBoard.TheIEEEdevelopsitsstandardsthroughaconsensusdevelopment process, approved by the AmericanNational Standards Institute,which brings together volunteersrepresentingvariedviewpointsandintereststoachievethefinalproduct.VolunteersarenotnecessarilymembersoftheInstituteandservewithoutcompensation.WhiletheIEEEadministerstheprocessandestablishesrulestopromotefairnessintheconsensusdevelopmentprocess,theIEEEdoesnotindependentlyevaluate,test,orverifytheaccuracyofanyoftheinformationcontainedinitsstandards.

InternationalStandardsaredraftedinaccordancewiththerulesgivenintheISO/IECDirectives,Part2.

Attention iscalled to thepossibility that implementationof this documentmayrequire theuseof subject matter covered by patent rights. By publication of this document, no position is takenwith respect to the existence orvalidityofanypatentrightsinconnectiontherewith.ISO/IECandIEEEarenotresponsibleforidentifyingessentialpatentsorpatentclaimsforwhichalicensemayberequired,forconductinginquiriesintothelegalvalidityorscopeofpatentsorpatentclaimsordeterminingwhetheranylicensingtermsorconditionsprovidedinconnectionwithsubmissionofaLetterofAssuranceoraPatentStatementandLicensingDeclarationForm,ifany,orinanylicensingagreementsarereasonableornon‐discriminatory.Usersofthisdocumentareexpresslyadvisedthatdeterminationofthevalidityofanypatentrights,andtheriskofinfringementofsuchrights,isentirelytheirownresponsibility.FurtherinformationmaybeobtainedfromISOortheIEEEStandardsAssociation.

This documentwaspreparedbyJointTechnicalCommitteeISO/IECJTC1,Information technology,SubcommitteeSC 7, Systems and software engineering, in cooperation with the Software & Systems Engineering StandardsCommittee of the IEEE Computer Society, under the Partner Standards Development Organization cooperationagreementbetweenISOandIEEE.

This third edition cancels and replaces the second edition (ISO/IEC/IEEE 15289:2015), of which it constitutesaminorrevision.ThisthirdeditionreflectsISO/IEC/IEEE15288:2015,Systems and software engineering—System life cycle processes,whichreplacedISO/IEC15288:2008(IEEEStd15288:2008).



126c0ad72200/iso-iec-ieee-15289-2017


vii©ISO/IEC2017–Allrightsreserved


Introduction

The purpose of this document is to provide requirements for identifying and planning the specific informationitems (information products) to be developed and revised during systems and software life cycles and serviceprocesses. This document specifies the purpose and content of all identified systems and software life‐cycleinformation items, as well as information items for information technology service management. Theinformation item contents are defined according to generic document types and the specific purpose of thedocument.Information itemsarecombined orsubdividedasneededforproject or organizationalpurposes.

This document is based on the life‐cycle processes specified in ISO/IEC 12207:2008 (IEEE Std 12207‐2008),Systems and software engineering — Software life cycle processes; ISO/IEC/IEEE15288:2015,Systems and software engineering — System life cycle processes; and the service management processes specified in ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013), Information technology — Service management — Part 1: Service Management System Requirements; and ISO/IEC 20000‐2:2012 (IEEE Std 20000‐2:2013), Information technology — Service management — Part 2: Guidance on the application of service management systems.

ISO/IEC 12207:2008 (IEEE Std 12207‐2008) and ISO/IEC/IEEE 15288:2015 define a set of processes formanaging and performing the stages of a system life cycle. They define an Information Managementprocess, but they do “not detail information items in terms of name, format, explicit content, and recordingmedia”. ISO/IEC/IEEE 15288:2015, and ISO/IEC 12207:2008 (IEEE Std 12207‐2008) establish a commonframeworkforsystemsandsoftwarelife‐cycleprocessesandidentifyorrequireanumberofdocumentationitems.Their process reference model does not represent a particular process implementation approach, nor does itprescribeasystem/software life‐cyclemodel,methodology,ortechnique. ISO/IEC12207:2008(IEEEStd12207‐2008) does not always specify when software information items are to be prepared, nor does it identifyinformation item contents. ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013) establishes comprehensiverequirements for documents and records, with some specific requirements. ISO/IEC 20000‐2:2012 (IEEE Std20000‐2:2013), Information technology—Servicemanagement—Part2: GuidanceontheapplicationofservicemanagementsystemsprovidesguidanceontheuseofPart1.

IEEE contributed IEEE 12207.1‐1997, Industry Implementation of International Standard ISO/IEC 12207:1995. (ISO/IEC 12207) Standard for Information Technology — Software life cycle processes — Life cycle data, asa sourceforthefirsteditionofthisdocument.



126c0ad72200/iso-iec-ieee-15289-2017



126c0ad72200/iso-iec-ieee-15289-2017

1

©ISO/IEC2017–Allrightsreserved


Systems and software engineering — Content of life-cycle information items (documentation)

1 Scope

This document specifies the purpose and content of all identified systems and software life‐cycle and servicemanagement information items (documentation). The information item contents are defined according togenericdocument types, aspresented inClause7, and thespecificpurposeof thedocument (Clause10).

This document assumes an organization is performing life‐cycle processes, or practicing servicemanagement,usingoneormoreofthefollowing:

— ISO/IEC 12207:2008 (IEEE Std 12207‐2008), Systems and software engineering — Software life cycleprocesses;

— ISO/IEC/IEEE15288:2015,Systemsandsoftwareengineering—Systemlifecycleprocesses;

— ISO/IEC20000‐1:2011 (IEEE Std 20000‐1:2013), Information technology—Servicemanagement—Part 1:Servicemanagementsystemrequirements;and

— ISO/IEC20000‐2(IEEEStd20000‐2:2013), Information technology — Service management — Part 2: Guidance on the application of service management systems.

This document provides a mapping of processes from the above standards to a set of information items. Itprovides a consistent approach to meeting the information and documentation requirements of systems andsoftwareengineeringandITservicemanagement.

Thisdocumentdoesnotestablishaservicemanagementsystem.

ISO/IEC 12207:2008 (IEEE Std 12207‐2008) and ISO/IEC/IEEE 15288:2015 define a set of processes formanagingandperformingthestagesofasoftwareorsystemlifecycle.TheydefineanInformationManagementprocess,butdonot“detailinformationitemsintermsofname,format,explicitcontent,andrecordingmedia”.

ISO/IEC/IEEE15288:2015andISO/IEC12207:2008(IEEEStd12207‐2008)establishacommonframeworkforsystem and software life‐cycle processes. They identify or require a number of documentation items. Theirprocess reference model does not represent a particular process implementation approach, nor prescribe asystem/softwarelife‐cyclemodel,methodologyortechnique.

ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013) establishes comprehensive requirements for documents andrecords,withsomespecificrequirements.

ISO/IEC20000‐2:2012(IEEEStd20000‐2:2013),providesguidanceon theuseof ISO/IEC20000‐1:2011(IEEEStd20000‐1:2013).

Thegenericdocumenttypesdefinedinthisdocumentareusedtoidentifytheinformationnecessarytosupportthefollowing:

— theISO/IEC/IEEE15288:2015agreement;

— organizationalproject‐enabling;

— technicalmanagementandprocesses;

— theISO/IEC12207:2008(IEEEStd12207‐2008)primary,supporting,andorganizationallife‐cycleprocesses;and




126c0ad72200/iso-iec-ieee-15289-2017


2©ISO/IEC2017–Allrightsreserved


— the ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013) service management system (SMS), service delivery,relationship,resolution,andcontrolprocesses.

The generic document types (which can be referred to as information item types) are used to identify theinformation necessary to support the ISO/IEC/IEEE 15288:2015 agreement, organizational project‐enabling,technical management, and technical processes; the ISO/IEC 12207:2008 (IEEE Std 12207‐2008) primary,supporting, and organizational life‐cycle processes; or the ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013)servicemanagementsystem(SMS),servicedelivery,relationship,resolution,andcontrolprocesses.

Foreachlife‐cycleprocessorservice, itwouldbepossibletoprepareapolicy,plan,procedures,andreports,aswell as numerous records, requests, descriptions and specifications. Such an elaborationof the documentationschemawouldbemorerigorousthanspecifiedbyISO/IEC/IEEE15288:2015orISO/IEC12207:2008(IEEEStd12207‐2008). As ISO/IEC/IEEE 15288:2015 points out (1.4), “The users of this document are responsible forselectingalifecyclemodelfortheprojectandmappingtheprocesses,activities,andtasksinthisdocumentintothat model. The parties are also responsible for selecting and applying appropriate methodologies, methods,modelsandtechniquessuitablefortheproject.”Thus,informationitemsarecombinedorsubdividedconsistentwith the life cycle model, as needed for project or organizational purposes, as further defined in Clause 4,Applicability,andClause5,Conformance.

Thescopeofthisdocumentdoesnotincludethefollowing:

a) the formatorcontentofrecommended inputdataor input information items,except for thecontentofthose inputitemsthatarealsooutputinformationitems;

b) instructionsoncombiningorsubdividing information itemsand information itemcontentsofasimilarnature;

c) guidanceonselectinganappropriatepresentation format,deliverymedia,andmaintenancetechnologyfor systems or software life‐cycle data, records, information items, or documentation, such aselectronic publishingsystems,contentmanagementsystems,ordatarepositories;

NOTE1 ISO/IEC12207:2008(IEEEStd12207‐2008)doesnotalwaysspecifywhensoftwareinformationitemsaretobeprepared,nordoesitidentifyinformationitemcontents.

NOTE2 ISO/IEC/IEEE26531, Systemand software engineering –Contentmanagement forproduct life‐cycle, user, andservicemanagementdocumentation, provides requirements for contentmanagement and component content managementsystems.

d) detailed content for information items related to general business, contractual, organizational, andfinancial management that is not specific to systems and software engineering and informationtechnologyservicemanagement, suchasbusinessstrategies, contract changenotices,humanresourcesand investment policies, personnel selection criteria, financial budgeting and accounting policies andprocedures,costreports,orpayrolldata;

e) information items showing only approval of an ISO/IEC 12207:2008 (IEEE Std 12207‐2008)subclause, suchasISO/IEC12207:2008(IEEEStd12207‐2008),6.1.2.3.4.5;

f) any ISO/IEC/IEEE15288:2015or ISO/IEC12207:2008 (IEEEStd12207‐2008) subclausenot explicitlyor implicitly identifying the recording of information about a process, activity or task, for example,ISO/IEC12207:2008(IEEEStd12207‐2008),6.4.4;

g) work products, models, software, and other artifacts of life‐cycle products and services that arenot informationitemsorrecordsusedininformationitems.

NOTE3 ISO/IEC26514:2008, Systemsand software engineering—Requirements fordesigners anddevelopersof userdocumentation,providesguidanceonformatsforuserdocumentation.



126c0ad72200/iso-iec-ieee-15289-2017


3 ©ISO/IEC2017–Allrightsreserved


2 Normative references The followingdocumentsare referred to in the text in suchaway that someorall of their content constitutesrequirementsofthisdocument.Fordatedreferences,onlytheeditioncitedapplies.Forundatedreferences,thelatesteditionofthereferenceddocument(includinganyamendments)applies.

—ISO/IEC 12207:2008(IEEEStd12207‐2008),Systems and software engineering — Software life cycle processes

—ISO/IEC/IEEE15288:2015,Systems and software engineering — System life cycle processes

— ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013), Information technology — Service management — Part 1: Service management system requirements

3 Terms, definitions, and abbreviated terms For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 24765 (availableatwww.computer.org/sevocab)apply.

ISO,IEC,andIEEEmaintainterminologicaldatabasesforuseinstandardizationatthefollowingaddresses:

—IECElectropedia:availableathttp://www.electropedia.org/

—ISOOnlinebrowsingplatform:availableathttp://www.iso.org/

—IEEEStandardsDictionaryOnline:availableathttp://ieeexplore.ieee.org/xpls/dictionary.jsp

NOTE ISO/IEC 20000‐1:2011 contains different definitions for the terms document, procedure, record and servicerequest.Thosedefinitionsareapplicablewhenconformingtothatdocument..

3.1 Terms and definitions

3.1.1 approval notification by an authorized representative that a deliverable item appears to satisfy requirements and iscomplete

Note1toentry: Such approval does not shift responsibility from the supplier tomeet requirements under a two‐partysituation.

3.1.2 complaint recordofperceivednon‐compliancewithaservicelevelagreementorcustomerdissatisfactionwithservice

3.1.3 complete [documentation] includingallcriticalinformationandanynecessary,relevantinformationfortheintendedaudience

3.1.4 consistent withoutinternalconflicts

3.1.5 Commercial-Off-The-Shelf COTS productavailableforpurchaseandusewithouttheneedtoconductdevelopmentactivities

3.1.6 criteria rules onwhich a judgment or decision can be based, or bywhich a product, service, result, or process can beevaluated



126c0ad72200/iso-iec-ieee-15289-2017




3.1.7 critical information information describing the safe use of the software, the security of the information createdwith the software,ortheprotectionofthesensitivepersonalinformationcreatedbyorstoredwiththesoftware

[SOURCE:ISO/IEC26514:2008]

3.1.8 database collectionofdataorganizedaccordingtoaconceptualstructuredescribingthecharacteristicsofthedataandtherelationshipsamongtheircorrespondingentities,supportingoneormoreapplicationareas

3.1.9 description informationitemthatrepresentsaplannedoractualconcept,function,design,orobject

3.1.10 document uniquelyidentifiedunitofinformationforhumanuse

EXAMPLE Areport,specification,manualorbook,inprintedorelectronicform.

Note1toentry: Adocumentcanbeasingleinformationitem,orpartofalargerinformationitem.

3.1.11 documentation plan planidentifyingthedocumentstobeproducedduringthesystemorsoftwarelifecycle

3.1.12 include [information] havingeithertheinformationorareferencetotheinformationpresentinthedocument

3.1.13 information item separatelyidentifiablebodyofinformationthatisproduced,stored,anddeliveredforhumanuse

Note1toentry: “Information product” is a synonym. A document produced tomeet information requirements can beaninformationitem,orpartofaninformationitem,oracombinationofseveralinformationitems.

Note2toentry: Aninformationitemcanbeproducedinseveralversionsduringaprojectorsystemlifecycle.

3.1.14 information item content information included in an information item, associated with a system, product or service, to satisfy arequirementorneed

3.1.15 information item type groupofinformationitemsconsistentwithapre‐arrangedsetofgenericcriteria

Note1toentry: A“genericdocumenttype”isasynonym.

EXAMPLE A“plan”istheinformationitemtypeforallplansand“report”istheinformationitemtypeforallreports.

3.1.16 modifiable structured and has a style such that changes can be made completely, consistently, and correctly whileretainingthestructure



126c0ad72200/iso-iec-ieee-15289-2017




3.1.17 plan information item thatpresentsa systematic courseofaction forachieving adeclaredpurpose, includingwhen,how,andbywhomspecificactivitiesaretobeperformed

3.1.18 policy clearandmeasurable statementofpreferreddirectionandbehavior tocondition thedecisionsmadewithinanorganization

[SOURCE:ISO/IEC38500:2008]

3.1.19 presentable retrievableandviewable

3.1.20 procedure informationitemthatpresentsanorderedseriesofstepstoperformaprocess,activity,ortask

Note1toentry: A procedure defines an established and approved way or mode of conducting business in anorganization. It details permissible or recommended methods in order to achieve technical or managerial goals oroutcomes.

Note2toentry: AccordingtoISO9000:2015,procedurescanbedocumentedornot.

3.1.21 process setofinterrelatedorinteractingactivitieswhichtransformsinputsintooutputs

3.1.22 record setofrelateddataitemstreatedasaunit

3.1.23 report information item that describes the results of activities such as investigations, observations, assessments, ortests

3.1.24 request informationitemthatinitiatesadefinedcourseofactionorchangetofulfillaneed

3.1.25 service request requestforinformation,orforaroutinechangeorprocedurewithpreviouslyevaluatedrisk

EXAMPLE Arequesttoprovideaccesstoacontrolledapplication,arequesttomovehardware.

3.1.26 software item identifiablepartofasoftwareproduct

EXAMPLE Identificationanddescriptionsof the softwareproduct, source code, software life‐cycle data, archive andreleasedata, andinstructionsforbuildingtheexecutableobjectcode.

3.1.27 specification information item that identifies, in a complete, precise, and verifiable manner, the requirements, design,behavior,orotherexpectedcharacteristicsofasystem,service,orprocess



126c0ad72200/iso-iec-ieee-15289-2017




3.1.28 traceable havingcomponentswhoseorigincanbedetermined

3.1.29 unambiguous describedintermsthatallowonlyasingleinterpretation,aided,ifnecessary,byadefinition

3.1.30 verifiable canbecheckedforcorrectnessbyapersonortool

3.2 Abbreviated terms

CFP CallforProposals

CM Configurationmanagement

COTS Commercial‐Off‐The‐Shelf

ITT InvitationtoTender

RFP RequestforProposal

SLA Servicelevelagreement

SMS Servicemanagementsystem

4 Applicability

4.1 Purpose

The purpose of this document is to provide requirements for users of ISO/IEC 12207:2008 (IEEE Std12207‐2008), ISO/IEC/IEEE 15288:2015, and ISO/IEC 20000‐1:2011 (IEEE Std 20000‐1:2013) for identifyingand planning the specific information items (information products) to be developed and revised duringsystems and software life cycles and service management processes. This document is intended for use asfollows:

a) To address the technical information needed by those involved in ISO/IEC/IEEE15288:2015and ISO/IEC12207:2008(IEEEStd12207‐2008)processes;

b) To specify information in an agreementprocess as described in ISO/IEC/IEEE15288:2015or a two‐partysituation as described in ISO/IEC 12207:2008 (IEEE Std 12207‐2008), ISO/IEC 20000‐1:2011 (IEEE Std20000‐1:2013) and ISO/IEC 20000‐2:2012 (IEEE Std 20000‐2:2013). The two‐party situation may rangefromaninformalagreementwithinanorganizationtoalegallybindingcontract betweenorganizations;

c) To develop information items that provide evidence for process assessment performed with respect toISO/IEC33001,andtoguideprocessimprovementactivities;and

d) Toguideasinglepartyinself‐imposedtasks.

4.2 Intended users of this document

Thisdocumentisapplicableforusebythefollowing:

a) projectmanagersresponsiblefortheInformationManagementprocessofISO/IEC/IEEE15288:2015(6.3.6)duringasystemlifecycle;



126c0ad72200/iso-iec-ieee-15289-2017




b) projectmanagers responsible for identifying information item requirements anddocument contentswhenusing ISO/IEC12207:2008(IEEEStd12207‐2008),oranyothersoftwareengineering life‐cycleprocess, tohelpdeterminewhat shouldbedocumented,when thedocumentation shouldbedeveloped, andwhat thecontentsofthedocumentsshouldbe;

c) acquirersresponsible fordeterminingwhat information itemsareneededtohelpensure thequalityof theproject,ordeliveredsystem,productorservice;

d) individualswhowriteorsupportthedesignanddevelopmentofservice,systemsandsoftwareinformationitems;

e) individuals responsible for identifying information items required to claim conformance with ISO/IEC12207:2008(IEEEStd12207‐2008),ISO/IEC/IEEE15288:2015,or ISO/IEC20000‐1:2011(IEEEStd20000‐1:2013);and

f) individualsundertakingservice,systemsorsoftwareprocessimprovementintheirorganizations.

4.3 Applicability to work efforts

Use of this document is not limited by size, complexity or criticality of the project. It may be applied to thefollowing:

a) anytypeofprojectandlife‐cycleprocess;

b) anyoftheactivitiesandtasksofaprojectandsystemorsoftwareproductorservicelifecycle;

c) allformsofinformationitems,informationitemcontentanddocumentdeliverymedia;and

d) documentation in Commercial‐Off‐The‐Shelf (COTS) productswhen the COTS product is specified as adeliverableunderatwo‐partysituation.

NOTE SeeISO/IEC12207:2008(IEEEStd12207‐2008),1.2.

4.4 Applicability to information item audiences

Users of this document should determine the relationship of the requirements in this document to therequirements and needs of their audience (customers or users of information), or project and organizationalprocedures.Thetypeofdecisiontobemade,ortheworktobeperformed,byusersoftheinformationshouldbeconsideredbeforean information itemisprepared.Reviewingandunderstandingtherequirements,needs,andbackgroundofusersandstakeholdersareessentialtoapplyingthisdocumentaccuratelyandeconomically,sincesomeinformationitemsaredesignedforvariouspurposesandusergroups:

a) Toprovideinformationtospecializedtypesofuserswhomaynotbeapartofaparticularproject;

b) Toaddressthesametypeofuserbutinenvironmentsnotnormallycoexistinginthesameeffort;and

c) To aid both users who are expected to understand technical concepts and terminology, and userswhomaynothavethisbackground.

5 Conformance

5.1 Definition of conformance

Thisdocumentmaybeusedasaconformanceoraguidancedocument forprojectsandorganizationsclaimingconformance to ISO/IEC/IEEE 15288:2015, ISO/IEC 12207:2008 (IEEE Std 12207‐2008), or ISO/IEC 20000‐1:2011(IEEEStd20000‐1:2013).



126c0ad72200/iso-iec-ieee-15289-2017

Documents

Systems and software engineering — Content of life-cycle