KARPAGAM COLLEGE OF ENGINEERING

SAVE HER FROM CANCER

SOFTWARE REQUIREMENTS SPECIFICATION

TEAM
SUNBEAMZ

MEMBERS
ARUN VARGHESE
KIRAN VARGHESE
JEFFRY JAMES P.
NIKHIL K.P.

PROJECT GUIDE
DHANABAL S.
LECT. KARPAGAM COLLEGE OF ENGINEERING.
 INDEX AND TABLES

1) Introduction: ..............................................................................................................................3

1.1) Purpose: ...............................................................................................................................3

1.2) Scope: ..................................................................................................................................3

1.3) Abbreviations:.....................................................................................................................3

1.4) References: ...........................................................................................................................5

1.5) Technologies: .......................................................................................................................5

2) Overall Description:..................................................................................................................6

2.01) Product Perspective: ..........................................................................................................6

2.02) Software Interface:.............................................................................................................7

2.03) Hardware Interface: ...........................................................................................................7

2.04) Communication Interface:.................................................................................................7

2.05) Product Function:...............................................................................................................7

2.06) User Characteristics:..........................................................................................................8

2.07) Constraints: ........................................................................................................................8

2.08) Use-Case Model Survey:...................................................................................................8

2.09) Architecture diagram:......................................................................................................10

2.10) Database design: ..............................................................................................................11

2.11) Assumptions and Dependencies: ....................................................................................14

3) Specific Requirements: ...........................................................................................................14

3.1) Use-Case Reports:..............................................................................................................14

3.2) Supplementary Requirements: ..........................................................................................43

INTRODUCTION:

1.1) PURPOSE: This system provides a wide range of user interface desk dealing with various types of
cancer affecting womens in day-to-day life. It also provides various treatments through online
medical assistance from doctors around the globe.

1.2) SCOPE:
>> The site contains write-ups which give a general awareness to the public about the
hazardous cancers which can affect women.
>> The users could be able to clarify their doubts about the disease with medical
practitioners.
>> Woman Welfare organizations announces the launch of programs or diagnosis camps
through the site.
>> A regular newsletter should be sent to registered users about the latest developments
in regard to the disease.
>> Admin would be able to view strategic data and graphs about contributors to the site,
regular users, age groups of users etc.
>> Disease affected or cured women can share their experiences through the site. Their
names are disclosed ,if they wish to do so.
>> Users attend Multiple Choice Questions (MCQs) to help identify whether they have
started to show the initial symptoms with doctors assistance information.
>> Information regarding the nearest hospital which provided diagnosis facility as well as
treatment for the disease according to the address given by the users.
>> The most active doctor or medical practitioner in each disease category will be adored
“e-certificate of appreciation” on yearly basis.
>> Facilitate appropriate communication between all stakeholders - Discussion
forum/chat/mail/polls

1.3) ABBREVATION

>> HTML: Hypertext Markup Language is a markup language used to design static web
pages.
>> EJB: Enterprise Java Beans.
 >> J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—
for developing and running distributed multitier architecture Java applications,
based largely on modular software components running on an application server.
>> DB2: DB2 Database is the database management system that delivers a flexible and
cost effective database platform to build robust on demand business applications.
>> WAS: Web sphere application server is an application server that runs business
applications and supports the J2EE and web services standards.
>> WSAD: Web sphere studio application developer is a toolkit which is designed for the
creation of more complex projects, providing fully dynamic web application
utilizing EJB’s . This consist of EJB tools , CMP ,data mapping tools & a universal
test client that is designed to aid testing of EJB’s.
>>HTTP: Hypertext Transfer Protocol is a transaction oriented client/server protocol
between web browser & a Web Server.
>> HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).
>> 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.

1.4) REFERENCE

>> IEEE SRS Format

>>Problem Definition (Provided by IBM)

1.5) TECHNOLOGIES
>> J2EE: Application Architecture
>>DB2: Database
>>WSAD: Development Tool
>> WAS: Web Server
>> Rational: Design Tool

1.6) OVERVIEW: SRS will include two sections:

>> Overall Description will describe major components of the system, interconnection and
external interfaces.
>>Specific Requirements will describe the functions of actors, their role in the system and
constraints.

