文案软件工程requirement.pptx

RequirementEngineeringXiaoyingBaiDepartmentofComputerScienceandTechnologyTsinghuaUniversity,Beijing,ChinaOctober23,20141

TheNightmare“It’syourworstnightmare.Acustomerwalksintoyouroffice,sitdown,looksyoustraightintheeyes,andsays,“IknowyouthinkyouunderstandwhatIsaid,butwhatyoudon’tunderstandiswhatIsaidisnotwhatImean.”Invariably,thishappenslateintheproject,afterthedeadlinecommitmentshavebeenmade,reputationareontheline,andseriousmoneyisatstake.Allofuswhohaveworkedinthesystemsandsoftwarebusinessformorethanafewyearshavelivedthisnightmare,andyet,fewofushavelearnedtomakeitgoaway.”--R.Young,EffectiveRequirementsPractices,Addison-Wesley,20012

“TheHardestsinglepartofbuildingasoftwaresystemisdecidingwhattobuild.Nopartoftheworksocripplestheresultingsystemifdonewrong.Nootherpartismoredifficulttorectifylater.”--FredBrooks3

Outline4WhyrequirementsengineeringiscriticalThebasicconceptsUniformModelingLanguage(UML)Behavior-drivenanalysisSummary

SolutionDomainSRSUserProblemDomainAnalystDeveloperWhyRequirementsEngineeringRequirementsengineeringbuildsabridgetodesignandconstruction.SRS:SoftwareRequirementsSpecification5

Whysoftwarefails?1.pleteRequirements 13.1%2.LackofUserInvolvement 12.4%3.LackofResources 10.6%4.UnrealisticExpectations 9.9%5.LackofExecutiveSupport 9.3%6.ChangingRequirementsSpecifications 8.7%7.LackofPlanning 8.1%8.Didn‘tNeedItAnyLonger 7.5%9.LackofITManagement 6.2%10.TechnologyIlliteracy 4.3%11.Others 9.9%Source:StandishGroup1995，350个公司，8000个项目6“Theseedsofmajorsoftwaredisastersareusuallysowninthefirstthreemonthsofcommencingthesoftwareproject.” CapersJones

WhereAretheDefectsComefrom?JonesThayer,1981,30-35KLOC,35%fromdesignactivities40-80KLOC,10%fromrequ