Object Collaboration. Sales ClerkSystem 1. Fill in retailer’s number2. Show retailer’s details. ** Set up a new order. 3. Inputs design number4. Retrieve.

Slides:



Advertisements
Similar presentations
Creating and Submitting Orders Remy Order Management System.
Advertisements

Polycom Quotes on Demand Tool Partner User Guide Version 1.1
Object Design Examples with GRASP
Object-Oriented Analysis and Design CHAPTERS 15: UML INTERACTION DIAGRAMS 1.
CSC Proprietary and Confidential 1 Tasks and Status Lesson 4.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1/20 Interaction Diagrams.
Screens for Order Garments. What happens in the Use Case? The user picks / adds a retailer –The user types in an account number. If the account number.
How to get started RMA Portal ZEBRA TECHNOLOGIES March 19, 2015.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
My Schedule Planner My Schedule Planner is a web-based schedule planner for use by students and advisors. It takes the guess work out of planning schedules.
Assess A Claim Object Interaction Diagrams. Object sequence Diagrams - Use case Sequence of events that occur during one particular execution of a system.
Michigan Electronic Grants System - Plus (MEGS+) Review Comments for Agencies Michigan Department of Education.
Drawing System Sequence Diagrams
Summary Class responsibility cards can be used to help allocate responsibilities between different classes. The use of stereotype classes, such as entity,
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 5: Restaurant.
Copyright W. Howden1 Lecture 4: Sequence Interaction Diagrams.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Object Collaborations. Objectives: Object Interaction (cont.) You will be able to:  Use sequence diagrams to detail object interactions.
Objectives Explain the purpose and objectives of object- oriented design Develop design class diagrams Develop interaction diagrams based on the principles.
Live Meeting 2007: Presenter's companion Interact with attendees You’re using Live Meeting to conduct an orientation session for new hires, and now you.
LECTURE 5 SEQUENCE DIAGRAM 1. INTRODUCTION – SYSTEM SEQUENCE DIAGRAM A system sequence diagram is a fast and easily created artifact that illustrates.
CCG Ordering Information 2014 For Questions, contact the Communications Analyst Alexandra Lazar
Facilities ESR Electronic Service Request. Use the ESR to do the following: Submit a service request electronically to the facilities department Submit.
Interaction diagrams Sequence and collaboration diagrams.
Introduction to Sequence Diagrams
Object Design Examples with GRASP (Ch. 18)
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 9: Interaction.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Pack Company Procedures. Accepting a HIP request from a supplier Allocating the Component Providers Sending the instruction through to the Component Providers.
Lesson 14: Incident and Other Issues. Copyright 2002 Sterling Commerce, Inc. All rights reserved. 2 Create Incident Issue.
BTS430 Systems Analysis and Design using UML Interaction Diagrams.
Starting Object Design
2 Object-Oriented Analysis and Design and the Unified Process Objectives  Explain the purpose and objectives of object- oriented design  Develop design.
1 אירוע אמאזון. 2 שלבי הפיתוח עם דיאגרמות UML 3 אמאזון תרשים תוכן.
Collaboration Diagrams CSIS3600. What is a Collaboration Diagram Collaboration diagrams illustrate interactions between objects The collaboration diagram.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Drawing System Sequence Diagrams
Sequence Models.
© 2008 Prentice Hall, Ovidiu Noran Lecture 7b 1 Modelling OO Logic Requirements: Sequence Diagrams and Activity Diagrams (Textbook Chapter 8, Appendix)
COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.
Sequence Diagrams And Collaboration Diagrams HungNM.
Quick Start Guide: Filters Learn about: 1.What filters Are & Their Functionality 2.How to Create A Filter.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
DESIGN PART 2: OBJECT-LEVEL SEQUENCE DIAGRAMS WITH AN EXAMPLE OF COMPOSITION BTS430 Systems Analysis and Design using UML.
Web Center Training ©2003 Optimum Technology, Inc.
Knowledge Management Platform Communities of Practice User Guide for CoP users Copyright © 2010 Group Technology Solutions. All Rights Reserved.
Integrated Enterprise System 11/1/11Create travel expense TRIP - SAP GUI ECC 6.03 vers SAP TRIP Transaction Creating a Travel Expense Report (TER)
Outline An Introduction to Market Advantage Basic Information Ordering Customized Marketing Collateral Ordering Promotional and other Material Question.
Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
1 SEQUENCE DIAGRAM EXAMPLE The domain model, showing the navigability of the associations, and the Reserve video (staff scenario) use-case description.
PestPac Software. Leads The Leads Module allows you to track all of your pending sales for your company from the first contact to the close. By the end.
After receiving the confirmation , use the link and Login Id provided to retrieve your password.
 System Sequence Diagrams Sheridan SYST Engineering Quality Systems 11.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
