Drafting the Software Requirement

Specification Documentation
Lesson Objective
Student be able to :
1. Plan the project
2. Draft the requirement specification on their project
Outline
1. Project overview
2. Project Final Deliverables
3. Project Requirements
4. Constraints
5. Resources
6. Evaluation
1. Overview
To provide project back ground to the project effort and the objectives of the project.

For example :
“This project named Expenses Tracking System. The main purpose of the Expense Tracker System
is to enable the user to keep track of their spending which indirectly helps in managing the user’s
money and takes control of the user’s financial. This system can increase the efficiency of tracking
daily expenses and ease the user as much as possible in the process of tracking expenses, rather
than using the manual system such as writing down in a notebook or keeping a log of expenses in
smartphones can be overwhelming and tedious. The objectives of the project are:
1. to develop a user friendly Expense Tracker System
2. to helps users to create financial awareness “
Project Final Deliverables
This should specify the final deliverable which is to be
produced upon the completion of the project. This includes
a brief description, functions and application of the
deliverable. The deliverable can be an invention, software,
system, solution or algorithm.
Example of Project Final Deliverables
1. This application will meet all the objectives and will solves all the user’s problems

2. A system that achieved and can be worked with all the functional and non-functional
requirements that had been proposed.

3. A complete report starting from the introduction until the conclusion.

Project Requirements
This outlines the list of the project requirements in terms of
features required and delivery mechanisms if appropriate.
Additional requirements to be implemented in future
phases should be listed (the “wish list”). Each requirement
should be presented in chronological order. The phase to
which each requirement belongs should be outlined.
Example
Functional Requirements:
FR1 Login
1. This allow user to access the system

FR2 Sign Up
1. This allow user to register their account to the systems
Example
Non-Functional Requirements :

NFR1:Usability
System will provide easy navigation for the user to access the system efficiently.
Consistency applies to all the modules and pages of the system.

NFR2:Reliability
Data records will be stored on an efficient database schema.
System can be used in long duration with less amount of or no bugs.

NFR3:Performance
The load-time of the system should be fast in order to allow users to perform task effectively.
To ease the accessibility, the category of expenses should have an option to name on the own.
Constraints
These define the boundaries of the work for this
specific project and typically include: Any limitations
should be described. Any limitations on access to
specific resources, budget, the project topic and
standards should be included.
Example
1. The system may require internet connection for some of the
system functions.
2. The system will not be able to link to the actual card account (eg,
credit/debit card).
3. The system will only enable one member to log into the system
from one device.
Resource
These define the access and assets that will be used during
the project and typically include: the sponsorship, the
number of people who will be involved in the project, their
skills, possibly naming individual, specific equipment,
services.
 Example
Operating System (OS): Windows 10

Software Specification :
◦ Visual Studio
◦ Microsoft Word
◦ QSEE Superlite
◦ Lucid Chart
◦ Android Studio

Hardware Specification
Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz 2.90GHz
8 GB RAM
64-bit operating system, x64-based processor
Evaluation
In this section the proposed evaluation of the project
outcome is outlined including the aim of the evaluation and
how the evaluation will be carried out
Example
Online survey will be conducted for the evaluation of the proposed project to get opinions and
feedbacks about the project from users. Users can also provide suggestions on the proposed
project. The conducted survey can help us to identify the users’ satisfaction and experience they
had towards the system.