RMUC课件

MASTERINGREQUIREMENTSMANAGEMENTWITHUSECASESMODULE2:INTRODUCTIONTORMUCDefinekeyrequirementsmanagementterms.Identifycontributingfactorstoprojectsuccessandprojectfailure.Describehowrequirementsmanagementincreasesthechancesofprojectsuccess.Describequalitiesofrequirementssets.Verifiable,traceable,unambiguous.DescribetheRUP.Requirementsmanagementworkflow,roles,andartifacts.ObjectivesCommonProjectProblemsOverviewRequirementAconditionorcapabilitytowhichthesystemmustconform.RequirementsmanagementAsystematicapproachto:•Eliciting,organizing,anddocumentingrequirements.•Establishingandmaintainingagreementbetweencustomer/userandtheprojectteamonthechangingrequirements.DefinitionsWhatDoSoftwareRequirementsSpecify?“What”To“How”RequirementsManagementIsNotEasyRequirements:Arenotalwaysobvious.Comefrommanysources.Maynotalwaysbeeasytoexpressclearlyinwords.Relatetooneanotherandtootherdeliverablesofthesoftwareengineeringprocess.Haveuniquepropertiesorpropertyvalues.Change.Aredifficulttocontrolinlargenumbers.WhatisinaRequirementsManagementPlan?•Typesofrequirementstocollectandwhereyouwillcollectthem.•Typesofattributestotrack.•Typesofrequirementstotrace.•Typesofdocumentstoproduce.•Managementguidelines.RequirementsManagementPlanMaintainaclearstatementoftherequirementswith:GoodqualityrequirementsApplicableattributesforeachrequirementtypeTraceabilitytootherrequirementsandotherprojectartifactsTheGOAListodeliverqualityproductsontimeandonbudgetthatmeetthecustomer’srealneeds.EffectiveRequirementsManagementOldConceptsSatisfiesrequirementsdocuments.Passedsystemtest.Developmentadheredtoprocess.ModernConceptUnderstandallstakeholderneeds.Continuallyassessallartifactstoseeifneedsaremet.Whatisa“QualityProduct”?ComponentsofFURPS+FunctionalityFeaturesetcapabilities,security,generalityUsabilityHumanfactorsaesthetics,consistency,documentationReliabilityFrequency/severityoffailure,recoverability,predictability,accuracy,MTBFPerformanceSpeedefficiency,resourceusage,throughput,responsetimeSupportabilityTestabilityExtensibilityAdaptabilityMaintainabilityCompatibilityConfigurabilityServiceabilityInstallabilityLocalizabilityRobustnessDimensionsofQualityOnTimeandOnBudgetBecauseyourtimeandresources(people,money,equipment,andsoon)arelimited,youcancompleteonlyafixedamountofwork.Todeliveraproduct“ontimeandonbudget”,youneedtofigureouthowmuchworkyoucanactuallycompletewithagivenscope,budget,andpoolofresources.Ifanyoneofthefourfactorschange,youneedtomakeadjustments.Forexample,ifyouincreasescope,youneedtoincreaseoneormoreofthefollowing:time,moneyandresources.Ifyoureducethebudget,youneedtodecreasethescopetodeliverthesysteminthesametimeandwiththesameresources.Failureoccursifyoukeepsqueezingmoreandmoreintothetrianglewithoutmovingoneofthesepointstocompensate.Ofcourseyouwanttodeliverthemaximumvalue,sobeasaccurateaspossible.MeettheCustomer’sRealNeedsHowdoyoureachagreementonwhatfeaturesshouldbeincludedinourproject?Whatstakeholderneedsdotheyrepresent?Howshouldtheybeprioritized?Whatshouldyouputinthebaselinecommitmentfordelivery?“Baseline”meansthesetoffeaturesthatconstitutestheagreed-uponbasisfordevelopmentandthatcanonlybechangedthroughaformalprocedure.Theideaofthebaseline在国际马拉松邀请赛中，一位名不见经传的选手夺得冠军，当记者问他凭什么取得如此惊人的成绩时，他说，每次比赛前，我都要乘车把比赛线路仔细看一遍，并把沿途比较醒目的标记画下来，比如第一标记是银行，第二是一座红房子等等，这样一直画到赛程的终点。比赛时，先全力冲向第一个目标，到达第一个目标后，再全力向第二个目标，把40公里的路程分解成几个小目标，直到终点。通过需求基线的建立，满足客户的真正需求。BaselineRequirementsEnableAgreementrequirementspecification（SRS）requirementfeatureSRSHelpProjectsSucceedProblemanalysisUnderstandtheproblem.Gainstakeholderagreement.Clearstatementofbusinessobjectives.RequirementselicitationIdentifywhowillusethesystem(actors).Elicithowthesystemwillbeused(usecases).RequirementsmanagementSpecifyrequirementscompletely.Manageexpectations,changes,anderrors.Controlscopecreep.Enlistallteammembers.ActorScenarioUsecaseUse-caseModel学生登陆注册课程查看报告QualitiesofSoftwareRequirementsSetsQualitiesofSoftwareRequirementsSets无歧义的需求如果项目开发人员、用户以及其他风险承担人对一条需求有不同的解释,那么需求可能是有二义性的。只要需求是用自然语言书写的,二义性就会存在。QualitiesofSoftwareRequirementsSets无歧义需求的保证无歧义需求保证的唯一方法是对每项需求编写验收标准。验收标准是对需求的量化，是需求的度量方式。只要有可能验收标准就使用数字而不是单词来表达需求。验收标准是需求的度量方式，它使测试者能够确定提交的产品是否满足需求，不会引起任何主观的判断。不同类型的验收标准使用不同的度量尺度和度量方法并且包括业务允许的误差范围。可验证的需求需求必须是可验证的或“可测试的”。“可验证的或可测试的”需要合理的定义良好的无歧义的需求。如果需求是不可验证的,则说明需求尚不明确，同时意味着缺乏开发依据,确认缺乏标准。验收标准和验证项有一定的区别,验收标准用于确认提交的软件最终产品,验证项用于确认需求。QualitiesofSoftwareRequirementsSets可验证需求的保证可验证需求保证的唯一方法是对每项需求编写足够的验证项并由用户参加对验证进行评审。可跟踪的需求从最初提出需求到最后需求的实现成为提交的工作产品,要经历许多阶段，每个阶段都是一种转换。在转换过程中需求做为一种知识和信息,有可能因为开发人员的误解造成知识和信息的失真和衰减。能够把最初的需求与最后提交的产品中实现该需求的部分联系起来是很重要的。如果需求是可跟踪的，那么当更改发生时，找出产品的哪些部分将受到更改的影响就更容易。确保需求可跟踪性意味着可以设计出最有效的方式来进行更改。QualitiesofSoftwareRequirementsSets跟踪性的保证为了确认每项需求是可追踪的，必须具备：唯一的需求标识需求或限制类型的说明该需求所属的所有业务事件和用例的引用对其它有冲突需求的引用对该需求有某种更改影响的相关需求的引用一致的使用术语(用引用的方法使用术语)QualitiesofSoftwareRequirementsSetsRequirementsDiscipline:WorkflowDetails问题分析可以通过了解问题及涉众的最初需要，并提出高层解决方案来实现。它是为找出“隐藏在问题之后的问题”而进行的推理和分析。问题分析期间，将对“什么是面临实际问题”和“谁是涉众”等问题达成一致。而且，您还要从业务角度界定解决方案，以及制约该解决方案的因素。已经对项目进行过商业理由分析，将便于我们更好地预