Overall Description:
Describe the general factors that affect the product and its requirements.

2.01) PRODUCT PERSPECTIVE:

 >> The web pages (XHTML/JSP) are present to provide the user interface on customer client
side. Communication between customer and server is provided through HTTP/HTTPS
protocols.
>> The Client Software is to provide the user interface on system user client side and for this
TCP/IP protocols are used.
>> On the server side web server is for EJB and database server is for storing the
information.
2.02)SOFTWARE INTERFACE
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: DB2, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),
DB2, OS (Windows), Web Server.
2.03)HARDWARE INTERFACE
Client side
Processor RAM Disk space
Internet Explorer Pentium II at 500 64 MB 1GB
6.0 MHz
Server side
Pentium III at 1 512 MB 2 GB
Web sphere GHz
application server
V5.0
DB2 V8.1 Pentium III at 1 512 MB 1GB (Excluding
GHz data size)

2.04)Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.

2.05)Product Function:
Track Account Level Data: In this module, receivables from customer are maintained.
Service Level Agreements: It contains the agreements of providing the services related to
product and customer.

2.06)User Contact Information:

It maintains all the details (Personal, Official, Contact, and
hospital) of the user

2.07)Product Ownership Details:

It maintains the information that does which customer own
which product.

2.08)Track Support Transactions:

Maintenance of services related to the to the user in the form of support.

2.09)Maintaining Logs:
Activities of the System Users can be tracked through the logs, which is maintained by the
system.
 USE CASE DIAGRAM

WRITE-UPS

ADMINISTRATOR DA/CP

VIEW ALL DETAILS

REGISTRATION
MANAGE USERS

WOMAN WELFARE
ORGANIZATION
VIEW LOGS
SERVICES

MANAGE STANDARD GROUPS

ADD SERVICES
DOCTOR AND
MEDICAL ACTIVISTS

VIEW DETAILS
UNREGISTERED USERS
USE-CASE DESCRIPTION

ADMINISTRATOR:
>>Manage System Users: The Administrator will create different roles. The system
users will be
created and will be assigned with the different roles. More than one task and
permissions can be
granted or revoked from the system users.
>> View Logs: Responsible for checking the logs of different system user for
auditing and
maintaining the integrity of the system.
>> Manage Standard Groups: Standard groups will be created and updated by the
administrator,
which will be visible to all the system users.
>> View All Details: View the customer details, payment details, purchase details,
daily service transaction details.

DOCTOR & MEDICAL ACTIVISTS:

>>clarify doubts: the doctor can use system to help user clarify their doubts on the
diseases and help in treatment providence.
>>create registration: The doctor can create his/her own registration for system
security and user inference.
>>ADD SERVICES: the doctor shall help user on request to identify and satisfy their
doubts making the system portable for the user of the site.
>>View all details: the doctor can view the details of the users registered in the site
and refer to their grievencies.

WOMEN WELFARE ORGANIZATION:

>>ADD SERVICES: the WWO can well support the site user and even can get
valuable resources for the user of the site.
>>Support site: the WWO can support the site by providing the best to user doubts in
no time and accurately.

DISEASE AFFECTED/CURED PERSON:

>>Registration: The DA/CP can register in the site and can get the best possible
solution to their greivencies at the earliest from the best doctors available.
>>Best Services: the DA/CP CAN ATTEND THE multiple choice questions and
their related greivences will be solved by providing the reference to the best doctor
and the treatment available.
>>View all details: the DA/CP shall view all the details of the women related cancer
and can find out their related symptoms & treatment available.
Share experiences: the Cured Persons CAN share their experience so that it maybe
helpful for the one in need.

SIMPLE USERS:
>>view details: these unregistered users can view various details regarding the site
and the cancers available.
Architectural diagram
DATABASE DIAGRAM
2.11) Assumptions and Dependencies:
>>Administrator is created in the system already.
>>Roles and tasks are predefined.

3.)SPECIFIC REQUIREMENTS

3.01)Use-case reports:

