You are on page 1of 19

17.12.

2015

Session: 2014 - 2016 | <Department/College Name>

Project Title

Revision History
Date
<date>

Description
<Version 1>

Author

Comments

<Your Name>

<First Revision>

Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
Signature

Printed Name
Dr.

Title
Supervisor, CSIT 21306

Date
<date>

Project Title

Table of Contents

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations.
1.4 References
1.5 Overview
2. The Overall Description
2.1 Product Perspective
2.1.1 Operations
2.1.2 Site Adaptation Requirements
2.2 Product Functions
2.3 User Characteristics
2.4 General Constraints
2.5 Assumptions and Dependencies
3. Specific Requirements
3.1 External Interface Requirements
3.1.1 System Interfaces
3.1.2 Interfaces
3.1.3 Hardware Interfaces
3.1.4 Software Interfaces
3.1.5 Communications Interfaces
3.2 Functional Requirements
3.2.1 <Functional Requirement or Feature #1>
3.2.2 <Functional Requirement or Feature #2>
3.3 Use Cases
3.3.1 Use Case #1
3.3.2 Use Case #2
3.4 Classes / Objects
3.4.1 <Class / Object #1>
3.4.2 <Class / Object #2>
3.5 Non-Functional Requirements
3.5.1 Performance
3.5.2 Reliability
3.5.3 Availability
3.5.4 Security
3.5.5 Maintainability
3.5.6 Portability
3.6 Inverse Requirements
3.7 Logical Database Requirements
3.8 Design Constraints

Project Title

3.8.1 Standards Compliance
4. Analysis Models
4.1 Sequence Diagrams
4.2 Data Flow Diagrams (DFD)
4.3 State-Transition Diagrams (STD)
5. Supporting Information
Appendix A – Background Research on:
Appendix B – Data Dictionary

Project Title

1. Introduction
Newly documentation assigned by the department is to maintain the function of any type
conducted in banquet hall. The SRS of banquet hall contains the whole material related to
the project. Banquet hall is an important place for the ceremonies and provides the place
and services to their customers. By the time it is important to maintain the system of this
type by a computer system. The record maintenance, services, booking and record
keeping is the major aspects of this project.
1.1 Purpose
This SRS elaborates the requirements and specifications of Banquet Hall. The system
was working on different platform, with time the time of system invention in new
technology it is necessary to convert the system on a single one. With the help of one
system it is more convenient to handle the all types of data in no time. The banquet
hall system is the basic and simple system to maintain the all records related to the
same sort problems. It is defined clearly that the system will work accordingly for
getting the desired services.
1.2 Scope

(1) Manage the function services.
(2) Keeping record of function.
(3) Manage new and old booking.
(4) Manage the services.
(5) Cancelling and submitting the booking.
(6) Change the function date in any case.
(7) Managing the catering(with meal and without meal), waiters and chef.
(8) Manage the VIP and common function.
(9) Provide QoS to User.
(10)

Applicable for only Windows.

Definitions, Acronyms, and Abbreviations.
SRS Document 1.0

Page 1 of 9

04/15/16

f

Project Title

1.1.1

QoS

Quality of Service – define what users really want, thus make the
most of their function.
1.1.2

Windows [2]

Microsoft Windows (or simply Windows) is a multifamily of
graphical operating systems developed, marketed, and sold by
Microsoft. It consists of several families of operating systems, each of
which cater to a certain sector of the computing industry. Active
Windows families include Windows NT, Windows Embedded and
Windows Phone; these may encompass subfamilies, e.g. Windows
Embedded Compact (Windows CE) or Windows Server. Defunct
Windows families include Windows 9x and Windows Mobile

1.1.3

Catering
A caterer provides food to the different parties. The caterer can be hired
independently or can be part of a package designed by the venue.

1.1.4

Catering with Meal
provide food services to the participants . In which have per head system.

1.1.5

Catering without Meal
Food services provide by users.

1.1.6

VIP
VIP Stand For very important person.

1.4 References
[1] National Electrical Contractors Association (1922). "Electrical Construction and Maintenance". Electrical
Construction and Maintenance (McGraw-Hill Publishing Company) 22: 58. Retrieved28 January 2015 Jump
up^ "Ngram View "Lesson 2 - Windows NT System Overview". Microsoft TechNet. Microsoft. Retrieved
November 25, 2014.er". Retrieved 28 January 2015.

SRS Document 1.0

Page 2 of 9

04/15/16

f

Project Title

[2] "Lesson 2 - Windows NT System Overview". Microsoft TechNet. Microsoft. Retrieved November 25, 2014.

