Fall 2009ACS-3913 Ron McFadyen1 Instances & Object Diagrams Joe: Customer Class instances/ Objects An individual object (instance of a class) is shown.

Slides:

Advertisements

Similar presentations

Winter 2007ACS-3913 Ron McFadyen1 Duck Example Consider the text example (up to page 6). Each type of duck is a subclass of Duck Most subclasses implement.

Advertisements

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

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.

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

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

Fall 2009ACS-3913 Ron McFadyen Composite Pattern Problem: How do we treat a composition structure of objects the same way as a non-composite object? Arises.

Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor, the one who initiates Each.

Sequence Diagram Objects are represented horizontally across the top of the diagram Each object has a lifeline some exist before and/or after some are.

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.

Fall 2009ACS-3913 Ron McFadyen1 Decorator Pattern The Decorator pattern allows us to enclose an object inside another object. The enclosing object is called.

Fall 2009ACS-3913 Ron McFadyen1 Observer Problem: There are many objects (subscribers) needing to know of the state changes, or events, of another object.

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

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

Nov Ron McFadyen1 Figure The Observer Pattern in a DCD.

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

Fall 2007ACS-1805 Ron McFadyen1 Boolean functions & expressions A boolean function is one that returns true or false The guidelines for class-level methods.

Spring 2010ACS-3913 Ron McFadyen1 Command The complex remote control (many pairs of buttons; null command) Undo … pages 216+ Macro … pages 224+

Fall 2007ACS-1805 Ron McFadyen1 Chapter 7 Repetition.

Fall 2007ACS-1805 Ron McFadyen1 Ch 7 Loops Alice has two control structures for controlling the repeated execution of statements Loop While.

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

Winter 2007ACS-3913 Ron McFadyen1 Classes Represented by a rectangle with possibly 3 compartments Customer Name Address Customer Name Address getName()

Spring 2010ACS-3913 Ron McFadyen1 Command The command pattern encapsulates a request or unit of work into an object. An invoker will ask a concrete command.

Object Interaction Models - Review The use case and its scenarios serve as a vehicle for organizing the object interactions that take place. Each scenario.

2007ACS-3913 R. McFadyen1 UML Statechart Diagram A UML Statechart Diagram describes states for an object how/why an objects’ state changes A Statechart.

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

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 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.

Winter 2007ACS-3913 Ron McFadyen1 Observer Pattern Problem: There are many objects (observers / subscribers) needing to know of the state changes, or events,

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.

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.

Fall 2007ACS-1805 Ron McFadyen1 Chapter 6 Functions & If/Else.

Winter 2011ACS-3913 Ron McFadyen1 Decorator Sometimes we need a way to add responsibilities to an object dynamically and transparently. The Decorator pattern.

Fall 2007ACS-1805 Ron McFadyen1 Chapter 3 Programming.

Spring 2010ACS-3913 Ron McFadyen1 Duck Example Consider the text example (up to page 6). Each type of duck is a subclass of Duck Most subclasses implement.

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.

Creating Entity Relationship Diagrams. Identify data stores The data stores are easy to identify if you have already created a data flow diagram If you.

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

BTS430 Systems Analysis and Design using UML Interaction Diagrams.

Sept Ron McFadyen1 Class Diagram Begins as a conceptual or analysis class model and evolves to a design class model Used throughout the development.

Interaction Diagram Notation

2007ACS-3913 Ron McFadyen1 Class Diagram See Schaum’s UML Outline, especially chapters 4, 5, 6, 7.

10 October, 2007Information System Design IT60105, Autumn 200 Information System Design IT60105 Lecture 17 Collaboration Diagrams.

Collaboration diagrams. Purpose A collaboration diagram is an alternate way to show a scenario. A collaboration diagram shows the objects and relationships.

Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.

Source Page US:official&tbm=isch&tbnid=Mli6kxZ3HfiCRM:&imgrefurl=

UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.

Путешествуй со мной и узнаешь, где я сегодня побывал.

Sept Ron McFadyen1 Include Relationship UC1:Process Sale … Main Success Scenario … 7. Customer pays and System handles payment. … Extensions.

What is the standard form of the number shown in exponential notation?

Chapter 11: Collaboration Diagram - PART1

Communication DIAGRAM

Page 1. Page 2 Page 3 Page 4 Page 5 Page 6 Page 7.

Requirements To Design In This Iteration

Minidimension Example

Communication DIAGRAM

Graphical User Interfaces in Java Event-driven programming

Chapter 2 Role of Information Systems in Organizations Link 2

Instructor: Ron McFadyen 3D

Class Diagram Begins as a conceptual or analysis class model and evolves to a design class model Used throughout the development process. More detail added.

Decorator Pattern The decorator pattern allows us to enclose an object inside another object. The enclosing object is called a decorator. The other object.

Event-driven programming

Page 37 Figure 2.3, with attributes excluded

Recursive Relationship

UML Interaction Diagrams

Presentation transcript:

Fall 2009ACS-3913 Ron McFadyen1 Instances & Object Diagrams Joe: Customer Class instances/ Objects An individual object (instance of a class) is shown as a rectangle with naming information underlined See Schaum’s Outline page 134 An unnamed customer : Customer A customer named Joe

Fall 2009ACS-3913 Ron McFadyen2 Diagramming notation :sale s4:sale A sale object named s4 An unnamed sale object s4 An object named s4 Object instances appear in sequence and object diagrams.

Fall 2009ACS-3913 Ron McFadyen3 Connections between Objects sam:CarSharer toWork:Journey visitMother:Journey home:Address mothersHouse:Address work:Address Registers StartsAt EndsAt Related objects are connected with a link. Readability shows direction of the link. Note that each object appears once.

Fall 2009ACS-3913 Ron McFadyen4 Connections between Objects sam:CarSharer toWork:Journey visitMother:Journey home:Address mothersHouse:Address work:Address Registers StartsAt EndsAt Directed lines show direction of the link.