System Requirement Specification

[BANASTHALI BULLETIN BOARD]

[GROUP ID: A4]

[B.Tech Computer Science 6th Semester Session 2018-19]

Guided by: Submitted by:

Dr. Kuldeep Yogi Ayushi Kharkwal (10487)

(AIM & ACT) Kanika Aggarwal (10530)

Madhavi Sharma (10542)
Muskan Bansal (10555)

1. Introduction

In order to grow and learn, we should grab the opportunities given to us which can be done
only if we are aware about them. The “Banasthali Bulletin Board” is a website that will cater
to the Vidyapith displaying events, seminars, sessions etc. and exploring these fields for more
participation and less fuss. The project “Banasthali Bulletin Board” tries to automate the events
and introduces the service at your desk providing the complete information regarding events.
The software allows the sculpting of the database based on the requirement of the event and
then provides all this as well as an easy interface to implement and access/modify registration
details, schedules, results and the like.

1.1 Purpose

The purpose of the website is to solve the problem of lack of awareness regarding the events
being conducted in the university premises.

The software will computerize the existing manual system of events. It requires a lot of paper
work to keep track of schedules, registration, results and is very hectic and time consuming.

The main aim behind developing the software is to provide the students of Banasthali Vidyapith
with easy tools at their fingertips that would help them to streamline their talent regarding their
interest for event participation.

1.2 Scope

1. The scope of the project is global as it is a web application and can be used by any
person anytime.
2. Users can view the application and get the information regarding the events and can
register for their favorite event.
3. System is able to handle extremely large volumes of data (i.e. large database support).
4. It reduces time.
5. Interactive.

1.3 Definitions, Acronyms, and Abbreviations.

1. Administration- The person who can access all areas of product. He is the person who
maintains the software and has the maximum rights.
2. Browser- A browser is an application program that provides a way to look at and
interact with all the information on the World Wide Web.
3. Database- Collection of interrelated data that contains information relevant to
enterprise.
4. Web page- Pages of information placed on network that may contain text, graphics
images, moving pictures, sound files and other type of electronic information.
5. Website- Collection of files called webpage, which can contain text and images.

1.4 Overview
This project enables the students for online registration to participate in different cultural and
technical events.

Section 2: Contains the general description of the system.

Section 3: Specifies the specific requirements of the system including functional requirement
(Use Cases, Use Case Diagram) and non-requirement.

Section 4: Gives the System Design Description using sequence diagram and activity diagram.

Section 6: Gives the Data Design Description using various database tables, Use-Case Diagram
and E-R diagram.

2. The Overall Description

This is an Online event management system software that serves the functionality of
an event manager. The system allows only registered users to login and new users are
allowed to Signup. The users are allowed to subscribe the events of their interest. This
is a web application developed in HTML and Sql. The project provides most of the
basic functionalities required for an event. The users can register for a particular the
event. The subscribers will be having the mails regarding the upcoming events. All
this data is logged in the database. This data is then sent to the administrator (website
owner) and they may interact with the client as per his requirements and his contact
data stored in the database.
2.1 Product Perspective

The main aim of project ‘Banasthali Bulletin Board’ is to maintain the information regarding
the events in Vidyapith. The objective behind developing the website is to provide the students
of Banasthali Vidyapith with easy tools at their fingertips to get notifications about the different
events happening or that are about to happen in different departments and thus on the basis of
this streamline, they will be able to showcase their talent regarding their interest for event
participation.

HTML CLIENT
HTTP /
(CUSTOMER)
HTTPS
IIS DATA
BASE
ADMIN TCP/IP
APPLICATION SERVER D/B
SERVER

USER COMMUNICATION PROTOCOL

 2.1.1 Product Function

1. Users can sign up as a participant.

2. Admin can login.
3. Admin can add new events along with respective departments.
4. Participants can register for different workshops.
5. Students are informed about different technical and cultural events.
6. Students can subscribe to events of their area of interest and get notifications regarding
them.
7. Result generation by Admin.

2.1.2 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.

2.1.3 Software Interfaces

Specify the use of other required software products and interfaces with other application
systems. For each required software product, include:

