Bài Giảng Phân tích thiết kế hướng đối tượng (phần 4)

Tham khảo tài liệu bài giảng phân tích thiết kế hướng đối tượng (phần 4), công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả
Nội dung trích xuất từ tài liệu:
Bài Giảng Phân tích thiết kế hướng đối tượng (phần 4)Contracts andUML interaction diagrams Lecture 4Hoa Sen University 1 Agenda System sequence diagram Operation Contract On to Object design – Interaction diagrams  Sequence diagrams  Communication diagrams Hoa Sen University 2System Sequence Diagram Sample UP Artifact Relationships Domain Model Sale 1 1..* Sales Business ... LineItem Modeling date ... ... quantity Vision Use-Case Model Process Sale Process Sale use 1. Customer case arrives ... Cashier names 2. Cashier makes new sale. 3. ... Glossary parameters and Require- Use Case Diagram Use Case Text return value details ments system events : System Operation: : Cashier enterItem(…) make Supplementary system NewSale() Specification Post-conditions: operations enterItem -... (id, quantity) Operation Contracts System Sequence Diagrams starting events to design for Design Model : Register : ProductCatalog : Sale enterItem Design (itemID, quantity) spec = getProductSpec( itemID ) addLineItem( spec, quantity ) Hoa Sen University 3 What is System Sequence Diagram A diagram that shows, for ONE particular scenario of a use case, the events that external actors generate, their order, and INTER-system events. (not detailed method calls between objects) Describe what a system does without explaining why Hoa Sen University 4System sequence diagram system as black box the name could be NextGenPOS but System keeps it simple the : and underline imply an instance, and are explained in a later chapter on sequence diagram notation in the UML external actor to Process Sale Scenario system : Cashier :System m ...