1. Case Study : A bit of Banner...

2. 1. Look at use case diagrams 2
1. Look at use case diagrams 2. Examine the detail in use case templates 3. Identify preliminary entity classes and relationships 4. Draw communication or robustness diagrams to show what classes collaborate to realise each use case.

3. Assign student to module
Student Registration Subsystem
View module
details
<<include>>
Register student
<<include>>
Assign student to module
Administrator
Produce class lists
Lecturer
<<extend>>

4. Module Manager? Programme Management Subsystem Create program delivery
Assign lecturer to subject
<<include>>
Head of Department
Module Manager?
Create Program
Add module to Program
<<extend>>
Create Module
Lecturer

5. Register Student Use Case outline Precondition : Student has had an offer of a place and an offer number
Student provides offer number
Offer information is displayed on the screen.
Modules that are mandatory for their programme are displayed and also electives
A student record is recorded in the registration table
Student is automatically registered on mandatory modules
Student is given the choice of specifying electives and registering on them
Students are given a college id
Student card is printed

6. Print Class List Use Case Outline Precondition : lecturer is logged onto banner
Staff member specifies programme and year
Staff member specifies details and format required
Class list [CRN and a list of student numbers and names] are displayed on screen in chosen format

7. Identify some entity classes
0..*
<entity>
Student
Id#
Name
Address
Mobile
Phone
Registeronprogram ()
Registeronmodule()
0..*
<entity>
Programme
Programmeid
<entity>
Student/module enrolment
Student id
CRN 1
0..* 1
Is enrolled on ..
0..*
0..*
<entity>
progrmodule
Progid
Moduleid
Status(mandatory/elective)
Year 1
<entity>
Module delivery
CRN
Module id
Lecturer id
Academic year/semester
<entity>
Lecturer
Id#
Name
Address
Mobile
Phone
Assigntomodule() 1
0..*
0..* 1
<entity>
Module
Module id
..... 1

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

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

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

11. Use class collaboration cards to ensure that you have all the functionality required for each use case