1.5 Overview
In this SRS description:
(1) Documentation defines the detail of the project material.
(2) Detail of the SRS working.

In the description of SRS it is defined everything clearly that the system will work
according to the directions given to it. The chances of failure has been reduced to its
minimum level. The SRS defined the every step of the working accordingly. The SRS
presentation elaborates the function of new version and removes the old one that is
manual.

SRS Document 1.0

Page 3 of 9

04/15/16

f

Project Title

2. The Overall Description
The banquet hall management system provides the best facilities to their
customers. In this system the administrative part will have the all records of the
system. The overall description summarize the all aspects of the system.
Banquet hall management system contains some facilities like booking of the
function, staff of the hall, services and food management etc. When a customer
will book the banquet hall for a specific date it is confirm to take the time of the
booking. The customer is allowed to change the date if condition but it is
compulsory to deduct the extra charges on condition. The customer is bound to
pay the amount on the booking time. The amount is based on the services and
the strength of the function attendant. The function will be provided the best
services to the customer. If the customer will not attend the function on the
booked date it is clearly mention that the banquet hall management system is not
responsible of any loss. The customer is supposed to be responsible to all
condition. The staff services and food services will be provided by the
management system anyhow a customer can make changes their own, like they
can change the menu before the time or they can prepare their food by their own
expenses. In such condition customer has facility to given the amount back after
deduction. All functions will be opened at 10:00 am and closed at the time of
10:00 pm All responsibilities will be fulfilled by the customer side and there will
not be interference by the management system but customers are bound to
follow the instructions of the system. The system is properly handled by the
managing side. All records are the assets of the management system.

2.1 Product Perspective
Banquet HALL is a managed hall that is being used for various functions
and purposes like Marriages, Engagements, Birthday parties, Child naming
Ceremonies, Anniversary parties, Baby Shower (Godh bharai),
Meetings/Conferences/ Workshops, Prayer meetings, Surveys etc. The
following subsections describe how the software operates inside various constraints.
2.1.1 Operations

 Every Organisation needs to manage all the different activities in
organisation. It is managed by a Manager or the owner.

SRS Document 1.0

Page 4 of 9

04/15/16

f

Project Title

 Owner manages booking of halls, Checks availability of halls, advance and
balance Payment by the customers.
 Categorising pricelist according to customer’s requirement and for time,
space and services utilized by clients for the function.
 Manager maintains each and every record for ease of its work.
 Manager keeps track of all the upcoming functions and arrangements to be
made.
2.1.2 Site Adaptation Requirements
In this section:
(1) Define the requirements for any data or initialization sequences that are specific to a
given site, mission, or operational mode
(2) Specify the site or mission-related features that should be modified to adapt the software
to a particular installation

If any modifications to the customer’s work area would be required by your system, then
document that here. For instance, “A 100Kw backup generator and 10000 BTU air
conditioning system must be installed at the user site prior to software installation”.
This could also be software-specific like, “New data tables created for this system must
be installed on the company’s existing DB server and populated prior to system
activation.” Any equipment the customer would need to buy or any software setup that
needs to be done so that your system will install and operate correctly should be
documented here.
2.2 Product Functions

 The System maintain the records of all the customers and long term clients.
 The System maintain the records of all the caterers, cleaning, decoration and
maintenance staff.
 The System maintaining and printing bills, keeping record of advance and
balance payments.
 The System maintaining the availability of dates of halls.

SRS Document 1.0

Page 5 of 9

04/15/16

f

Project Title

 The System easy addition (insertion), retrieval and updating of client details
and requirements.
 In system ,Client/Customer feedbacks and suggestions can be entered and
taken in to consideration for further development.
 Manager and staff logins are different and have specific rights to access,
retrieve or update data.
 The System generate reports on progress of the banquet hall on monthly
basis.
 Data and Report can be generated as a when required by the user.
2.3 User Characteristics
Describe those general characteristics of the intended users of the product including
educational level, experience, and technical expertise. Do not state specific requirements
but rather provide the reasons why certain specific requirements are later specified in
section 3.
What is it about your potential user base that will impact the design? Their experience
and comfort with technology will drive UI design. Other characteristics might actually
influence internal design of the system.
2.4 General Constraints
Provide a general description of any other items that will limit the developer's options.
These can include:
(1) Regulatory policies
(2) Hardware limitations (for example, signal timing requirements)
(3) Interface to other applications
(4) Parallel operation
(5) Audit functions
(6) Control functions
(7) Higher-order language requirements
(8) Signal handshake protocols (for example, XON-XOFF, ACK-NACK)
(9) Reliability requirements
(10) Criticality of the application
(11) Safety and security considerations
This section captures non-functional requirements in the customer’s language. A more
formal presentation of these will occur in section 3.
SRS Document 1.0

