Professional Documents
Culture Documents
0>
Software Requirements Specification
Smart Academy
S.S market, Bidhan market Road
Siliguri, West Bengal
Team
Hunterz
Team Members
Winning Thaole A
Anil Ojha
Jimut Kumar Roy
Ranjan Kumar Sah
Project Guide
Mr. Jayanta Kr. Sarkar
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definition of Acronyms and Abbreviations
1.4 Technologies to be used
1.5 References
1.6 Overview
2. Overall Description
2.1 Product Perspective
2.2 Software Interface
2.3 Hardware Interface
2.4 Communication Interface
2.5 Product Function
2.6 User Characteristics
2.7 Constraints
2.8 Data Flow Diagram(Level 0, High Level)
2.9 Use Case Model Survey
2.10 Class Diagram
2.11 Assumptions and Dependencies
3. Specification Requirement
3.1 Use Case Report
3.2 Supplementary Requirements
4. Supporting Information
1. Introduction
1.1 Purpose
Development of a central system will help management of a group of hotels, owned by a
Hotel Group of national or international repute to incorporate all features including hotel
management, customer relationship management and central management of the group of
hotels by the firm head. This integrates customer services like online and ‘any place’ booking
along with features like central assessment of performance reports by the Managing Director.
It provides a partial set of solutions to all hotel management problems like basic facilities of
financing, accounting, inventory, asset management, restaurant management and house-
keeping. It will usher an environment which will not only provide unlimited services to the
customers but also help the Managers, Employees and other people related to the hotels to
function effectively and efficiently.
1.2 Scope
1.5 References
• http://en.wikipedia.org/wiki/Main_page
• Hotel Management by JP Sangar
• Hotel Organization by M N Ahmed
1.6 Overview
SRS will include two sections
• Overall Description, that describes major components of the system, interconnection
and external Interfaces
• Specific Requirements, that describes the function of actors, their role in the system
and constraints.
2. Overall Description
WAS
HTML
Client HTTP/HTTPS
(Customer) Web Components
DB2
Client EJB
Software EJB Components
(System User)
1. The web pages (html) provide the user interface on customer client side.
Communication between customer and server side is provided through HTTP
Protocol.
2. The Client Software is to provide the user interface on system user client side and for
this TCP/IP protocols are used.
3. On the server side web server is for AJAX (Asynchronous JavaScript and XML) and
database server is for storing the information.
Client side
Processor RAM Disk Space
Internet Explorer 6.0/ Core 2 Duo 512 MB 1 GB
Morzila/ Firefox 2.40 GHz
Server Side
Web sphere application Core 2 Duo 4 GB 2 GB
serverV5.0 2.40 GHz
IBMDB2 Core 2 Quad 4 GB 1GB (Excluding data
2.40 GHz size)
Login: In this module, users, customers and agents login to get information of the
hotels.
Hotel Reservation: Customers make reservation
Billing: In this module, bill payments, cash transaction are maintained.
Report Management: Report management takes into account daily reports of
Inventory section, Cashier section, Administrators section.
2.7 Constraints
• GUI is only in English.
• Login and password is used for identification of Hotel Staff, Managing Director,
system administrator, agent and suppliers.
• This system is working for single server.
• Limited to HTTP/HTTPS.
Bo
ok
i ng
& r
C u sto m er Or
der
De se Or
de S u p p lier
tai ha
ls P urc
Re als
ce
iv ed
H o tel et
ar i
dM
D eta
ils
M an ag em en t ce
iv
e
Re
S ystem
t ails
nto ry De Hot e
Inve l Rep
o rt
tus
Sta Ask
In ven to ry en
tory for h
o tel r M an ag in g
k Inv e po
C hec rts
D irecto r
Ro D e
Mgmt.
De pan cy Re Pu
om tai
Check-Out tail qu Module rch
s isi as
tio
Se ls
B ill n e
rv
T ra
De
ice
Or
ta ils
de
de
Tabl
Pu rch
e
r De
Orde
Inven
r C on
firmat
t a ils
ase
Tab ion
le O
tories
rde r Billing Module
Tab
le B Bill
o ok
ing Restaurant Purchase Order
Module Table Order Bill Details
Procurement
Inv en
Staff to ry De
KOT tails
Float Tender
n
tr atio
regis
pli er
n
o rts
n
io
d Sup
gi
at
Lo
re
refer
Re p
li d
or p te
Va
Manager f upda
uest s
t
Statu
R epor
R eq
y
tor
Order
rts
Tender
en
hase
po
Pur c
Inv
e ry
Re
gin
Lo Buy
v
se
of
n
De li
io
ha
n
at
io
ort
lid
rc
Rep Purchase Invoice
s
is
om
Pu
Va
ol
Suppliers ontr
bm
lity C
Ro
of
Su
Qua io n
gin iss
of
Lo bm
n
tio n u
io
lid a S
i ss
Va Report
bm
Su
Login Va li
datio Tender Information
t
n
p or
Login t Re
Admin
Ge
Fe
o rt
ed Attendance
Va
ep
ba
c
lid
it R
k/
Lo
at
Lo
gi
io n
bm
g
n
Re
po
Su
Ac rt
Va
ce s
lida
s co
MD ntro
t ion
Lo
l
Admin
gin
Agent
Check Performance
M.D.
View Details
Service Management
Report M.D.
Managing Officers
Grievance Handling
General
Manager Declaring Polices
Managing Suppliers
Managing Infrastructure
Manage Accounts
Manage Payments
Stock Management
Stock
Manager
Room Booking
Room Allotment
Report G.M.
Production
Manager Manage System User
View Logs
System
Booking Details Administrator
i) Managing Director: Responsible for checking the status and performance of hotels.
• Checking Hotel status: Check the status of all hotels in terms of expenditure, profit
and losses.
• Check performance: check the performance of hotels in terms of monthly, quarterly,
half-yearly and annual sales reports.
ii) System Administrator: Responsible for managing system users, viewing logs, etc.
• Manage System Users: The Administrator will create different system users. The
system users will be created and will be assigned with different roles. More than one
task and permissions can be granted or revoked from the system users.
• View Logs: Responsible for checking the logs of different system user for auditing
and maintaining the integrity of the system.
iii) General Manager: Responsible for service management , managing employees,
declaring policies, handling grievances, managing suppliers, managing assets and reporting to
Managing Director.
• Service Management: Records the details of services provided to customers.
• Managing Employees: Responsible for adding or removing of employees,
managing remunerations etc.
• Declaring Policies: Responsible for declaring and enforcing of policies for a
particular hotel.
• Grievance Handling: Responsible for checking & managing grievances and take
necessary steps.
• Managing suppliers: Responsible for issuing tenders contacting suppliers and
purchasing materials.
• Managing Assets: Keeping track of assets details in terms of availability, stocks in-
use and purchase.
• Reporting to Managing Director: Responsible for submitting the hotel reports to
Managing Director.
• View details: View the finance details, inventory details, daily transaction details,
customer’s details.
iv) Production Manager: Responsible for managing orders and reporting to General
Manager.
• Managing orders: Responsible for taking invoice orders, processing and delivering
orders.
• Reporting to General Manager: Responsible for submitting daily order-processing
details to General Manager.
• View details: View the finance details, inventory details.
v) Account Manager: Responsible for managing accounts, daily transactions and Cash.
• Managing accounts: Responsible for updating general registers and back-office
reports daily.
• Daily Transaction details: Maintains and updates daily sales, payments and
purchase.
• Manage payments: Store all payment transactions made by the hotel.
• View details: View inventory details, employee’s details, customers’ details, finance
details.
vi) Stock Manager: Responsible for keeping track of stock and managing stock.
3. 10 Class diagram
Class diagrams are widely used to describe the types of objects in a system and their
relationships. Class diagrams model, class structure and contents using design elements such
as classes, packages and objects. Class diagrams describe three different perspectives when
designing a system, conceptual, specification, and implementation. These perspectives
become evident as the diagram is created and help solidify the design. Classes are composed
of three things: a name, attributes, and operations.
Association is a generic relationship between two classes and is modelled by a line
connecting the two classes. This line also shows the feature multiplicity (One-to-one, one-to-
many, many-to-many).
Composition relationship means the class is a member of another class. It cannot be present
by itself. It is represented by
The above class diagram given below reveals the main class is library management system
which is divided in to two users like student and librarian. Student and librarian perform tasks
according to their need. The other class name is transaction and book.
Agent
Customer Staff Agent_id Supplier
Login_id Name Supplier_Id
Customer_Id Login_pwd 1 n Contact_no Name
Customer_Name Name Email_id Contact_No
Address Designation No_of_cust E-mail_Id
Contact Number
Avg_comm No_of_Trans
E-mail _Id Update Reservation
Gender Trans_date
Update Front Office Reports Update Agent_info
Date of Birth QOP
Update Sales Report
Marital Status 1 Amount
Update House Keeping
Nationality Update Inventory & Assets Update
Update Account Supp_info
Check-in
Check-out
Add Reservation 1 1
Orders for room service n
Cancel Reservation 1
n n n
Reservation Inventory
Rooms
Reservation_Id Item_code
Room_no
Hotel_Id Item_name
Type n m
Cust_Id Item_desc
Rates
Agent_id Item_qnty
Status
Cust_Name Item_amt
Update_Room_info
Check_In Date Qnty_in_hnd
Check_Room_avail
Check_Out Date ROL
Days of stay Min_L
Room_type
Update_stock
Number of Room
Number of Persons
Rent
Deposit Amount
Update_Deposit_Amt
Update_Reservation
Cancel_Reservation
Update_Room_avail
3. Specific Requirements
3. 01 Use-Case Reports
include
Manage System Create System
Users in cl Users
ude
Update System
Users
System User
Enter login
Name, password, details, role name, check the
Tasks and permissions
[System User]
ii) General Manager: Responsible for service management , managing employees, declaring
policies, handling grievance, managing suppliers and reporting to Managing Director.
• Service Management: Records the details of services provided to customers.
• Managing Employees: Responsible for adding or removing of employees,
payments.
• Declaring Policies: Responsible for declaring and enforcing of policies.
• Grievance Handling: Responsible for checking grievances and giving feedback.
• Managing suppliers: Responsible for issuing tenders, contacting suppliers and
purchase of materials.
• Managing Assets: Keeping track of assets details in terms of availability, assets-in-
use and purchase.
• View details: View the finance details, inventory details, daily transaction details,
customer’s details.
R eport M.D.
View List of
Services Provided
View Customer
Details
Generate
Feedback Report
Update Details
Employee Details
Ask for
Employee id
If
required
Select Employee Add Employee
Or
Add
PaymentDetails
Remove
Employee
Update
Send
Frame Policies For
Update
Display
Customer
Grievance
Select Grievance
Add feedbacks
Update
Information
View Supplier
Details
If Required
Select Suppliers Filling of tenders
Add Purchase
Details
Store Changes
Generate Asset
Details
If purchased
Check Assets
Add Purchase in Use
Details
Update Total
Stock
Store Changes
iii) Production Manager: Responsible for managing orders and reporting to General
Manager.
• Managing orders: Responsible for taking invoice orders, processing and delivering
orders.
• Reporting to General Manager: Responsible for submitting daily order-processing
details to General Manager
• View details: View the finance details, inventory details.
M a n a g in g O rd e rs
in clu de
P ro d u c t io n M a n a g e r
in clu de
R e p o rt .M.
G
Generate Order
Details
Select Order
Add Processing
Add Delivery
Details
Update
iv) Account Manager: Responsible for managing accounts, daily transactions and payments.
• Managing accounts: Responsible for updating general registers and back-office
reports.
• Daily Transaction details: Maintains and updates daily sales, payments and
purchase.
• Refer to Information System: View inventory details, employee’s details,
customers’ details, finance details.
M a na g e A c c ou n ts
inc lu de
A c c ount M anager include D a ily T ra n s a c t io n D e t a ils
inclu d
e
M an a g e P a y m e n ts
View Front
Office details
Generate
Add Transaction
back Office
Details
Report
Update
v) Stock Manager: Responsible for keeping track of stock and managing stock.
• Stock details: Keeping track of stocks purchase and stock availability
• Managing stock: Keeping track of incoming stock, stock damage and purchase.
• Refer to Information System: View the inventory details, finance details
S t o c k D e t a ils
include
S to c k M an a g e r
inclu de
S to c k M a na g e m e nt
View Stock
Details
Check avaibility
Material
If Damage
Stock in Use
required
If
Any
Add Purchase
Update Total
Add Purchase
Stock
Store Changes
R oo m B oo k in g
inc lude
B oo k in g O ffic e r include R oom A llotm e nt
in clu de
C us t om er B illing
Flow of events:
Generate room details.
Check availability.
Make reservation.
Add confirmation.
Update changes.
Post Condition: None
Search Room
Details
Check room
availability
Make
Reservation
Confirm
Reservation
Update
Reservation
Store Changes
Generate Check -
in Details
Check stay
duration details
Billing
Update
vii) Security Officer: Responsible for managing security guards and reporting to General
Manager.
• Managing Security Guards: Keeping track of guard’s details in terms of addition
and removal of guards, remunerations.
• Report to General Manager: Submission of reports to General Manager.
• View details: View Security details.
M a n a g in g S e c u rit y G u a rd s
in clu de
S e c u rit y O f fic e r
include
R e p o rt .MG
Generate Generate
Accidental Risk Security Details
Report
If any
Select Guard
Add Losses If R
ed eq
ui r
u ir
e d
eq
If R
3. Specification Requirements
3.1 Supplementary Requirements
Have hours of operation that are 24 x 7 - Because system can be an automated
process, so it can stay open for 24 hours a day. If the base is now the entire world,
staying open 24 hours a day becomes critical. System is required to be available 24X7
so UPS support must be on server site for at least 8 hours in case of power failure.
System will remain inaccessible to users at 2:00 to 4:00 am for backup and
maintenance purpose.
Make the existing Web site more dynamic in nature - Many early Web
implementations consisted of static HTML pages. This becomes very difficult to
manage if the number of pages gets too large. An effective system should be largely
dynamic taking advantage of technology that automates this process rather than
relying on manual processes. Application should serve dynamic user based
customized web pages to its Clients from server.
Tie the existing Web site into existing enterprise systems – Any existing Web site
that relies on the manual duplication of data from another system is one that can be
improved. Most of the business data in the world today exists in enterprise servers
that can be connected to the Web servers to make this process far more effective.
Provide good performance and the ability to scale the server – The Web
Application Server should provide good performance and the ability to manage
performance with techniques, such as support for caching, clustering, and load
balancing.
Providing session management capability - Web application developers should not
spend valuable time worrying about how to maintain sessions within the application.
The Web Application Server should provide these services.
4. Supporting Information
The supporting information in this SRS includes:
a) Table of contents.