(1) Name
(2) Mnemonic
(3) Specification number
(4) Version number
(5) 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.

2.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.

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.

2.1.4 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.

2.2 User Characteristics

The user must be familiar to work with GUI components.

1. Administrator: The head of the database, only he/she can add events and other event
constraints. He/she should be well-versed in using the system and should be known to the
database. Since this class of users is the basic controller of all the data in the event, they are to
be trained in designing proper schema, entering meaningful data, proper moderation and
optimal use of the database.

3. Participants: In both the case of the individual and the group participant, we assume the
user is computer literate, well aware of English, has a valid ID and also types in the right kind
of data.

2.3 Constraints

1. Our project is GUI based application.

2. Login ID and password is used for the identification of the authorized user.
3. The system is dependent on the departments for the event details.
 4. The system is working for a single sever.
5. The entries have to be done manually by the administrators.
6. Online registration must be done till last date announced by admin.
7. Unique ID must be created for all the students who are subscribing/registering in the
system.

2.4 Technologies Used

 Front End: HTML,CSS, Bootstrap

 Back End: Java, SQL Server 2008
 Design Tool: NetBeans IDE 8.0.2

3. Specific Requirements

This section contains all the software requirements at a level of detail sufficient to enable
designers to design a system to satisfy those requirements, and testers to test that the system
satisfies those requirements. Throughout this section, every stated requirement should be
externally perceivable by users, operators, or other external systems. These requirements
should include at a minimum a description of every input (stimulus) into the system, every
output (response) from the system and all functions performed by the system in response to an
input or in support of an output. The following principles apply:

(1) Specific requirements should be stated with all the characteristics of a good SRS
 correct
 unambiguous
 complete
 consistent
 ranked for importance and/or stability
 verifiable
 modifiable
 traceable
(2) Specific requirements should be cross-referenced to earlier documents that
relate
(3) All requirements should be uniquely identifiable (usually via numbering like
3.1.2.3)
(4) Careful attention should be given to organizing the requirements to maximize
readability (Several alternative organizations are given at end of document)

Before examining specific ways of organizing the requirements it is helpful to understand the
various items that comprise requirements as described in the following subclasses. This
section reiterates section 2, but is for developers not the customer. The customer buys in with
section 2, the designers use section 3 to design and build the actual application.
Remember this is not design. Do not require specific software packages, etc unless the
customer specifically requires them. Avoid over-constraining your design. Use proper
terminology:

The system shall… A required, must have feature

The system should… A desired feature, but may be deferred till later

The system may… An optional, nice-to-have feature that may never make it to implementation.

Each requirement should be uniquely identified for traceability. Usually, they are numbered
3.1, 3.1.1, 3.1.2.1 etc. Each requirement should also be testable. Avoid imprecise statements
like, “The system shall be easy to use” Well no kidding, what does that mean? Avoid
“motherhood and apple pie” type statements, “The system shall be developed using good
software engineering practice”

Avoid examples, This is a specification, a designer should be able to read this spec and build
the system without bothering the customer again. Don’t say things like, “The system shall
accept configuration information such as name and address.” The designer doesn’t know if
that is the only two data elements or if there are 200. List every piece of information that is
required so the designers can build the right UI and data tables.

3.1 Functional Requirements

Module 1 Admin
I/P- Login and password
Process- Information is verified from the D/B.
O/P- Logged in, admin can handle all the D/B updating .He can add new events,
announce the important dates, manage workshops and give results of different
events.

Module 2 Registration
I/P- Student name, smart card ID, password, course, their field of interest,
email id, contact no.
Process- All information is stored in D/B and student is registered.
O/P- Student gets registered/has subscribed for the event.

Module 3 Event
I/P:-Click on the particular event for which you want to get the information.
Process- Information is fetched from D/B.
O/P- Information is displayed.

Module 4 Results
I/P- Click on particular results item (registration result or event result).
 Process:-Information is fetched from D/B.
O/P- Results of different technical or cultural events are displayed.

Module 5 Dates and Announcements

I/P- Click on particular date.
Process- Important dates and announcements are fetched from the D/B which
was updated by the Admin.
O/P- Information regarding the scheduling of the different events, results and
the like are displayed.

