SCM

SoftwareConfigurationManagement(SCM)DocumentNumber:[nn]Date:Day,MonthDay,Year[ProjectName][Author1][Author2-ifnone,leaveblankline][Author3-ifnone,leaveblankline][Author4-ifnone,leaveblankline]Professor[Name]SoftwareEngineeringDepartmentMonmouthUniversityWestLongBranch,NJ07764-1898TableofContents1.SCOPE31.1.IDENTIFICATION31.2.SYSTEMOVERVIEW31.3.DOCUMENTOVERVIEW32.REFERENCEDDOCUMENTS33.REQUIREMENTSSUMMARY33.1.BACKGROUND,OBJECTIVES,ANDSCOPE43.2.OPERATIONALPOLICIESANDCONSTRAINTS43.3.DESCRIPTIONOFCURRENTSYSTEMORSITUATION53.4.USERSORINVOLVEDPERSONNEL53.4.1CONFIGURATIONREQUIREMENTS63.5.SOFTWARECONFIGURATIONMANAGEMENTCRITERIA64.JUSTIFICATION94.1ASSUMPTIONSANDCONSTRAINTS94.2ADDITIONALITEMSFORCONSIDERATION:95.NOTES91Scope[Thissectionshallbedividedintothefollowingparagraphs.]1.1Identification[Thisparagraphshallcontainafullidentificationofthesystemandthesoftwaretowhichthisdocumentapplies,including,asapplicable,identificationnumber(s),title(s),abbreviation(s),versionnumber(s),andreleasenumber(s).]1.2SystemOverview[Thisparagraphshallbrieflystatethepurposeofthesystemandthesoftwaretowhichthisdocumentapplies.Itshalldescribethegeneralnatureofthesystemandsoftware;summarizethehistoryofsystemdevelopment,operation,andmaintenance;identifytheprojectsponsor,acquirer,user,developer,andsupportagencies;identifycurrentandplannedoperatingsites;andlistotherrelevantdocuments.]1.3DocumentOverview[Thisparagraphshallsummarizethepurposeandcontentsofthisdocumentandshalldescribeanysecurityorprivacyconsiderationsassociatedwithitsuse.]2ReferencedDocuments[Thissectionshalllistthenumber,title,revision,anddateofalldocumentsreferencedinthisspecification.Thissectionshallalsoidentifythesourceforalldocuments.]3RequirementsSummary[Thissectionshallbedividedintothefollowingparagraphstodescribetheriskmanagementrequirementsasitcurrentlyexists.]3.1Background,Objectives,andScope[Thisparagraphshalldescribethebackground,missionorobjectives,andscopeoftheproductorsituation.][Example:Requirementsregardingsoftwareconfigurationmanagement(SCM)coverabroadarena.SCMisconsideredoneoftheintegralprocessesthatsupporttheotheractivitiesinthestandard.Thedeveloper'sapproach,describedintheproject'sSDP,istoaddressallapplicablecontractclausesforSCMincluding:ConfigurationidentificationConfigurationcontrolConfigurationstatusaccountingConfigurationauditsPackaging,storage,handling,anddelivery3.2OperationalPoliciesandConstraints[Thisparagraphshalldescribeanyoperationalpoliciesandconstraintsthatapplytothecurrentsystemorsituation.][Example:SCMactivitiesapplytoallsoftwareproductsprepared,modified,and/orusedtodevelopsoftwareproductsaswellastotheproductsunderdevelopment,modification,reengineering,orreuse.Ifasystem/subsystemorSWIisdevelopedinmultiplebuilds,SCMineachbuildistobeunderstoodtotakeplaceinthecontextofthesoftwareproductsandcontrolsinplaceatthestartofthebuild.]3.3DescriptionofCurrentSystemorSituation[Thisparagraphshallprovideadescriptionofthecurrentsystemorsituation,identifyingdifferencesassociatedwithdifferentstatesormodesofoperation(forexample,regular,maintenance,training,degraded,emergency,alternative-site,wartime,peacetime).Thedistinctionbetweenstatesandmodesisarbitrary.Asystemmaybedescribedintermsofstatesonly,modesonly,stateswithinmodes,modeswithinstates,oranyotherschemethatisuseful.Ifthesystemoperateswithoutstatesormodes,thisparagraphshallsostate,withouttheneedtocreateartificialdistinctions.]3.4UsersorInvolvedPersonnel[Thisparagraphshalldescribethetypesofusersofthesystem,orpersonnelinvolvedinthecurrentsituation,including,asapplicable,organizationalstructures,training/skills,responsibilities,activities,andinteractionswithoneanother.][Example:Developer'skeyactivitiesrelatedtoSoftwareconfigurationmanagement:Describetheapproachtobefollowedforsoftwareconfigurationmanagement,identifyingrisks/uncertaintiesandplansfordealingwiththem.Coverallcontractualclausespertainingtosoftwareconfigurationmanagement.ParticipateinselectingCSCIsduringsystem(architectural)design.Identifyentitiestobeplacedunderconfigurationcontrol.Assignaproject-uniqueidentifiertoeachSWIandeachadditionalentitytobeplacedunderconfigurationcontrol,includingsoftwareproductstobedevelopedorusedandtheelementsofthesoftwaredevelopmentenvironment.Useanidentificationschemethatidentifiesentitiesatthelevelofcontrolandincludeversion/revision/releasestatus.Establishandimplementproceduresdesignatinglevelsofcontroleachidentifiedentitymustpassthrough,thepersonsorgroupswithauthoritytoauthorizechangesandtomakechangesateachlevel,andthestepstobefollowedtorequestauthorizationforchanges,processchangerequests,trackchanges,distributechanges,andmaintainpastversions.Proposetotheacquirer,inaccordancewithcontractuallyestablishedformsandprocedures,changesthataffectanentityalreadyunderacquirercontrol.Prepareandmaintainrecordsofconfigurationstatusofallentitiesthathavebeenplacedunderproject-levelorhigherconfigurationcontrol.Maintainconfigurationstatusrecordsforthelifeofthecontract.Include,asapplicable,version/revision/release,changessincebeingplacedu