Page 6 of 9

04/15/16

f

Project Title

2.5 Assumptions and Dependencies
List each of the factors that affect the requirements stated in the SRS. These factors are
not design constraints on the software but are, rather, any changes to them that can affect
the requirements in the SRS. For example, an assumption might be that a specific
operating system would be available on the hardware designated for the software product.
If, in fact, the operating system were not available, the SRS would then have to change
accordingly.
This section is catch-all for everything else that might influence the design of the system
and that did not fit in any of the categories above.

3. Specific Requirements
This will be the largest and most important section of the SRS. The customer
requirements will be embodied within Section 2, but this section will give the Drequirements that are used to guide the project’s software design, implementation, and
testing.
Each requirement in this section should be:
 Correct
 Traceable (both forward and backward to prior/future artifacts)
 Unambiguous
 Verifiable (i.e., testable)
 Prioritized (with respect to importance and/or stability)
 Complete
 Consistent
 Uniquely identifiable (usually via numbering like 3.4.5.6)
Attention should be paid to the carefully organize the requirements presented in this
section so that they may easily accessed and understood. Furthermore, this SRS is not
the software design document, therefore one should avoid the tendency to over-constrain
(and therefore design) the software project within this SRS.
3.1 External Interface Requirements
3.1.1 System Interfaces
List each system interface and identify the functionality of the software to accomplish the
system requirement and the interface description to match the system. These are external
systems that you have to interact with. For instance, if you are building a business
application that interfaces with the existing employee payroll system, what is the API to
that system that designer’s will need to use?
3.1.2 Interfaces
Specify:
SRS Document 1.0

Page 7 of 9

04/15/16

f

Project Title

(1) The logical characteristics of each interface between the software product and its users.
(2) All the aspects of optimizing the interface with the person who must use the system

This is a description of how the system will interact with its users. Is there a GUI, a
command line or some other type of interface? Are there special interface requirements?
If you are designing for the general student population for instance, what is the impact of
ADA (American with Disabilities Act) on your interface?
3.1.3 Hardware Interfaces
Specify the logical characteristics of each interface between the software product and the
hardware components of the system. This includes configuration characteristics. It also
covers such matters as what devices are to be supported, how they are to be supported
and protocols. This is not a description of hardware requirements in the sense that “This
program must run on a Mac with 64M of RAM”. This section is for detailing the actual
hardware devices your application will interact with and control. For instance, if you are
controlling X10 type home devices, what is the interface to those devices? Designers
should be able to look at this and know what hardware they need to worry about in the
design. Many business type applications will have no hardware interfaces. If none, just
state “The system has no hardware interface requirements” If you just delete sections
that are not applicable, then readers do not know if: a. this does not apply or b. you
forgot to include the section in the first place.
3.1.4 Software Interfaces
Specify the use of other required software products and interfaces with other application
systems. For each required software product, include:
(1)
(2)
(3)
(4)
(5)

Name
Mnemonic
Specification number
Version number
Source

For each interface, provide:
(1) Discussion of the purpose of the interfacing software as related to this software product
(2) Definition of the interface in terms of message content and format

Here we document the APIs, versions of software that we do not have to write, but that
our system has to use. For instance if your customer uses SQL Server 7 and you are
required to use that, then you need to specify i.e.
3.1.4.1 Microsoft SQL Server 7

The system must use SQL Server as its database component. Communication with the
DB is through ODBC connections. The system must provide SQL data table definitions
to be provided to the company DBA for setup.

SRS Document 1.0

Page 8 of 9

04/15/16

f

Project Title

A key point to remember is that you do NOT want to specify software here that you think
would be good to use. This is only for customer-specified systems that you have to
interact with. Choosing SQL Server 7 as a DB without a customer requirement is a
Design choice, not a requirement. This is a subtle but important point to writing good
requirements and not over-constraining the design.
3.1.5 Communications Interfaces
Specify the various interfaces to communications such as local network protocols, etc.
These are protocols you will need to directly interact with. If you happen to use web
services transparently to your application then do not list it here. If you are using a
custom protocol to communicate between systems, then document that protocol here so
designers know what to design. If it is a standard protocol, you can reference an existing
document or RFC.
3.2 Functional Requirements
Requirem
ent No

Requirements

Priority

Req 1

Check date of booking either it is available or not.

High

Req 2

Change the date or book to another date if previous booking exists. High

