SRS-System Requirements Specification for SV-ONLINE

BOOKING EVENT MANAGEMENT SYSTEM

What is a Software Requirements Specification document?

A Software requirements specification document describes the intended purpose, requirements and nature
of software to be developed. It also includes the yield and cost of the software.
TABLE OF CONTENTS:

0 Abstract

1. Introduction

1.1 Purpose

1.2 Document Conventions

1.3 Intended Audience and reading suggestions

1.4 SVEMS Specifications(PROJECT SCOPE)

1.5 Existing system Disadvantages

1.6 New system Advantages

2. General Description

2.1 Product Perspective

2.2 Product Features

2.3 System Features

2.4 Operating Environment

2.5 Design Implementation, Constraints, Assumptions and Dependencies

3. Functional Requirements

4. External User Interface Requirements:

4.1 User Interface
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communication Interfaces

5. NONFUNCTIONAL REQUIREMENTS

5.1 Performance
5.2 Reliability
5.3 Availability
5.4 Security
5.5 Maintainability
5.6 Portability
5.7 Software Quality Attributes
 ABSTRACT:
Our main aim of this project is to make and provide an ideal software solution to book – events ,to cancel
events, to protect user data and to save the valuable time of the user . To fulfill the requirements of user.
To make the user experience of using this software is a pleasure one.

1. Introduction:
With the most recent developments and changes in the business environment, data and information must
be effectively gathered, managed and stored in order to keep pace and compete in the event industry.
Thus, an easier and cost-efficient manner of handling information is necessary.
SV Event Management System (SVEMS) shall address this need specifically for organizers of various sub-
events. This user-friendly software will provide the facility of scheduling events, recording and retrieving
participant and managerial information and billing of lodging and logistics facilities of clients and managers.

1.1 Purpose
This System Requirement Specification (SRS) aims to provide the readers and users information about the
system and its functions and specifications.SRS describes the data, functional and behavioral requirements
of the software. This will make it easier for the users to control and manage the use of SVEMS.
It shall reduce the costs associated with manual recording and updating such as over time of managers
and volunteers, reporting delays, mismanaged conflicts and other inconsistencies in the information.
Moreover, it shall improve the efficiency and it shall also maximize the productivity of the staff of an events
organizing firm because of its convenient usage.

1.2 Document Conventions

Component Object Model:
An interface standard for software components used to enable inter-process communication and dynamic
object creation.
Database(DB):
A system intended to organize, store, and retrieve large amounts of data easily; a repository of information.
Events:
A social gathering or activity.
Operating System:
The essential program in a computer that maintains disk files, runs applications, and handles devices such
as the mouse and printer.
SVEMS:
A software that will provide event organizers tools for efficient management of organizing events.

1.3 Intended Audience and reading suggestions

The intended readers of this SRS are developers, event heads, managing staffs and the event
organizers. Reading the general descriptions before proceeding to the specific requirements would help the
readers easily understand the background behind the functions of the system.

1.4 SVEMS Specifications(PROJECT SCOPE):

Our SVEMS is a software which provides each and every information of the event like event
calendaring, venue scheduling, providing details of manager and volunteer. It can be accessible from
any place. It helps to build good communication between user and manager by providing full details of
 manager and knowing full details of user. It makes easy for user to access any event. It can provide an
option for users to update information. Protect the DB of the user by requiring a correct and registered
username and password. It can add and delete the information of new and old clients easily. It can add
new supplier contacts with which future communication is expected. It protects and hides the user
details from many other external and internal threats.

1.5 EXISTING SYSTEM: In the existing system, the person has on visit the particular office for enquiry.
The existing system’s process is quite complex and manual one. The Event management system has to
keep records of events manually.

DISADVANTAGES OF EXISTING SYSTEM:

1. It consumes lot of time of user.

2. Lack of security.
3. Paper work results in a lot of space to keep the data.
4. It have Chance of happening human errors.

1.6 ADVANTAGES OF NEW SYSTEM:

1. It is easy to use and fast to implement.

2. it is a web based and easy to access their information anywhere on any device.
3. It helps to control problems that are usually happened in any event.
4. Quick and easy registration for the participants.
5. Automatic conformation emails .
6. Online data submission is secured dual time .
7. Real time reports.
8. Saves time.
9. It helps for checking appointment of particular venue.
10. It also to check and know the target audience.
11. User friendly.

2.   General Description:

2.1 Product Perspective

The software will be a new independent product, that it, it is not a component of another program.
All the forms used in the product follows a clear and logical structure. Errors will be minimized through the
use of drop-down buttons and command buttons to eliminate the excessive use of text input. Management
of data includes searching, adding, modifying and deleting.

2.2 Product Features

Protect the database of the firm by requiring a correct and registered username and password.  Make data
organization easier by classifying participants according to sub-types of personal events. Facilitate a step-
by-step process of entering, organizing, retrieving, modifying and deleting data from the database without
the need to go the database itself.
Add new client information easily.
Provide an option for users to update information.
Delete existing client information.
Create new events.
Provide an easy function where you can go back one form whenever necessary.
Present a list of participant codes representing existing clients.
Add new supplier contacts with which future collaboration is expected.
Display client information in an organized manner for easy understandability.
Display payment terms of participant including the total event fee, amounts paid by the participants and the
balance.

