Less04- Use-Case Analysis

Chia sẻ: An Nguyen | Ngày: | Loại File: PPT | Số trang:77

Thêm vào BST

Báo xấu

244
lượt xem 64
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

Object Oriented Analysis and Design Using the UML Module : Use-Case Analysis Rational Proprietary and Confidential 1 .Objectives: Use-Case Analysis  Understand the purpose of Use-Case Analysis and where in the lifecycle it is performed 

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Less04- Use-Case Analysis

Object Oriented Analysis and Design Using the UML Module : Use-Case Analysis Rational 1 Proprietary 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 classes Rational 2 Proprietary and Confidential
Use-Case Analysis in Context U se ase C D esi gner Anal s ysi Rational 3 Proprietary and Confidential
Use-Case Analysis in Context  w e have ade i talatem ptatdefni our m an nii t i ng ar t ur e chiect e w have i defned he t upperl ayer ofour s ar t ur he chiect e,t key abstactons,and r i som e key anal s ysi m echani s. s nii chiect e,al sm Thi i talar t ur ong ih he wt t sofw ar r t e equiem ent defned n he equiem ent r s i i t R r s w or l ,gui kfow des and ves i ser as nputt t U se ase o he C Anal s i t ysi actviy.  I U se ase n C Anal s,w e dentf t anal s asses ysi i iy he ysi cl and i t rr defne hei esponsi ltes. t anal s asses biii As he ysi cl and hei esponsi ltes e i t rr biii ar defned,w e ilal not t w l so e he usage ofany chiect al( or specii l ar t ur m e fcaly,anal s) ysi pater defned n chiect alAnal s. t ns i i Ar t ur ysi The ar t ur ayer and hei chiect all s t rdependenci m ay f he es afectt alocaton esponsi lt t t defned l i ofr biiy o he i anal s asses. ysi cl Rational 4 Proprietary and Confidential
Use-Case Analysis Overview Software Architecture Glossary Use-Case Document Modeling Guidelines Analysis Classes Supplementary Specifications Use-Case Use-Case Realization Use-Case Realization (identified) Analysis (developed) Use-Case Model Design Model Analysis Model (optional) Rational 5 Proprietary 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 interest Rational 6 Proprietary 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 functions Rational 7 Proprietary and Confidential
Requirement Capture and Analysis –Conceptual Model (Cont.) modeling Problem word Concept model Rational 8 Proprietary 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 9 Proprietary and Confidential
Use-Case Analysis Steps  Supplement the Use-Case Description  For each use-case realization  Find Classes from Use-Case Behavior  Distribute Use-Case Behavior to Classes  For each resulting analysis class  Describe Responsibilities  Describe Attributes and Associations  Qualify Analysis Mechanisms  Unify Analysis Classes  Checkpoints Rational 10 Proprietary and Confidential
Use-Case Analysis Steps  Supplement the Use-Case Description  For each use-case realization  Find Classes from Use-Case Behavior  Distribute Use-Case Behavior to Classes  For each resulting analysis class  Describe Responsibilities  Describe Attributes and Associations  Qualify Analysis Mechanisms  Unify Analysis Classes  Checkpoints Rational 11 Proprietary and Confidential
Supplement the Use-Case Description • The system • The retrieves and system displays a list of displays a current course list of offerings from the course course catalog offerings. legacy database. Rational 12 Proprietary and Confidential
Use-Case Analysis Steps  Supplement the Use-Case Description  For each use-case realization  Find Classes from Use-Case Behavior  Distribute Use-Case Behavior to Classes  For each resulting analysis class  Describe Responsibilities  Describe Attributes and Associations  Qualify Analysis Mechanisms  Unify Analysis Classes  Checkpoints Rational 13 Proprietary and Confidential
Review: Class  An abstraction  Describes a group of objects with common:  Properties (attributes)  Behavior (operations)  Relationships  Semantics Class Name Professor name Attributes professorID: UniqueId Operations create( ) save( ) delete( ) change( ) Rational 14 Proprietary and Confidential
Review: Use-Case Realization Use-Case Model Design Model Use Case Use-Case Realization Sequence Diagrams Collaboration Diagrams Use Case Class Diagrams Rational 15 Proprietary and Confidential
Find Classes From Use-Case Behavior  The complete behavior of a use case has to be distributed to analysis classes Rational 16 Proprietary and Confidential
What is an Analysis Class? Use-case behavior coordination System boundary System information Rational 17 Proprietary and Confidential
Analysis Classes: A First Step Towards Executables Use Cases Analysis Design Source Exec Classes Elements Code Use-Case Analysis Rational 18 Proprietary and Confidential
What is a Boundary Class?  Intermediates between the interface and something outside the system  Several Types  User interface classes  System interface classes  Device interface classes  One boundary class per actor/use case pair Analysis class stereotype Environment Dependent Rational 19 Proprietary and Confidential
The Role of a Boundary Class Customer Model interaction between the system and its environment Rational 20 Proprietary and Confidential