1.

2. 1. 2. 3. 4. 3. 4. 1.1 . , , , , , , 5. 1.2 What does the User really need? (, , )) (Needs)Stakeholder Needs/Goal Stated Requirements(Candidate Requirements) ?System built Find and Listen Voice of Customer Carefully Whos Smart? needs . : You are Smart Stakeholder is Smart Care : 6. 1.3 Analyst 7. 1.4 1.4.1 / 1. 2. --- 8. 1.4 One Stakeholder can not speak for All , / / R & R 9. 1.4 Stakeholder , ? Assumptions risks : 10. 1.4 , / 1 PM QA PM 50%80% 11. 1.4 1.4.2 , -/1. / --- 12. 1.4 1.4.3 , Business Vision -/ 1. 2. , , --- 13. 1.4 - Business Rationale for authorizing the project Vision : product long-term view Scope : product / Big picture of view: : High-level Technical/Non-technical features business process : , , ROI 14. 1.4 - Vision , : Concrete Goal Conflicting goals Tunnel Vision : sensible starting point () / : milestone, Vaporware : 15. 1.4 - Scope Product boundary External Interface : ? : expectation Gold-Plate : / , / Divide and Conquer : Feature level : Endless Scope Change : : (Cole, Andy) Needs vs., vs.// balancing 16. 1.4 - Business Assumption/Constraints Goal Scope / : Business Assumption TBD(To Be Defined) : Open Issue : / Technical constraints : HW/SW/NW/DB/PL, / , SW , // : // , / , (SLA) , Standard : , , , ( )Compliance : / / , 17. 1.4 - An Insurance Domain Project Business Requirement Scope ItemExampleNeeds .Goal .ObjectiveAgent .Business rule . . agent . Agent .Operation conceptAssumption . .Constraints . . 18. 1.4 1.4.4 -/ 1. 2. (Repository )--- 19. 1.4 Business Vision Stakeholder Repository 20. 1.4 No one technique is sufficient for realistic projects (asking) (discussing and formulating) (reuse) Interviews Questionnaires Brainstorming Role Playing Reuse documents/data Scenario-oriented/Goal-oriented/Use cases-driven - High Interviews Role Playing Customer Brain Storming Requirements Workshop Prototyping LowAnalysist High Use Case Surveys Questionnaires/ 20 21. 1.4 - Interview Ask Question & Listen answer /SME - lack of structure Closed Interview : No bias : ? . : : Rationale Source Open-ended Interview 22. 1.4 Interview Before InterviewContext-free QuestionsContext-Setting contextual , (High-level) attribute : bias During Interview : Listen, listen, listen Feedback sketches After InterviewContext-free Questions ? ? ? : Do you need a larger screen, dont you? : Are fifty items about right? : Can we get back to my questions? : I have a three part questions, : ? / ? Unanswerable : How to tie your shoes? Closed ended questions : Yes/No 23. 1.4 - Brainstorming Group Session (2~4, 4~20) : wild, crazy or impractical (generation)(consolidation ) . : reword, . w . w . 24. 1.4 Brainstorming : , - / : : Listing & : Post-it, whiteboard large sheets Domination by a Few : Five-Minute Position Statement Coupon Group Lack of Participation by Some : Great Idea CouponSessions Cheap Shot Coupon 25. 1.4 1. : xx : ? ? ?2. SW ? USE CASE 3. 4. 5. 6. ? - 26. 1.4 1. 3 => 3 2. , => , , , 3. ( , )4. , , , 5. A/B feature/function => 1. feature function ? 2. feature function ? 3. feature/function ? 27. 28. 2.1 , , ( ) . , , . . . . . 29. 2.2 + balance Business owners View Architects View / , ? , (Candidate Requirement)(Agreed Requirements) : : / : needs 30. 2.3 Analyst Use Case Use Case Model 31. 2.4 2.4.1 . / 1. 2. 3. , --- 32. 2.4 (How much does the customer want it?) (How much cost to develop?) (How much time to deliver?) (How technologically difficult?) (How much will the business benefit?)Value Core Business Value, Cost, Risk Cost, Risk Product value 33. 2.4 2.4.2 ( ) . Use Case Model / 1. 2. 3. 4.Actor Use Case Use Case Use Case Diagram , --- 34. 2.4 BusinessUser RequirementsRequirementsAlternative ModelsWho?Stakeholder CategoriesActor Table Actor Map Dialog mapPrototypes Dialog HierarchyWhat?Relationship Map Glossary Context DiagramData modelClass Model Data Dictionary Data tablesWhen?Event-Response TableState DiagramState Data MatrixBusiness RulesDecision tables Decision TreesUse CasesScenarios, Stories Activity Diagrams DFDProject VisionWhy?Business policesHow?Process MapWhy the project is being undertakenWhat users will be able to do with the productDesign & DevelopmentHigh-Level &DetailsSoftware RequirementsScopeWhat developers need to build 35. 2.4 2.4.3 Use Case Use Case Design Use Case Model / 1. 2.Actor Use Case .--- 36. 37. 3.1 . Agreed Requirements Requirements Specification Formal Requirements 38. 3.2 SW , CommunicationBaseline , / SW Develop LifecycleMarket Needs Behavior Requirem entsBusinessSRS SW Product Lifecycle , / 39. 3.3 AnalystUse Case Use Case Model Use Case Specification SRS( ) 40. 3.4 3.4.1 Use Case Use Case . Use Case Specification Use Case Model/ 1. 2.Use Case Flow of Event ( ) --- Use Case Actor , Use Case . 41. 3.4 : . - : Model/Picture : : : , , . .Glossary : , 42. 3.4 3.4.2 Use Case Specification Use Case Model/ 1. 2. --- 43. 3.4 3.4.3 SRS( ) Use Case Model/ 1. 2. 3. --- 44. 45. 4.1 (Walkthrough) (Inspection) , , , , (Formal Review) , , , , , : : : , 46. 4.2 , . . , . . 47. 4.3 Analyst 48. 4.4 4.4.1 --/1. --- 49. 4.4 4.4.2 , , , , . -/ 1. 2. 3. ,, --- 50. 4.4 4.4.3 . -/ 1. 2. 3. 4. 5. Use Case / --- 51. 4.4 4.4.4 --- -/1. //---