1 Kyung Hee University Interaction Diagrams Spring 2001.
Login Screen The login screen provides you with a dashboard view of activities that need attention. Let’s start by creating a product by clicking the ‘Products’
Compatible with the latest browsers; Chrome, Safari, Firefox, Opera and Internet Explorer 9 and above.
Communication DIAGRAM
Sequence Diagram.
Custom Workflow Template
Sequence Diagrams.
Requirements To Design In This Iteration
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Communication DIAGRAM
Creating and Sending Message Links
Software Design (SE321) Lect6-Collaboration Diagram
Chapter 9: Sequence Diagrams Chapter 5 in Software Engineering Book
Completing the Primary Reference portion of the Student Profile
Presentation transcript:

Object Collaboration

Sales ClerkSystem 1. Fill in retailer’s number2. Show retailer’s details. ** Set up a new order. 3. Inputs design number4. Retrieve and display garment price, size range and description 5. Input design no, quantity and size6. Write order line with order no, design no, quantity and size. Write ‘quantity’ new instances of garment with status ‘not started’. Display accumulated price. Display new set of orderliness. 7. Indicate finished8. Enable ‘confirm order’ button. 9. Order confirmed10. Order saved. Happy path ** New retailer is now an alternate path!

Elaborate Steps 1 & 2 1.Control class RegisterNewOrder displays OrderUI. –Sales clerk responds Uses OrderUI to enter the retailer’s number 2.System responds: –RecordOrder requests retailer info from Retailer. –If successful, requests constructor on order, giving retailer number and waiting for order number in response.

3.Signals to OrderUI to display order number and value. 4.Sales clerk responds Clicks AddLine on OrderUI 5.RecordOrder displays DesignUI 6.Sales Clerk responds –Enters Design number RecordOrder requests design info from Design. –If successful, Sends info to DesignUI DesignUI –displays info –Waits for size and quantity –enables buttons. –Awaits confirmation…

Continue building… Invent your classes as you go.

Messages… NoMessageFrom classTo class 1Enter CustomerIdSales clerkOrderUI 2GetRetailerOrderUIRegisterNewOrder 3Get CustomerRegisterNewOrderRetailer 4DisplayCustomerRegisterNewOrderOrderUI 5AddOrderRetailerRetailer Order 6AddGarmentSales ClerkOrderUI 7DisplayOrderUIDesignUI

…Messages… NoMessageFrom classTo class 8Enter DesignSales ClerkDesignUI 9PickDesignDesignUIRegisterNewOrder 10Get DesignRegisterNewOrderDesign 11Show DesignRegisterNewOrderDesignUI 12EnterSize and Quantity Sales ClerkDesignUI 13EnableOrderDesignUI 14ConfirmLineSales ClerkDesignUI

…Messages NoMessageFrom classTo class 15OrderDesignSizeDesignUIRegisterNewOrder 16AddaLineRegisterNewOrderRetailerOrderLine 17DisplayLine+TotalsRegisterNewOrderOrderUI 18ConfirmOrderSales ClerkOrderUI 19ConfirmOrderOrderUIRegisterNewOrder 20ConfirmOrderRegisterNewOrderRetailer Order

Collaboration Diagram Is another illustration of the interaction between objects during a Use Case. Classes are shown as icons on the diagram. Classes that collaborate are linked. The links are populated with messages, showing the operation that the sender invokes on the recipient.

Making a Collaboration diagram Identify the objects involved –Sales Clerk, OrderUI, RegisterNewOrder, Retailer, Retailer Order, Retailer Order Line, DesignUI, Design. Arrange them in layers. Link all objects that communicate with each other. Add the messages.

The objects added to the diagram

The objects as icons, in layers

The objects communicating

Collaboration Diagram

Adding the garment class

