Q.3.9.1 3.

9 Preparation: Break
3. 2.
1.
Follow-up
Enactment Ensure
Possible Find
Objectives
up
specification
non-availability the
manual possible lost beOrline Case Determine the erors
A Select
library that
year recorded in interview
alternatives
mail. Studies i.e. analyst
i.e. model and
systems
and toreceivesLibrary making documents
conducting problems
for get
Unless and into is
subscription i.e. corect
anreplacement. of to
is displayed.1300 System of the the threecustom
information not earlier
request SRSrequiredreviewers
the to stages:
able journals Interview be
software
issues
renewed reviewed
to Action
for changes.
Periodicals
systems meet replacement
or of development.
paying in has
varying
these time.
for to
ordering have be
higher
requirements. Late periodicals.
taken
Periodical to
payment be
amounts journals
Periodicals. ordered
is The
Prepare of sent
for
^ubscription atjournals are
thosedifferentquickly, not
SRS received
issues. received
and
maytimes may it
systems
Current lead in
during not timehave
to be or to
 Software Engineering(MU-Bsc-Comp.) 3-26 Requirement Analysis and System Modeling

1. Introduction

Borrowing, returning and viewing the available books at the Library of ITM College is currently
done manually where the student has to go to the Library to do the book transactions. Students
check the list of available books and borrow it if it is not borrowed by any other else it is wastage
of time for the student to come to the library.Then the librarian checks the student id, allows him to
check out the book and then updates the member and the books database. This takes at least one to
two hours for the member to go to and fro to the library and get his work done.
(a) Product overview : The proposed system would be Online Library Management System
which would be used by members i.e. either students or professors to check th» availability
and borrow the books and by the librarian to update the corresponding databases.
The purpose of this SRS is to analyze the needs and features of this proposed Online Library
System on an high-level.
Online
(b) Purpose : The purpose of SRSdocument is to describe the external behaviour of the
Library System - operations, interfaces, performance,quality assurance requirements and the
design constraints. The SRS includes the complete software requirements for the proposed
system.
Library with
(c) Scope :The Online Library System provides the members and employees of the The Online
all the books infornation, online blocking of books and many other facilities.
Library System will have the following features.
The system will be running allday.
Users can sign-up and login to the system.
Members can check their account and change their password whenever needed.
day and all through the
The system allows the menmbers to block the books 24 x 7 hours a
semester.
and whether they can
Library staff can check which members have blocked the books
borrow any more books or not.
add/delete books.
Librarian can create and maintain the books catalog -
member borrows or returns a book.
The system updates the billing system whenever a
to add or remove a book from the
We also have an order department which manages
Library.
(d) Definitions and Abbreviations :
ITM- Information Technology and Management
Number
PIN - Personal Identification
LAN -Local Area Network
ASP - Active Server Pages
HTML- Hyper Text Markup Language
(e) References :
documents as references :
The SRS document uses the following
to provide security to the proposed system based
ITM Information Security Requirements ITM.
used by
on the security system currently
System toprovide the interface between the proposed system and the billing
The Billing member account due whenever they borrow
system currentlyin use by ITM to update the
and return the books.
 Software Engineering (MU-Bsc-Comp.) 3-27 Requirement. Analysis and
2. Overall Description System b

(a) Product perspective :

The Online Library System is a software package that is useful to
Libraries, Librarians and Users. The complete overview of the improve
the
diagram below. The proposed product has interactions with varioussystem is as
Members i.e. students and professors of ITM. kinds of
users shefownicie,j
The software has to interact with other
ITM systems also like: Internet, Billing
Information Security System.
(b) Product functions System and
The
Product functions of the system describe the
system based on the type of users different types of services
[Member/Librarian].
The mernber is provided with the
updated information about the books catalog.
provided
by t.
The members can borrow the
The member can check his books they want, if all the other required
rules
period. account information and change it any time in theholdgivencomerval
The members are
The librarian can provided
get the
with the books catalog to
choose the books which they need
the bookS. information about the members who have
The librarian can borrowed or returmed
add/delete
The due to be paid by the the books available in the book
or his fees is member is calculated if in catalog.
pending and the case he is late in
sent to the university
biling information along with the due amount submitting
system. about the
the books
The system uses the ITM member is
the users. information security requirements to provide the
(c) User characteristics login facility to
The users of the
systen are members and
who
system. The memberslibrarians
of the
maintain the
and the ITM College and the
knowledge of the computers and
more knowledge about the Internet browsing. Thelibrarian are assumed toadministrators
have basic