Req 3

Save and record the customer information.

High

Record the customer with first and then last name.

Record the customer’s CNIC and address.

Function type either the function is wedding or birthday, VIP or
common etc.
Record the male and female strength attending the function.

SRS Document 1.0

Page 9 of 9

04/15/16

f

Project Title

Record the function amount according to function type.

Take 50% amount before the function or at the booking time.

Deduct 40% amount in case of cancelling the booking.

Time to function is about to 10:00 am to 10:00 pm.

System will keep the record of serving dishes,
steam dishes, bowls, plates, spoons, and stoves.

The System maintain the records of all the caterers, cleaning,
decoration and maintenance staff.

NON Functional
Requirements
Only admin and manager can login to the system.

On phone call , booking not grunted until credit is confirm.

Provide simple and VIP format to user.

Every function decoration show the type of function.

In simple category common material is used.

SRS Document 1.0

Page 10 of 9

04/15/16

f

Project Title

In VIP category , stylish material is used like vine glass, carpets etc.

According to weather cooling fans and hitters are used.

Provide sound system that’s extra charges.

User pay holding tax and GST tax.

Print the booking form.

Provide annual and monthly report of all function.

In per head system the price is should less as increase of members

SRS Document 1.0

Page 11 of 9

04/15/16

f

Project Title

3.3 Use Cases
This section contains use cases of the ------------------------ system.
3.3.1 Use Case #1
3.3.2 Use Case #2

3.4 Classes / Objects
This section contains major classes of the ------------------------ system.
3.4.1 <Class / Object #1>
3.4.1.1 Attributes
3.4.1.2 Functions

<Reference to functional requirements and/or use cases>
3.4.2 <Class / Object #2>

SRS Document 1.0

Page 12 of 9

04/15/16

f

Project Title

3.5 Non-Functional Requirements
1. Only admin and manager can login to the system.
2. On phone call , booking not grunted until credit is confirm.
3.

Provide simple and VIP Function format to user.

4. Function decoration should be according to the type of function.
5. In simple arrangement, common material used.
6. In VIP arrangement , stylish material is used like vine glass, carpet.
7. In summer provide cooling fans facility that is consume extra charges.
8. In spring provide hitters that is also consume extra charges.
9. Provide sound system that’s increase charges.
10. The food menu according to the user.
11. In cause of load shading the generator will use that’s also extra charges.
12. Provide AC room for bridle.
13. User also pay holding tax and GST tax.
14. Print the booking form.
15. Provide annual and monthly report of all function.
16. In annual report tell the function type and catering with meal and without mean
17. In catering with meal per head system.
18. In per head system the price is should less as increase of members.
19. Different category for stage that according to the function type also in common and VIP
format like using flower.
20. Contain all record of products that in stock like tissue box , marble catering.
21. Display record of kitchen.
22. System provide facility to store all information of catering like stove , spoon ,dishes.
23. Waiter and chef provide services to user.
3.7 Logical Database Requirements
This section specifies the logical requirements for any information that is to be placed
into a database. This may include:


Types of information used by various functions
Frequency of use
Accessing capabilities

SRS Document 1.0

Page 13 of 9

04/15/16

f

Project Title



Data entities and their relationships
Integrity constraints
Data retention requirements

If the customer provided you with data models, those can be presented here. ER
diagrams (or static class diagrams) can be useful here to show complex data relationships.
Remember a diagram is worth a thousand words of confusing text.
3.8 Design Constraints
Specify design constraints that can be imposed by other standards, hardware limitations,
etc.
3.8.1 Standards Compliance
Specify the requirements derived from existing standards or regulations. They might
include:
(1) Report format
(2) Data naming
(3) Accounting procedures
(4) Audit Tracing
For example, this could specify the requirement for software to trace processing activity.
Such traces are needed for some applications to meet minimum regulatory or financial
standards. An audit trace requirement may, for example, state that all changes to a
payroll database must be recorded in a trace file with before and after values.

4. Analysis Models
List all analysis models used in developing specific requirements previously given in this
SRS. Each model should include an introduction and a narrative description.
Furthermore, each model should be traceable the SRS’s requirements.
4.1 Sequence Diagrams

4.2 Data Flow Diagrams (DFD)

4.3 State-Transition Diagrams (STD)

5. Supporting Information

SRS Document 1.0

Page 14 of 9

04/15/16

f

Project Title

Appendix A – Background Research on:
 Topic 1
 Topic 2
 Topic 3
 ………
 Topic n
Appendix B – Data Dictionary

SRS Document 1.0

Page 15 of 9

04/15/16

f