SCHOOL NAME

DEPARTMENT NAME
STUDENT NAME
STUDENT NUMBER
LECTURER NAME
DATE DUE

A Software Requirement Specification Document Submitted in partial fulfillment of

the requirements of Bachelor of Science in Computer Science of Zetech University
Declaration
Provide a declaration statement about the authenticity and originality of your work

Sign

……………………………...

Lecturer’s Name

Sign

………………………………………… ……… ..

Student’s Name

Admission number

2|P a g e
Abstract
The abstract page is a brief description of the whole document. This page is usually written at the end of
writing this technical document.

3|P a g e
Table of Contents

This list should be auto generated.

4|P a g e
List of figures

This list should be auto generated.

List of Tables

This list should be auto generated.

5|P a g e
CHAPTER ONE: INTRODUCTION

1.0 Project title:

The title of this project shall be: xxx

1.1 Background information

<Describe the business-related reason for initiating the project and the system requests to solve
the problem or to achieve any objective according to the business needs of stakeholders.>
Sample:

<In a learning institution, library management functions are mostly practiced in manual ways
with the aid of various computer systems. For those libraries that implemented individual
systems to streamline their workflow, the systems are typically used for keeping records ...>

1.2 Current System Description

<Include brief description of the current systems information in the organization that placed the
tender notice.>

Sample:
<The current system allows Users to borrow books, which must first manually search if there
are any available stocks. The User then must display their library card to a Librarian, who will
then issue the book…>

Problem statement
<Define the problem or shortcomings that are identified in the existing system(s)>

1.3 Scope of the proposed system

<Describe the basic information of proposed system functions which can deliver value to the
business needs according to the collected system requirements.>

System Overview
Sample:
The proposed IT system will enable Users to sign into the library system using their mobile
application, and where they can search for their desired book and immediately see if there is any
stock available. If the book is available and not reserved, and the User has no outstanding fines,
the librarian will issue the book to the User…

6|P a g e
1.4 Objectives of the proposed system
<Highlight at least three objectives that you wish to meet by implementing a new
system>

1.5 Justification
<Justify the need for the proposed system. Why should the organization consider to
implement a new system>

7|P a g e
CHAPTER TWO: SYSTEM ANALYSIS
2.0 System analysis:
2.1 <Introduction: Give a brief description of what system analysis is?>
2.2 Feasibility study
2.2.1 Technical Feasibility- Provide the technical expertise needed for the
project with their qualifications
2.2.2 Economic Feasibility- Provide a realistic Project budget that will be
required to execute the project.
2.2.3 Schedule Feasibility- Provide project plan.
2.2.4 Legal Feasibility- Provide a detailed analysis of the legal implications
related to the project
2.2.5 Operational Feasibility- Provide any foreseen operational viability in
relation to the system
2.3 Functional Requirements

<State the Functional Requirements in this section in numbered tables or paragraphs by

grouping them according to business nature or types of requirements and assigned with a unique
requirement number, for ease of reference.>
2.4 Non Functional Requirements

<State the Non-Functional Requirements for the non-functional features such as audit, control
and security, global business rules, data requirements, usability requirements, service level
targets, user volume and equipment requirements, data growth and retention requirements, etc.
that the proposed IT system must possess from a business perspective. The following proposed
non-functional requirements can be changed or removed to suit project needs.>

List of Functional Requirements

1.1 <All functional requirements of the proposed IT system should be listed in the
following table and then explained in detail one by one. Each requirement is
assigned with a priority to indicate its importance, e.g.MUST (M), SHOULD (S),
COULD (C) and WON’T (W). B/Ds may assign priorities using other ranking,
e.g.High, Medium and Low.>
2.5 Technical Requirements

<State the Technical Requirements in this section in numbered tables or paragraphs by grouping
them according to the type of requirement and assigned with a unique requirement number,
e.g.TR 001, 002, 003, etc. for ease of reference.>

<Provide a list of technical requirements. The technical requirements supplement the non-
functional requirements and are not raised by the Business Analyst, but from the IT project
member(s) who raise(s) the technical requirements and is/are responsible for the acceptance of
the requirements in UAT.>

8|P a g e
 2.6

CHAPTER TWO: SYSTEM DESIGN

2.0 System Design:
2.1 <Introduction: Give a brief description of what system design is?>
2.2 Flowcharts <Develop and simulate at least three processes in the system and
develop flowcharts>

2.3 Entity relationship diagram<Design the Database and clearly depict the entities,
their attributes and the relationships therein>

9|P a g e
 2.4 Use Case Diagrams<Design the use cases that clearly depict the entities, their
attributes and the relationships therein>

10 | P a g e
CHAPTER THREE: SYSTEM IMPLEMENTATION
3.0 Introduction to System Implementation
3.1 Introduction: give a brief introduction about this chapter

3.2 Implementation
3.2.1 Test plan
3.2.2 Unit testing
3.2.3 System testing
3.2.4 Training of staff
3.3 Installation
3.3.1 Introduction to System change over strategies
3.3.2 Parallel changeover strategy
3.3.3 Phased changeover strategy
3.3.4 Straight changeover strategy
3.3.5 Conclusion- defend your choice of the strategy to be used

11 | P a g e
4.0 RECOMMENDATIONS AND CONCLUSION
4.1 RECOMMENDATION

12 | P a g e
 4.2 CONCLUSION

13 | P a g e
5.0 REFERENCES

Provide the list of references in APA Style of references

14 | P a g e