Use cases

Use case 1- Login

USE CASE NO. 1

USE CASE NAME Login

ACTORS Admin

DESCRIPTION Login

PRE-CONDITION The users must be the member of the system

POST-CONDITION

PRIORITY High

NORMAL COURSE 1) Actors enter their username

EVENTS 2) Actors enter their password

3) Actors click login button

4) System connects to database

5) Homepage displayed

ALTERNATIVE COURSE 1) Actors can enter their username and password incorrectly

EVENTS 2) Error message appears

3) Continue with step 1 in the normal course events

4) An error may occur during the database operation.

Use case 2- Registration

USE CASE NO. 2

USE CASE NAME Registration

ACTORS Users

DESCRIPTION Login

PRE-CONDITION Users Signup

POST-CONDITION

PRIORITY Medium

NORMAL COURSE 1) Actors enter their smart card id

EVENTS 2) Actors enter their password

3) Actors enter required information

4) Actor click register/subscribe button

5) System connect to database

6) A message appears which shows the subscription applied

ALTERNATIVE COURSE 1) Same smart card id exists in database

EVENTS 2) Error message will appear

3) Continue with step1 in normal course events

4) An error may occur during database operation

5) System show error messages

Use case 3- Admin Tool

USE CASE NO. 3

USE CASE NAME Admin Tool

ACTORS Admin

DESCRIPTION Updating the database for the site

PRE-CONDITION Administration must be logged on to the system

POST-CONDITION

PRIORITY High

NORMAL COURSE 1) The admin must be logged on to the System which is defined
EVENTS on use case no.1.

2) The Admin must click on the admin operations.

3) The System gives opportunity to the admin to do the

following :

a) View all registrations/subscriptions regarding

events

b) The admin update the registration result, event

result and important date & announcements.

c) Add new event.

ALTERNATIVE COURSE 1) The system cannot access to the database

EVENTS 2) The system puts a message on the window about the

problem.

3) Continue the step2 in the normal course events

Use case 4- Participants Tool

USE CASE NO. 4

USE CASE NAME Participants Tool

ACTORS Participants

DESCRIPTION View information regarding events and can register for it

PRE-CONDITION Participants must be logged to the system for the registration

POST-CONDITION

PRIORITY Medium

NORMAL COURSE 1) The participants must be logged on to the System which

EVENTS is defined on use case no.1.

2) The participants must click on the options on the home

page.

3) View all information regarding events

4) Registration for different events and workshops.

5) View all important dates & announcements.

6) Give their feedback regarding events.

ALTERNATIVE COURSE 1) The system cannot access to the database

EVENTS 2) The system puts a message on the window about the

problem.

3) Continue the step2 in the normal course events

Non-functional Requirements (Software System Attributes)

 3.2.1 AVAILABILITY
The availability of this web-site depends upon the Internet connection of the client. Since this
is client-server related web-site, it shall be attainable all the time. User should have an account
to enter the system, even if the user doesn’t have an account he/she can see the information
which will be displayed on the homepage of the web-site.

3.2.2 SECURITY
Security is one of the crucial parts of this project. Only the valid user will be allowed to
access the database. The authorization mechanism of the system will block any unwanted
attempts to the server and also let the system decide on which privileges the user may have.
The system has different types of users so there are different levels of authorization. Also the
system is secure as it does not allow user to upload any document from his/her side.

3.2.3 RELIABILITY

The system made is reliable i.e. not only the program will not crash but other
reliability features like proper exception handling ,maintenance of integrity and
consistencies of database are taken care of . A backup file is maintained so that in
case of system crash, the data will not be affected.

3.2.4 PORTABILITY
The system is developed using java technology that is why the application can run on
any system i.e it’s portable.

3.2.5 MAINTAINABILITY
The project is made in a simple and lucid style so that future maintenance of the
project is easy .All the variables are with valid variable names; different module for
each different function is made to enhance the readability of the code.This website
will follow the modular structure so it will be easy to maintain.

SDS
1. Introduction