ADMINISTRATOR:
>>Manage System Users: The Administrator will create different roles. The system
users will be
created and will be assigned with the different roles. More than one task and
permissions can be
granted or revoked from the system users.
>> View Logs: Responsible for checking the logs of different system user for
auditing and
maintaining the integrity of the system.
>> Manage Standard Groups: Standard groups will be created and updated by the
administrator,which will be visible to all the system users.
>> View All Details: View the customer details, payment details, purchase details,
daily service transaction details.

Manage system user:

VIEW LOGS

CREATE ACCOUNT

MANAGE USER

UPDATE ACCOUNT

UPDATE USER
• Name of usecase:- create the user.
Descriptions:-to create the user by providing the username,password and granting a revoking
certain rights.
Pre-conditions:- administrator is already logged in.
Normal flow of events:-
@new login, password, details of the user location id, roles, permissions are granted.
@save details.

Alternative flow of events:-if login is wrong then message appears.

Post conditions:-login id is generated with details saved.

GET THE USER

INFORMATION

GRANT
PERMISSION

REVOKE
PERMISSION

INSERT IN TO
DATABASE

STORE THE
INFORMATION

• Name of usecase:- view the user

Descriptions:- To view the details of the users of the system
Pre-conditions:-
@system administrator have already logged in.
@users have been created.

Normal flow of events:-

@system administrator have logged in.
@ Query will be submitted.
@Relevant output will be displayed

Alternative flow of events:-none.

Post conditions:-none.
 GET THE
USER

SELECT USER

ASK THE DATA

TO VIEW

SELECT DATA

DISPLAY THE DATA

• Name of usecase:- update the user

Descriptions:-to update the user details if any provided.
Pre-conditions:-
@administrator already logged in.
@user details already present.
@any change in details of the user.
Normal flow of events:-
@administrator logged in.
@update details of the user.
@save updates.
Alternative flow of events:-
@message is provided if update details are not present.
Post conditions:-
@Details are updated.

SELECT THE
USER

UPDATE THE USER

STORE THE
UPDATED USER
 • Name of use case: View logs
Description: To view the activities (logs) of the system users.
Precondition:
@Administrator is already logged in.
@ System Users have already been created.
Normal flow of events:
@ Select user name.
@ Select date.
Post Condition: None

SELECT THE
USER

SELECT DATE

LOGS OF SYSTEM USER

OF SELECTED DATES

USER USE-CASE
DISEASE AFFECTED/CURED PERSON:
>>Registration: The DA/CP can register in the site and can get the best possible
solution to their greivencies at the earliest from the best doctors available.
>>Best Services: the DA/CP CAN ATTEND THE multiple choice questions and
their related greivences will be solved by providing the reference to the best doctor
and the treatment available.
>>View all details: the DA/CP shall view all the details of the women related cancer
and can find out their related symptoms & treatment available.
Share experiences: the Cured Persons CAN share their experience so that it maybe
helpful for the one in need.
 CREATE ACCOUNT

REGISTRATION

UPDATE ACCOUNT

• Name of usecase:-CREATE the account

Descriptions:-the user can create a new account in the site.
Pre-conditions:-@not a member of the site.
@invalid username and password.
Normal flow of events:-
@enter the details and submit.
@login the site.
@logout the site.
Alternative flow of events:-
@invalid username.
@invalid password.
Post conditions:-
@user can use the valuable resources in the site including MCQs and doctor
aonline help.

ENTER THE
USER DETAILS

ENTER ALL DETAILS INVALID

CORRECTLY

VALID LOGIN

EDIT PROFILE

VIEW PROFILE
• Name of usecase:-update the account
Descriptions:- the user can update an existing account in the site.
Pre-conditions:-
@user account is already present.
@user detail(s) are invalid.
Normal flow of events:-
@update the account information.
@login the account.
@view the profile.
@logout the account.
Alternative flow of events:-error message if details aer wrong.
Post conditions:-details are correct.

USER_ID

SELECT USER
CREATE INVALID
USER_ID
VALID

PASSWORD

SELECT PASSWORD
CREATE INVALID
PASSWORD

VALID
USER PROFILE
DISPLAYED

UPDATE PROFILE OF USER

SAVE THE
CHANGES

STORE UPDATES IN
THE LOGS
DOCTOR & MEDICAL ACTIVISTS:

