Less04- Use-Case Analysis

Object Oriented Analysis and Design Using the UMLModule : Use-Case AnalysisRational Proprietary and Confidential1.Objectives: Use-Case Analysis Understand the purpose of Use-Case Analysis and where in the lifecycle it is performed 
Nội dung trích xuất từ tài liệu:
Less04- Use-Case Analysis Object Oriented Analysis and Design Using the UML Module : Use-Case AnalysisRational 1Proprietary and Confidential Objectives: Use-Case Analysis  Understand the purpose of Use-Case Analysis and where in the lifecycle it is performed  Identify the classes which perform a use- case flow of events  Distribute the use-case behavior to those classes, identifying responsibilities of the classes  Develop use-case realizations that model the collaborations between instances of the identified classesRational 2Proprietary and Confidential Use-Case Analysis in Context U se ase C D esi gner Anal s ysiRational 3Proprietary and Confidential Use-Case Analysis in Context  w ehave ade i talatem ptatdefni our m annii t i ng ar t ur e chiect ew have i defnedhe t upperl ayer ofour s ar t ur he chiect e,t key abstactons,and r i som ekeyanal s ysi m echani s. snii chiect e,al sm Thi i talar t ur ong ihhe wt t sofw ar r t eequiem ent defnednhe equiem ent r s i i t R r s w or l ,gui kfow des and ves i ser asnputt t U se ase ohe C Anal s i t ysi actviy.  I U se ase n C Anal s,w edentf t anal s asses ysi i iyhe ysi cl and i t rr defneheiesponsi ltes. t anal s asses biii Ashe ysi cl andheiesponsi ltes e i t rr biii ar defned,w e ilal not t w l so ehe usage ofany chiect al( or specii l ar t ur m e fcaly,anal s) ysi pater defnedn chiect alAnal s. t ns i i Ar t ur ysi The ar t ur ayer andhei chiect all s t rdependenci m ay f he es afectt alocaton esponsi lt t t defned l i ofr biiyohe i anal s asses. ysi clRational 4Proprietary and Confidential Use-Case Analysis Overview Software Architecture Glossary Use-Case Document Modeling Guidelines Analysis Classes Supplementary Specifications Use-Case Use-Case RealizationUse-Case Realization (identified) Analysis (developed) Use-Case Model Design Model Analysis Model (optional)Rational 5Proprietary and Confidential Requirement Capture and Analysis –Conceptual Model  Conceptual Model – Concepts and Classes Important and typical activity in object-oriented requirement analysis is to identify concepts related to the requirements and to create a conceptual model of the domain  Conceptual Model or domain model illustrates meaningful (to the modelers) conceptual classes in a problem domain  A domain model OR conceptual models is a visual representation of conceptual classes or real-world objects in a domain of interestRational 6Proprietary and Confidential Requirement Capture and Analysis –Conceptual Model (Cont.)  The aim of this step is to decompose the problem in terms of individual concepts or objects  A central distinction between OOA and structured analysis is decomposition by concepts (objects) rather than decomposition by functionsRational 7Proprietary and Confidential Requirement Capture and Analysis –Conceptual Model (Cont.) modeling Problem word Concept modelRational 8Proprietary and Confidential Requirement Capture and Analysis –Conceptual Model (Cont.)  Conceptual Models Are not Models of Software Components they models Conceptual Classes  The conceptual modeling process is fundamentally an inside-out approach. Inside- out means that we’re starting with the core objects in the system, then working from the inside outward, to see how those objects are going to participate in the system we’re building.Rational 9Proprietary and Confidential Use-Case Analysis Steps  Supplement the Use-Case Description  For each use-case realization  Find Classes from Use-Case Behavior  Distribute Use-C ...