MonashUniversity
School of Information Management and Systems
IMS9300
IS/IM FUNDAMENTALS
Semester 1, 2004
Assignment:
SALTWATER LIBRARY
Requirements Specification
Aims :
•to gain an understanding of the process of analysis by determining and
modelling the requirements for a new system
•to produce a system requirements definition for a case study
•to demonstrate an ability to produce data and process models
Outline of the task :
The assignment requires you to play the role of a systems analyst. You are required to analyse the current situation and to develop a systems requirements specification.
You should ensure that the development of a new logical solution addresses the problems of the current situation, and where possible addresses new business needs and opportunities for the client.
Use the description of the case study provided, as well as any relevant information given to you by your lecturer or tutor, to produce a word-processed report which includes the items listed for each part.
Clearly note in your report any assumptions you need to make about any processing or data which may not be fully described in the case study.
Submissions : Students will be required to work individually.
Assignment value: 20% of subject assessment
Note : The problems and opportunities are not all covered by the written
description of the case study. You will need to look at the way data is
currently recorded on the forms in order to understand the reasons for
some of the problems.
Due date: End Week 9 Friday May 7th, 20045:00pm
The assignment is to be handed in to your tutor’s pigeon hole.
Your report should include the following sections :
1. Introduction: this should include
a) a description of your task, the scope of the proposed system,
b) the objectives for the proposed system together with
c) a brief analysis of the problems with the existing system, plus
d) a brief descriptions of opportunities for the proposed system
2. Brief descriptive overview of the proposed system. What it will do, and who will operates it.
5 marks
3. Data models for the proposed system :
4.1 Entity Relationship (ER) Diagram
-identifying the data entities
- showing the relationships between data entities, ordinality (mandatory/optional) and cardinality (one-to-many, one-to-one, etc).
5 marks
4.2Data Dictionary :
- definition for one data element
- definition for one data store
(the composition of the entity expressed as a list
of attributes is required;)
5 marks
4. Process models for the proposed system :
5.1Logical process model:
- Context Diagram for the proposed system
- Level 0 DFD for proposed system (including mini specs).
5.2Data Dictionary, as follows :
- Entry for one process from your level 0 DFD.
5 marks
Total: 20 marks