other catastrophes.
that may arise due to administraresponsi
internals of the system because he is
system in cases of small problems
disk
tors ble
of the
system have
to rectify the
(d) Constraints
crashes, power failures or any
Information of all the users (members and librarians) must be
must be accessible by the proposed stored in a database
System.
ITM information security system must be and that
compatible with the
The Online Internet applications.
Library System should be running all 24 x 7 hours a day.
The users must be able to access the Online Library
System from any
Internet connection.
The billing system is connected to the Online Library System
Computer that has
and the database
billing system must be compatible the Internet applications. used by the
 Software Engineering(MU-Bsc-Comp.) 3-28 Hequirement Analysis and System Modeing
The userS must be provided with correct
Library System.
usernames and passwords to lOgin to u
ie) Assumptions and dependencies :
Users have basic knowiedge of computers.
ITM College computer should have Internet connection and Internet server capab1lities.
Users knew English language as the user interface is in
English
The proposed application software can access the college student database.

3. Specific requirements
:
(a) External interfaces
() User interfaces : Web Browsers :Microsoft Internet Explorer or Netscape.
The user-interface of the system shall be designed as shown in the user-interface prototypes.
Login screen : Home page of ITM ibrary:
Look Hob Rk Edt Kow Fayotes Ioos ep
A t ow Fvortas

Library Management System |Library ManagementSystem

