Software Requirements Specification: Event Management System
Software Requirements Specification: Event Management System
Software Requirements Specification: Event Management System
Specification
for
Prepared by
Department of
IGIT, Sarang
DATE-16.11.2017
DECLARATION
It is hereby declared that this report is an authentic record of my work carried out under the
supervision of Prof. Susanta Kumar Sahoo, DEPT. OF CSEA, IGIT, SARANG. I have not
submitted this report elsewhere for any other degree or diploma.
Department of CSEA
IGIT, SARANG
The main purpose of event management system is to provide a platform for the users
to view the information about the events that took place in the past and the ones which
are about to take place in the near future. The users can be faulty, students and
administrator. They can first login into the website and see through the information
such as details about the events like the venue, theme of the event , participants, chief
guests ,etc. The faculty can keep the record of the attendance also .The administrator
can login and update the information ,delete any unwanted data ,arrange the
information accordingly so that the user can go through an user friendly and know all
the whereabouts of their college.
In the existing system lot of paper work was required and it was time consuming
process. As it was manual process retrieving data was very difficult. More than one
person cannot access the data.
Lot of paper work required.
Man power was more.
Time consuming process.
Event Management System (EMS) is a web based application that supports
online registration and feedback evaluation for event training programs such as games,
seminars and workshops. It helps program attendees, organizers, the authors and the
reviewers in their respective activities.
Development of Event management system is an attempt to address the
problems of managing registration forms, feedback forms and evaluating feedback.
The main goal of this software is to give working solution to store, manage and
consolidate the registration data and the feedback data.
EMS is web-based system for collecting registration forms and evaluating the
feedback automatically. It increases the scope of the report generation even by
generating report over a period of time.
Typical functions supported by TMIS are:
Registering students participants,
Getting attendance from faculty,
Collecting feedback from students,
Generating feedback reports.
The EMS is easy to use, full-featured and flexible participant registration and
feedback assessment web application.
Students
Faculty
Administrator
ADMINISTRATOR does login, upload events, and verify events registration form,
logout.
Use cases:
Login
Upload events
Delete events
Verify events registration
Logout
A STUDENT does login, registration, view events, events registration, event status,
logout.
Use cases:
Login
Registration
View events
Event Registration
Event status
Logout
FACULTY does login, register, and view events, view register students, logout.
Use cases:
Login
Register
View events
View register students
Logout
SERVLETS:
Servlets are Java classes that can generate dynamic HTML content
using print statements. Servlets run in a container, and the APIs provide session and
object life-cycle management. Consequently, using servlets, we gain all the benefits
from the Java platform, which include the sandbox (security), database access API via
JDBC, and cross-platform portability of servlets.
JSP:
A JSP page is basically a web page with traditional HTML and bits of Java code. The
file extension of a JSP page is .jsp rather than .html or .htm, which tells the server that
this page requires special handling that will be accomplished by a server extension or a
plug-in.When a JSP page is called, it will be compiled (by the JSP engine) into a Java
servlet.
Oracle 10g:
Oracle 10g is a flexible and capable RDBMS that has a rich feature set, performs well
on the majority of queries, and has a large support base for access from many different
languages. Oracle 10g released its 5.0 database which added such enterprise features
as triggers, stored procedures and constraints to its Open Source database engines.
This application can run in any environment. The product is developed using
platform-independent language. Hence the product is portable and is platform
independent. The resources of the project will be available, when required.
Hard disk:
The database connectivity requires a hardware configuration that is on-line. This
makes it necessary to have a fast database system running on high rpm hard disk
permitting complete data redundancy and back-up systems to support the primary goal
of reliability.
The system must interface with the standard output device, keyboard and mouse to
interact with this software.
HARDWARE REQUIREMENTS:
Microprocessor: i3
Hard Disk Drive:512MB
RAM: 256MB
Keyboard
Mouse
SOFTWARE REQUIREMENTS:
Technology: java, jdbc, jsp.
Database: SQL.
Web Server: Tomcat Apache8.0.
Operating system: Windows 10.
Browser: Internet Explorer, Chrome
ADMINISTRATOR MODULE: This module is the one who organizes all the users
data, allow the various users to create the id function.
Stimulus/Response Sequences:
Stimulus: Administrator logins with his/her user id and password.
Response: If it is validate user then it get accessed or accessed
denied.
Stimulus: Administrator provides user id and password to all the
users.
Response: Administrator updates, modify the data if required.
USER MODULE:
A user is the one that create an id and then login with the help of it and
performs various activities like view events, register for the events, checks the
events status.
Stimulus/Response Sequences:
Stimulus: User logins with id and passwords.
Response: if it is validate then it get accessed or denied.
FACULTY MODULE:
A faculty is the one who register and checks for the registered students
for attendance and view the events.
Stimulus/Response:
Stimulus: faculty login with id and password.
Response: if it is validate faculty then it get accessed or denied.
The system should be fast, despite many users accessing the database at once.
5.2 Security Requirements
Availability: Availability defines the proportion of time that the system is functional
and working.
6. UML DIAGRAMS:
6.1 USE-CASE DIAGRAM:-
The use case diagram is used to identify the primary elements and processes
that form the system. The primary elements are termed as "actors" and the processes
are called "use cases." The use case diagram shows which actors interact with each
use case.
Use case diagrams model the functionality of a system using actors and use cases. Use cases
are services or functions provided by the system to its users.
registration
login
view event
student
logout
login
faculty
view events
logout
upload event
logout
The class diagram is used to refine the use case diagram and define a detailed design of the
system. The class diagram classifies the actors defined in the use case diagram into a set of
interrelated classes. Each class in the class diagram may be capable of providing certain
functionalities. These functionalities provided by the class are termed "methods" of the class.
Apart from this, each class may have certain "attributes" that uniquely identify the class
Fig: 6.3.2 Class Diagram
7. CONCLUSION
Event management system supports online registration, online application for
programs and online feedback. It is web-based system for collecting and
evaluating the feedback automatically. It increases the scope of online
registration for participating in the event and boosting the morale of the college
as well as the event. It helps event attendees, organizers, students and faculty in
their respective activities.
Thus event management system is easy to use, full-featured and flexible participant
registration and feedback assessment application.