SCM参照模板.docx
- 文档编号:5602708
- 上传时间:2022-12-28
- 格式:DOCX
- 页数:6
- 大小:74.24KB
SCM参照模板.docx
《SCM参照模板.docx》由会员分享,可在线阅读,更多相关《SCM参照模板.docx(6页珍藏版)》请在冰豆网上搜索。
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
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.2Additi
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- SCM 参照 模板