Meniber Eatry Assount t LÄraN Catsicg
Liysy (stelog

L.ocin Page Login Fage

User Nane
PORWor hdant

Sudent

Submit Rese!
SubmtReset
Caspter
y Conpua

Member information once logged in:

Member registration screen : itrary andepment Ssen içrosof ntgnal íxolger
Re Edk View Feortes Tocos Heb

Library Manggement System

Library Management System
ienke sty

NMember Rsrxn Fom

Mernber ActOuNi View
Pese erter you intoinia:

Adtess

Noné
James Keosh 0072227109
CeCx Nber Rofotence 0321117425
nME: The Complete Robart L, Glass
Software Engineering
Facts and Falacles of YCam

Setrn Rese
 Requirement Analysis and
Software Engineering (MU-Bsc-Comp.) 3-29
System
Mainsearch page of library catalog :

Library Management System

The Ortte ibre Cectog contns re holdings he i

eoch by

Subiect Headng

Avtor te (Combinaion)
hhoer stted Conputa

(i) Hardware interfaces : LAN wil be used for collecting data from the users and ako:
updating the Library Catalogue.
(itii) Software interfaces : A firewall will be used with the server to prevent unauthori
access to the system.
(iv) Communications interfaces : The Online Library System
will be connected to th
World Wide Web.
(b) Design constraints
Programming Language : The languages that will be used for coding the Online Librar
System are ASP, HTML, JavaScript, and
Information Services (IS) Server needs to be VBScript.
installed.
To run ASP pages, the Intemne
Development Tools : We will
application in ASP, HTML using themake use of online references for
two scripting languages - developing th
(c) Functionality JavaScript and VBScript.
Login Capabilities :The system shall
Mobile Devices : The Online Library provide the users with login capabilities.
such as cellphones. System will also be supported on
mobile devices
Alerts : The system will alert the Librarian or the
(d) Software system attributes
administrator in case of
any problems.
(i)
Reliability : The system has to be very much reliable to
prevent from entering incorrect or incomplete data. avoid the
(ii) Availability : The system is available to the user all 24 x7 damages
to data and
(ii) Security : The system shall support the ITM information hrs and 365 days a
the same standard as the ITM information security year.
security
requirements.
(iv) Maintainability : The maintenance of the system shallbe
Çontract. done as
requi rements
and use
per the
(v) Portability : The users will be able to access the Online Library maintenance
computer that has Internet connection. System from any
 Software Engineering (MU-Bsc-Comp.) 3-30 Requirement Analysis and System Modeling
(vi) Performance:
Response Time : The Information Dage shouldbe able to be downloaded within seconds
using a SóK modem. The information is refreshed every two minutes. The response une
for a mobile device must be less than a
minute.
Throughput :The number of transactions is dependent on the number of users.
Capacity :The system is capable of handling 200 users at a time.
(e) Other requirements
@ Licensing requirements : The usage is restricted to only ITM Library who is
purchasing
contract.
the Online Library System from Library InfoSys and signs the maintenance
(ü) Applicable standards : The ISOIEC 6592 guidelines for the documentation of
computer based application systems will be followed.
3.9.2 Purchase Order System
Q. The purchase order system functions as followWs:
After receiving the purchase requisition from store department, enguiries are made to
various suppliers. The suppliers send quotation to the company. All quotation are
analysed and final selection of supplier is done and accordingly purchase order to
respective supplier are send. The supplier sends invoice along with raw material.
Prepare SRS for the above system.
1. Introduction
Store department of acompany offers purchase requisition. Upon receiving this requisition, it
makes enquiries to various suppliers. Store department then gives specification for stock, name of
products and their quantity. Depending on thisspecification form, suppliers send their quotations of
submitting
stock quantity and rate of the required products. Depending on the number of suppliers supplier is
the Quotation, comparative charts are prepared to analyze and then final selection of
a number of days to send the
done. AIl these functions are currently done manually which takes
requisition and then receive quotations and then analyze them manually one by one.
(a) Product Overview
systemn which would be used by
The proposed system would be Online Purchase Order (OPO) requisition and send the
company staff and various suppliers to offer the purchase to select the
corresponding quotations, also computationally analyze the quotations so as
appropriate suppliers.
(b) Purpose
external behaviour of the Store Departments,
The purpose of this document is to describe the
description of products, including handling persons, product perspective, overview of
the specific requirements and
requirements, general constraints. It will also provide
functionality needed for this system.
(c) Scope needs
company to purchase product according to their
The purchase order system assists the minimum time so that it fulfills storekeeper's needs
and specification at minimum rate and in product will be fulfilled before the shortage and
the
and specifications. The availability of have the following features :
requirements rose. The OP0 System will
 Software Engineering (MU-Bsc-Comp.) 3-31 Requirement Analysis
and Sysiem
Stock Maintenance
Regular product master
Payment and receipt maintenance according to date and time specification.
Report Generation (weekly,Monthly, Yearly) of various detals such as:
(i) Total stock of products
(ii) Total Form collection (total number of
applied suppliers)
(iiü) List of products expired.
(d) Definition, Acronyms and Abbreviation
OPOS -Online Purchase Order
ITM- Information System
(e)
Technology Management
References
The SRS document uses the
Store requisition fom andfollowing documents as references:
the formn in the same supplier's quotation form as a sample
format when the current system is format so as to desjzr
Information Security
the security system Requirements to provide automated.
currently used by
the company.
security to the proposed
system based on
The Billing System to
provide the
system currently in use by store interface
product is to updatebetween
the
the proposed
system and the billing
2. Overali Descriptionpurchased or ordered (sold). product information
whenever a new
(a) Product Functions
OPOS generates
OPOS will be Quotation form for different suppher for
automated
product specification and
centralized
but different
same
hence it will create a product requirements.
Also that chart have to show rating. comparative chart for same
suppliers. sorting of rates through which
we can
OPOS keeps the record of the product code, easily analyze the
specification. product name,
(b) User Characteristics quantity and the other
System user is storekeeper/ Store
knowledge. Manager/suppliers. The users have
(c) Design Constraints
OPOS requires a computer
elementary computer
minimum 64/a24 MB RAM, aequipped with 133 MHZ
CPU speed of 200 MHZ orIntel
At least WIN OS above for Pentium Processor, with a
should be there. good
Minimum 64 MB RAM recommended.
ORACLE server should be installed.
performance.
Minimurn DOT MATRIX PRINTER should be
installed.
 Software Engineering (MU-Bsc-Comp.)
3-32 Hequirement Analysis and System Modeling
Assumptions and dependencies
Users have basic knowledge of
computers.
Company's computers should have Internet connection and Internet server capabilities.
1Üsers knew
English language as the user interface is in English
The proposed application software can
access the company product database.
Specific. Requirements
(a) Userinterface
A11 the forms are GUI based and are used
by user and manager interactively exvop
Quotation form.
Database Names
(b)
Product Master
Stock Mater
Concession Rule Details
Tax Details
Suppliers' Norms
Departure details
(c) Functional Requirements
Determine the last date and time for the filling of Quotation form and constraints are satisfied.
Nomore than one Quotation form should be filled at the same time for same product
specification.
The supplier should follow the whatever stock requirement specification.
Preferences is given to discount offering and quality maintained suppliers.
manner they does not
The supplier should follow rules an constraint as defined, in any
violate these constraints.
supplier.
Allow the user to maintain separate form for each
quantity.
Allow the user tomaintain a database of products,
a list of all product and stock specification available in store department.
To maintain
number of products, quality details,
Togenerate report for number of suppliers, supplying etc.
supplying after receiving order
date of
rates, discount and tax calculation,
(d) Software System Attributes
should be solvable.
Ihe generated problems synchronized with record generated.
be properly
Ihe database should be very much reliable to avoid
the damages to data and
has to
) Reliability :: The system
incorrect or incomplete data.
prevent from entering to the user all 24 X7
hrs and 365 days a year.
systemis available use
(i) Availability :: The information security requirements and
shall supportthe ITM
(ii) Security :The system information security requirements.
standard as the ITM
he same
 Software Engineering (MU-Bsc-Comp.) 3-33 Requirement Analysis and
