Modeling With Classes - Chpater 5 Of The Text Book - Updated 19-9-08

Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 5: Modelling with Classes

5.1 What is UML? The Unified Modelling Language is a standard graphical language for modelling object oriented software • At the end of the 1980s and the beginning of 1990s, the first object-oriented development processes appeared • The proliferation of methods and notations tended to cause considerable confusion • Two important methodologists Rumbaugh and Booch decided to merge their approaches in 1994. — They worked together at the Rational Software Corporation • In 1995, another methodologist, Jacobson, joined the team —© Lethbridge/Laganière Chapter Modelling 2 His work focused on 5: use caseswith classes 2001

UML diagrams •Class diagrams — describe classes and their relationships •Interaction diagrams — show the behaviour of systems in terms of how objects interact with each other •State diagrams and activity diagrams — show how systems behave internally •Component and deployment diagrams — show how the various components of systems are arranged logically and Chapter 5: Modelling with classes physically © Lethbridge/Laganière 2001

3

UML features •It has detailed semantics •It has extension mechanisms •It has an associated textual language — Object Constraint Language (OCL) The objective of UML is to assist in software development — It is not a methodology

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

4

What constitutes a good model? A model should •use a standard notation •be understandable by clients and users •lead software engineers to have insights about the system •provide abstraction Models are used: •to help create designs •to permit analysis and review of those designs. •as the core documentation describing Chapter 5: Modelling with classes 5 © Lethbridge/Laganière 2001 the system.

5.2 Essentials of UML Class Diagrams The main symbols shown on class diagrams are: •Classes - represent the types of data themselves

•Associations

- represent linkages between instances of classes

•Attributes

- are simple data found in classes and their instances

•Operations

- represent the functions performed by the classes and their instances

Chapter © Lethbridge/Laganière 2001 •Generalizations

5: Modelling with classes

6

Classes A class is simply represented as a box with the name of the class inside •The diagram may also show the attributes and operations •The complete signature of an operation is: operationName(parameterName: parameterType …): returnType

Rectangle

Rectangle getArea resize

© Lethbridge/Laganière 2001

Rectangle height width

Rectangle

Rectangle

height width

height: int width: int

getArea resize

getArea(): int resize(int,int)

Chapter 5: Modelling with classes

7

5.3 Associations and Multiplicity An association is used to show how two classes are related to each other •Symbols indicating multiplicity are shown at each end of the association Employee

*

Secretary

*

Company 1..**

Company

Office

Person

Manager

BoardOfDirectors 0..1

0,3..8

© Lethbridge/Laganière 2001

*

*

Employee

BoardOfDirectors

Chapter 5: Modelling with classes

8

Labelling associations •Each association can be labelled, to make explicit the nature of the worksFor association Employee * Company Secretary

*

1..** supervisor

Company

Office

Person

Manager

BoardOfDirectors 0..1

0,3..8

allocatedTo

*

*

Employee

BoardOfDirectors

boardMember © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

9

Analyzing and validating associations •Many-to-one — A company has many employees, — An employee can only work for one company.

- This company will not store data about the moonlighting activities of employees!

— A company can have zero employees - E.g. a ‘shell’ company

— It is not* possibleworksFor to be an Employee employee unless you work for a company © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

Company

10

Analyzing and validating associations •Many-to-many — A secretary can work for many managers — A manager can have many secretaries — Secretaries can work in pools — Managers can have a group of secretaries — Some managers might have zero secretaries. 1..** Secretary * Manager — Is it possible for a secretary supervisor to have, perhaps temporarily, zero managers? © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

11

Analyzing and validating associations •One-to-one — For each company, there is exactly one board of directors — A board is the board of only one company — A company must always have a board — A board must always be of some Company BoardOfDirectors company

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

12

Analyzing and validating associations Avoid unnecessary one-to-one associations Person

Avoid PersonInfo this

name

© Lethbridge/Laganière 2001

address email birthdate

do this Person name address email birthdate

Chapter 5: Modelling with classes

13

A more complex example •A booking is always for exactly one passenger — no booking with zero passengers — a booking could never involve more than one passenger. •A Passenger can have any number of Bookings — a passenger could have no bookings at all * * Passenger Booking SpecificFlight — a passenger could have more than one booking © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

14

Association classes •Sometimes, an attribute that concerns two associated classes cannot be placed in either of the classes •Association itself is modeled as a class * * CourseSection Student •The following are equivalent Registration grade

Student

*

Registration *

