專業(yè)課課件-軟件工程reqelicitation cn forstudents

需求工程與系統(tǒng)建(一(一(三(四

需需求建(二 2 需求抽 產(chǎn)品設(shè)計(jì)目標(biāo)不明確干系人參與不 干系人之間缺少共識(shí)

協(xié)同工作（Collaborative面 （Interviewing 建 非功能性需求列表（Checklistsof識(shí)別與磋商 Identificationand 準(zhǔn)確正確明確（Non-可行可證現(xiàn)實(shí)精確全面一致評(píng)審原型化 模型驗(yàn)證（Model確認(rèn)測(cè)試（Acceptance貫穿從需求獲取到軟件系統(tǒng)下線的全過程。需求管理設(shè)計(jì)軟件配置管理、需 、影響析和版本控制需 （Requirements變更請(qǐng)求管（Change需求屬性管理（Requirementsvs. 需求抽Requirements —Steve四世界模AdaptedfromLoucopoulos&Karakostas,1995, 進(jìn) 找出所有干系分析其隸屬于哪個(gè)世用戶設(shè)計(jì)師系統(tǒng)分析師培訓(xùn)與用戶支持人員—技術(shù)文檔作者——客戶—為新系 的Whatisa(fromAlanM.Davis,JREMFormallyIEEStdAconditionorcapabilityneededbyausertosolveaproblemorachieveanAconditionorcapabilitythatmustbemetorpossessedbyasystemorsystemcomponenttosatisfyacontract,standard,specification,orotherformallyimposed edrepresentationofaconditionorcapabilityasin(1)orWhatisaArequirementissomeaspectofasystem’scontentorbehavior,whichnecessaryordesiredbythecustomerorProvidesaclearunderstandingoftheEstablishesacontextoftheRequirementsWhatthesystemmustWhatcharacteris*csorproper*esthesystemmustWhatinforma*onisWhatdegreeofqualityisWhatconstraintsapplytotheWhowillusetheHowthesystemistobeWellde?nedrequirementsaremeasurableandprovidethebasisforprojectRequirementsWhatisaWellde?nedrequirements

Requirementscanbestated,unstatedorStatedRequirements:RequirementsstatedintheStatementofWork(SOW)ora*oniden*fyingspeci?cproblemstobeUnstatedRequirements:RequirementsimpliedorunderstoodalthoughnotapparentinSOWor DerivedRequirements:Requirementsiden*?edduring ysisRequirementsProduct/ProductprocessProductFunc*onal

LevelsofUserrequirements,customer contractor endcustomersystemSystemrequirements,endcustomersystemcontractorSo=waredesignspeci?ca0on,customerengineerssystemcontractorWhyDefineDisagreementwithcustomersonrequirementsandproductUnrealis*ces*matesandcommitmentstoScheduleCostUncertaintyregardingprojectTeamUnhappyItiscri*caltoinvolvethecustomersandstakeholdersearlyinthede?ni*onRequirementsSOURCESOFBusinessOrganiza*onalPoliciesandOrganiza*onTechnicalExis*ngAutomatedUserDataInterfaceSampleSampleRequirementsStakeholdersincludeanyonewithaninterestinthesystem,forSystem ProjectIden*fystakeholdersbyaskingWhowillusetheWhowillprovidetheWhowillgettheWhohasanoversightWhohasarelatedWhowillbeWhowillbeRequirementsInvolvingstakeholdersinindividualorgrouprequirementssessionstosystemResultsinahighqualitysystemfromthecustomer/userpointofHelpstoeducatecustomer/useraboutsystemthroughtheirRawRawRealRawRealRequirementsBene?tsofstakeholderinvolvementImprovedsysteminforma*onImprovedsysteminforma*onImprovedsystemImprovedcustomer/userunderstandingoftheCrea*onofcustomer/userCrea*onofcustomer/usercommitmenttosystemDetermina*onofearly Increasedcon?dencethatconsensuswillbeImprovedqualityofDevelopmentofanintegratedRequirementsBusinessysisoftheexis*ngbusinessprocessesfacilitatesiden*?ca*onofproblemsandpoten*alIden*fyandlistproblemswiththecurrentbusinessConsiderproblems(missing,notworking,Consideropportuni*esforImprovementsmayinvolveopportuni*esforautoma*on(systemrequirements)and/ortothecurrentbusinessprocess(businessprocessRequirementsPoliciesandPoliciesandproceduresde?neworkprac*cesandhowthingsaredoneintheReviewand ysisofpolicies,procedures,protocolsandtechnicalstandardsaidindeterminingbusinessrulesandconstraintsBusinessRule:astatementthatde?nessomeaspectofthebusinessprocess.Itisintendedtoassertstructureortocontrolorin?uencethebehaviorofthebusinessprocessessurroundingthesystemConstraint:restric*onsinthewayasystemisdeveloped.Constraintscanbeeconomic,poli*cal,technical,orenvironmentalandpertaintoprojectresources,schedule,targetenvironment,ortothesystemitself a*onmayalsoexplicitlyde?nerequirementsprocessautoma*on,includingwork?ow,rela*onships,and ExistingAutomatedysisofexis*ngautomatedsystemsprovidesinsightintodatathatmightusedbythenewDataDataDatabasestructureandSystemRequirementsWhatIs“JustEnough”Requirements Secretsof“JustEnough”ExpandedonNextFewSlides’ExpandedonNextFewSlides Who’sMyElevatorsTooIlMeWhyYouFeelTheyAreToo

IDon’tThinkIThinkYouHaveElevatorProblem,notaSpeedMaintainUseAppropriateElicitationWhatElicita*onTechniquesdoyouknowWhendoyouusethemWhataretheirprosandTechniquesfor Group<20

UseinterviewstoclarifyandvalidatestatedandelicitunstatedandderivedWorkwithindividuals?rst,thenwithgroups;dynamicschangeresponsesandTalktothepeoplewhoactuallydotheworkandthewhoarefundingtheUseaPrepareinterviewques*onsUseaPrepareinterviewques*onsinAskessen*alWhat?Why?When?Who?How?Useataperecorder,ifMay26, RequirementsWhenDoYouWhena“Few”PeopleEachKnowa Interviewing WhenDoYouUse e Watch GroupGather(3to20)StakeholdersinOneEverybodySharesIdeasOutTeamAnswersAreUsuallyBe^erthanIndividualWhenConductGroupWhenManyPeopleEachKnowsa(Small)PartoftheWhenProblemNeedsInterac*ontoOp*mizeWhenYouCanGetThemAllAnonymityNecessary?UseaDistributed?UseaTricksforMakingGroupSessionsMoreGroupElicitation e“ActionResearch”WhenObserverWhentoParticipant WatchUnderstandwhatneedstobeUseasbasisforfurtherstudy,businessprocessDeterminewhatisrightandwrongwiththecurrentprocessorIden*fyopportuni*estoreuseexis*ngproductsorExtractrequirementsfrommanydiversesourcesintoaconsolidatedrequirementslist

sRequestforStatementofContract/Task May26, RequirementsIDEAIDEABroadideasmayyieldgoodrequirementsorresultinrequirementscreepSetexpecta7onsUsethegroupe?ecttogeneratenewideasfortheUsefulwhentherearemanyunstatedorUseinafacilitatedAllideasaregood;donotevaluate,debateorDonotbeboundedbywhatisA^empttoproducelotsofideas,novelUserandomwordstoseedthePiggybackonothers’May26, RequirementsLearnthejobbyobserva*onandaskingImmediateUsersaretoobusytotake*meo?forPeoplearenotawareofwhattheySeethesametaskperformedmanyLearnthetaskandrepeatwhileuserisEstablisharela*onshipwith

“NobodycantalkbeDeraboutwhattheydo,andwhytheydoit,thantheycanwhileinthemiddle ngit.”[BeyerandMay26, Requirements AndAndthenClearlydelineatestheseriesofstepstocompletebusinesseventtotheIden*fypossibleinterac*onsbetweenandotherbusinessevents sofBreakdownthebusinesseventsintodiscreteorbusinessMay26, Requirements ,Mock-Ups,ClarifyrequirementsthatareambiguousorSimplify a*onandacceptanceProvideearlyfeedbacktocustomerandendAusefulcommunica*onUsetovalidateUsetoprovidesizingdataforcostUsetoassessalterna*veuserHelpusersvisualizeessen*al

AApicturesaysaMay26, RequirementsUsespicturestorepresent ysiscreatesmodelsofthesystem-‐to-‐be,thatis, representa*onsofwhatwill ethesystemModelingfacilitatestheevalua*on,extension,andclari?ca*onofrawrequirementstothemclear,complete,correctandModelObjectUseMay26, RequirementsIntroducetheprojectteamandprojectGatheracomprehensiverequirements"wishlist"fromstakeholdersoftheProvidesaframeworkforapplyingtheotherelicita*ontechniques,suchasstoryboarding,roleplaying,reviewofexis*ngThefacilitatorleadsthesession,whichGivingeveryoneanopportunityto thesessiononGatheringinputforapplicableRequirementRecordingtheSummarizingthesessionandworkingoutRequirementsTechniqueInterfaceInterfacetohumans/userUse ,scenarios,Essen*alEssen*alopera*ngUseappren4cing,interviews,Policyarchitecture,storedUseinterviews,exis4ng

Rigorousmodelingofeverythingislikelynot everythingislikelynotMatchrequirements/ ysistechniquestoneedsandsitua*onsRequirementsPrepareforPrepareforTRIAGTRIATRIAGTRIAGSPECIFICATIOSPECIFICATIODEVELOPMENDEVELOPMENDEVELOPMENWhenfacedwithnewsituationsor ?2007AlanM. HowDoExpertsDo 60ofWestBankGaza(WBG)USAID/Wisassis*ngtheWBGMissionindesignanddevelopmentofaninforma*onsystemtoreplaceasimpledatabasethatisnotmee*nguserneedsScopeofworkincludesde?ni*onofprocess a*onsystemrequirementsanddevelopmentofanenhancedAc*vi*esincludeTDYtripstotheMissiontode?neandvalidateReviewedapplicablematerialsand a*oninprepara*onforCurrentdatabaseandreportProceduralDiscussionAutomatedDirec*vesSystem545,Informa*onSystemsApplicableWBGMission→Elicita4on a4onMetwithsubjectma^erexpertstodiscussbusinessprocessand→Elicita4on→RequirementsPROJECTWestBankGaza(WBG)ConductedaTDYtotheWBGMissioninApril2006t