Scribd
Upload
85 views

Software Requirements Specification (SRS) : Purpose

The document provides a software requirements specification for an event management system. It describes performance requirements including limits on users (1000) and files (10,000), with responses below 2 seconds. It outlines design constraints such as hardware, software, reliability, security, and interface requirements. Functions are described like registration, login, forgot password, logout, selecting and cancelling events. The admin can add events and manage the user database. Users can provide feedback.

Uploaded by

Prashant Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
85 views

Software Requirements Specification (SRS) : Purpose

The document provides a software requirements specification for an event management system. It describes performance requirements including limits on users (1000) and files (10,000), with responses below 2 seconds. It outlines design constraints such as hardware, software, reliability, security, and interface requirements. Functions are described like registration, login, forgot password, logout, selecting and cancelling events. The admin can add events and manage the user database. Users can provide feedback.

Uploaded by

Prashant Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Requirements Specification (SRS)

Purpose

This Software Requirements Specification provides a complete description of all the functions
,performance,design constraints and exertnal interfaces for Event Management System.

Performance Requirements

· Static Requirements: Number of users must be atmost 1000 and the number of files in
the database must be no more than 10,000.

· Dynamic Requirements :The system must be interactive and the delays involved must be
less .So in every action-response of the system, there are no immediate delays. In case
of opening windows forms, of popping error messages and saving the settings or
sessions there is delay much below 2 seconds. In case of opening databases and
evaluation there are no delays and the operation is performed in less than 2 seconds for
opening , posting > 95% of the files. Also when connecting to the server the delay is
based on the distance of the 2 systems and the configuration between them so there is
high probability that there will be or not a successful connection in less than 20 seconds
for sake of good communication.

Design Constraints

· Standard Complaince : All the languages and database format must be according to the
software requirements listed below.

· Hardware Requirements:

1. Pentium or AMD processors with speed minimum 1GHz.

2. Minimum256MB RAM.

3. Accelerated Graphics Card.

4. Minimum 2GB Hard Disk.

5. Better performance with 82KB and above Cache Memory.

· Software requirements:

Database: MS SQL Server2000 with Microsoft SQL Desktop Engine installed.

Framework: NET Framework Version

Platform: Windows XP/NT Server


Components: Windows Components needs to be updated by Service Packs (XP/NT)

Web Server: Web Matrix Server.

Technology: ASP.Net

Server Side Coding Tool: C#

Browser: Internet Explorer6.0

· Reliability and Fault Tolerance :

1 All the users must be backed up.

2 The database must be updated regularly and must be properly maintained .

3 Users are authenticated.

· Security:

1 The access to all the databases is available only to admin.

2 The transactions happening must be controlled by the admin .

3 A log of all activities must be stored

4 Cryptography techniques will be used.

External Interface Requirements

· User Interfaces : The users will work on a graphical user interface. All the required
steps for the user to perform must me specified on each page so that it is easy for users
to understand the procedure to perform. The steps must be brief so that the content is
not a trouble.There must be a search bar on every page for basic queries. Limited
feedbacks and reviews should be there on main page to give an user overall idea of the
website.

· Software Interfaces : The system shall make use of the operating system calls to the file
management system to store and retrieve files.

Registration

Description : To enter into this site user has to register himself first. Requirements of
registration are first name, last name, user name, email-id, password, confirm password
etc.
Input : User Details
Output : Filled Registration Details.
Functionality : User details are included with database. Password constraint is checked
as per Validation.

User Login

Description : The System provides facility to login into the system.


Input : Enter username and password
Output : User Profile page
Processing : The system will check the input of user and if valid then login is done.
Otherwise user will be asked to re-enter the username and password.

Forgot Password

Description : The user can send reset link to the mail id to reset password.
Input : Email id
Output : Reset link send to Email id.
Processing : By reset link we can easily change the password and update store in
database.

Logout

Description : The system provides the facility to logout from the site
Input : Select logout option
Output : Logout from the system
Processing : User will logout

Selecting events and sub-events

Description : The user can select the event and also select payment method.
Input : Main event , Sub event, Enrollment number
Output : Event selected Successfully ,also see all detail and cancellation option also .
Processing : The system will add selected data into both main event database as well as
sub-event database.Necessary mails will be
sent to sub-event supplier regarding the event to be held.

Cancellation of An Event
Description : An user can cancel the sub-events in proper time frame.
Input : Enter the user details
Output: A cancellation mail will be generated.
Processing: Cancellation mail will be sent to sub-event supplier.

Admin Side

Description:The Admin can add main event and sub-event also.He will manage the users
database too.
Input : main event, sub-event,check for user details.
Output : Add successfully in database.
Processing : The system will add selected data into database.

Feedbacks

Description : An user can give feedbacks after the event happens.


Input : Views of user
Output : Add feedbacks to main page.
Processing : New feedbacks will be regularly updated on main page.

You might also like