CourseSection

grade

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

15

Reflexive associations •It is possible for an association to connect a class to itself

successor *

*

Course *

isMutuallyExclusiveWith

* prerequisite

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

16

Directionality in associations •Associations are by default bidirectional •It is possible to limit the direction of an association by adding an arrow at one end

Day

© Lethbridge/Laganière 2001

*

Note

Chapter 5: Modelling with classes

17

Avoiding unnecessary generalizations Inappropriate hierarchy of classes, which should be Instances Something should be different

© Lethbridge/Laganière 2001

Recording

VideoRecoding

MusicVideo

JazzRecording

AudioRecording

ClassicalRecording

BluesRecording

Chapter 5: Modelling with classes

RockRecording

18

Avoiding unnecessary generalizations Inappropriate hierarchy of classes, which should be Instances Something should be different Recording * title artist

hasCategory

Recording

VideoRecoding

MusicVideo

RecordingCategory description

© Lethbridge/Laganière 2001

* subcategory

JazzRecording

AudioRecording

ClassicalRecording

BluesRecording

RockRecording

Improved class diagram

Chapter 5: Modelling with classes

19

5.4 Generalization Specializing a superclass into two or more subclasses •The discriminator is a label that describes the criteria used in the specialization •Can be thought of an attribute that will have a different value in each subclass. Animal Animal •The differences in properties of typeOfFood habitat discriminated classes – attributes, operations, or associations AquaticAnimal

LandAnimal

© Lethbridge/Laganière 2001

Carniv ore

Herbiv ore

Chapter 5: Modelling with classes

20

Handling multiple discriminators •Creating higher-level

Drawbacks:

Properties associated with generalization both discriminators have to be present

Animal

No. of classes can grow very large

habitat

AquaticAnimal typeOfFood

AquaticCarniv ore

typeOfFood

AquaticHerbiv ore

© Lethbridge/Laganière 2001

LandAnimal

LandCarniv ore

LandHerbiv ore

Chapter 5: Modelling with classes

21

Handling multiple discriminators Animal •Using multiple inheritance typeOfFood

habitat

AquaticAnimal

AquaticCarnivore

LandAnimal

AquaticHerbivore

© Lethbridge/Laganière 2001

Carnivore

LandCarnivore

Herbivore

LandHerbivore

Chapter 5: Modelling with classes

22

Player-Role Pattern (from Chapter 6) • Forces: — It is desirable to improve encapsulation by capturing the information associated with each separate role in a class. — You want to avoid multiple inheritance. «Player» «AbstractRole» — You cannot allow an instance to change class • Solution: «Role1»

© Lethbridge/Laganière 2001

«Role2»

Chapter 5: Modelling with classes

23

Player-Role Example 1:

Animal typeOfFood

Carniv ore

Herbiv ore

© Lethbridge/Laganière 2001

Omniv ore

0..2

HabitatRole habitat

AquaticAnimal

LandAnimal

Chapter 5: Modelling with classes

24

Avoiding having instances change class •An instance should never need to change class •You have to destroy the old one and create a new one. •What happens to associated objects? •You have to make sure that all links that connected to the old object now connect to the new one.

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

25

Hierarchy traineeEmployee •salary, sick time, medical plan •taxes(), benefits() fullEmployee •salary, sick time, medical plan, life insurance, vacation, car •taxes(), © Lethbridge/Laganière 2001 benefits()

traineeEmployee salaray, sick time, medical taxes(), benefits()

fullEmployee salaray, sick time, medical life insurance, vacation, car taxes(), benefits()

Chapter 5: Modelling with classes

26

Hierarchy traineeEmployee • salary, sick time, medical plan • taxes(), benefits() fullEmployee • salary, sick time, medical plan, life insurance, vacation, car • taxes(), benefits()

traineeEmployee salaray, sick time, medical taxes(), benefits()

fullEmployee life insurance, vacation, car benefits()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

27

Hierarchy Are fullEmployees special kind of newEmployees? If we add orientation to newEmployees, what will happen to fullEmployees?

traineeEmployee salaray, sick time, medical taxes(), benefits()

fullEmployee life insurance, vacation, car benefits()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

28

Hierarchy allEmployees salaray, sick time, medical taxes(), benefits()

fullEmployee traineeEmployee life insurance, vacation, car orientation benefits()

Everything seems satisfactory until we think about the life of the traineeEmployee object Chapter 5: Modelling with classes 29 © Lethbridge/Laganière 2001

