SRS Documentation of E-Event Management Portal

CONTENTS
1. Introduction
1.1. Purpose
1.2. Document Conventions
1.3. Intended Audience and Reading Suggestion
1.4. Project Scope
1.5. References
2. Overall Description
2.1. Product Perspective
2.2. Product Features
2.3. User Classes and Characteristics
2.4. Operating Environment
2.5. Design and Implementation Constraints
2.6. Assumptions and Dependencies
3. System Features
3.1. Functional Requirements
4. External Interface Requirements
4.1. User Interfaces
4.2. Hardware Interfaces
4.3. Software Interfaces
4.4. Communications Interfaces
Page | 1
 5. Nonfunctional Requirements
5.1. Performance Requirements
5.2. Safety Requirements
5.3. Security Requirements
5.4. Software Quality Attributes

Introduction
Purpose:

The purpose of this SRS Document is to describe the behavior of the E-Event Management System to be
developed. This project is targeted for the event management organizations. While managing the
events, event mangers get in to lots of stress in scheduling the tasks, budgeting the expenses, managing
the field staff and to minimize the stress and maximize the success rate. This document includes the
functionalities that describe all of the interactions the users will have with the software. This includes
but not limited to Manage Template, Manage Registration, Manage Profile and Manage Event. The
classes include but not limited to User, Attendee, Administrator, Registration, Template, Event and
Event Planner.

Document Conventions:

IEEE Recommended Practice for Software Requirements Specification- IEEE Std. 830-1993.

Project Scope:

It is a Web‐based event creation and registration system. Here the end‐users will have the ability to
either create or register for events at locations of their choosing, with management of the system falling
into the Event Management team’s hands. The system will have separate access for end‐users and the
Event Management team.

Intended Audience and Reading Suggestion:

This project is an abstract model, representing various aspects of Event Management System and is
restricted within the specific companies and its domain vicinity. Accordingly, the project will be useful
for Event management team, Event Mangers, Event Team leaders, Event Team members, and Staffs,
who have direct and indirect involvement with the Event.

References:

Page | 2
[1]. A.A.Zaidan, B.B.Zaidan, Anas Majeed, "Event management strategies for NEXA ", World Academy of
Science Engineering and Technology (WASET), Vol.54, ISSN : 2070-3724, P.P 468-479.

[2]. New Comparative Study Between EMS, SMSSE and AEMS within Nine Factors, 2010.

[3]. J. Farrell and H. Lausen. Event monitoring for INFOSYS 28 August 2007, June 2007.

[4]. Palshikar, G. K., Kale, M. S., &Apte, M. M. (2007). Event management for AXISI Engineering, 61, 93–
113.

Overall Description
Product Perspective:

E-Event Management Portal is developed to manage any kind of event smoothly with the coordination
of all the actors involved in the system. The Admin is allowed to access all the services in the system like
register a new event, view and update the events, assigns different departments, add employees etc.
After assigning the works the Event Manager/Task Manager budgets the estimate and manages the
resources, views the tasks provided by the admin and devides the works among the employees. Then
the employees check the event status, register and update the events and the tasks.

User Classes and Their Characteristics:

As per gathering and analysis phase, this project possible to have following classes of users,
Such as:

1. Administrator: The Administrator of the E-Event Management Portal is allowed to access all the
services in the system. The admin can register a new event, view and update the event details
and can register/enroll new employees.
2. Event Manager: The Event Manager can login to the system, add, update and delete resource
types, view the events and tasks and assigns different tasks to the employees.
3. Employee: The Employee of the E-Event Management Portal is allowed to access the
functionalities provided by the admin. The Employee can Login to the system, check the status
of the event, register and update the events and the tasks.

Operating Environment:
The operating environment section deals with the basic requirements required to run the system.
The basic requirement includes windows operating system, tomcat server, web browser, and
database system from oracle. Detail specifications are:

Page | 3
Operating System : Windows 7/8/10.

User side scripting : HTML, CSS. JavaScript.

Programming Language : Java.

Web Applications : JDBC, Servlets, JSP.

IDE/Workbench : Eclipse Oxygen.

Database : Oracle 11g.

Server Deployment : Tomcat 8.x.

Processor : intel core i3/i5/i7.

Hard Disk : 512GB.

RAM : 4 GB or more.

Assumption and Dependencies:

Basic knowledge of the computers should be known by the users and we also assure that software user
manual and training documentation will be given to the users.

System Features
Functional Requirements:

1. Administrator Module: The Administrator of the E-Event Management Portal is allowed to

access all the services in the system. The admin can register a new event, view and update the event
details and can register/enroll new employees.

 Login:
Introduction: Admin allowed to access all the services after proper login.
Input: Admin enters the User Id/Email Id and password.
Process Definition: Checks User Id/Email Id and password is valid or not.
Output: Admin is directed to admin home page or shows the message box “Login Failed”.

 Register Events

Introduction: Admin can register a new event.

Input: Admin enters the event name, event type, venue, timing and other details.
Process Definition: The new event is registered with all the details.
Output: The event is regiisterd successfully.

Page | 4
  Add Departments

Introduction: Admin can add different departments according to the requirement of the event.
Input: Admin enters the department name, department id, work type and other details.
Process Definition: The departments are created with all the details.
Output: All the departments are created and assigned their work.

 Add Event Manager

