1. Trang chủ
  2. » Giáo án - Bài giảng

3-Use-case Analysis.ppt

126 528 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Định dạng
Số trang 126
Dung lượng 1,24 MB

Nội dung

Use-Case Analysis 2 Topics  Use-Case Analysis Overview  Class Diagram and key concepts  Domain modeling  Use-Case Analysis Steps  Supplement The Use-Case Description  Find Classes From Use-Case Behavior  Distribute Use-Case Behavior to Classes  Describe Responsibilities  Describe Attributes and Associations  Unify Analysis Classes  Review 3 Objectives: Use-Case Analysis  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 4 Use-Case Analysis Overview Supplementary Specifications Glossary Use-Case Model Use-Case Analysis Project Specific Guidelines Use-Case Realization Analysis Classes Analysis Model Software Architecture Document Use Case Analysis is performed By the Designer – once per Iteration per use case realization 5 Class Diagram?  Là mô hình chính để phân tích yêu cầu CloseRegistrationForm + open() + close registration() Student + get tuition() + add schedule() + get schedule() + delete schedule() + has pre-requisites() Schedule - semester + commit() + select alternate() + remove offering() + level() + cancel() + get cost() + delete() + submit() + save() + any conflicts?() + create with offerings() + update with new selections() Professor - name - employeeID : UniqueId - hireDate - status - discipline - maxLoad + submitFinalGrade() + acceptCourseOffering() + setMaxLoad() + takeSabbatical() + teachClass() CloseRegistrationController + is registration open?() + close registration() 6 Class Diagram Usage  When modeling the static view of a system, class diagrams are typically used in one of three ways, to model:  The vocabulary of a system  Collaborations  A logical database schema 7 Review: Class  A class is a description of a set of objects that share the same attributes, operations, relationships, and semantics.  An object is an instance of a class.  A class is an abstraction in that it  Emphasizes relevant characteristics.  Suppresses other characteristics. 8 Representing Classes and Objects in the UML Professor - name - employeeID : UniqueId - hireDate - status - discipline - maxLoad + submitFinalGrade() + acceptCourseOffering() + setMaxLoad() + takeSabbatical() + teachClass() class name attributes operations Class J Clark : Professor : Professor Named Object Anonymous Object Object 9 Review: What Is an Attribute?  An attribute is a named property of a class that describes the range of values that instances of the property may hold.  A class may have any number of attributes or no attributes at all. Attributes Student - name - address - studentID - dateOfBirth 10 Attributes in Classes and Objects Class Objects Student - name - address - studentID - dateOfBirth :Student - name = “M. Modano” - address = “123 Main St.” - studentID = 9 - dateOfBirth = “03/10/1967” :Student - name = “D. Hatcher” - address = “456 Oak Ln.” - studentID = 2 - dateOfBirth = “12/11/1969” . classes 4 Use-Case Analysis Overview Supplementary Specifications Glossary Use-Case Model Use-Case Analysis Project Specific Guidelines Use-Case Realization Analysis Classes Analysis Model Software. Use-Case Analysis 2 Topics  Use-Case Analysis Overview  Class Diagram and key concepts  Domain modeling  Use-Case Analysis Steps  Supplement The Use-Case. Classes  Describe Responsibilities  Describe Attributes and Associations  Unify Analysis Classes  Review 3 Objectives: Use-Case Analysis  Identify the classes which perform a use-case flow of events  Distribute

Ngày đăng: 16/07/2014, 04:00

TỪ KHÓA LIÊN QUAN

w