Mobile Technology…

SRS

1 of 16
Overview
 SRS – System Requirement Specifications or commonly called
Specs/Requirements Document.
 SRS captures User Requirements
 Not important to worry about implementation feasibility at this point.
 Need good amount of domain knowledge to be able to interact with client/end
user to understand his perspective and capture requirements
 SRS is the first stage of Application development

2 of 16
Modules
 As Part of capturing requirements, the whole application is generally divided
into Modules instead of one complex application.
 There is no hard and fast rule of how many number of modules /sub modules
in an application.
 The number of module/sub modules division depends on the amount of
modularity you want in your application.

3 of 16
How to Identify Modules
 Let us take a common example of hospital management system.
 Let us identify the modules???
 Most often people would identify the following modules in Hospital
Management System:
 Doctor Module
 Patient Module
 Nurse Module!!!
 Etc.
Is it right???
4 of 16
How to Identify Modules
 Alas! It is wrong!!!
 Modules should never be divided based on entities like doctor , Nurse, Patient
 Generally speaking the Patient role is in every module, similarly the doctor
role could be in quite a few modules.
 Doctor, Patient, Nurse are Actors in this application not Modules.
 Let us Identify Modules correctly in Hospital Management system

5 of 16
Correct Identification of Modules
 The Correct Identification of modules in Hospital Management system:
 Administration
 Patient Admission
 Patient Monitoring
 Inventory Management
 Pharmacy Management
 Test and Diagnostics
 Payment
 If you observe the above modules clearly show the flow of application and modules
have been divided based on the demarcation of functionality of the application.
 Module Names are always Verbs and not Nouns. Actors are nouns

6 of 16
College Management System
 Let us take another common example of College Management System:
 The modules are Student , Faculty , Admin , Alumni etc
Or
• Admission, Attendance Management, Examination, Library
Management, Events Schedule, Alumni Management

• Obviously the second set of modules are right identification

7 of 16
Moving Ahead
 Once the modules are listed, write a few lines about the main purpose of the
modules.
 Each Module will have the following components:
 Provisioning
 Functionality
 Queries
 Alerts
 Reports

8 of 16
Provisioning
 Provisioning is the initial information/ initial intelligence you give to the
system
 Provisioning information does not change very often in the application
 Provisioning information remains same for all users.

 Example: In A college Management Application to do the functionality

of Admissions :
Provisioning information is the names of departments
Total number of seats available in the department
Unless this information is given, the admissions cannot be done

9 of 16
Functionality
 Functionality is the main purpose of the module
 Example: in Admissions module of College info system:
 Registering candidates is the functionality
Functionality information may change per user

10 of 16
Queries
 Queries is what you ask the system
 Example:
 In College Info system – Attendance Module:
Query: What is the attendance of the class
Hence, Query is a type of functionality where you ask info
from the system based on the functionality.

11 of 16
Alerts
 Alerts are notifications given by the system
 Example: In college info system
 Alert in Admissions module : Seats completed
 Alerts in Library module: Last date for submission two days away

 The Alerts can be in the form of screen alerts/mails or sms!!! We are interested in
the fact that they are notifications. Not the way in which this notification is
propagated.
 The alerts are notified when the pre defined condition is satisfied

12 of 16
Reports
 Reports are similar to Queries
 Reports also mean seeking info from the system
 However Reports are either
 comparative Analysis or
 Analysis spread over a period of time
Reports are generally graphical in nature (bar graph, Pie chart )
 Example: In college Info System
 What is the attendance of the class today is a query
 What is day wise attendance of class in the last one month
 Or What is the comparative attendance of all branches in this semester are two examples of
reports.

13 of 16
Recap
 List out the modules
 Write A few lines explaining each module
 Under each module list out the Provisioning info, Functionalities, queries,
Alerts and Reports.
 As a simple verification, check the functionality and see if info used in
functionality , queries and Reports has been provisioned or not.
 Similarly , check the Provisioning info and verify if the provisioned info has
been used or not in the functionality.
 By following the above points, you can be certain that your requirements
capturing will be successful.

14 of 16
Example
 Two Example Documents on SRS with Annotations are available for
reference:
 College information Mangement_Srs.doc
 Hospital Management_Srs.doc

15 of 16
Remarks

QUERIES??

Email: il@renintech.com

16 of 16