CMM Level 23 Outline.docx
- 文档编号:29826092
- 上传时间:2023-07-27
- 格式:DOCX
- 页数:145
- 大小:106.20KB
CMM Level 23 Outline.docx
《CMM Level 23 Outline.docx》由会员分享,可在线阅读,更多相关《CMM Level 23 Outline.docx(145页珍藏版)》请在冰豆网上搜索。
CMMLevel23Outline
ReachingCMMLevel2–Repeatable
RequirementsManagement
ThepurposeofRequirementsManagementistoestablishacommonunderstandingbetweenthecustomerandthesoftwareprojectofthecustomer'srequirementsthatwillbeaddressedbythesoftwareproject.RequirementsManagementinvolvesestablishingandmaintaininganagreementwiththecustomerontherequirementsforthesoftwareproject.Thisagreementisreferredtoasthe"systemrequirementsallocatedtothesoftware."The"customer"maybeinterpretedasthesystemengineeringgroup,themarketinggroup,anotherinternalorganization,oranexternalcustomer.Theagreementcoversboththetechnicalandnon-technical(e.g.,deliverydates)requirements.Theagreementformsthebasisforestimating,planning,performing,andtrackingthesoftwareproject'sactivitiesthroughoutthesoftwarelifecycle.
Theallocationofthesystemrequirementstosoftware,hardware,andothersystemcomponents(e.g.,humans)maybeperformedbyagroupexternaltothesoftwareengineeringgroup(e.g.,thesystemengineeringgroup),andthesoftwareengineeringgroupmayhavenodirectcontrolofthisallocation.Withintheconstraintsoftheproject,thesoftwareengineeringgrouptakesappropriatestepstoensurethatthesystemrequirementsallocatedtosoftware,whichtheyareresponsibleforaddressing,aredocumentedandcontrolled.
Toachievethiscontrol,thesoftwareengineeringgroupreviewstheinitialandrevisedsystemrequirementsallocatedtosoftwaretoresolveissuesbeforetheyareincorporatedintothesoftwareproject.Wheneverthesystemrequirementsallocatedtosoftwarearechanged,theaffectedsoftwareplans,workproducts,andactivitiesareadjustedtoremainconsistentwiththeupdatedrequirements.
Goals
Goal1Systemrequirementsallocatedtosoftwarearecontrolledtoestablishabaselineforsoftwareengineeringandmanagementuse.
Goal2Softwareplans,products,andactivitiesarekeptconsistentwiththesystemrequirementsallocatedtosoftware.
Commitmenttoperform
Commitment1Theprojectfollowsawrittenorganizationalpolicyformanagingthesystemrequirementsallocatedtosoftware.
Thesystemrequirementsallocatedtothesoftwarearereferredtoas"allocatedrequirements"inthesepractices.
Theallocatedrequirementsarethesubsetofthesystemrequirementsthataretobeimplementedinthesoftwarecomponentsofthesystem.Theallocatedrequirementsareaprimaryinputtothesoftwaredevelopmentplan.Softwarerequirementsanalysiselaboratesandrefinestheallocatedrequirementsandresultsinsoftwarerequirementswhicharedocumented.
Thispolicytypicallyspecifiesthat:
1.Theallocatedrequirementsaredocumented.
2.Theallocatedrequirementsarereviewedby:
Thesoftwaremanagers,andotheraffectedgroups.
Examplesofaffectedgroupsinclude:
osystemtest,
osoftwareengineering(includingallsubgroups,suchassoftwaredesign),
osystemengineering,
osoftwarequalityassurance,
osoftwareconfigurationmanagement,and
odocumentationsupport.
3.Thesoftwareplans,workproducts,andactivitiesarechangedtobeconsistentwithchangestotheallocatedrequirements.
Abilitytoperform
Ability1Foreachproject,responsibilityisestablishedforanalyzingthesystemrequirementsandallocatingthemtohardware,software,andothersystemcomponents.
Analysisandallocationofthesystemrequirementsisnottheresponsibilityofthesoftwareengineeringgroup,butisaprerequisitefortheirwork.
Thisresponsibilitycovers:
1.Managinganddocumentingthesystemrequirementsandtheirallocationthroughouttheproject'slife.
2.Effectingchangestothesystemrequirementsandtheirallocation.
Ability2Theallocatedrequirementsaredocumented.
Theallocatedrequirementsinclude:
1.Thenon-technicalrequirements(i.e.,theagreements,conditions,and/orcontractualterms)thataffectanddeterminetheactivitiesofthesoftwareproject.
Examplesofagreements,conditions,andcontractualtermsinclude:
oproductstobedelivered,
odeliverydates,and
omilestones.
2.Thetechnicalrequirementsforthesoftware.
Examplesoftechnicalrequirementsinclude:
oenduser,operator,support,orintegrationfunctions;
operformancerequirements;
odesignconstraints;
oprogramminglanguage;and
ointerfacerequirements.
3.Theacceptancecriteriathatwillbeusedtovalidatethatthesoftwareproductssatisfytheallocatedrequirements.
Ability3Adequateresourcesandfundingareprovidedformanagingtheallocatedrequirements.
1.Individualswhohaveexperienceandexpertiseintheapplicationdomainandinsoftwareengineeringareassignedtomanagetheallocatedrequirements.
2.Toolstosupporttheactivitiesformanagingrequirementsaremadeavailable.
Examplesofsupporttoolsinclude:
ospreadsheetprograms,
otoolsforconfigurationmanagement,
otoolsfortraceability,and
otoolsfortestmanagement.
Ability4Membersofthesoftwareengineeringgroupandothersoftwarerelatedgroupsaretrainedtoperformtheirrequirementsmanagementactivities.
Examplesoftraininginclude:
othemethods,standards,andproceduresusedbytheproject,and
otheapplicationdomain.
Activitiesperformed
Activity1Thesoftwareengineeringgroupreviewstheallocatedrequirementsbeforetheyareincorporatedintothesoftwareproject.
1.Incompleteandmissingallocatedrequirementsareidentified.
2.Theallocatedrequirementsarereviewedtodeterminewhethertheyare:
∙feasibleandappropriatetoimplementinsoftware,
∙clearlyandproperlystated,
∙consistentwitheachother,and
∙testable.
3.Anyallocatedrequirementsidentifiedashavingpotentialproblemsarereviewedwiththegroupresponsibleforanalyzingandallocatingsystemrequirements,andnecessarychangesaremade.
4.Commitmentsresultingfromtheallocatedrequirementsarenegotiatedwiththeaffectedgroups.
Examplesofaffectedgroupsinclude:
osoftwareengineering(includingallsubgroups,suchassoftwaredesign),
osoftwareestimating,
osystemengineering,
osystemtest,
osoftwarequalityassurance,
osoftwareconfigurationmanagement,
ocontractmanagement,and
odocumentationsupport.
RefertoActivity6oftheSoftwareProjectPlanningkeyprocessareaforpracticescoveringnegotiatingcommitments.
Activity2Thesoftwareengineeringgroupusestheallocatedrequirementsasthebasisforsoftwareplans,workproducts,andactivities.
Theallocatedrequirements:
1.Aremanagedandcontrolled.
"Managedandcontrolled"impliesthattheversionoftheworkproductinuseatagiventime(pastorpresent)isknown(i.e.,versioncontrol),andchangesareincorporatedinacontrolledmanner(i.e.,changecontrol).
Ifagreaterdegreeofformalitythanisimpliedby"managedandcontrolled"isdesired,theworkproductcanbeplacedunderthefulldisciplineofconfigurationmanagement,asisdescribedintheSoftwareConfigurationManagementkeyprocessarea.
2.Arethebasisforthesoftwaredevelopmentplan.
3.Arethebasisfordevelopingthesoftwarerequirements.
Activity3Changestotheallocatedrequirementsarereviewedandincorporatedintothesoftwareproject.
1.Theimpacttoexistingcommitmentsisassessed,andchangesarenegotiatedasappropriate.
∙Changestocommitmentsmadetoindividualsandgroupsexternaltotheorganizationarereviewedwithseniormanagement.
RefertoActivity4oftheSoftwareProjectPlanningkeyprocessareaandActivity3oftheSoftwareProjectTrackingandOversightkeyprocessareaforpracticescoveringcommitmentsmadeexternaltotheorganization.
∙Changestocommitmentswithintheorganizationarenegotiatedwiththeaffectedgroups.
RefertoActivities5,6,7,and8oftheSoftwareProjectTrackingandOversightkeyprocessareaforpracticescoveringnegotiatingchangestocommitments.
2.Changesthatneedtobemadetothesoftwareplans,workproducts,andactivitiesresultingfromchangestotheallocatedrequirementsare:
∙identified,
∙evaluated,
∙assessedforrisk,
∙documented,
∙planned,
∙communicatedtotheaffectedgroupsandindividuals,and
∙trackedtocompletion.
Measurementandanalysis
Measurement1Measurementsaremadeandusedtodeterminethestatusoftheactivitiesformanagingtheallocatedrequirements.
Examplesofmeasurementsinclude:
ostatusofeachoftheallocatedrequirements;
ochangeactivityfortheallocatedrequirements;and
ocumulativenumberofchangestotheallocatedrequirements,includingtotalnumberofchangesproposed,open,approved,andincorporatedintothesystembaseline.
Verifyingimplementation
Verification1Theactivitiesformanagingtheallocatedrequirementsarereviewedwithseniormanagementonaperiodicbasis.
Theprimarypurposeofperiodicreviewsbyseniormanagementistoprovideawarenessofandinsightintosoftwareprocessactivitiesatanappropriatelevelofabstractionandinatimelymanner.Thetimebetweenreviewsshouldmeettheneedsoftheorganizationandmaybelengthy,aslongasadequatemechanismsforexceptionreportingareavailable.
RefertoVerification1oftheSoftwareProjectTrackingandOversightkeyprocessareaforpracticescoveringthetypicalcontentofseniormanagementoversightreviews.
Verification2Theactivitiesformanagingtheallocatedrequirementsarereviewedwiththeprojectmanageronbothaperiodicandeventdrivenbasis.
RefertoVerification2oftheSoftwareProjectTrackingandOversightkeyprocessareaforpracticescoveringthetypicalcontentofprojectmanagementoversightreviews.
Verification3Thesoftwarequalityassurancegroupreviewsand/orauditstheactivitiesandworkproductsformanagingtheallocat
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- CMM Level Outline