System
(iv) Maintainability: The maintenance of the system shall be done as per the
Contract.
(V) Portability : The users will be able to access the OPOS from
Internet connection.
any computer
maineika
(vi) Performance:
Response Time : The Information page should be able to be downloaded within
using a 56K modem. The information is refreshed every two minutes. The Seco
for a mobile device must be less than a
minute. response
Throughput : The number of transactions is dependent on the number of users.
tite
Capacity:The system is capable of handling 200 users at a time.
4. Acceptance Criteria
Before accepting the system, the developer must
demonstrate that the system
specification. The developer will have to showworks
of stock data, product, quantity on the numbe.
that all conditions are through test case
satisfied.
3.9.3 Hospital
1.
Management System
INTRODUCTION
1.1 PRODUCT OVERVIEW
This Software
Requirements
(HPMS). It includes Specification formally specifies Hospital Patient
the resulting
The objective of this decisions of both - business analysis and Management System
document is to describe the systenms analysis efforts.
functional requirements, non-functional system's high level requirements such as
The detail structure of this requirements and business rules and
constraints.
Section 2 of this document document is organized as follows:
provides overview of the business
proposed Hospital Patient Management
Section 3 presents detail System (HPMS) will support.domain functions that the
System's functions. requirements and overview of the
Hospital Patient
A
1.2 PURPOSE Management
The
purpose of this SRS document is to describe the
Management System (HPMS) - operations, interfaces, external behaviour
and the design constraints. performance, quality of the Hospital Patient
Developers should refer to this document as the only assurance requirements
They should not consider any source of
requirements
document or in its revised version. written or verbal requirementappear
as valid until
they s-
for the
in project.
1.3 SCOPE this SRS
The system will allocate beds to
designated wards as needed. patients on priority basis, and assigns doctors
to
Doctors will use the system to keep track of the patients
assigned to them.
patients in the
Nurses will use the system to keep track of available beds,
given and to be required for each patient. patients, and the type of m

medication
 R
SottwareEngineering (MäU-Bsc-Comp.) 3-34
Requirement Analysis and System
Modeling

The current system in use is a paper-based system which cannot provide updated lists of
patientswithin areasonable timeframe. Therefore, the aim of the system is8toreduCe over-time pay
andincreasethe number of patients that can bc treated accurately.
14 AUDIENCE
Theintended audience include all stakeholders such as administrative staff, doctors, nurses,
surgeons and developers.
Front-desk staff: They are responsible for patient's check-in or notification of appropriate
neople (e.g. notuty adMinistrator or nurse when an event occurs).
responsible for
.Administrators: Every administrator has basic computer knowledge. They arei doctors and
all the scheduling and updating the dayfnight employee shifts; and assignng
nurses to patients.
are
wards if the beds
Nurses: They are responsible for assigning patients to appropriate
available, otherwise putting patients on the waiting list.
HPMS to check their patient's list and their duty
iv Doctors and Surgeons: They willuse the
schedule.
,16 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
HPMS Hospital Patient Management System
health card
PHN Personal Health Number on
an accountof patients
Report
information in a structured form
collection of
Database
desk
Front-desk staff administrative staff at reception
system
Logon lID a user identification number to enter the
aword that authenticates a user
to the system
Password
application that runs on Internet
Web-based application an
Patient Identification number
ID
Graphical User Interface
GUI Software Requirements Specification
SRS
2. OVERALL DESCRIPTION
PERSPECTIVE bed
} 2.1 PRODUCT at most activities of the hospital such as
self-contained system that manages issues.
This HPMS is a management and administrative
scheduling, personnel
asSignment, operations
2.2 PRODUCT FUNCTIONALITY
follows: whether the patient
The system functions are as the front-desk staff checks
Registration : When a patient is
admitted,
his/her PHN is entered into the computer
with the hospital. If so, including his date of birth.
i.
is already registeredgiven tothis patient and his information
else a new PHN is number is entered intothe system. condition s0
address and contact consultation-desk to explain his/her
goes to
Consultation:The patient thendecide what kind of ward should be assigned to him/her.
nurse can
that the consulting situations wait for
There are two possible patient is allotted that bed and asked to
the ward, then the
If a bed is available in
the doctor to come.
 Software Engineering (MU-Bsc-Comp.) 3-35