2.3 System Features

The system will operate in a graphical environment where the users interact with the program by clicking
buttons and choosing from menus. However some specific information (e.g. participants name, Address,
contact numbers, etc.) requires the user to directly input the data by typing it. It will be fully operational on
any personal computer with a Windows operating system.

2.4 OPERATING ENVIRONMENT

Operating environment for the airline

management system is listed below:
distributed database
client/server system
Operating system: Windows.
database: sql+ database
platform: vb.net/Java/PHP

2.5 Design Implementation, Constraints, Assumptions and Dependencies

On the other hand, this system will help to regulate the clientele and therefore provide guaranty that the
services offered by the managing body are of outstanding quality. With regard to scheduling of the events,
it is assumed that the venue shall be the choice of the event.
The primary responsibility of the managing body is to contact the suppliers of services and coordinate with
them about the event. Supplier contacts of the firm are those which are known of rendering high quality
service. Thus, the manager, who is the only person who can add suppliers, must study and assess a
supplier’s background and past performance before adding the same to the system for future collaboration.
The participant information may be accessed and updated by both the manager and the head. Therefore,
any changes with regard to the date of event, change of supplier, among others are updated easily. With
regard to payments, a fixed service fee shall be charged for every participant.
A client who wishes to cancel his / her participation in an event is provided with the option of the intended
cancellation.

3. FUNCTIONAL REQUIREMENTS

DISTRIBUTED DATABASE:
 Distributed database implies that a single application should be able to operate transparently on
data that is spread across a variety of different databases and connected by a communication
network as shown in below figure.

CLIENT/SERVER SYSTEM
A client/server system is a distributed system in which, Some sites are client sites and others are
server sites.
All the data resides at the server sites. All applications execute at the client sites.

FUNCTIONAL REQUIREMENTS for SVEMS are:

REGISTRATION
LOG IN
SELECTING EVENT
PAYMENT OF EVENT
CANCELLING EVENT
FORGOT PASSWORD
LOG OUT
For explaining the functions and methods of the functional requirements, we have drawn class
diagrams of each functional requirement.

4.  External User Interface Requirements:

4.1 User Interfaces

The interface of the software will provide options for a relatively easy data input processes text-boxes that
will be properly labeled. It will also have a user-friendly view of the whole system with simple and easy
undertaking of action-driven processes as command buttons are functionally labeled. With all these, target
users of this software will relatively find it not difficult to use it.

4.2 Hardware Interfaces

To be able to run the system, the minimum requirements of the hardware for this system are:
Windows.
A browser which supports CGI, HTML & Javascript.
The hardware used must have a competent firewall to secure the data in the system

4.3 Software Interfaces

The system was developed to serve as a database for the events' organizers. It is a stand-alone system;
hence, it does not need an internet connection. However, the system requires minimum specifications for
the software interfaces to be able to use it efficiently.
Following are the software used for the event management online application:

Software used Description

Operating system Windows operating system is chosen for its best support
and user-friendliness.
Database To save the flight records, passengers records we have
chosen SQL+ database.
 RQM tool RQM lets test teams work together more efficiently by
storing test data in a central repository which all team
members can see and update.

4.4 Communication Interfaces

All web browsers support communication for online ticket booking for any event using pc or any other
electronic device.

5. NONFUNCTIONAL REQUIREMENTS

The Non- Functional requirements describes the constraints under which specific features of the system to
be achieved.
Some Non-Functional requirements are:
5.1 Performance
5.2 Reliability
5.3 Availability
5.4 Security
5.5 Maintainability
5.6 Portability
5.7 Software Quality Attributes

PERFORMANCE : Response time The software the responds very quickly in a very short period to save
the user’s time. Capacity It have the capability of accessing and handling to over 1500 user’s at a time.
Software interfaces System shall interface with an Oracle or Access database. Hardware interfaces System
shall run on Microsoft window as well as android.
RELIABILITY: The reliability of total project depends on the reliability of various components. The important
component of reliability of the system is providing backup for the database which is continuously
maintained and updated to reflect the most recent changes also the system be functioning inside a
container. Thus the overall stability of the system depends on the stability of the container and its
underlying operating system.
AVAILABILITY : The system should available at all times, meaning the user can access it using a web
browser , only restricted by the down time of the server on which the system runs . We will provide the
working time of the software is 24x7 in a week. 
SECURITY: After entering the user name and password the user can access his profile and details of user
must be safe and secure. It provides high level security for the database of user.
MAINTAINABILITY : Software developed shall be easy to maintain and any modification to database is
done only by admin. It helps for maintaining the database and the application server takes care of the site.
Also the software design is being done with modularity in mind so that maintainability can be done
efficiently. 
 PORTABILITY : The code and supporting modules of the system will be well documented and easy to
understand. Online User Documentation and Help System Requirements.
SOFTWARE QUALITY ATTRIBUTES: Correct information must be entered into the system to prevent
mismanaged conflicts to occur. This will make the information provided by the system to be reliable and
useful. However, in case an error occurs, changes may be immediately effected provided the user notices
the error. This is why periodic monitoring and run-through of the database and the system must be done.