System Design Specification tells us HOW our software is going to built. It includes various
diagrams to show the entire database and relationship among all database tables. The project
“Banasthali event management system” tries to automate the event (Mayukh) management
in Banasthali University, Tonk, Rajasthan. As the name suggests this projects provides the
service at your desk which tries to provide the complete information regarding events.

Our project is one-step solution for managing the event .The software allows the sculpting of
the database based on the requirement of the event and then provides all this as well as an easy
interface to implement and access/modify registration details ,schedules, results and the like.

1.1 Purpose

1. The purpose of the website is to solve the problem of lack of awareness regarding the
events being conducted in the university premises.

2. The software will computerize the existing manual system of event. The existing manual
system require a lot of paper work to keep track of schedules, registration, results, this is very
hectic and time consuming.

3. The main aim behind developing the software is to provide the students of Banasthali with
easy tools at their fingertips that would help them to streamline their talent regarding their
interest for event participation

1.2 Scope

1. The scope of the project is global as it is a web application and can be used by any person
anytime.

2. Users can view the application and get the information regarding the events and can register
for their favorite event.

3. System is able to handle extremely large volumes of data (i.e. large database support).

4. Students can also give their feedback after visiting the application in the form of suggestions,
comments or queries.

5. It reduces time.

6. Interactive.
 System Requirement Specification
[BANASTHALI BULLETIN BOARD]

[GROUP ID: A4]

[B.Tech Computer Science 6th Semester Session 2018-19]

Guided by: Submitted by:

Dr. Kuldeep Yogi Ayushi Kharkwal (10487)

(AIM & ACT) Kanika Aggarwal (10530)

Madhavi Sharma (10542)
Muskan Bansal (10555)

1. Introduction
In order to grow and learn, we should grab the opportunities given to us which can be done
only if we are aware about them. The “Banasthali Bulletin Board” is a website that will cater
to the Vidyapith displaying events, seminars, sessions etc. and exploring these fields for more
participation and less fuss. The project “Banasthali Bulletin Board” tries to automate the events
and introduces the service at your desk providing the complete information regarding events.
The software allows the sculpting of the database based on the requirement of the event and
then provides all this as well as an easy interface to implement and access/modify registration
details, schedules, results and the like.

1.1 Purpose

The purpose of the website is to solve the problem of lack of awareness regarding the events
being conducted in the university premises.

The software will computerize the existing manual system of events. It requires a lot of paper
work to keep track of schedules, registration, results and is very hectic and time consuming.

The main aim behind developing the software is to provide the students of Banasthali Vidyapith
with easy tools at their fingertips that would help them to streamline their talent regarding their
interest for event participation.

1.2 Scope

6. The scope of the project is global as it is a web application and can be used by any
person anytime.
7. Users can view the application and get the information regarding the events and can
register for their favorite event.
8. System is able to handle extremely large volumes of data (i.e. large database support).
9. It creates awareness regarding the events being organized in the campus and saves the
time to go to the departments and read about them.
10. The website is interactive in nature and also saves time.

1.3 Definitions, Acronyms, and Abbreviations

Definitions

6. Administration- The person who can access all areas of product. He is the person who
maintains the software and has the maximum rights.
7. Browser- A browser is an application program that provides a way to look at and
interact with all the information on the World Wide Web.
 8. Database- Collection of interrelated data that contains information relevant to
enterprise.
9. Web page- Pages of information placed on network that may contain text, graphics
images, moving pictures, sound files and other type of electronic information.
10. Website- Collection of files called webpage, which can contain text and images.

Acronyms

11. HTML: Hypertext Mark-up Language is a mark-up language used to design static web
pages.
12. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol
between web browser & a Web Server.
13. HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (Secure Socket
Layer).
14. WWW: World Wide Web
15. TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication
protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two
main ones being TCP and IP.
16. RAM: Random Access Memory
17. HDD: Hard Disk Drive
18. IIS: International Information Server
19. IE: Internet Explorer

1.4 Overview

This project enables the students for online registration to participate in different cultural and
technical events.

Section 2: Contains the general description of the system.

Section 3: Specifies the specific requirements of the system including functional requirement
(Use Cases, Use Case Diagram) and non-requirement.

Section 4: Gives the System Design Description using sequence diagram and activity diagram.