Requirement Analysis and
If thereis no bed,the patient is put on a waiting list until a bed System
ii. Check out : When a patient checks out, the front-desk staff
PHN from the system and the just vacate bed is included in
be comes
shall deletaevailable
iv. Report Generation : The system generates reports of the
available-beds ist.
patients, bed availability and staff schedules after every six hours.
2.3 USER CHARACTERISTICS fol owing infortma
The system will be used by the hospital staff who
desk staff who will be trained on using the include administrators, doctors.
by making use of a system. The systemis also designed to
Graphical User nterface (GU). nurbe ses and
2.4 OPERATING ENVIRONMENT
"The system will use MySQL
user-frienm
ii.
The Development Database which is open source and free.
iii. The system will beenvironment
a
will be Windows XP SP2.
2.5 DESIGN AND Web-based application,
IMPLEMENTATION CONSTRAINTS
The system must be
delivered by August 25 2012.
The existing
Telecommunication
standards and the system must infrastructure
conform to this
of HPMS is
based on
2.6
ASSUMPTIONS AND standard. EEE1008023
assumed that DEPENDENCIES
i It is
installed and tested. 100 TBM compatible computers will be
ii. It is
assumed that the hospital will have available before the system is
3. SPECIFIC REQUIREMENTS enough trained staff to take care of
the system
3.1 FUNCTIONAL REQUIREMENTS
i.
Registration
Add
patients : The front-desk staff will
Assign ID: The front-desk staff will use HPMS to add new
give each patients
the patient's record. use HPMS to to the
i.
Consultation patient ID andsystem.
an
add it to
Assign Ward: The
ward. consulting nurse will use HPMS to
Assign to Waiting List : The assign the patient to an
appropriate
waiting list if no bed is available. consulting nurse will use
ii. HPMS to assign Patient
Medical Management to a
Assign Doctor : The
patient. administrative staff will use HPMS to
Assign Nurse : The
assign a doctor to a
patient. administration staff will use HPMS to given
assign nurse to a
a
Inform Doctors: The HPMS will inform
doctors about the new patients. given
Inform Nurses:The HPMS will inform the
nurses about new patients.
 Software Engineering (MU-Bsc-Comp.) MOdeling
3-36 Requirement Analysis and System
Emergency Case : In case of emergency, the administrative staff will use HPMS to asSign
an emergency room,
doctors and nurses
Surgery case immediately
to the
In case of suurgery, the administrative staffpaticnt.
will use HPMS to assign a
surgery room, surgeon and nurses to the patient.
Generate Report : The HPMS will
for normal patients, and for every generate the Datient's situation record every
half hour for severe patients.
Record Procedure: The complete statement procedure for the patient will be recorded
the system.
Inform Patient : The HPMS will automatically inform about the patients who are o
waiting list and about available beds whenever they become available.
iv. Check Out
Delete Patient ID: The administrative staff will use HPMS to delete the ID of the patient
from the system when the patient checks out.
Add to beds-available list : The administrative staff allowed to put the beds just evacuated
in beds-available list.
Report Generation
Patient information :Every six hours the HPMS will generate reports about the following
information - patient's PHN, patient's name, ward name, bed number and the doctor´'s
name.
that
Bed Availability : Every six hours the HPMS will generate report on bed availability
includes ward name, bed number, occupied/unoccupied.
report on staff schedule that
Staff Schedule : Every six hours the HPMS will generate
includes staff ID, staff name, staff type, duty shift.
vi. Database
last name, phone number, personal health
Patient Mandatory Information : first name,
patient identification number.
number, address, postal code, city, country, patient's
Patient Information : The HPMS shall allow the user to update any of the
Update
above information. last
HPMS will allow user to search for patient'sinformation by
Search for Patient: The
name or PHN or patient ID. number, first name, last name, phone
: identification
Staff Mandatory Information employee type, duty schedule.
postal code, city, country, staffs
number, address, will allow user to update any of the
The HPMS
Update Staff Information :
information described above.
allow user to search for emplovee
Employee Information : The HPMS will
Search
ID number.
Information by last name, or
: Maternity, Surgical, Cancer and Cardiac. in ward.
Ward Types number, list of rooms
ward name, ward
Ward Information: number, list of beds in room,
full/not full.
room
KOom Information : occupied/unoccupied, patient PHN. hy
Information : bed number,
search the ward, room, and bed directly
Bed to
Search : The HPMS will allow users respectively.
Ward
number, room number and bed number
Ward
 Software Engineering (MU-Bsc-Comp.) 3-37 Requirement Analysis and

3.2 BEHAVIOUR REQUIREMENTS

System o

3.2.1 USE CASE VIEW

Patient archive
management system,

System administrator
Bed assignment
system Doctor
Directorial staff

Medicine Nurse
Front desk staff
management system

