Information System Requirements Specification Document
for
Project Name
Prepared by authors
Lecturer Lecturer Name
Victoria University
BCO3447
date created
Table of Contents
Table of Contents ii
Authors’ Contribution Acknowledgement ii
1. Introduction 1
1.1 Organisation/Department Under Study 1
1.2 Purpose 1
1.3 Existing (Manual) System 1
1.4 Proposed New Information System 1
2. Analysis of the Existing System 1
2.1 Data Flow Diagrams 1
2.2 Describe Data Handling 1
3. Design of the New IS 2
3.1 Overview 2
3.2 Use Cases 2
3.3 Data Flow Diagrams 2
3.4 Data Modelling 3
3.5 User Interfaces 3
3.6 Managerial reports 3
4. Plan for Implementation 4
Appendix: 4
Authors’ Contribution Acknowledgement
Author Name Section(s) of the report written by the author
(match with Table of content headings)

By signing below, I(we) acknowledge that the author contribution as stated above is correct.
Author ______________ Signature _______________ Date ____________
Author ______________ Signature _______________ Date ____________
Author ______________ Signature _______________ Date ____________

1. Introduction
1.1 Organisation/Department Under Study
This section describes the organization/Department under study, its business and function.
1.2 Purpose
This section describes the purpose of this report, and explains the new Information System very briefly, and notes if it is the whole system or part of a larger system.
1.3 Existing (Manual) System
This section describes how the processes are currently operated in the organization under study. It also explains the manual system, and the business processes currently in place.

1.4 Proposed New Information System
This section describes the proposed new IS, and its associated business processes.
2. Analysis of the Existing System
2.1 Data Flow Diagrams
Draw DFDs for the existing system.
2.2 Describe Data Handling
Describe how data is currently captured, stored, processed and disseminated in the existing (manual) system (eg., forms, folders, cabinets, reports etc).
3. Design of the New IS
3.1 Overview
Explain the aim of the new IS. What you would like to achieve through the new IS which wasn’t achievable in the existing manual system. Who are the actors of the new system.
3.2 Use Cases
Draw the overall use case diagram followed by diagrams for all use cases.
3.2.1 Overall Use Case
3.2.2 Use Case 1
3.2.3 Use Case 2
3.2.4 Use Case 3
3.2.5 …
3.3 Data Flow Diagrams
Draw the overall DFD (also called context diagram) followed by diagrams for all DFDs as required.
3.3.1 Overall DFD
3.3.2 DFD 1 (Name)
3.3.3 DFD 2 (Name)
3.3.4 DFD 3 (Name)
3.3.5 …
3.4 Data Modelling
3.4.1 Entity Relationship Diagram
Draw the ERD for your system using the notation introduced in the class (include entity names, attributes, PK/FK, relationship names, relationship types (connectivities)).
3.4.2 Data Dictionary
Provide the data dictionary for your ERD.
3.4.3 Relational Schema (database design)
Draw the relational schema for your ERD.
3.5 User Interfaces
Provide the text description of each user interface your new system has (eg, main menu, data entry forms, adding/editing/deleting etc). If you would like to include figures, you can insert in appendices.
3.6 Managerial reports
List and explain various managerial reports (and queries) that your new IS is able to produce. Managerial reports are very important as they provide input which inform managers’ decisions. The more useful, and innovative your reports are, the higher your mark for this assessment (also the more the reports, the better). You can use the following sub-headings, if you want, to explain your reports in a more structured way:
3.6.1 Report 1 (Name)
3.6.2 Report 2 (Name)
3.6.3 Report 3 (Name)
3.6.4 Report 4 (Name)
3.6.5 …
4. Plan for Implementation
This section explains your plan for implementing the proposed IS (final report and presentation due in week 11). It should include project schedule (eg, using Gantt chart, PERT, CERT, or at least a table listing activities/timing/persons assigned to do).
Appendix:
If you would like to include any text, figure, table as side information, you can inset here (example, user interfaces if you have already created).
End.