Presentation is loading. Please wait.

Presentation is loading. Please wait.

April 3, 200291.3913 R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..*

Published by Modified over 9 years ago

Similar presentations

Presentation on theme: "April 3, 200291.3913 R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..*"— Presentation transcript:

1 April 3, 200291.3913 R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..* Assignment 3 Question 1

2 April 3, 200291.3913 R McFadyen2 BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..* Find all persons waiting at any bus stop on a bus route Collaborating classes: Assignment 3 Question 1

3 April 3, 200291.3913 R McFadyen3 BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..* Suppose the class model is modified to incorporate Villages: VillageList Village villages 0..* Assignment 3 Question 1

4 April 3, 200291.3913 R McFadyen4 class BusRoute { VillageList villages; void printWaitingPassengers () { villages->printWaitingPassengers (); } } class Village { BusStopList busstops; void printWaitingPassengers () { busstops->printWaitingPassengers (); } } class VillageList { Village villages[]; void printWaitingPassengers () { for (int i = 0; i < stops.length; i++) villages[i].printWaitingPassengers (); } Assignment 3 Question 1

5 April 3, 200291.3913 R McFadyen5 class BusStop { PersonList waiting; void printWaitingPassengers () { waiting.print (); } } class PersonList { Person people[]; void print () { for (int i = 0; i < people.length; i++) people[i].print (); } } class Person { String name; void print () { System.stdout.println (name); } } Assignment 3 Question 1

6 April 3, 200291.3913 R McFadyen6 :BusRoute :BusStopList :BusStop:PersonList:Person : VillageList: Village printWaitingPassengers () *printWaitingPassengers () printWaitingPassengers () *printWaitingPassengers () printWaitingPassengers () *print () printWaitingPassengers () Note: use of multiobjects, lifelines, names of messages/methods Assignment 3 Question 1

7 April 3, 200291.3913 R McFadyen7 Q 2. a AW1:AlarmWindowAC1:AlarmClock Alarmlisteners:Object 1:addAlarmListener(AW1) 1.1:add (AW1) B1:BeeperAC1:AlarmClock Alarmlisteners:Object 1:addAlarmListener(B1) 1.1:add (B1) Similar to Fig23.22 … subscribing

8 April 3, 200291.3913 R McFadyen8 Q 2. b AC1:AlarmClockAlarmlisteners:Object publishAlarmEvent onAlarmEvent setTime Note names of the messages and the names of the methods in the class model Similar to Fig23.23 … the alarm clock notifying its list of listeners

9 April 3, 200291.3913 R McFadyen9 Q 2. b AW1:AlarmWindow:field onAlarmEvent Note names of the messages and the names of the methods in the class model Similar to Fig23.24 … the alarm window displaying its alarm displayAlarm()

10 April 3, 200291.3913 R McFadyen10 Q 2. b B1:Beeper onAlarmEvent Note names of the messages and the names of the methods in the class model Similar to Fig23.24 … the beeper making its sound beep()

11 April 3, 200291.3913 R McFadyen11 Q 2. c AW1:AlarmWindowAC1:AlarmClock Alarmlisteners:Object 1:removeAlarmListener(AW1) 1.1:remove (AW1) B1:BeeperAC1:AlarmClock Alarmlisteners:Object 1: remove AlarmListener(B1) 1.1: remove (B1) Similar to Fig23.22 … unsubscribing Object is removed from the list of listeners – opposite of subscribing

12 April 3, 200291.3913 R McFadyen12 Q 3 :Store pc:ProductCatalog :ProductSpecification ps:ProductSpecification :Register create *:create *:add loadProdSpecs create Note that repetition is shown for two messages Note the activation box that is the origin for the repeated messages

13 April 3, 200291.3913 R McFadyen13 Q 4 Pmt:CreditPayment Cas:Object :ServicesFactory as:Object 1:requestApproval() authorize Note the associations and the direction indicators Note the numbering 2.3:postReceivable() 2.1:getAccountingService() 2.2:postSale() 2[reply.isApproved]:handleApproval()

Download ppt "April 3, 200291.3913 R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..*"

Similar presentations

Winter 2007ACS-3913 Ron McFadyen1 Also known as publish/subscribe The essence of this pattern is that one or more objects (called observers or listeners)

Winter 2007ACS-3913 Ron McFadyen1 Also known as publish/subscribe The essence of this pattern is that one or more objects (called observers or listeners)
February 200592.3913 R. McFadyen1 Polymorphism Indirection Pure Fabrication Protected Variations (Law of Demeter) More GRASP Patterns.

February R. McFadyen1 Polymorphism Indirection Pure Fabrication Protected Variations (Law of Demeter) More GRASP Patterns.
Interaction Diagrams CS 124. Object collaboration A use case carried out involves objects and interaction or collaboration between these objects Method.

Interaction Diagrams CS 124. Object collaboration A use case carried out involves objects and interaction or collaboration between these objects Method.
Jan 29, 200391.3913 Ron McFadyen1 UML Class Diagram Examples Based on well-known patterns Exhibit ways of providing dynamic structures and behaviour.

Jan 29, Ron McFadyen1 UML Class Diagram Examples Based on well-known patterns Exhibit ways of providing dynamic structures and behaviour.
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,
October 200391.3913 R. McFadyen1 Polymorphism Indirection Pure Fabrication Protected Variations (Law of Demeter) Ch 22: More GRASP Patterns.

October R. McFadyen1 Polymorphism Indirection Pure Fabrication Protected Variations (Law of Demeter) Ch 22: More GRASP Patterns.
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.
Oct 200291.3913 R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..*

Oct R McFadyen1 Recall UML Class Diagram BusRoute BusStopList BusStop BusList BusPersonList Person passengers buses busStops waiting 0..*
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.
March 200391.3913 Ron McFadyen1 Observer P. 368+ Also known as Publish-Subscribe Applied in order to implement the Model-View Separation principle (see.

March Ron McFadyen1 Observer P Also known as Publish-Subscribe Applied in order to implement the Model-View Separation principle (see.
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.
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 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,

Fall 2009ACS-3913 Ron McFadyen1 Design Class Diagrams n Class diagram with – classes – associations – attributes – methods – navigability – interfaces,
Spring 2010ACS-3913 Ron McFadyen1 Weather Station Page 39+ In this application, weather station devices supply data to a weather data object. As the data.

Spring 2010ACS-3913 Ron McFadyen1 Weather Station Page 39+ In this application, weather station devices supply data to a weather data object. As the data.
3/7/2003Bioinformatics1 How To Address Rapidly Changing Data Representations in an Evolving Scientific Domain Using Aspect-oriented Programming Techniques.

3/7/2003Bioinformatics1 How To Address Rapidly Changing Data Representations in an Evolving Scientific Domain Using Aspect-oriented Programming Techniques.
January 200491.3913 Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.

January Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Elaboration Iteration 1: a simple cash-only success scenario of.
Sept 2003 91.3913 Ron McFadyen Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor,

Sept Ron McFadyen Sequence Diagram Objects are represented horizontally across the top of the diagram The first object is typically an Actor,
Nov 200391.3913 Ron McFadyen1 Figure 23.21 The Observer Pattern in a DCD.

Nov Ron McFadyen1 Figure The Observer Pattern in a DCD.
March 200692.3913 R. McFadyen1 Principle of Least Knowledge – page 265 Principle: talk only to your immediate friends Also called Law of Demeter (LoD)

March R. McFadyen1 Principle of Least Knowledge – page 265 Principle: talk only to your immediate friends Also called Law of Demeter (LoD)

Similar presentations

Ads by Google