Introduction: Admin can add event manager who is responsible to supervise the employees.
Input: Admin enters the manager’s name, address, contact number, age, work experience and
other details.
Process Definition: The event manager is registered with all his details.
Output: Event Manager’s data is saved successfully.

 View Events
Input: Event name/Event id, Event type.
Process Definition: In the view section admin can view the event types and the status of the
event which has already been saved.
Output: The event details are shown in table format.

 Register Employees
Introduction: Admin can register different employees to do the different tasks.
Input: Admin enters the employee name, address, contact number, age, work experience and
other details.
Process Definition: The employee is registered with all his details and assigns an employee id.
Output: Employee details are created and saved successfully.

 Update Password:

Input: Admin enters the new password and confirm password.

Process Definition: Check new password and confirmation password same or not.
Output: If both the new password and confirm password are same, then update the password.
Or else display an error message, “Password updation failed”.

2. Event Manager: The Event Manager can login to the system, add, update and delete resource
types, view the events and tasks and assigns different tasks to the employees.

 Login:
Introduction: The Event Manager allowed to manage the tasks and supervise the employees.
Input: Event Manager enters the User Id/Email Id and password.
Process Definition: Checks User Id/Email Id and password is valid or not.

Page | 5
 Output: Event Manager is directed to Event Manager home page or shows the message box
“Login Failed”.

 Resource Management

Introduction: Event Manager can add, update or delete the resource types.
Input: Event Manager enters the resource type, amount, source and other details.
Process Definition: All the resource details are saved in the database.
Output: The resource details are updated successfully.

 Task Management

Introduction: Event Manager can assign different tasks to the employees.

Input: Event Manager enters the task name, type, employee name and other details.
Process Definition: All the task details are saved in the database.
Output: The tasks are assigned to the employees and the details are updated successfully.

 Update Password:

Input: Event Manager enters the new password and confirm password.
Process Definition: Check new password and confirmation password same or not.
Output: If both the new password and confirm password are same, then update the password.
Or else display an error message, “Password updation failed”.

3. Employee: The Employee of the E-Event Management Portal is allowed to access the
functionalities provided by the admin. The Employee can Login to the system, check the status of
the event, register and update the events and the tasks.

 Login:
Introduction: The Employee allowed to do the tasks given by the event manager after proper
login.
Input: Employee enters the User Id/Email Id and password.
Process Definition: Checks User Id/Email Id and password is valid or not.
Output: Employee is directed to Employee home page or shows the message box “Login Failed”.

 Check Event Status

Introduction: Employee can check the status of the event.

Input: Employee enters the event name, event type.
Process Definition: Status of the event will be retrieved from the database.
Output: The event status will be shown to the employee.

 Register Events

Introduction: Employee can register a new event.

Input: Admin enters the event name, event type, venue, timing and other details.

Page | 6
 Process Definition: The new event is registered with all the details.
Output: The event is created successfully.

 Update Events

Introduction: Employee can update a particular event.

Input: Admin enters the event name, event typeand other details.
Process Definition: The event status is updated with the inputted data.
Output: The event status is updated successfully.

 Update Tasks

Introduction: Employee can updatethe task details.

Input: Employee enters the task name, type and other details.
Process Definition: All the task details are updated with the inputted data.
Output: The task status are updated successfully.

 Update Password:

Input: Employee enters the new password and confirm password.

Process Definition: Check new password and confirmation password same or not.
Output: If both the new password and confirm password are same, then update the password.
Or else display an error message, “Password updation failed”.

External Interface Requirement

User Interfaces:
 GUI is provided by the software which is self-explanatory.
 User friendly forms, menus and options are contained by the software.
 Designing of the product have to be studied by the developer.
 Software gives warnings with necessary assistance to the clients.
Hardware Interfaces:
 Keyboard and mouse are the input for all the systems designed forms.
 Keyboard and mouse will provide user friendly interaction between the user and the system and
the forms can be viewed through a monitor in GUI.
Software Interfaces:
 The software is developed with all the basic controls and class provided in Java.
 Application Package must be installed.
 A confirmation prompt is presented by the system to the user like continue or cancel operation,
if any modifications to be done.
 All the data’s inserted will be stored in SQL.

Nonfunctional Requirements

Page | 7
Performance Requirements:
 Good memory space is required.
 Should be Error-free.
 Large amount of data should be handled easily.

Safety Requirements:
 Backups can be done regularly.

Security Requirements:
 A password is given to the SQL server.
 Administrator and the end user, who have their own user name and password, have only the
right to open the software.

Software Quality Attributes:

Portability:
 Installation of this project can be done in any windows platform.
Flexibility:
 As the editing/updating takes place, the system keeps on updating the data.

Maintainability:
 In this stage, validation will be referred from the given SRS.

Timeliness:
 The system performs all the operations in less amount of time.

Reliability:
 Validations even for user inputs will be done.
 Avoid incorrect storage of records.

Group Number: 11
Roll No: Name: Signature:

1) 15CS05 Ajit Kumar Sahu

2) 15CS13 Manoj Kumar Sahu

3) 15CS15 Ajaya Kumar Panda

(Signature of Guide)
Page | 8
Page | 9