Presentation is loading. Please wait.

Presentation is loading. Please wait.

Jan 23, 200291. 3913 Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented.

Published by Modified over 9 years ago

Similar presentations

Presentation on theme: "Jan 23, 200291. 3913 Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented."— Presentation transcript:

1 Jan 23, 200291. 3913 Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented programming when we say a message foo invokes the method foo

2 Jan 23, 200291. 3913 Ron McFadyen2 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented programming when we say a message foo invokes the method foo We’ll refer to this as the enterItem system operation

3 Jan 23, 200291. 3913 Ron McFadyen3 Messages sent for enterItem( … ) Figures 17.8, 20.6 This diagram shows a collaboration among objects. The collaboration is a sequence of messages. They occur in response to the system event enterItem. We’ll explain this diagram, but note that we’ll study the notation more thoroughly in future lectures

4 Jan 23, 200291. 3913 Ron McFadyen4 Messages sent for enterItem( … ) Figures 17.8, 20.6 The messages are sent in the order: 1, 1.1, 2, 2.1, 2.2.

5 Jan 23, 200291. 3913 Ron McFadyen5 Messages sent for enterItem( … ) Figures 17.8, 20.6 The diagram would be created if the designer thought the illustration would be useful … to communicate to someone how the system will work.

6 Jan 23, 200291. 3913 Ron McFadyen6 Messages sent for enterItem( … ) Figures 17.8, 20.6 The system operation is received by the Register object. On page 314 you’ll note that Register has an enterItem method.

7 Jan 23, 200291. 3913 Ron McFadyen7 Messages sent for enterItem( … ) Figures 17.8, 20.6 The register object sends a message to the product catalogue. (The register will eventually tell the sale object to create a line for this.)

8 Jan 23, 200291. 3913 Ron McFadyen8 Messages sent for enterItem( … ) Figures 17.8, 20.6 The catalogue will search the catalogue data structure for the item that was scanned at the register. Note that on Page 314 the Java code only has to invoke the get method for the HashMap.

9 Jan 23, 200291. 3913 Ron McFadyen9 Messages sent for enterItem( … ) Figures 17.8, 20.6 The sale object is sent a message that will cause it to create a new sales line

10 Jan 23, 200291. 3913 Ron McFadyen10 Messages sent for enterItem( … ) Figures 17.8, 20.6 A new sales line is created

11 Jan 23, 200291. 3913 Ron McFadyen11 Messages sent for enterItem( … ) Figures 17.8, 20.6 The newly created sales line will be added to the collection of lines belonging to this sale.

12 Jan 23, 200291. 3913 Ron McFadyen12 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3

13 Jan 23, 200291. 3913 Ron McFadyen13 Contracts A technique for describing system operations in terms of state changes to objects in a Domain Model major proponent - Bertrand Meyer based on concept of assertion a statement, a declaration, that must be true a false value indicates a bug UML has OCL - very formal syntax which we will ignore at the requirements gathering stage, these are informal and likely incomplete

14 Jan 23, 200291. 3913 Ron McFadyen14 Contracts Contract Components Operation - name and parameters Cross References - where operation used Preconditions - assumptions about the state of the system or Domain Model objects Postconditions - state of objects after the operation completes objects:any new ones? any attributes modified? associations: any new or modified associations? Larman’s version is very informal - focus on what, not how

15 Jan 23, 200291. 3913 Ron McFadyen15 SalesLineItem quantity Product Specification itemID Sale 1 1..* * 1Described by Contained in The part of the Domain Model that is relevant to enterItem( )

16 Jan 23, 200291. 3913 Ron McFadyen16 Contracts Example Operation enterItem (itemID : ItemID, quantity : integer) Cross References Use Case Process Sale PreconditionsThere is a sale underway Postconditions - a SalesLineItem instance was created - an association between the sale and the sales line item was created - an attribute, quantity, was modified - an association between the product specification and the sales line item was created

17 Jan 23, 200291. 3913 Ron McFadyen17 OCL Object Constraint Language UML has a formal language for specifying constraints on object-oriented models context Salesperson:: sell ( item: Thing ) : Real pre: self.sellableItems -> includes (item) post: not self.sellableItems -> includes (item) and result=item.price

18 Jan 23, 200291. 3913 Ron McFadyen18 Ch 15. Interaction Diagrams Now, we are shifting towards design - how do the objects in the model interact? Interaction Diagram - illustrates how objects collaborate to fulfill requirements - the messages that are sent from one object to another collaboration diagrams sequence diagrams

19 Jan 23, 200291. 3913 Ron McFadyen19 SalesLineItem quantity Product Specification itemID Sale makePayment() 1 1..* * 1Described by Contained in More of the Domain Model - we’ve included some methods Register makePayment() Payment create() 1 * 1 1 Captured on Paid by

20 Jan 23, 200291. 3913 Ron McFadyen20 Figure 15.3 Collaboration Diagram

21 Jan 23, 200291. 3913 Ron McFadyen21 Figure 15.4 Sequence Diagram

Download ppt "Jan 23, 200291. 3913 Ron McFadyen1 SSD for a samplePOS Use Case Figure 13.1 Input Events invoke a system operation of the same name same idea as in object-oriented."

Similar presentations

Object Design Examples with GRASP

Object Design Examples with GRASP
91.3913Feb 2003 R McFadyen1 Contracts (Ch 13) Used to help understand requirements more completely based on assertions; assertions are applicable to any.

Feb 2003 R McFadyen1 Contracts (Ch 13) Used to help understand requirements more completely based on assertions; assertions are applicable to any.
Jan 15, 200391. 3913 Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.

Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.
Sept 2003 91.3913 Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.

Sept Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.
Oct 200391.3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Oct 22, 200291.3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

Oct 22, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
March 200391.3913 Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.

March Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.
Jan 200591.3913 Ron McFadyen1 Consider a simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase.

Jan Ron McFadyen1 Consider a simple cash-only Process Sale scenario 1. Customer arrives at a POS checkout with goods and/or services to purchase.
Fall 2009AXS-3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Fall 2009AXS-3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Oct 200391.3913 Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns P. 248: “The assignment of responsibilities and design of collaborations.

Oct Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns P. 248: “The assignment of responsibilities and design of collaborations.
Object-Oriented Analysis and Design

Object-Oriented Analysis and Design
92.3913Jan 2005 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;

Jan 2005 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;
Sept 2003 91.3913 Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.

Sept Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.
NJIT Use Case Model Operation Contracts Prepared By: Sumit Sharma.

NJIT Use Case Model Operation Contracts Prepared By: Sumit Sharma.
ACS-3913Fall 2009 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;

ACS-3913Fall 2009 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;
Oct 200391.3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Oct Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.
Feb 200592.3913 Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

Feb Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.
91.3913September 2002 R McFadyen1 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3.

September 2002 R McFadyen1 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3.
Object-Oriented Analysis and Design

Object-Oriented Analysis and Design
November 200491.3913 Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

November Ron McFadyen Visibility Visibility: the ability of one object to see or have a reference to another object. e.g. When a register object.

Similar presentations

Ads by Google