Financal
management system
Surgeon
Patients
Medical matter
system
System maintenance staff

Personnel
management system

Fig. 3.9.1
4. OTHER NON FUNCTIONAL
4.1 RELIABILITY REQUIREMENTS
The system has to be very
much
entering incorrector incomplete data.reliable to avoid the damages to data
4.2 AVAILABILITY and prevent from
The system is available to the user all
24 × 7 hrs and 365days a year.
4.3 SAFETY and SECURITY
Patient Identification: The system identifies the patient
using PHN.
Login ID: Anyuser who uses the system shall have a Login ID
and Password.
 BSoftwareEngineering(MU-Bsc-Comp.) 3-38 Requirement Analysis and System
Modeling

Modification : Any modification such as insert, delete, update for the Database shall be
allowed only to the administration staff.
Compliancee:The system must comply with the Regional Hcalth Authority Regulations.
but
Front Desk staff Rights : Front Desk staff can view and add all information in HPMS,
shall not be able to modify any information in it.
Administrators' Rights : Administrators can view and modify all information in HPMS.
-
Nurses' Rights : Nurses can only view the information in HPMS.
Doctors Rights : Doctors can view all information in HPMS.
MAINTAINABILITY
Back Up :The system will provide back-up capability to the Data.
Erors : The system shallkeep a log of all types of errors.
> 4.5 PERFORMANCE
patient's
will give responses in a second after checking the
Response Time: The system
information.
Capacity:The System will support 1000 people at a time.
seconds.
User-interface : The GUI will respond within 5 guidelines.
the Microsoft Accessibility
Conformity : The systems must conform to
3.9.4 Catering System
Example 3.9.1:
and billing software which presently works
wants to develop the order processing
Joshi Caterers Pvt, Ltd.
as under:
individuals. The customer fills up the order
different corporate
customers or number of
collects order from customer details, menu item details and
Company Kitchen
various details like order details, customers. Then after receiving the orders,
form describing collected only from individual kitchen issues the list of raw material
(excluded
thalies. 50% advance is
issued to the kitchen and
then ordered material is
(KOT), is Purchase order is given and
Order Ticket
be purchased from the suppliers.
kitchen. After completion of the delivery of
from available stock) to further to the number of
the fixed suppliers and forwarded actual number of thalies or ordered
received from
issued to the customer on the basis of
given to the customer. Prepare SRS and
ne order, billis receipt is
more. Payment is accepted and
ualies whichever is
above system.
System specification for the
Soln.:
1. INTRODUCTION
enable
1.1 PRODUCT OVERVIEW
scalability, reliability and efficiency toreduced
to provide resulting in
of the new system isordering and invoicing prccess
The objectiveincreases
productivity over the
administration and processing costs.
(JCPL).
1.2 PURPOSE
formallyspecifies Joshi Caterers Pvt. Ltd. The
Software Requirements Specification business analysis and systems analysis efforts.
This
resulting decisions of both -
It includes the
 Requirement Analysis and
SoftwareEngineering(MU-Bsc-Comp.)
3-39

