Crackers 1

February 28, 2011

Team name: Crackers 1

Life Rescue System

Software requirement Specification

Team guide:- Soujanya Reddy

Members:- 1.manish shukla

2.sameer singh

3.Ajay pal

4. Bhargavi Vyasaa Bwattu

college name: CMR College of Engineering and Technology

Department:- MCA

State:- Andhra Pradesh

<Crackers 1 >/< College of Engineering and Technology> Page 1

Crackers 1
February 28, 2011

Description

1.0 introduction
1.1 Purpose
This Software Requirements Specification (SRS) specifies
the Requirements of the Life Rescue System (LRS), which
will be used in hospital . This project will gather all the
information about donor who want to donate their body parts
, blood etc It will trace the exact location the basis of mob no
address of that person according to requirement of the
patient to desire hospital and provide exact position nearest
to the hospital by sms and e-mail to donor.

1.2 Scope

this project convenience to donor and receiver .project work

on the according to receiver requirement .and admin will
decide according to nearest donor and give the address of
the donor to receiver through the mail or phone number.
This project will gather all the information about donor who
want to donate their body parts , blood etc It will trace the
exact location the basis of mob no address of that person
according to requirement of the patient to desire hospital and
provide exact position nearest to the hospital.

<Crackers 1 >/< College of Engineering and Technology> Page 2

Crackers 1
February 28, 2011

1.3 Definition acronyms and abbreviations

1)SRS: Software Requirement Specification

2)LRS: life rescue System
3)Client/User: donor and receiver
4)Server: A system that runs in windows always monitoring the
actions.
5)RAM: Random Access Memory
6)SQL: Structured Query Language
7)HTTP: Hyper Text Transfer Protocol
8)UserID: Unique username issued to each donor or receiver on
login time
9)Password: Unique word given to each user donor or receiver

1.4 References
http://www.scribd.com/
http://www.google.co.in/

1.5 Technology to be used

J2EE (servlet, jsp ,jaxp and java beans) application architecture
JAVA Application architecture
DB2 IBM database
AJAX Asynchronous java script and xml
XML Extension Markup language

<Crackers 1 >/< College of Engineering and Technology> Page 3

 Crackers 1
February 28, 2011

1.6 Overview

Overall description :-This section will describe major component of

the system ,interconnection and external interface

Specific Requirements :- This section will describe the function of

actor their rules in the system and the constraints faced by the
System

Overall description
2.1 product perspective

Browsing

Server tracking

View Account

Donner
Admin
Display Details

<Crackers 1 >/< College of Engineering and Technology> Page 4

Crackers 1
February 28, 2011

The client will be given Internet access only by the knowledge of

the server. When a client is accessing Internet the server will be
tracking the username and the account details of the user logged
in. There is also an option for the user to view the account details
of the use
2.2 Software Interface
It enables the donor to interact with the admin and attain access
to the Internet and also leaves a recording the inbuilt database. It
uses java servlets as the front end programming tool and SQL as
the backend application tool.
2.3 Hardware Interface
The server is directly connected to the client systems. Also the
donor has the access to the database for accessing the account
details and storing the login time.
The client access to the database in the server is only read only.

2.4 Production Function

The admin should be running on the client system so as to track

the account details of the donor. The server will only respond to
those systems where
the donor is running.
2.5 User characteristics

<Crackers 1 >/< College of Engineering and Technology> Page 5

Crackers 1
February 28, 2011

General Users: They will be in a position to permit access to the

users in the Internet and acknowledge their account status.
Administrators: They are the core users and are able to add new
donor and receiver to the system and permit them to access the
Internet resources.
Client Users: They login at the client level and this is to get access
to the Internet
at the client level. They can also view their account status in the
client system.
2.6 constraintsEach user must keep their password as
confidential. More over the user must have individual ID for
creating a login in the LRS system. Only Admin can control user
addition and deletion in the LRS system.
2.6 Use Case model description
Donor registrations

Profile management

Organs Specification &

Patient requirement

Organs Management

Address Locater

Database Management

Doctors Requirements

Information sender and Receiver

3.0 Specific requirements

3.1 use case reports

<Crackers 1 >/< College of Engineering and Technology> Page 6
 Crackers 1
February 28, 2011

Hospital manager

Donor registrations

Profile management

Organs Specification &

Patient requirement

Organs Management

Address Locater

Database Management

Admin
Doctors Requirements donor

Information sender and Receiver

3.2 Supplementary Requirements

<Crackers 1 >/< College of Engineering and Technology> Page 7

Crackers 1
February 28, 2011

Performance Requirements –LRS(life rescue system) is real

time and hence should be performed in minimum requirements

Safety Requirements : the data handle LRS is very vital .the server
should always be confirmed to rum properly and the data are saved
to all the databases

Security Requirements :LRS having security at the login time for the
all users those access the LRS

<Crackers 1 >/< College of Engineering and Technology> Page 8