Messages… NoMessageFrom classTo class 1Enter CustomerIdSales clerkOrderUI 2GetRetailerOrderUIRegisterNewOrder 3Get CustomerRegisterNewOrderRetailer 4DisplayCustomerRegisterNewOrderOrderUI 5AddOrderRetailerRetailer Order 6AddGarmentSales ClerkOrderUI 7DisplayOrderUIDesignUI

…Messages… NoMessageFrom classTo class 8Enter DesignSales ClerkDesignUI 9PickDesignDesignUIRegisterNewOrder 10Get DesignRegisterNewOrderDesign 11Show DesignRegisterNewOrderDesignUI 12EnterSize and Quantity Sales ClerkDesignUI 13EnableOrderDesignUI 14ConfirmLineSales ClerkDesignUI

…Messages NoMessageFrom classTo class 15OrderDesignSizeDesignUIRegisterNewOrder 16AddaLine*RegisterNewOrderRetailerOrderLine 17DisplayLine+TotalsRegisterNewOrderOrderUI 18ConfirmOrderSales ClerkOrderUI 19ConfirmOrderOrderUIRegisterNewOrder 20ConfirmOrderRegisterNewOrderRetailer Order * This version omits the creation of garment instances – see later

…Messages NoMessageFrom classTo class 15OrderDesignSizeDesignUIRegisterNewOrder 16AddaLine*RegisterNewOrderRetailerOrderLine 16aAddAGarmentRetailerOrderLineGarment 17DisplayLine+TotalsRegisterNewOrderOrderUI 18ConfirmOrderSales ClerkOrderUI 19ConfirmOrderOrderUIRegisterNewOrder 20ConfirmOrderRegisterNewOrderRetailer Order

Refining the OCD 2. Separate out reusable functionality into another control class. There are a group of messages that only use the DesignUI boundary class and the Design entity. –Introduce a new control class called OrderDesign. –The main control class invokes OrderDesign. –OrderDesign acts as ‘go-between’ between the DesignUI and the Design entity. –When all functionality relating to picking a quantity of a particular design has been completed, OrderDesign hands control back to RegisterNewOrder.

Contained functionality Msge no MessageFrom classTo class 11Show DesignOrderDesignDesignUI 12EnterSize and Quantity Sales ClerkDesignUI 13EnableOrderDesignUI 14ConfirmLineSales ClerkDesignUI 15OrderDesignSizeDesignUIOrderDesign

Make all the messages in a happy path step be increments of the step. –To do this, you need to Check the model properties to ensure that hierarchical numbering is enabled on diagrams. Create the Sequence diagram from the OCD. Move the messages so that they originate in the lifeline that has been created by the previous message in the group.

Messages… NoMessageFrom classTo class 1Enter CustomerIdSales clerkOrderUI 1.1GetRetailerOrderUIRegisterNewOrder 1.1.1Get CustomerRegisterNewOrderRetailer 1.1.2DisplayCustomerRegisterNewOrderOrderUI AddOrderRetailerRetailer Order 2AddGarmentSales ClerkOrderUI 2.1PickDesignOrderUIRegisterNewOrder 2.1.1AddOrderLineRegisterNewOrderOrderDesign DisplayOrderDesignDesignUI

…Messages… NoMessageFrom classTo class 3Enter DesignSales ClerkDesignUI 3.1GetDesignDesignUIOrderDesign 3.1.1Get DesignOrderDesignDesign 3.1.2DisplayOrderDesignDesignUI 4.EnterSize and Quantity Sales ClerkDesignUI 4.1EnableOrderDesignUI 4.2ShowsubtotalDesignUI

…Messages NoMessageFrom classTo class 5.ConfirmLineSales ClerkDesignUI 5.1AddOrderLineDesignUIOrderDesign 5.1.1OrderDesignSize RegisterNewOrder AddALineRegisterNewOrderRetailerOrderLine AmendOrderRetailerOrderLineRetailerOrder * This version omits the creation of garment instances – see later

…Messages… NoMessageFrom classTo class Create garmentRetailerOrderLineGarment DisplayLine and total RegisterNewOrderOrderUI 6.ConfirmOrderSales ClerkOrderUI 6.1ConfirmOrderOrderUIRegisterNewOrder 6.1.1ConfirmOrderRegisterNewOrderRetailer Order