specify the
software
requirements for
JCPL Syandstemh cofware Engineering (MU-Bsc
document is to
pro
this oVERALL DESCRIPTION
purpose of staff.
reference for project 2. PRODUCT PERSPEC
ongoing 2.1
1.3 SCOPE functionalities: The proposed system
allow the following forrm
describing various details
The JCPLsystem wll the order
customer fills up details and numberof
thalies for order processing an
order: As indicated in below
i. Collect details. menu item individual
details, customer advance is collected only from cústomers.
Ticket (KOT), is
data stores. Each of t
required between any
Advance Paymentt: 50% Kitchen Order
i.

1. lssue KOT :
After receiving the orders. issucd
Utensils and Food Items
kitchen.
iv. Check Stock Level: kitchen
issues the list of below
minir
stock level Order : Purchase order is given and ordered material is received rrom
Purchase Order process

forwarded further to the kitchen.

bill: Afterandcompletion of the delivery of the order, bill is issued to the custome:
Issue suppliers
fixed
vi. User
of thalies whichever is me
the basis of actual number of thalies or ordered number
VIL. Payment :customer makes paymnent and gets receipt.
vii. Total Income :income generated from services annually
14 AUDIENCE
Payment proc

The intended audiences include administrative staff, customers and developers.

administrative staff: Every administrator has basic computer knowledge. They User
responsible for collecting orders, informing the suppliers for raw material and collectir
payment from the customers.
15 DEFINITIONS and ABBREVATIONS

Acceptance the date on which the contract is made. Report ge

Change Database manages all
change proposals and this is
management system. linked to a versir User
Critical Failure - failure that results in System'
users.
's data not being
Data Recovery - restoring data that has been 'available to more than.

Fault Tolerance - a technique that ensures physically

systemdamaged.
2.2 PRODUCTT E
failures.
that
Form Editor - allows change proposal forms to be
erTors do not result in
systet
JCPL col
filled in
Interface Generator - graphical screen design system once
JCPL stc
as menus, field, icons and buttons are selected
where inagai
tertance. numberc
interface. from tool
a
Components sucl
box and
JCPL ge
JCPL fir
System Availability -total number of hours the system
total number of hours the system was under a
critical failurewas positioned onthe
JCPL pl
JCPL- Joshi Caterers Private Limited.
KOT- Kitchen Order Ticket Operational divided bythe JCPL g
custome
CM - Configuration Management a standard process
predetermined procedures. They require careful management
data and attention to detail is essential. involvofinverg ythe
\argappl ication 0!
e aramounts of
 Softvware Engineering (MJ-Bsc-Comp.)
3-40 Requirement Analysis and Systerm Modeling
OVERALL DESCRIPTION
2.
1 PRODUCT PERSPECTIVE
The propOsed system would be Online Calering Management Systerm which
for order processing and billing. would be used
As indicated in below figure, interaction between the subsysterms will be via the
data stores. Each of the subsystems in self-contained. bence, there is no direct underiyng
interaclon
required between any of the subsystems.
System boundary

Order processing Invoice processing

User
User

Payment processing Stystem databases Inventory management

User
User

Report generation Database maintenance

User
User

Fig, P. 3.9,1

> 2.2 PRODUCTFUNCTIONALITY

corporate customers or individuals.
JCPL collects order from different item details and
stores various details like order details, customer details, menu
JCPL
number of thalies.
then issued to the kitchen.
- JCPL generates KOT which is stock level.
finds the list of Utensils and Food Items below minimum
- JCPL
suppliers giving the list of requirement.
JCPL places purchase order to its acknowledgement after delivering the order to
the
bill and issues
JCPL generates catering
customer.
 Software Engineering (MU-Bsc-Comp.) Softwa
following context level

Allthe above
functions can be
summarizedthroughthe
Staff
diagrar 3.2

Supplier
Customer Functions,Menus,Utensils
Food
items.utensils

-Booking
Order
Booking
-Payment
Invoice

3.3

i)
JCPL
catering
system

Fig. P. 3.9.1(a)
2.3 USER CHARACTERISTICS

System user is the administrative staff of JCPL who has elementary computer knowledge.
2.4 DESIGN CONSTRAINTS

JCPL requires a computer equipped with 133 MHZ Intel Pentium Processor, with:
minimum 64/a24 MBRAM, a CPUspeed of 200 MHZ or above for good performance.
At least WIN OS should be there.
i
Minimum 64 MB RAM recommended.
ORACLE server should be installed.
Minimum DOT MATRIX PRINTER should be installed.
2.5 ASSUMPTIONS AND DEPENDENCIES
Users have basic knowledge of computers.
Users knew English language as the user interface is in
The proposed application software can access the
English
2.6 USER DOCUMENTATION company product database.
The System shall be delivered to JCPL attached with all of
the
A complete online help facility that will assist following documents:
system users to easily
Electronic user manual on CD-ROM in Adobe Acrobat operate the system.
foormat
initial training of System users. which will be useful for
Instruction manual for System Administrator on CD-ROM
in
which will be useful for initial training of System
Administrators. Adobe Acrobat
format
3. SPECIFICREQUIREMENTS
3.1 USER INTERFACE
All the forms are GUI based.
 SofiwareEngineering(MU-Bsc-Comp.) 3-42 Hequirement Analysis and System Modeiing
DATABASE NAMES
D
32
> MenuMaster
StockMater
Order Master
Concession/Discount Rule Details
Suppliers Details
PaymentDetails
Customer Details
FUNCTIONAL REQUIREMENTS
Customer Details
i)
of information about
) JCPL enables addition, modification, deletion, display and storage
number and E-mail addresS
address. contact
customers such as aunique identifier, name.
(optional).
details, if the customer's
h) JCPL avoids redundancy - while the user is adding custoemT
customer entry, the System will reject the new
name and address match an existing
information and tells the user that the customer already exists.
i) Supplier Details
deletion, display and storage of information about
a) JCPL enables addition, modification, contact number and E-mail address
name, address,
supplierssuch as a unique identifier,
(optional).
Utensii Details
i) Food Item and of information about
deletion, display and storage
a) JCPL enables addition, modification,
food items and utensils. unique identifier,
information about food item and utensils - a
b) JCPL stores following
suppliers who provide this food items and utensils, and
Food Item and UtensilName, charges for the food item and utensil.
per-unit price that each supplier minimum level of food items and
utensils
details about below
c) JCPL provides following
in stock : stock
food items and utensils currently in
The number of units of the currently on order
number of units of the food items and utensils
The utensil
price per unit of the food item and
The level
or minimum stock
The stock reorder level
iv) Service Details about
modification, deletion, display and storage of information
a JCPL enables addition,
services.
following details about each service:
b) JCPL provides
A unique identifier
Service Type
dishes on ordered menu
The number of food
required for the service
The number of utensils
 Requirement Analysis and
