Week 7 đánh giá giai đoạn i project các nhóm bài đọc thêm; collaboration diagram, communication diagram sequence diagram 1 (2)

Collaboration Diagrams Collaboration Diagrams Dumitru Radoiu Dumitru Radoiu Spring 2009 PET RU M AI OR UNIVERSITY Object-Oriented World time OO Analysis Create the vocabulary Requirements OO Design Give vocabulary ocabu a y behavior (model the system) OO Programming Program the model ode Deliverables Activity UML Diagram Understand System Usage Use Case Diagram Identify Classes Identify Classes High Level Class Diagram High Level Class Diagram Define Workflows Activity Diagram 9 Use Case Model diagnose car Mechanic fix car drive car Car owner Use case di diagnose car Mechanic High Level Class Diagram [talk] Car Diagnosis Mechanic uses> :Diagnosis diagnosis> :Mechanic :Car fixes> Activity Diagram Start Turn Offof Diagnosis Name State Diagnosis equipment problem [error] Display Name ofError State Turn NameOn of Diagnosis State [valid] Car electronic problem [error] Turn On Name of Car State [valid] Turn OffofCar Name State Fix Problem Name of State Diagnose Name of State Object-Oriented World time OO Design OO Analysis Create the vocabulary Requirements Give vocabulary ocabu a y behavior (model the system) A ti it Activity OO Programming Program the model ode Deliverables UML Di UML Diagram Identify interactions  among objects Sequence and  Collaboration Diagrams9 Analyze state changes l h Sate Diagrams Refine class diagrams Class Diagrams Sequence Diagram [talk] Car Diagnosis Mechanic Car Diagnosis Mechanic Turn On Turn On Set to check Diagnose Fix the problem Turn Off Turn Off Agenda  • • • • Why We Model Collaboration Diagrams Why We Model Collaboration Diagrams Notation Different Types of Messages Model a Collaboration Diagram: Case Study High Level Class Diagram :Diagnosis diagnosis> uses> 1 :Mechanic :Car fixes> Message types Load(File) Synchronous (wait) :FileSystem :Compiler Link(ProgramName,Options) y Asynchronous (continue) :Compiler :Linker :DialogOne g Flat (unimportant) :Mechanic :DialogTwo Message Sequencing 1:Message1 :FileSystem 4:M Message4 2:Messag ge2 :Compiler 3:Message3 :Compiler :Linker Multiple Messages 2:AddStudent(Name) :Student 1:LoadClass((name) :Teacher 1.1:LoadStudents() 2:LoadClassInfo() 1.2:LoadClassInfo() 1.3:LoadRoom() :Class : FileSystem y Guard Conditions 1:Compile(Project) 3a:NotifyOfSuccess :FileSystem [Project Loaded] :Editor :Compiler :ErrorDialog Creating Instances Constructor :ObjectB :ObjectA 1:CreateStudent (Name) :GradingSystem G di S : Student Iterations (repeating processes) 1.* Message :ObjectB :ObjectA * 1.* Message :ObjectB :Student * Iterations (repeating processes) Loop through each grade Calculate GPA 1.* [[1 N]: ] GPA+=Grade 2: GPA=GPA/Count(Grades) :Grade :Student * Agenda  • • • • Why We Model Collaboration Diagrams Why We Model Collaboration Diagrams Notation Different Types of Messages Model a Collaboration Diagram: Case Study Model a Collaboration Diagram: Case Study Identify the elements that belong in your diagram Model the relationships between these elements Model the instance level diagram Use Case Model distribute electronically record g grades save grades Teacher upgrade pg g grades load grades logon view i grades d Administrator generate report cards Student Class Diagram maintains > < contains ReportCard p Grades Teacher ^ displays ^ generates WebSite uses > ^ grants access to Administrator Securityy Student uses > < uses Identify the elements Domain Classes :Teacher :Grades :Student Control Classes :Securityy :Database Interface Class :WebSite Model the Relationships Between these Elements :Teacher :Security uses > :WebSite uses > uses > :Student :Database uses > :Grades Model an Instance-Level Diagram 1.1:Validate(UID,PWD) 12 [ 1.2a:[pass] ] DisplayMenu() Di l M () 1.2b:[fail] Logout() 1:Logon(UID PWD) 1:Logon(UID,PWD) 2:[menu displayed] LoadStudent(Name) :Teacher WebSite :Security 2.2:LoadStudentInfo(Name) :Database : Student :Grade ... Mechanic fix car drive car Car owner Use case di diagnose car Mechanic High Level Class Diagram [talk] Car Diagnosis Mechanic uses> :Diagnosis diagnosis> :Mechanic :Car fixes> Activity Diagram. .. Why We Model? ?Collaboration? ?Diagrams Why We Model Collaboration Diagrams Notation Different Types of Messages Model a? ?Collaboration? ?Diagram:  Case Study High Level Class Diagram :Diagnosis diagnosis> uses>... UML? ?Diagram Understand System Usage Use Case? ?Diagram Identify Classes Identify Classes High Level Class Diagram High Level Class? ?Diagram Define Workflows Activity? ?Diagram 9 Use Case Model diagnose