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.

Slides:

Advertisements

Similar presentations

Object-Oriented Analysis and Design CHAPTERS 15: UML INTERACTION DIAGRAMS 1.

Advertisements

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

Jan 15, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration: a simple cash-only success scenario of Process Sale.

Jan 23, 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.

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, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

Jan Ron McFadyen1 Singleton To guarantee that there is at most one instance of a class we can apply the singleton pattern. Singleton Static.

March Ron McFadyen1 Ch 17: Use Case Realizations with GRASP Patterns Assigning responsibilities to objects to achieve user goals Section 17.4.

Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together to achieve some functionality.

Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.

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.

Sept Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.

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

Fall 2009ACS-3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

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

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

Sept Ron McFadyen Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor,

Sept Ron McFadyen Interaction Diagrams - Chapter 15 Describe/illustrate sequence of message exchanges among objects that are working together.

Oct 21, R. McFadyen1 Pure Fabrication P Problem: You have a responsibility to assign to a class, but assigning it to a class in the conceptual.

Essentials of interaction diagrams Lecture Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.

Fall 2009ACS Ron McFadyen1 The context maintains an instance of a concrete state subclass State Pattern Each subclass (concrete state) implements.

ACS-3913Fall 2009 Ron McFadyen1 Contracts Used to help understand requirements more completely (and so may not always be necessary) based on assertions;

October 16, 2001Class Diagrams1. October 16, 2001Class Diagrams2 (Design) Class Diagrams (1) zA class diagram is a visual representation of various classes.

Feb 4, Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – (interfaces,

Oct Ron McFadyen1 Collaborations Collaboration : an arrangement of classes, links, roles in a context to implement some behaviour. Useful for.

Feb Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

September 2002 R McFadyen1 Domain Model Use Case Model text diagram SSD System operation contracts Design Model Figure 13.3.

November Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,

Fall 2009ACS-3913 R. McFadyen1 Protected Variations Principle: How do you design so that variations in the future do not have an undesirable affect on.

Object-Oriented Analysis and Design

NJIT Designing for Visibility Chapter 19 Applying UML and Patterns Craig Larman.

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.

Oct R. McFadyen1 Statechart Diagrams Example: Suppose we have a class Copy, representing copies of books. We can consider two states: available,

Sept Ron McFadyen1 Extend Relationship.

Winter 2007ACS-3913 Ron McFadyen1 Singleton To guarantee that there is at most one instance of a class we can apply the singleton pattern. Singleton Static.

Designing with Interaction and Design Class Diagrams Chapters 15 & 16 Applying UML and Patterns Craig Larman With some ideas from students in George Blank’s.

Object-Oriented Analysis and Design

Relationships. In the Interaction diagrams, we began to look at how classes communicate with one another. Now, we'll focus on the relationships between.

Objectives Design Class Diagrams Issues in system design Generalization Review UML papers.

Chapter 2 (Horstmann’s Book) – Part 2 The Object-Oriented Design Process Hwajung Lee.

Object Design Examples with GRASP (Ch. 18)

Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.

Design Class Diagrams (DCDs)

Chapter 16 Applying UML and Patterns Craig Larman

NJIT UML Class Diagrams Chapter 16 Applying UML and Patterns Craig Larman.

Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.

Fall 2009ACS-3913 Ron McFadyen1 Use Case Realizations with GRASP Patterns “The assignment of responsibilities and design of collaborations are very important.

Object-Oriented Analysis and Design Week 11, 2009.

INFO 620Lecture #71 Information Systems Analysis and Design Design Class Diagrams and others INFO 620 Glenn Booker.

OO Methodology Elaboration Phase Iteration 1- Part 3.

TK2023 Object-Oriented Software Engineering CHAPTER 11 CLASS DIAGRAMS.

Use-Case Model: Adding Detail with Operation Contracts.

BTS430 Systems Analysis and Design using UML Design Class Diagrams (ref=chapter 16 of Applying UML and Patterns)

 The Sequence Diagram models the collaboration of objects based on a time sequence.  It shows how the objects interact with others in a particular scenario.

Oct 3, Ron McFadyen1 GRASP Patterns 1.Expert 2.Creator 3.Controller 4.Low Coupling 5.High Cohesion.

Design Model: Determining Visibility CH-18. Objectives Identify four kinds of visibility. Design to establish visibility. Illustrate kinds of visibility.

Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.

Mapping Designs to Code. It specify how to map the design into object oriented language The UML artifacts created during the design work, the interaction.

System Sequence Diagrams and Operation Contracts

UML Class Diagrams (more notation)

Used to help understand requirements more completely

Chapter 16 UML Class Diagrams.

GRASP: Visibility and Design

Chapter 10: Visibility Chapter 18 in Applying UML and Patterns Book.

Chapter 20 Applying UML and Patterns Craig Larman

Chapter 11: Class Diagram

Object Oriented System Design Class Diagrams

Page 37 Figure 2.3, with attributes excluded

Design Model: Creating Design Class Diagrams

Presentation transcript:

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 sends a message to a sale object, the register must have visibility to the sale. enterItem() :Register:Sale 2:makeLineItem() Register has to know about sale in order to send this message. The sale must be visible to the register. Ch 18

Oct Ron McFadyen Figure 18.1 Visibility from Register to Product Catalogue is required due to the collaboration diagram Visibility

Oct Ron McFadyen Visibility Visibility from A to B can occur in four ways: Attribute B is an attribute of A Parameter B is a parameter of a method of A Local B is a non-parameter local object in a method of A Global B is globally visible

Oct Ron McFadyen Figure 18.2 Attribute Visibility Register has an attribute that holds the reference to the catalog, and so register has attribute visibility to the Product Catalog. This is very common.

Oct Ron McFadyen Figure 18.3 Parameter Visibility In our collaboration, register asks the product catalog to find a specific product specification. The catalog returns the product specification to the register, and register passes that on the sale. Sale will just pass that product specification on to the sales line item, and so the sale only has parameter visibility to the product specification

Oct Ron McFadyen Figure 18.4 from Parameter to Attribute visibility

Oct Ron McFadyen Figure 18.5 Local Visibility The enterItem method of Register has an attribute that will hold a product specification. When the method ends, the attribute value is lost. Visibility here is temporary – while the method executes. The visibility is local to the method.

Oct Ron McFadyen Figure 18.4 showing visibility in the UML

Oct Ron McFadyen Preview Figure DCD with dependency relationships indicating non-attribute visibility

Oct Ron McFadyen Preview Figure DCD with dependency relationships indicating non-attribute visibility Dependency of Sale on Product Specification is shown with a dashed directed line. Sale has parameter visibility to Product Specification Dependency of Register on Product Specification is shown with a dashed directed line. Register has local visibility to Product Specification – register’s enterItem method gets a reference to a product specification and passes that on to the sale Attribute Dependencies are shown with the solid directed lines