公司SCM供应链管理

2020年4月19日

公司SCM供应链管理

文档仅供参考

SoftwareConfigurationManagement(SCM)

DocumentNumber:[nn]

Date:Day,MonthDay,Year

[ProjectName]

[Author1]

[Author2-ifnone,leaveblankline]

[Author3-ifnone,leaveblankline]

[Author4-ifnone,leaveblankline]

Professor[Name]

SoftwareEngineeringDepartment

MonmouthUniversity

WestLongBranch,NJ07764-1898

TableofContents

TOC\o"1-3"

1.Scope

3

1.1.Identification

3

1.2.SystemOverview

3

1.3.DocumentOverview

3

2.ReferencedDocuments

3

3.RequirementsSummary

3

3.1.Background,Objectives,andScope

4

3.2.OperationalPoliciesandConstraints

4

3.3.DescriptionofCurrentSystemorSituation

5

3.4.UsersorInvolvedPersonnel

5

3.4.1ConfigurationRequirements

6

3.5.SoftwareConfigurationManagementCriteria

6

4.Justification

9

4.1AssumptionsandConstraints

9

4.2AdditionalItemsforconsideration:

9

5.Notes

10

1Scope

[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,anddelivery

3.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,changessincebeingplacedunderproject-levelorhigherconfigurationcontrol,andstatusofassociatedproblem/changereports.

Supportacquirer-conductedconfigurationauditsasspecifiedinthecontract.

Establishandimplementproceduresforpackaging,storage,handling,anddeliveryofdeliverablesoftwareproducts.Maintainmastercopiesofdeliveredsoftwareproductsforthedurationofthecontract.

Prepareaversiondescriptionforthesystem.

Meetgeneralrequirementsandperformintegralprocessesofthestandard.]

3.4.1ConfigurationRequirements

[Thisparagraphdescribestheconfigurationmanagementrequirementsfortheproject.]

[Example:SCMrequirementstaskthedeveloperto"keeptrackof"everythingduringthecourseofthedevelopment.SCMisanactivity,notanorganization.SCMmaybeperformedbymembersofthedevelopmentteam,individualswithinaprojecttaskedwiththatresponsibility,aseparateorganization,orotherarrangementsuitablefortheproject.]

3.5SoftwareConfigurationManagementCriteria

[Thisparagraphdescribesthesoftwareconfigurationmanagementcriteriatobefollowedduringtheproject.

[Example:Thestandardrequiresthedevelopertoestablishlevelsofcontrolforallworkproducts.Someexamplesofpossiblelevelsofcontrolandofthingsthedevelopermightidentifyandcontrolare:

Authorcontrol:

Engineeringdata--notes,records,workinprogress(i.e.,dataspecifiedindocumentsassociatedwithparticulardevelopmentactivities)

Softwaredevelopmentfiles

Projectcontrol:

Sourcecodefiles,datafiles,installationsoftware

Informationindocumentsagreeduponbytheprojecttobecorrect

Reuselibraries

Evaluationrecords

Organizationalcontrol:

Generalpurposesoftware--operatingsystems,databasemanagementsystems,e-mail,wordprocessors,spreadsheets

Engineeringanddevelopmenttools--CASEtools,editors,compilers,debuggers,SCMtools,testsoftware

Computersystemadministrativetoolsandproducts--diagnosticsoftware,networkmanagers,archives,backups

Evaluationrecords

Acquirercontrol:

Specifications

SomekeygoalsofSCMrequirementsaretoensurethatthedeveloper:keepstrackofallsoftwareandsoftwareproductdescriptionsassociatedwiththeproject;implementsonlyauthorizedchangestorequirements;andknowswhatsoftwareandassociatedproductsmatchaspecificsetofrequirementsorchangestothoserequirements.

Toimplementchangestorequirements,theacquireranddevelopermustagreeuponwhatthosechangesare.Whenrequirementshavebeendefinedandrecordedasspecificationsandthosespecificationshavebeenplacedoncontract,changesareimplementedthroughcontractmodifications.Whenspecificationshavenotbeenmadeapartofthecontract,theacquireranddeveloperwillneedtoprovideameansforcontrollingandmakingchangestorequirements.Thesemeanscanbeasinformalasaphonecallorhand-shake,orasformalasdocumentssignedbyauthorizedacquireranddeveloperrepresentatives.Thestandarddoesnotprovidecontractualformsornoticesconcerningchangesinrequirements,suchasEngineeringChangeProposals(ECPs),EngineeringChangeNotices(ECNs),ornotificationtousersofchangesinaparticularversionofthesoftware.Althoughthestandarddoesprovideareminderintheformoftwo"shell"requirementstosupportacquirerconfigurationmanagementactivitiesfor(1)

proposingchangestoacquirercontrolledentities,and(2)

supportingconfigurationaudits,theseactivitiesmaynotapplytoallprojects.

Allworkproducts(includingcomputerizedfiles,thesoftwareproductsthatconstitutethedevelopmentenvironment,andhardware),notjustdeliverables,aretobeidentifiedandcontrolledduringthedevelopmentandunderdevelopersoftwareconfigurationmanagementactivity.Thephysicallycontrolleditemscaninclude:computerfiles,magneticmedia(tapes,diskettes,videocassettes),paperdocuments,books,manuals,anddrawings.

Thestandardleavesituptothedevelopertodescribewhatsoftwareconfigurationmanagementrecordswillbeproduced,whentheywillbeproduced,thelevelofdetailofinformationthatwillbecontainedineachrecordandwhoisresponsibleforperformingtheseactivities.

4Justification

[Thissectionshallbedividedintothefollowingparagraphs.]

4.1AssumptionsandConstraints

[Thisparagraphshallidentifyanyassumptionsandconstraintsapplicabletothechangesidentifiedinthissection.]

4.2AdditionalItemsforconsideration:

[Thisparagraphshallidentifyadditionalitemsthatshouldbetakenintoconsideration.]

[Example:Additionalitemsthatshouldbetakenintoconsiderationare:

Desc