Section 6: Gives the Data Design Description using various database tables, Use-Case Diagram
and E-R diagram.

2. The Overall Description

The project “Banasthali Bulletin Board” tries to automate the events and introduces the service
at your desk providing the complete information regarding events. . The system allows only
registered users to login and new users are allowed to Signup. The users are allowed to
subscribe the events of their interest. This is a web application developed in HTML and SQL.
The project provides most of the basic functionalities required for an event. The users can
register for a particular the event. The subscribers will be having the mails regarding the
upcoming events. All this data is logged in the database. This data is then sent to the
administrator (website owner) and they may interact with the client as per his requirements and
his contact data stored in the database.

2.1 Product Perspective

The main aim of project ‘Banasthali Bulletin Board’ is to maintain the information regarding
the events in Vidyapith. The objective behind developing the website is to provide the students
of Banasthali Vidyapith with easy tools at their fingertips to get notifications about the different
events happening or that are about to happen in different departments and thus on the basis of
this streamline, they will be able to showcase their talent regarding their interest for event
participation.

HTML CLIENT
HTTP /
(CUSTOMER)
HTTPS
IIS DATA
BASE
ADMIN TCP/IP
APPLICATION SERVER D/B
SERVER

USER COMMUNICATION
PROTOCOL

2.1.1 Product Function

8. Users can sign up as a participant.

9. Admin can login.
10. Admin can add new events along with respective departments.
11. Participants can register for different workshops.
12. Students are informed about different technical and cultural events.
13. Students can subscribe to events of their area of interest and get notifications regarding
them.
14. Result generation by Admin.

2.1.2 Hardware Interfaces

1. Server side requirements

 Processor: Pentium p4 (1-2 GHZ) or onwards.
 RAM: 1 GB or more.
 HDD: 20 GB (free space excluding data size).
2. Client side requirements
 Processor: Pentium p2 (1 GHZ) or onwards.
 RAM: 128 MB or more
 HDD: 8 GB or more.
3. Developer side requirements
 Processor: Pentium p4 (1-2 GHZ) or onwards.
 RAM: 2 GB or more.
 HDD: 10 to 12 GB or more

2.1.3 Software Interfaces

1. Server side requirements

 Operating system: Microsoft Windows Server 2000 or onwards
 Web server: IIS 6.0
2. Client side requirements
 Operating system: Any operating system.
 Browser: Any browser compatible with IE5.0.
3. Developer side requirement
 Operating system: Windows XP or onwards.
 Browser: Any browser.
  Frontend: CSS, HTML, JSP, Bootstrap
 Backend: SQL Server 2008.
 Design Tools: Net Beans 8.1

2.1.4 Communications Interfaces

1. Web browser (Mozilla, Opera etc.)

2. Internet connection

3. Server on Internet will be using HTTP/HTTPS protocol.

4. Client on Intranet will be using TCP/IP protocol

2.2 User Characteristics

The user must be familiar to work with GUI components.

1. Administrator: The head of the database, only he/she can add events and other event
constraints. He/she should be well-versed in using the system and should be known to the
database which basically could be a person from the department or a student representative.
Since this class of users is the basic controller of all the data in the event, they are to be trained
in designing proper schema, entering meaningful data, proper moderation and optimal use of
the database.

3. Participants: In both the case of the individual and the group participant, we assume the
user is computer literate, well aware of English, has a valid ID of Banasthali Vidyapith (for
registration and subscription) and also types in the right kind of data.

2.3 Constraints

8. Our project is GUI based application.

9. Login ID and password is used for the identification of the authorized user.
10. The system is dependent on the departments for the event details.
11. The system is working for a single sever.
12. The entries have to be done manually by the administrators.
13. Online registration must be done till last date announced by admin.
14. Unique ID must be created for all the students who are subscribing/registering in the
system.
 2.4 Technologies Used

 Front End: HTML,CSS, Bootstrap,JSP

 Back End: Java, SQL Server 2008
 Design Tool: NetBeans IDE 8.0.2

3. Specific Requirements

3.1 Functional Requirements

