Introduction to information systems T. Cornford, M. Shaikh is1 060 2013

2.3 Database assignment
Reading activity
Read Section 13.2, Chapter 13 of Curtis and Cobham (2008), Chapter 6 of Laudon and 
Laudon (2013).
The aim of this assignment is to demonstrate an understanding of the 
basics of analysis and design for databases as well as to provide evidence 
of the use of the main features of a database package. In carrying out this 
assignment, you should refer to the class modelling section of this guide 
(Chapter 8) as well as the relevant bibliography. You will be expected to 
demonstrate the following through the analysis, design and construction 
of a small database application:
• selection of a suitable problem to be solved by a database application
• production of a class diagram using UML notation– this is a logical 
database design that reflects the aspects of the world that you store 
data about
• production of a set of normalised relations – a physical database design 
• design of a data input screen or screens
• design of a query screen
• design of a report for use on screen and/or for printing on paper.
Two example assignments are given below. These are intended 
to illustrate the type of problem that you are expected to 
tackle. You must choose your own database problems from 
the world around you – from your college or a local business 
or something associated with some hobby or pastime. 
Suitable problems are those that require the recording of data on three 

---

Chapter 2: Preparing for the project work
23
or more related classes of things and allow the production of a number 
of contrasting reports. You should not attempt designs that exceed five 
classes. Two classes is probably too simple but may be the starting point 
for your work.
Consider this example. Develop a database that will allow a person to 
review all the films that are on in London this week and discover at 
which cinemas they are showing. The aim is to help people plan their 
entertainment and book tickets. 
At first sight this suggests two classes of things about which a system 
will store data – various films and various cinemas – and of course the 
association between them (an association is the name we use for the link 
between things of one class and things of another. This usage comes from 
UML. Sometimes we express the same idea as a ‘relationship’). 2001: A 
Space Odyssey – a classic film from 1968 by Stanley Kubrick and in part 
about computers – is showing at five particular cinemas. A user of the 
database would want to know this to answer their query about where the 
film is showing. But, just knowing where is not enough. They will want 
to know when. This will lead us to add another class – another class of 
relevant thing in the world – which we might call a showing or screening. 
We will then need to reflect in our class diagram these three classes. Below 
are two simple examples of such class diagrams with the second one 
showing some of the attributes (data items) that we would want to store 
for items of each of the three classes.