Software Engineering(MU-Bsc-Comp.) 3-43
Systernh. Software Engineer

The price per service An

A
v) Booking Details and storage of
a)

b)
JCPL enables
bookings.
addition, modification, deletion, display

following information about each

JCPL will provide
booking:
infomair, ix)
Report Ge
JCPL
Ar

A unique identifier infor

b) JCP
booking date
the customer that made the booking
The quantity and type of each service booked
The invoice associated with the booking Minimu
an ind. A)
details for a booking if the customer is
JCPL stores 50% advance payment
W
c)
person. le
order from the Customer. This krr
JCPL generates KOT after accepting the menu
St
d)
then issued to the kitchen. b) J

vi) Inyoice Details

thalies or or'
a) JCPL generates catering billinvoice on the basis of actual number of
number of thalies whichever is more.
JCPL stores following information for each invoice: Cust
b) B)
A unique identifier a)
Inyoice date - the date that the invoice is entered
The customer to whom the invoice applies C) Nil
The services that make up the invoice
a)
vii) Payment Deiails
a) ICPL enables addition, modification, deletion, isplay and storage of
payments.
information abc. D) To
b) JCPL provides following information for each payment: a)
A unique identifier
Payment date 4. OTHEL
The customer making the payment
4.1 P
The invoice against which the payment is being done.
The amount paid
vii) Unique Identifier Selection
JCPL shall automatically assign and display a unique
instance of any of the following objects is created:
A customer,
numerical identifier when a
new

A supplier,
A menu, A 4.2
A company,
Afood item,
A utensil,
 Software Engineering (MU-Bsc-Comp.) 3-44 Requirement Analysis and System Modeling
An order,
A payment,or
An invoice.
ix) Report Generation

a) JCPL shall display a requested report at the user's data display device by sorting uo
information according to the preference specified by the user.
) JCPL shall include the following information at the start of
cach report:
The date and time at which the report was
The title of the report.
produced, and
A) Minimum Stock Level Report

a) When requested by auser, JCPL System shall automatically generates a minimun stock
level report for all food items and utensils where the quantity in stock is below the
stipulated minimum level for that food item or utensil.
b) JCPL system shal display at least the following information when a minimum stock
level report has been generated:
The nominated minimum storage level for the food item or utensil
The actual storage level for the food item or utensil.
B) Customer Report
JCPL System shall automatically generate customer monthly service report that lists al!
a)
details of customer services during the last month.
C) Nil Payment Report
payment report that lists all details of all
a) JCPL System shail automatically generate nil been made.
invoices raised in the previous month against which no payments have
D) Total Income Report
income report that calculates the total
a) JCPL System shall automatically generate a total
during the whole annual year.
income generated from functions andservices
REQUIREMENTS
4. OTHERNON FUNCTIONAL
> 4.1 PERFORMANCE
of any
System shall display the latest information stored in the System at the time
The
user request. time of 5 seconds of a
System shall respond to ail user commands within an average
The
request being made. an average
complete all users commands and display the result within
The System shall
being made.
time of 15 seconds of a request
4.2 PORTABILITY operating
under any combination of each of the following
run
The System shall be able to
systems: Windows 2000,
a) Windows XP b)
d) Unix.
c) Solaris
 Q.Q.9 Q.8 Q.
6 Q.5 Q.
4 Q.3
10 Q.
2 Q.
1
4.3
(MU-Bsc-Comp.)
Engineering
Software
List
lManagement.
Requirement
Write Explain What
Describe What WhatExplain What
the access
SECURITY The
an is is are
various the is
Requirements
the the Systemto
SRS the SRS
need issues the
requirementstechniques ? information
eholders
for shall
of Explain
htra Requirements' of
requirement provide
engineering?
of need stored
involved engineeringrequirement
& appropriate
Questions
Review
benefits in
State gathering the
Validation
in System.
city
irement tasks? gathering of facilities 3-45
SRS.
? ?
to
Requirement
ard. ?
analysis ensure

e that
? Analysis
only

authorised
and
System
users
Modeim
have