Module 1 Admin
I/P- Login and password
Process- Information is verified from the D/B.
O/P- Logged in, admin can handle all the D/B updating .He can add new events,
announce the important dates, manage workshops and give results of different
events.

Module 2 Registration
I/P- Student name, smart card ID, password, course, their field of interest,
email id, contact no.
Process- All information is stored in D/B and student is registered.
O/P- Student gets registered/has subscribed for the event.

Module 3 Event
I/P:-Click on the particular event for which you want to get the information.
Process- Information is fetched from D/B.
O/P- Information is displayed.

Module 4 Results
I/P- Click on particular results item (registration result or event result).
Process:-Information is fetched from D/B.
O/P- Results of different technical or cultural events are displayed.

Module 5 Dates and Announcements

I/P- Click on particular date.
Process- Important dates and announcements are fetched from the D/B which
was updated by the Admin.
 O/P- Information regarding the scheduling of the different events, results and
the like are displayed.

Use cases
Use case 1- Login

USE CASE NO. 1

USE CASE NAME Login

ACTORS Admin

DESCRIPTION Login

PRE-CONDITION The users must be the member of the system

POST-CONDITION

PRIORITY High

NORMAL COURSE 1) Actors enter their username

EVENTS 2) Actors enter their password

3) Actors click login button

4) System connects to database

5) Homepage displayed

ALTERNATIVE COURSE 1) Actors can enter their username and password incorrectly

EVENTS 2) Error message appears

3) Continue with step 1 in the normal course events

4) An error may occur during the database operation.

Use case 2- Registration

USE CASE NO. 2

USE CASE NAME Registration

ACTORS Users

DESCRIPTION Login

PRE-CONDITION Users Signup

POST-CONDITION

PRIORITY Medium

NORMAL COURSE 1) Actors enter their smart card id

EVENTS 2) Actors enter their password

3) Actors enter required information

4) Actor click register/subscribe button

5) System connect to database

6) A message appears which shows the subscription applied

ALTERNATIVE COURSE 1) Same smart card id exists in database

EVENTS 2) Error message will appear

3) Continue with step1 in normal course events

4) An error may occur during database operation

5) System show error messages

Use case 3- Admin Tool

USE CASE NO. 3

USE CASE NAME Admin Tool

ACTORS Admin

DESCRIPTION Updating the database for the site

PRE-CONDITION Administration must be logged on to the system

POST-CONDITION

PRIORITY High

NORMAL COURSE 1) The admin must be logged on to the System which is defined
EVENTS on use case no.1.

2) The Admin must click on the admin operations.

3) The System gives opportunity to the admin to do the

following:

a) View all registrations/subscriptions regarding

events

b) The admin update the registration result, event

result and important date & announcements.

c) Add new event.

ALTERNATIVE COURSE 1) The system cannot access to the database

EVENTS 2) The system puts a message on the window about them.
3) Continue the step2 in the normal course events
Use case 4- Participants Tool

USE CASE NO. 4

USE CASE NAME Participants Tool

ACTORS Participants

DESCRIPTION View information regarding events and can register for it

PRE-CONDITION Participants must be logged to the system for the registration

POST-CONDITION

PRIORITY Medium

NORMAL COURSE 1) The participants must be logged on to the System which

EVENTS is defined on use case no.1.

2) The participants must click on the options on the home

page.

3) View all information regarding events

4) Registration for different events and workshops.

5) View all important dates & announcements.

6) Give their feedback regarding events.

ALTERNATIVE COURSE

EVENTS 1) The system cannot access to the database.

2) The system puts a message on the window about them.

3) Continue the step2 in the normal course events.

USE CASE FO PARTICIPANT

Login/Logout

bo
Registrations
for Events and
Workshops

Updating
results of
Participants

Managing events
and Work shops
 USE CASE FOR ADMIN

Login/Logout

Announce
important
dates
bob
Add Events

Edit Events

View all profiles

Updating
results of
participants

Managing events
and workshops
Non-functional Requirements (Software System Attributes)

3.2.1 AVAILABILITY
The availability of this web-site depends upon the Internet connection of the client. Since this
is client-server related web-site, it shall be attainable all the time. User should have an account
to enter the system, even if the user doesn’t have an account he/she can see the information
which will be displayed on the homepage of the web-site.

