Lecture 11 - Case Study

Lecture 11 - Case Study - Lecture 11 Case Study...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Lecture 11 Case Study Implementing a small integrated application 2 A system will be developed to maintain records of the residents of a student hostel. We will look at the following stages – an informal description of the requirements; – a specification and design of the system using UML notation; – an implementation of the system in Java. 3 Problem Statement • A system is required by a local university to manage one of its student hostels. The hostel contains a number of rooms, each of which can be occupied by a single tenant who pays rent on a monthly basis. • The system must maintain a list of tenants; the information held for each tenant will consist of a name, a room number and a list of all the payments a tenant has made (month and amount). The system must allow the user to add and delete tenants, to display a list of all tenants, to record a payment for a particular tenant, and to display the payment history of a tenant. 4 The use case model’s primary purpose is to communicate the system’s functionality and behaviour to the customer or end user What is a Use Case Model? – A use case model is commonly used to document system requirements in UML – A use case model is a model of the system’s intended functions (use cases) and its surroundings (actors) 5 Actor Use Case Major Concepts in Use Case Modelling – An actor represents anything that interacts with the system – A use case is a sequence of actions a system performs that yields an observable result of value to a particular actor 6 Actors – Actors are not part of the system, they represent roles a user of the system can play – An actor may actively interchange information with the system – An actor may be a passive recipient of information – An actor can represent a human, a machine or another system Actor
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
7 Use Cases – A use case models a dialogue between actors and the system – A use case is initiated by an actor to invoke a certain functionality in the system – A use case is a complete and meaningful flow of events – Taken together, all use cases constitute all possible ways of using the system Use Case 8 Use Case Model Record tenant information Record tenant payment Delete tenant information Display list of tenants Hostel Administrator Display tenant payment information 9 Use Case Descriptions: Behaviour Specification • The next part of use case modelling is to describe the individual use cases in more detail. This is commonly referred to as a behaviour specification. This is used to describe the system’s functionality in some detail by giving the main flow of events and exceptions to it. • E.g. Use Case: Record tenant information – A hostel administrator attempts to register a new tenant to the system by entering the tenant’s name and a room number. If the room is already occupied an error is signalled. If all the rooms are occupied an error is signalled. If the room number is invalid an error is signalled.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 8

Lecture 11 - Case Study - Lecture 11 Case Study...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online