>>clarify doubts: the doctor can use system to help user clarify their doubts on the diseases
and help in treatment providence.
>>create registration: The doctor can create his/her own registration for system security and
user inference.
>>user services: the doctor shall help user on request to identify and satisfy their doubts
making the system portable for the user of the site.
>>View all details: the doctor can view the details of the users registered in the site and refer
to their grievencies.

• Name of usecase:- create doctor account

Descriptions:- the doctors can separately register in the site.thus providing greater security to
the user in getting the medical assistances.
Pre-conditions:-
@the user be a certified doctor holding a unique doctor_id provided by the
aims.
Normal flow of events:-
@enter the details.
@view the profile.
@login the site.
@logout the site.
Alternative flow of events:-none
Post conditions:-none
 ASK FOR
USER_ID

SELECT USER_ID
CREATE INVALID
PASSWORD

VALID

ASK FOR
PASSWORD

SELECT PASSWORD
CREATE INVALID
PASSWORD

VALID

ENT ER THE PROFILE

INFORMATION

SUBMIT PROFILE

NEW ACCOUNT
LOGGED IN

Add services:

MEDICAL SERVICES

ADD SERVICES

PERSONAL SERVICES

• Name of usecase:-assist the user

Descriptions:-doctor should assist the user who have submitted their request through the
REPORTS of MCQs they attended.
Pre-conditions:-
@user is valid.
@doctor is valid.
 @reports submitted of MCQs
Normal flow of events:-
@user is logged-in.
@doctor is logged –in.
@user attended the MCQs.
@doctor view the report.
@medical assistance.
Alternative flow of events:-
@user and doctor is not logged-in.
Post conditions:-
@a best medical assistance is achieved.

USER
LOGGED IN

SELECT USER
CREATE INVALID
ACCOUNT

VALID

DOCTOR
LOGGED IN

SELECT DOCTOR
CREATE INVALID
ACCOUNT

VALID

USER ATTENDS
MCQ's

SUBMIT THE TEST

DOCTOR VIEW THE

RESULT OF MCQ's

ANALYSE THE RESULT

MEDICAL
ASSISTANCE

• Name of usecase:-view the user profile.

Descriptions:-the doctor can view the valid user profile and suggest the medical assistance.
Pre-conditions:-
 @user is valid.
@doctor is valid.
Normal flow of events:-
@user is logged-in.
@doctor is logged –in.
@doctor view the profile.
@medical assistance.
Alternative flow of events:-
@invalid user account.
Post conditions:-
@ medical assistance.

USER
LOGGED IN

SELECT USER
CREATE DOCTOR INVALID
ACCOUNT

VALID

DOCTOR
LOGGED IN

SELECT DOCTOR
CREATE DOCTOR INVALID
ACCOUNT

VALID

DOCTOR VIEW THE USER

PROFILE

ANALYSE THE USER

MEDICAL
ASSISTANCE

• Name of usecase:-MCQ’s attending

Descriptions:-the doctor can view the valid user profile and suggest the medical assistance.
Pre-conditions:-
 @user is valid.
Normal flow of events:-
@user is logged-in.
@attend all the MCQ’s
@find a doctor
Alternative flow of events:-
@ invalid user account.
@answer all queries
Post conditions:-
@find a doctor
3.02)Supplementary requirements:
>>Secure access of confidential data (user’s details)
The user details at any cost is not revealed at any means.there will be a secure use of
data and profile of the user securely.providing the best security to the data

>>24 X 7 availability.
Because system can be an automated process, so it can stay open for 24 hours a day.
If the base is now the entire world, staying open 24 hours a day becomes critical.
System is required to be available 24X7 so UPS support must be on server site for at
least 8 hours in case of power failure. System will remain inaccessible to users at
2:00 to 4:00 am for backup and maintenance purpose.

>>Better component design to get better performance at peak time.

The Web Application Server should provide good performance and the ability to
manage performance with techniques, such as support for caching, clustering, and
load balancing.

>>Flexible service based architecture will be highly desirable for future extension
The web supports and withstands multiselection and is not prone to any kind of
hanging,providing the best dynamicity to the site.