3.2.2 SECURITY
Security is one of the crucial parts of this project. Only the valid user will be allowed to
access the database. The authorization mechanism of the system will block any unwanted
attempts to the server and also let the system decide on which privileges the user may have.
The system has different types of users so there are different levels of authorization. Also the
system is secure as it does not allow user to upload any document from his/her side.

3.2.3 RELIABILITY

The system made is reliable i.e. not only the program will not crash but other
reliability features like proper exception handling ,maintenance of integrity and
consistencies of database are taken care of . A backup file is maintained so that in
case of system crash, the data will not be affected.

3.2.4 PORTABILITY
The system is developed using java technology that is why the application can run on
any system i.e. it’s portable.

3.2.5 MAINTAINABILITY
The project is made in a simple and lucid style so that future maintenance of the
project is easy .All the variables are with valid variable names; different module for
each different function is made to enhance the readability of the code.This website
will follow the modular structure so it will be easy to maintain.
System Design Specification
1. Introduction

System Design Specification tells us HOW our software is going to built. It includes various
diagrams to show the entire database and relationship among all database tables. The project
“Banasthali event management system” tries to automate the departmental events of Banasthali
Vidyapith. As the name suggests this projects provides the service at your desk which tries to
provide the complete information regarding events.

Our project is one-step solution for managing the event .The software allows the sculpting of
the database based on the requirement of the event and then provides all this as well as an easy
interface to implement and access/modify registration details ,schedules, results and the like.

1.3 Purpose

1. The purpose of the website is to solve the problem of lack of awareness regarding the
events being conducted in the university premises.

2. The software will computerize the existing manual system of event. The existing manual
system require a lot of paper work to keep track of schedules, registration, results, this is very
hectic and time consuming.

3. The main aim behind developing the software is to provide the students of Banasthali with
easy tools at their fingertips that would help them to streamline their talent regarding their
interest for event participation.

1.4 Scope

1. The scope of the project is global as it is a web application and can be used by any
person anytime.
2. Users can view the application and get the information regarding the events and can
register for their favorite event.
3. System is able to handle extremely large volumes of data (i.e. large database support).
4. It creates awareness regarding the events being organized in the campus and saves the
time to go to the departments and read about them.

5. The website is interactive in nature and also saves time.

 1.5 Overview

Section 2: Specifies detailed description of application using Sequence diagram, Activity

diagram
Section 3: Specifies data designing (all database tables).
Section 4: Specifies user interface design.

2. System Architectural Design

2.1 High-level Design Overview

The User/Participant, at first tier, communicates with the Internet to access details from the
database with the help of a web server (a type of IIS) with web server and SQL server being at
second tier and third tier respectively.

2.2 Detailed Description of Components

2.2.1 Activity Diagram

Activity diagrams are graphical representation of workflows of stepwise activities and actions
with support for choice, iteration and concurrency. In the UML, activity diagrams are intended
to model both computational and organizational process. There are two activity diagrams that
we will be describing:

A) Login/Signup Activity
B) Activities that can be performed by the users and the administrators.
 Admin Participant

Selecting Events

Announce View Participants

Add Events Registration
Dates

Give
Give Event Registration Event Registration Event Subscription
Results Result

Managing Registered Subscription

Events Successfully mail sent

Subscription
View Results
Successful

View Results

Logout
2.1.2 Sequence Diagram
A sequence diagram is an interaction diagram that shows how processes operate with one
another and in what order. It is a construct of message sequence chart. A sequence diagram
shows object interaction arranged in time system.

A) Sequence Diagram for Administrator

B) Sequence Diagram for Participants
ADMIN INTERFACE DATABASE

LOGIN CHECK
P

VERIFIED

LOGGED IN

ADD DATES AND ANNOUNCEMENTS STORE

UPDATE LIST
SHOW LIST

INSERT REGISTRATION RESULT STORE

UPDATE LIST
SHOW LIST

ADD EVENT ADD

RESPONSE UPDATE EVENT LIST

INSERT WINNER LIST

STORE
 WINNER LIST RESPONSE