Roles

Student Name, Contact Registration No.

© Lethbridge/Laganière 2001

Teacher

Parent

Name, Contact

Name, Contact

Employee ID

Something

Chapter 5: Modelling with classes

30

Roles Person Name, Contact

Student

Teacher

Parent

Registration No.

Employee ID

something

If one person plays different roles Data Coherence Problem © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

31

Role Object Person

1

*

Person Role

Name, Contact

Student

Teacher

Parent

Registration No.

Employee ID

something

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

32

Inverted Hierarchy

All dogs know how to wag their tails.

Dog wagTail()

DogNoWag is a special type of dog. DogNoWag does not know how to wag its tail.

DogNoWag wagTail() ≡ NOP

Ignoring the functionality defined in the base class is a sign of inverted hierarchy. It is a psychological problem! © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

33

Inverted Hierarchy

DogNoWag chaseCats()

Dog wagTail()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

34

Inverted Hierarchy

Mammal producesMilk() liveBirth() warmBlood()

Platypus layEggs() liveBirth() ≡ NOP

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

35

Inverted Hierarchy

WarmAnumals producesMilk() warmBlood()

Platypus

Mammals

layEggs()

layEggs()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

36

Attribute or Derived Class Ball color

cricketBall

squashBall

color

dotColor

bounce(), swing()

speed()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

37

Attribute or Derived Class squashBall speed()

whiteDot

yellowDot

redDot

speed()

speed()

speed()

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

38

5.6 More Advanced Features: Aggregation •Aggregations are special associations that represent ‘part-whole’ relationships. — The ‘whole’ side is often called the assembly or the aggregate — This symbol is a shorthand notation association named isPartOf Vehicle

*

VehiclePart

Country

*

Region

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

39

When to use an aggregation As a general rule, you can mark an association as an aggregation if the following are true: •You can state that — the parts ‘are part of’ the aggregate — or the aggregate ‘is composed of’ the parts •When something owns or controls the aggregate, then they also own or control the parts © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

40

Composition •A composition is a strong kind of aggregation — if the aggregate is destroyed, then the parts are destroyed as well * Building

Room

Employee Employee Address •Two alternatives for addresses address: Address

© Lethbridge/Laganière 2001

street municipality region country postalCode

Chapter 5: Modelling with classes

41

Aggregation hierarchy Vehicle

*

Chassis

BodyPanel

*

Door

*

Frame

Engine

© Lethbridge/Laganière 2001

Transmission

Wheel

Chapter 5: Modelling with classes

42

Propagation •A mechanism where an operation in an aggregate is implemented by having the aggregate perform that operation on its parts •At the same time, properties of the parts are often propagated back to the aggregate •Propagation is to aggregation as inheritance is to generalization. — The major difference is: * - inheritance mechanism Polygon is an implicit LineSegment - propagation has to be programmed when required

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

43

Interfaces An interface describes a portion of the visible behaviour of a set of objects. •An interface is similar to a class, except it lacks instance variables and implemented methods Person

«interface»

Cashier

Machine

withdraw deposit

Employee

© Lethbridge/Laganière 2001

Person

Machine

Cashier

ATM

Employee

Chapter 5: Modelling with classes

Cashier

ATM

44

5.7 Detailed Example: A Class Diagram for Genealogy Person

