Case Study : A bit of Banner...

1. Look at use case diagrams2. Examine the detail in use case templates3. Identify preliminary entity classes and

relationships4. Draw communication or robustness diagrams

to show what classes collaborate to realise each use case.

Student Registration Subsystem

AdministratorProduce class lists

Register student

View moduledetails

Assign student to

module

<<include>>

<<include>>

<<extend>>Lecturer

Programme Management Subsystem

Head of Department

Create program delivery

Create Program Add

module to Program

Assign lecturer to

subject<<include>>

<<extend>>

Lecturer Create

Module

Module Manager?

Register Student Use Case outlinePrecondition : Student has had an offer of a place and an offer number

1. Student provides offer number2. Offer information is displayed on the screen. 3. Modules that are mandatory for their programme are

displayed and also electives4. A student record is recorded in the registration table5. Student is automatically registered on mandatory

modules6. Student is given the choice of specifying electives and

registering on them7. Students are given a college id 8. Student card is printed

Print Class List Use Case OutlinePrecondition : lecturer is logged onto banner

1. Staff member specifies programme and year2. Staff member specifies details and format

required3. Class list [CRN and a list of student numbers

and names] are displayed on screen in chosen format

Identify some entity classes<entity>

Student/module enrolment

Student id

CRN

<entity>

Student

Id#

Name

Address

Mobile

Phone

Email

Registeronprogram ()

Registeronmodule()

1

0..*

Is enrolled on ..

<entity>

Module delivery

CRN

Module id

Lecturer id

Academic year/semester

1

0..*

<entity>

Lecturer

Id#

Name

Address

Mobile

Phone

Email

Assigntomodule()

1

<entity>

Module

Module id

.....

<entity>

Programme

Programmeid

<entity>

progrmodule

Progid

Moduleid

Status(mandatory/elective)

Year

0..* 0..*

0..*

0..*

1

11

0..*

Identify operations

• Note that an operation changes the state of an object.

• Remember the ones we don’t need to write– Constructors– Destructors– Get (query) operations– Set (modify) operations

Note that our diagram will be refined as we go on.

Look at each use case..

See what classes collaborate to realise that use case (boundary and control needed).

• Display Progamme Information• Register student on programme• Assign student to modules• Produce class lists• Create delivery of module

• Exercise 1• Draw collaboration or robustness diagrams for

each use case, creating any classes you think might need created.

• Exercise 2• Use class collaboration cards and role-play each

use case. One person per class. Use this walkthrough to ensure that you have all the functionality required to enable each use case, specified as the responsibility of some class.

Use class collaboration cards to ensure that you have all the functionality

required for each use case