PARTICIPANTS INTERFACE DATABASE

TSTS
LOGIN CHECK
P

VERIFIED RESPONSE

SHOW DATE DATA FETCH

RESPONSE
SHOW LIST

REGISTRATION STORE DATA

UPDATE LIST
REGISTERED

SHOW EVENT RESULT DATA FETCH

SHOW LIST RESPONSE

2.2 Component Interface Description

Admin
I/P- Login and password

O/P- Logged in, admin can handle all the D/B updating .He can add new events, announce the
important dates, results of different events, and view the feedback of the students regarding
events.

Registration
I/P- Student name, smart card ID, password, course, their field of interest, email id, contact no.

O/P- Student gets registered to be part of team member and participants.

Event
I/P- Click on particular event for which you want to get information.

O/P- Information displayed.

Results
I/P- Click on particular results item (registration result or event result).

O/P:-The desired information as different technical or cultural event winner and the like are
displayed.

Dates and Announcements

I/P- Click on particular date.

O/P- Information regarding the scheduling of the different events, results and the like are
displayed.
 Data design

Event Registration Table

Field Type Description Constraints

p_id Number(20) Participant ID Primary key

e_id Number(20) Event ID Not null

e_name Varchar2(50) Event name Not null

p_course Varchar2(20) Participant course Not null

Admin Table
Field Type Description Constraints

a_id Number(20) Admin ID Primary key

a_name Varchar2(50) Admin name Not null

a_pass Varchar2(20) Admin password Not null

a_dept Varchar2(50) Admin department Not null

Participant Table
Field Type Description Constraints

p_id Number(20) Participant ID Primary Key

p_name Varchar2(50) Participant name Not null

p_pass Varchar2(20) Participant password Not null

p_email Varchar2(50) Participant email Not null

Event Table
Field Type Description Constraints

e_id Number(20) Participant ID Primary Key

e_name Varchar2(50) Participant name Not null

e_venue Varchar2(20) Event venue Not null

e_time Time Event time Not null

e_sdate Date Event start date Not null

e_edate Date Event end date Not null

e_type Varchar2(20) Event type Not null

Subscribers Table
Field Type Description Constraints

p_id Number(20) Participant ID Not null

s_id Number(20) Subscribers ID Primary key

e_type Varchar2(20) Event type Not null

Winners Table
Field Type Description Constraints

e_id Number(20) Event ID Not null

P_id Number(20) Participant ID Primary key

p_name Varchar2(50) Participant name Not null

Announcment Table
Field Type Description Constraints

e_id Number(20) Event ID Primary key

date Date Event date Not null

content Varchar2(500) Event content Not null

4) User Interface Design

The user will firstly view the landing page of the website. Navigating through it, the user can
either sign up or login. He/she can view the website’s events page if no login activity is
performed. The user can explore through the events and perform tasks under the constraints
provided to them. For example: the participant cannot add an event as this functionality is not
provided to them. Only the admin can add events.

4.1 Description of the user interface

The landing page will consist of links to the login and sign up page and the home page as well.
The user can click on them to view various events and register for them.

The home page will be different for the participant and the admin because of the functionality
difference. The participant accessible page will show various events, options to register for
them, subscribing events based on there are of interest, etc. The admin accessible page will
show the options to view the database entries and also update them. The admin can add the
events and announce the important dates as well.

4.2 Screen images

Above is a screenshot of the view of the landing page of the “Banasthali Bulletin Board”.
 PARTICIPANT
+ p_id : String

- email_id : String

- p_name: : String
ADMIN
- pwd : String
+ a_id : String

- a_name : String + login()

- a_pwd : String + view()

- register()
+ a_dept : String
- subscribe()
+ login()
-viewresult()
- update()

+ view() 1..*
+ announce()
.*
+ add_event()

1. .*
1..* VIEW
.*

VIEW
MAKES

SUBSCRIPTION
*
-<p_id : String

+ type : String

+ s_id : String

- checklogin()

- sendmail()
VIEW

*
*
 WINNER
+e_id : String

-p_id : String

-name : String

ANNOUNCEMENTS
+ e_id : String

+data : String

+content : String