name sex placeOf Birth dateOf Birth placeOf Death {husband.sex dateOf Death = #male} placeOf Marriage child husband dateOf Marraige 0..1 dateOf Div orce * parent 2 0..1 wife {wife.sex = #female}

{parent->forAll(p1,p2: p1 <> p2 implies p1.sex <> p2.sex)}

•Problems — A person must have two parents — Marriages not properly accounted for © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

45

Genealogy example: Possible solutions Person

Person

name sex placeOfBirth dateOfBirth placeOfDeath dateOfDeath

name placeOfBirth dateOfBirth placeOfDeath dateOfDeath

child

*

partner * 0..2 {partner->forAll(p1,p2 | p1 <> p2 implies p1.sex <> p2.sex)} *

Union placeOfMarriage dateOfMarriage dateOfDivorce

Woman 0..1

parents

femalePartner child

child

*

Man

malePartner 0..1 * 0..1 child

*

*

Union 0..1 placeOfMarriage parents dateOfMarriage dateOfDivorce

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

46

5.8 The Process of Developing Class Diagrams You can create UML models at different stages and with different purposes and levels of details •Exploratory domain model: — Developed in domain analysis to learn about the domain •System domain model: — Models aspects of the domain represented by the system •System model: — Includes also classes used to build the user interface and system architectureChapter 5: Modelling with classes 47 © Lethbridge/Laganière 2001

System domain model vs System model •The system domain model omits many classes that are needed to build a complete system — Can contain less than half the classes of the system. — Should be developed to be used independently of particular sets of - user interface classes - architectural classes

•The complete system model includes — The system domain model — User interface classes — Architectural classes —© Lethbridge/Laganière Utility classes Chapter 5: Modelling with classes 2001

48

Suggested sequence of activities •Identify a first set of candidate classes •Add associations and attributes •Find generalizations •List the main responsibilities of each class •Decide on specific operations •Iterate over the entire process until the model is satisfactory — Add or delete classes, associations, attributes, generalizations, responsibilities or operations — Identify interfaces Chapter 5: Modelling with classes6) 49 Lethbridge/Laganière 2001 —© Apply design patterns (Chapter

Identifying classes •When developing a domain model you tend to discover classes •When you work on the user interface or the system architecture, you tend to invent classes — Needed to solve a particular design problem — (Inventing may also occur when creating a domain model) •Reuse should always be a concern — Frameworks — System extensions Chapter 5: Modelling with classes 50 —© Lethbridge/Laganière Similar systems 2001

A simple technique for discovering domain classes •Look at a source material such as a description of requirements •Extract the nouns and noun phrases •Eliminate nouns that: — are redundant — represent instances — are vague or highly general — not needed in the application •Pay attention to classes in a domain model that represent types of users or other actors © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

51

Object/Class Identification Techniques

Textual Specification Analysis - Abbot nouns and verbs – objects and methods Data-flow Analysis - Booch look for both concrete and abstract objects in the problem space found from the bubbles and data stores in the DFD. Next, methods are obtained from the process bubbles. Object Relationship Patterns - Coad

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

52

Textual Analysis Approach

Abbott’s Noun Approach

• Use noun, pronoun, and noun phrases to identify abstract objects and classes. • Use singular proper nouns (e.g., sensor number 5) and nouns of direct reference (e.g., the fifth sensor) to identify abstract objects. • Use plural and common (e.g., sensor) nouns to identify classes. • Use verbs and predicate phrases (e.g., are simultaneously activated) to identify the associated operations.

Comments

• This approach is the oldest approach

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

53

Textual Analysis Approach Benefits:

• Easy for beginners to use • Abbott’s mapping should usually work • Can be used with pre-existing textual requirements specifications • Does not require a complete paradigm shift

Risks

• Indirect • Assumes user’s requirements are coherent, complete and correct • Proliferation of classes • No tool support

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

54

Guidelines for Textual Analysis Abbot’s approach extended by Graham et al. Part of Speech

Model Component

Example

Proper noun

Instance

Mehdi Hassan

Improper noun

Class/type/role

Student

Doing verb

Operation

Buy

Being verb

Classification

Is an

Having verb

Composition

Has an

Adjective

Attribute value or class

unsuitable

Adjective phrase

Association

Customer with children

Operation

The customer who bought the kite

Operation

Enter

Transitive verb

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

55

Selecting Good Classes  Classes should make sense in the problem domain.  Good classes classify the objects which need to be modeled in the system.  Classes often correspond to NOUNS.  Avoid redundant or irrelevant classes which add no value in the problem domain.  Remove classes which have no attributes.

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

56

Elimination of Inappropriate Classes

• After initial pass, discard classes which are: Redundant Irrelevant to the problem domain Vague Attributes If class name has no attributes of its own, it is probably an attribute. © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

57

Identifying associations and attributes •Start with classes you think are most central and important •Decide on the clear and obvious data it must contain and its relationships to other classes. •Work outwards towards the classes that are less important. •Avoid adding many associations and attributes to a class —A system is simpler if it manipulates less information © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

58

Tips about identifying and specifying valid associations •An association should exist if a class -

possesses controls is connected to is related to is a part of has as parts is a member of, or has as members

some other class in your model •Specify the multiplicity at both ends •Label it clearly. © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

59

Actions versus associations •A common mistake is to represent actions as if they were associations LibraryPatron * borrow

*

*

Loan

return

*

*

CollectionItem

borrowedDate dueDate returnedDate

* *

LibraryPatron

CollectionItem

Better: Theborrow operation createsLoan a, and Bad, due to the use of associations the return operation setsreturnedDate the that are actions attribute.

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

60

Identifying attributes •Look for information that must be maintained about each class •Several nouns rejected as classes, may now become attributes •An attribute should generally contain a simple value — E.g. string, number

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

61

Tips about identifying and specifying valid attributes •It is not good to have many duplicate attributes •If a subset of a class’s attributes form a coherent group, then create a Person Person Person Address * addresses distinct class containing these name name name * street street1 municipality attributes addresses Bad due to a plural attribute

municipality 1 prov OrState1 country 1 postalCode1 street2 municipality 2 prov OrState2 country 2 postalCode2

prov OrState country postalcode ty pe

Good solution. The type indicates whether it is a home address, business address etc.

Bad due to too many attributes, and inability to add more addresses © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

62

An example (attributes and associations) Employee

Passenger

name employeeNumber jobFunction

name number

RegularFlight

* supervisor

time flightNumber

* *

Booking

* *

seatNumber

© Lethbridge/Laganière 2001

*

SpecificFlight date

Chapter 5: Modelling with classes

63

Identifying generalizations and interfaces •There are two generalizations: — bottom-up

ways

to

identify

- Group together similar classes creating a new superclass

— top-down

- Look for more general classes specialize them if needed

first,

•Create an interface, instead of a superclass if — The classes are very dissimilar except for having a few operations in common — One or more of the classes already have their own superclasses Chapter 5: Modelling with classes 64 © Lethbridge/Laganière 2001

An example (generalization) PersonRole 0..2

Person name idNumber

EmployeeRole

PassengerRole

jobFunction

RegularFlight

* supervisor

time flightNumber

* *

Booking

* *

seatNumber

© Lethbridge/Laganière 2001

*

SpecificFlight date

Chapter 5: Modelling with classes

65

Allocating responsibilities to classes A responsibility is something that the system is required to do. • Each functional requirement must be attributed to one of the classes — All the responsibilities of a given class should be clearly related. — If a class has too many responsibilities, consider splitting it into distinct classes — If a class has no responsibilities attached to it, then it is probably useless — When a responsibility cannot be attributed to any of the existing classes, then a new class should be created • To determine responsibilities — Perform use case analysis —© Lethbridge/Laganière Look for verbs and nouns describing actions Chapter 5: Modelling with classes 66 2001

Categories of responsibilities •Setting and getting the values of attributes •Creating and initializing new instances •Loading to and saving from persistent storage •Destroying instances •Adding and deleting links of associations •Copying, converting, transforming, transmitting or outputting •Computing numerical results 5: Modelling with classes 67 •Navigating andChapter searching © Lethbridge/Laganière 2001

An example (responsibilities) — Creating a new PersonRole 0..2 regular flight — Searching for a flight PassengerRole — Modifying attributes * of a Booking flight * seatNumber — Creating a specific flight — Booking a passenger Chapter 5: © Lethbridge/Laganière 2001 — Canceling

*

Person

Airline

name idNumber

*

EmployeeRole jobFunction

RegularFlight

* supervisor

time flightNumber

* *

*

SpecificFlight date

Modelling with classes

68

Prototyping a class diagram on paper •As you identify classes, you write their names on small cards •As you identify attributes and responsibilities, you list them on the cards — If you cannot fit all the responsibilities on one card: - this suggests you should split the class into two related classes.

•Move the cards around on a whiteboard to arrange them into a class diagram. •Draw lines among the cards to represent associations and Chapter 5: Modelling with classes 69 © Lethbridge/Laganière 2001 generalizations.

Identifying operations Operations are needed to realize the responsibilities of each class •There may be several operations per responsibility •The main operations that implement a responsibility are normally declared public •Other methods that collaborate to perform the responsibility must be as private as possible

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

70

An example (class collaboration) EmployeeRole + getName [e2] crewMember *

**

Booking Booking [c2]

*

*

PassengerRole

SpecificFlight + specifyAirplane [a1] + createFlightLog [b1] + changeAirplane [d1] + findCrewMember [e1] addLinkToBooking [c3]

+ makeBooking [c1] addLinkToBooking [c4]

© Lethbridge/Laganière 2001

*

0..1

Airplane addLinkToSpecificFlight [a2, d3] deleteLinkToSpecificFlight [d2]

0..1

FlightLog FlightLog [b2]

Chapter 5: Modelling with classes

71

Class collaboration ‘a’

SpecificFlight + specif y Airplane [a1]

*

0..1

Airplane addLinkToSpecif icFlight [a2, d3]

Making a bi-directional link between two existing objects; e.g. adding a link between an instance of SpecificFlight and an instance of Airplane.   1.(public) The instance of SpecificFlight — makes a one-directional link to the instance of Airplane — then calls operation 2. 2.(non-public) The instance of Airplane — makes a one-directional link back to the instance of SpecificFlight © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

72

Class collaboration ‘b’

SpecificFlight + createFlightLog [b1]

0..1 0..1

FlightLog FlightLog [b2]

Creating an object and linking it to an existing object e.g. creating a FlightLog, and linking it to a SpecificFlight.   1. (public) The instance of SpecificFlight — calls the constructor of FlightLog (operation 2) — then makes a one-directional link to the new instance of FlightLog. 2. (non-public) Class FlightLog’s constructor — makes a one-directional link back Chapter 5: Modelling with classes 73 © Lethbridge/Laganière 2001 to the instance of

Class collaboration ‘c’

PassengerRole + makeBooking [c1] addLinkToBooking [c4]

Booking *

Booking [c2]

SpecificFlight *

addLinkToBooking [c3]

Creating an association class, given two existing objects e.g. creating an instance of Booking, which will link a SpecificFlight to a PassengerRole.

1. (public) The instance of PassengerRole — calls the constructor of Booking (operation 2). 2. (non-public) Class Booking’s constructor, among its other actions — makes a one-directional link back to the instance of PassengerRole — makes a one-directional link to the instance of SpecificFlight — calls operations 3 and 4. 3. (non-public) The instance of SpecificFlight — makes a one-directional link to the Chapter 5: Modelling with classes 74 © Lethbridge/Laganière 2001 instance of Booking.

Class collaboration ‘d’

SpecificFlight

*

0..1

+ changeAirplane [d1]

Airplane addLinkToSpecif icFlight [a2, d3] deleteLinkToSpecif icFlight [d2]

Changing the destination of a link e.g. changing the Airplane of to a SpecificFlight, from airplane1 to airplane2  1. (public) The instance of SpecificFlight — deletes the link to airplane1 — makes

a

airplane2

one-directional

link

to

— calls operation 2 — then calls operation 3.

2. (non-public) airplane1 — deletes its one-directional link to the instance of SpecificFlight. 3. (non-public) airplane2 — makes a one-directional link to 5: Modelling with classes © Lethbridge/Laganière 2001 instance of Chapter SpecificFlight.

the 75

Class collaboration ‘e’

EmployeeRole * + getName [e2] crewMember

*

SpecificFlight + f indCrewMember [e1]

Searching for an associated instance e.g. searching for a crew member associated with a SpecificFlight that has a certain name.   1.(public) The instance of SpecificFlight — creates an Iterator over all the crewMember links of the SpecificFlight\ — for each of them call operation 2, until it finds a match. 2.(may be public) The instance of EmployeeRole returns its name. Chapter 5: Modelling with classes 76 © Lethbridge/Laganière 2001

5.9 Implementing Class Diagrams in Java

• Attributes are implemented as instance variables • Generalizations are implemented using extends • Interfaces are implemented using implements • Associations are normally implemented using instance variables • Divide each two-way association into two one-way associations — so each associated variable.

class

has

an

instance

• For a one-way association where the multiplicity at the other end is ‘one’ or ‘optional’ — declare a reference)

variable

of

that

class

(a

• For a one-way association where the multiplicity at the other end is ‘many’: © Lethbridge/Laganière 2001

— use

a

Chapter 5: Modelling with classes

collection

class

implementing

77

List,

Example: SpecificFlight class SpecificFlight { private Calendar date; private RegularFlight regularFlight; private TerminalOfAirport destination; private Airplane airplane; private FlightLog flightLog; private ArrayList crewMembers; // of EmployeeRole private ArrayList bookings

}

...

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

78

Example: SpecificFlight // Constructor that should only be called from // addSpecificFlight SpecificFlight( Calendar aDate, RegularFlight aRegularFlight) { date = aDate; regularFlight = aRegularFlight; }

© Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

79

Example: RegularFlight class RegularFlight { private ArrayList specificFlights; ... // Method that has primary // responsibility

}

public void addSpecificFlight( Calendar aDate) { SpecificFlight newSpecificFlight; newSpecificFlight = new SpecificFlight(aDate, this); specificFlights.add(newSpecificFlight); } ... © Lethbridge/Laganière 2001

Chapter 5: Modelling with classes

80