SRS Example Libre

Table of Cont ent s
Virt ual M edical Home
1. Introduction
1.1 M ethodology
1.2 Purpose
1.3 Scope
1.4 Definitions, Acronyms and Abbreviations
1.5 Tools Used
1.6 References
1.7 Technologies t o be used
1.8 Overview
2. Overall Descript ion

2.1 Product Perspective
2.2 Softw are Interface
2.3 Hardw are Int erface
2.4 Communication Interface
10
2.5 Const raints
10
2.6 ER Diagram
10
2.7 Use-Case M odel Survey
11
2.8 Archit ecture Design
12
2.9 Dat abase Design
13
3. Specific Requirement s
3.1 Use-Case Reports
14
3.2 Activity Diagrams
18
3.3 Sequence Diagrams
28
4. Support ing Informat ion

4.1 Index
34
1 . I ntr oduction
1.1 Methodology
Rat ional Unified Process
2009
Page 2
The Rat ional Unified Process brings toget her element s from all of t he generic process models, supports it eration and illustrates good practice in specification and design. The RUP is normally described from three perspectives:
A dynamic perspective t hat shows the phases of the model over time.
A static perspective t hat show s the process activities that are enact ed.
A practice per spective that suggests good practices t o be used during the process.
Fig 1.1:Phases of RUP

The different phases in RUP are
Inception
The goal of the inception phase is to est ablish a business case for t he syst em. Ident ifying all ext ernal
entities that w ill interact w ith the syst em and defining these interact ion. This informat ion is used to
assess t he cont ribut ion of syst em t o business.
Elaboration
The goals of the elaboration phase are to develop an understanding of the problem domain, establish an architectural f ramew ork, develop project plan and ident ify key project risks.
Construction
This phase is concerned w ith system design, programming and testing. Parts of the syst em are developed in parallel and integrat ed during this phase.
Transition
2009
Page 3
This is the final phase of RUP and is concerned w ith moving the syst em from the development community to the user communit y and making it work in real environment.
1.2 Pur pose

Virtual M edical Home is a w eb applicat ion w hich provides online medical services to everyone
at their doorstep.
The users living in metro or remot e village can connect through int ernet or approach nearby
kiosk t o get these services. This w eb application is m ore effective, quick in providing medical help
especially t o people in villages w here very few doct ors are present . This helps the pat ients t o maintain a neat health record and to lead a healthy life.
1.3 Scope
There are four basic users - Patient, Admin, Doctors and Kiosk M anager.
All users have t heir ow n profiles in VM H.
The w eb-cam interaction betw een doctor and patient.
Patients can search for doctor and make online appointm ents. They also can view their
health record, lab reports, doctors prescription and medical expenses. Pat ient can also regist er
complaint on any doctor.
Doctors can give appointments, e-prescription and can view patients health record.
Kiosk M anager view s and manages the appoint ment s, performs day open and close activities
and calculat es his commission. He also sends reports to admin.
Admin has the authorit y t o add/ delet e users, grant permission to doct ors and kiosk manager, t o generat e and view report s. He also view s the complaints of patients and takes necessary
actions.
1.4 Definitions, Acronyms and Abbreviations
VM H
Vir tual Medical Home. Its a w eb applicat ion that provides online medical services for
people.
Admin
Administr ator . He has the aut horit y to add/ delete users, grant permission to doctors and
kiosk manager.
2009
Page 4
KM
Kiosk Manager . He is the ow ner of kiosk and manages appointment s of doctors.

W ASCE
WebSphere Application Server Community Edition. It is an application server t hat runs

and supports J2EE and w eb service applications.
DB2
Database_2 .A database management syst em that provides a flexible and efficient database
platform to maintain records of student s, teachers, admin and dm.
JSP
Java Server Pages. It is used to creat e dynamic w eb content.

J2EE
Java 2 Enterprise Edition . A programming platform w hich is a part of java platform for
developing and running distributed java.
UM L
Uni fied Modeling Language is a standard language for w rit ing softw are blueprints. The
UM L may be used to visualize, specify, const ruct and document
XM L
Extensible Markup Language is a text based format that let developers describe, deliver
and exchange struct ured data betw een a range of applications to client for display and manipulation.
HTTP
Hypertext Tr ansfer Protocol . Its a service protocol.

RAD
Rational Application Developer is a development tool that helps to design w eb pages

and also helps t o design the diagrams like ER, Database schema diagrams and to generat e DDL.
1.5 Tools Used
2009
Page 5
Application architecture JAVA, J2EE

JAVA
Java is an object -orient ed programming language developed by Sun M icrosyst ems a company best know n for its high end UNIX w orkstat ions. Java language w as designed t o be small, simple,
and portable across platforms, operating syst ems, bot h at the source and at the binary level, w hich
means t hat Java programs (applet and application) can run on any machine that has t he Java virt ual
machine (JVM ) inst alled.
J2EE
Java Platform, Enterprise Edition or Java EE is a w idely used platform for server programming in t he Java programming language. The Java platform (Ent erprise Edit ion) differs from t he Java
Standard Edition Platform (Java SE) in that it adds libraries w hich provide funct ionality to deploy
fault-tolerant, distribut ed, mult i-t ier Java softw are, based largely on modular components running
on an application server.
W eb server W ASCE
W ebSphere Application Server Community Edition (fr om now on WASCE) is a fr ee, certified
Java EE 5 server for building and managing Java applications. It is IBM 's support ed dist ribut ion of
Apache Geronimo that uses Tomcat for servlet container and Axis 2 for w eb services. Over 15
WASCE developers are commit t ers in the Apache Geronimo project.
Development tool RAD

IBM Rat ional Applicat ion Developer for WebSphere Softw are (RAD) is an integrat ed development environment (IDE), made by IBM 's Rational Softw are division, for visually designing, constructing, testing, and deploying Web services, portals, and Java (J2EE) applications.
Database platform DB2

DB2 Database is the database management syst em that delivers a flexible and cost effect ive
database platform to build robust on demand business applications and supports the J2EE and w eb
services st andards.
Design tool Rational Softw are M odeler

IBM Rational Software M odeler, (RSM ) made by IBM 's Rational Softw are division, is a Unified M odeling Language UM L 2.0-based visual modeling and design tool. Rat ional Softw are M odeler
is built on the Eclipse open-source soft w are fram ew ork and includes capabilities focused on visual
modeling and model-driven development (M DD) w it h the UM L for creating resilient , thought-out
applicat ions and w eb services.
1.6 Refer ences

Object Orient ed M odeling and Design w ith UM L-M ichael Blaha, James Rambaugh.
Soft w are Engineering, Sevent h Edit ion, Ian Sommerville.
IBM Red Books.
IBM TGM C Sample Synopsis.
IBM w w w .ibm.in/ developerw orks .
2009
Page 6
Java - ww w .sun.com
Wikipedia - www.wikipedia.com
Database M anagement Syst ems - Navat he.
Complet e Reference - J2EE - Keogh.
1.7 Technologies to be used

DB2: Relational Database M anagement Syst em.
RAD: Rational Application Developer.
WASCE: Websphere Application Server Community Edit ion.
Rational Softw are M odeler.
1.8 Overview
Existing System:
Registrat ion for users
Discussion forum
Drawbacks:
No web camera interaction
Remot e area users and people w ho doesn't have know ledge of internet cannot use the system
Proposed System:
Registrat ion for users, doct ors
Kiosk M anagers - help t he pat ients who doesn' t have know ledge of int ernet to use the syst em.
w eb camera int eraction.
Our Plan:
Registrat ion for users.
Online maint enance of health record.
Online prescription from doctor.
Web camera interact ion.
Online appointment facilit y.
Pat ient review s and rat ings for doctor .
2. Over all Descr i pt i on

2.1 Pr oduct Perspective
2009
Page 7
Fig 2.1: Pr oduct Per spective
2.2 Software Interface

Client on Internet
Web Brow ser, Operating System (any)
Client on Intranet
Web Brow ser, Operating System (any)
W eb Server
WASCE, Operating Syst em (any)
Data Base Server

DB2, Operating System (any)
Development End
RAD (J2EE, Java, Java Bean, Servlet s, HTM L, XM L, AJAX), DB2, OS (Window s),
WebSphere(W eb Server)
2.3 Har dware Interface

M inimum Requirements:
Client Side
Inter net Explor er - 6
Processor
RAM
Disk Space
Int el Pent ium III or AM D 800 M Hz
128 M B
100 M B
2009
Page 8
Server Side
Processor
RAD
DB2 - 9.5
Int el Pent ium III or AM D 800 M Hz
RAM
Disk Space
1 GB
3.5 GB
500 M B
256 M B
(Excluding Data
Size)
Processor
RAM
Disk Space
All Int el or AM D - 1 GHZ
256 M B
100 M B
Recommended Requirements:
Client Side
Inter net Explor er - 6

Web cam
5.0 M egapixel Camera
Server Side
Processor
RAD
RAM
Disk Space
2 GB
3.5 GB
500 M B
All Int el or AM D - 2 GHZ
DB2 - 9.5
512 M B
(Excluding Dat a
Size)
2.4 Communication Interface

Client (customer) on Internet w ill be using HTTP/ HTTPS protocol.
Client (syst em user) on Internet will be using HTTP/ HTTPS protocol.
2.5 Constraints
GUI is only in English.
Login and password is used for the identification of users.
Only registered patients and doctors will be authorized to use t he services.
2009
Page 9
Limit ed to HTTP/ HTTPS.

This syst em is working for single server.
2.6 ER Diagr am
2.7 Use Case Model Sur vey
2009
Page 10
Fig2.2 : Use Case Model Survey

Patient:
Patients can search for doctor and make online appoint ments. They also can view t heir healt h record, lab
report s, doctors prescript ion and m edical expenses. Patient can also regist er complaint on any doct or.
Doctor:
Doctors can give appointm ents, e-pr escription and can update and view pat ient s healt h record.
Kiosk M anager:
Kiosk M anager view s and manages t he appointm ents, perf orms day open and close act ivities and calculates his
commission. He also sends reports to admin.
Admin:
Admi n has the aut hority t o add/ delete users, grant permission t o doct ors and kiosk manager, to generate and
view report s. He also view s t he complaint s of pat ient s and t akes necessary act ions.
2.8 Ar chitecture Diagram
2009
Page 11
Fig2.3: Ar chitecture Diagr am
2.9 Database Design
2009
Page 12
Fig2.4 :Database Design
3.Speci fic Requi r ement s

3.1 Use Case Reports
3.1.1 Patient use-case r epor t
2009
Page 13
Fig3.1: Use case diagram for patient
USE CASE
SignIn
View profile
Update profile
Create health record
Update health record
Select doctor
Take an appointment
Interact w ith doctor
File complaint
W ithdraw complaint
View thread
Create thread
Create new post
Send M essage
Receive mail
Search
DESCRIPTION
The pat ient has to SignIn in order to .
Every regist ered patient has his/ her own profile containing personal det ails.
The pat ient has the opt ion to updat e his/ her own profile.
The pat ient can creat e his/ her own health recor d.
The pat ient can updat e his/ her healt h record.
The pat ient can select doctor based on various criteria.
The pat ient can request f or an appointm ent to a particular doct or .
The pat ient can int eract w it h doct or .
The pat ient can file complaint on doctor to admin.
The pat ient has opt ion t o wit hdraw his/ her complaint .
The pat ient can view already cr eat ed t hr ead in a discussion f orum.
The pat ient can creat e a new t hread in a discussion forum.
The pat ient can creat e a new post in a new ly created or already present thr ead.
The pat ient can send privat e message t o doct ors and admin.
The pat ient can receive mail.
The pat ient can search for a particular it em in websit e by entering t he keyword.
3.1.2 Doctor use-case report
2009
Page 14
Fig3.2: Use case diagr am for Doctor
USE CASE
Sign in
View profile
Update profile
Create health record
Update health
record
Acknowledge an appointment
Select a patient
Prescribe treatment
View complaints
View thread
Create thread
Post thread
Send message
Receive mail
Search
DESCRIPTION
The doct or has t o Sign In in order t o start begin his w ork.
Every regist ered doctor has his/ her own profile cont aining personal and professional d etails.
The doct or has the option t o updat e his/ her own profile.
The doctor can creat e health record of a patient .
The doct or can make necessar y changes to health recor d.
The doct or accept / reject s t he request of pat ient for an appoint ment .
The doctor
The doct or
The doct or
The doct or
The doct or
The doct or
The doctor
The doct or
The doctor
selects a patient for further int eraction.

prescribe t he t reat m ent for pat ient .
view s t he feedback of t he admin t o the complaints issued t o a doct or .
can view alr eady created thr ead in a discussion forum.
can creat e a new t hread in a discussion f orum.
can post a new creat ed or already pr esent t hread.
can send private messages to patients and admin.
can receive mail.
can search for a particular item in websit e by ent ering t he keyword.
3.1.3 Kiosk Manager use-case repor t
2009
Page 15
Fig3.3: Use case diagr am for Kiosk Manager
USE CASE
Sign in
View profile
Update profile
Add Kiosk
M anage appointment s
Calculate fees
Views logs
Send report
Approval from admin
DESCRIPTION
The Kiosk M anager has t o Sign In in order t o start begin his w ork.
Every regist ered KM has his/ her own profile containing personal and professional det ails.
The KM has t he option t o updat e his/ her own profile.
The KM can add new Kiosk .
The KM can manage t he appointm ents of doctors and pat ients .
Send message
Receive mail
View thread
Create thread
Create new post
Search
The KM
The KM
The KM
The KM
The KM
The KM
The KM can charge f ees for pat ient for using t he kiosk.
The
The KM can send report to admin.
The KM should get approval from the admin .
can send private messages to patients and admin.
can receive mail.
can view already creat ed t hread in a discussion for um.
can creat e a new t hread in a discussion for um.
can creat e a new post in a new ly creat ed or already present thr ead.
can search for a part icular it em in websit e by ent ering t he keyword.
3.1.4 Admin use-case report
2009
Page 16
Fig3.4: Use case diagr am for Admin
USE CASE
Sign in
View profile
Update profile
View reports
Generate reports
Authenticate doctor/ KM
View complaint
Take action
Take backup
Delete users
Send mail
Receive message
View thread
Create thread
Post thread
Search
DESCRIPTION
The admin has t o Sign In in order to st art begin his w ork.
Admi n has his/ her own profile containing per sonal and prof essional details.
The admin has t he opt ion t o update his/ her own profile.
The admin can view report s sent by KM .
The admin can generate r eports.
The admin will aut hent icat e doct or s and KM .
The admin views t he com plaint sent by other users.

The admin can t ake necessary act ions .
The admin can t ake backup of t he syst em.
The admin is given t he opt ion t o delet e t he users .
The admin can send mail.
The admin can receive pr ivat e messages from pat ient s, KM s and doct ors.
The admin can view already created thread in a discussion forum.
The admin can creat e a new t hread in a discussion f orum.
The admin can post a new creat ed or already present t hread.
The admin can search f or a part icular it em in websit e by ent ering t he keyword.
3.2 Activity Diagrams

3.2.1 User Registr ation Activity
2009
Page 17
Initially user is made to fill all mandatory fields filled in registration form. Once the user clicks submit, t he username is verified. If the username is already present, then t he user is again taken back,
so t hat he can change the username. If the username is not present then it checks for passw ord and
remaining mandat ory fields. If any of the mandatory field is left empt y or filled incorrect, then t he
user is informed to ent er t he correct values. Once all these verifications are succeeded, t hen the regist rat ion is done.
Fig 3.5: Activity Diagr am Repr esenting User Registr ation
3.2.2 Doctor and Kiosk Manager Registr ation Activity

The doct or and KM needs t o fill all mandat ory fields filled in regist ration form. Once they click submit, the username is verified. If the username is already present, then t hey are again taken back, so
that they can change the username. If the username is not present then it checks for passw ord and
2009
Page 18
remaining mandat ory fields. If any of the mandatory field is left empt y or filled incorrect, then they
are informed to ent er the correct values. These details are sent to admin for verification and the
admin verifies t he dat a and approves registrat ion and grant s privileges.
Fig 3.6: Activity Diagr am Repr esenti ng Doctor and KM Registration
3.2.3 User Login Activity

User is made t o ent er t he user nam e and passw ord, if he is signing in t hrough KIOSK, KIOSK ID has t o be entered, then ent ered values are verified. If it is a valid user name and passw ord, t hen t he user is logged in, or
else t hey are asked to re ent er the correct values.
2009
Page 19
Fig 3.7: Activity Diagr am Repr esenti ng User Login
3.2.4 Privileged User Login Activity

Privileged User such as Doct or, Kiosk M anager and Administ rat or is made t o ent er t he usernam e and password, ent ered values are verified. If it is a valid user nam e and password, t hen t he user is logged in and assigned the respective privileges, or else they is asked to retry by ent ering t he corr ect values.
2009
Page 20
Fig 3.8: Activity Diagr am Repr esenting Pr ivileged User Login
3.2.5 Take Appointment Activity

The patient w ill search for a doctor using search option. Then the patient select s a doctor from
search results
and ent ers date and time for an appointment and sends it to the doctor.
Doctor view s t his request.
2009
Page 21
Then he can either reject t he request or can approve it by sending an appropriate message to patient.
Fig 3.9: Activity Diagr am For Taking Appoint ment
3.2.6 Web Camera I nter action Activity

The patient w ill select a doctor and then if he has an appointment w ith that doctor, he can directly
start
w eb cam interaction session. If the patient does not have appoint ment, t hen he should check
w hether
the doct or is busy or available. If the doctor is available, the pat ient w ill send a request to doctor.
2009
Page 22
If t he doct or accepts t he request , the pat ient can start the int eraction session. Finally, patient w ill
close
t he session.
Fig3.10 : Activity Diagr am Repr esenting Web Cam Inter acti on
3.2.7 Providing Pr escr iption Activity

The doct or select s a particular patient, then view s his/ her health record to analyze his/ her condit ions,
sympt oms of diseases etc.. And then doctor ent ers the prescript ion and send it to the patient .
2009
Page 23
Fig3.11 : Activity Diagr am For Giving Pr escription
3.2.8 Lodging a Complaint Activity

The patient ent ers the complaint text and sends it to admin and the syst em generat ed Complaint _ID
is returned to user.
2009
Page 24
Fig 3.12: Activity Diagr am For Lodging Complaint
3.2.9 Replying a Complaint Activity

The admin view s the complaint and then he may reply to the user or he may select the respective
doctor and forw ards the complaint to him.
2009
Page 25
Fig 3.13: Activity Diagr am For Repr esenting Reply To Complaint
3.2.10 Par ticipating in a Discussion For um Activity

The syst em displays all t he post s t o t he users. The user can select a t hread from the recent post s and
can reply for that post or he/ she can creat e the new post. The user can directly creat e a new thread
and in t hat he/ she can creat e a new post. The user can also search for a particular topic and can select a thread from the result s and can create a new post .
2009
Page 26
Fig 3.14: Activity Diagr am Repr esent ing Discussion For um
3.3 Sequence Diagrams

3.3.1 Users Login Sequence Diagram
2009
Page 27
Fig 3.15: Sequence Diagr am Repr esenting Login Pr ocess
3.3.2 Mak e an Appointment Sequence Diagr am
2009
Page 28
Fig3.16:Sequence Diagr am Repr esenting Appointment
3.3.3 Lodge Complaint Sequence Diagram
2009
Page 29
Fig3.17:Sequence Diagr am for Lodging Complaint
3.3.4 Pr escr iption Sequence Diagr am
2009
Page 30
Fig3.18:Sequence Diagr am for Pr escription
3.3.5 Authentication of Pr ivileged User s Sequence Diagr am
2009
Page 31
Fig3.19:Sequence Diagr am for Authentication of Pr ivileged User s
3.3.6 Web Cam Interaction
2009
Page 32
Fig3.20:Sequence Diagram Repr esenting Web Cam Inter action
4 . Suppor ting I nfor mation
2009
Page 33
4.1 Index
2009
Page 34
Proposed System 8
HTTPS 8
Purpose 4
A
I
Abbreviations 5
Acronyms 5
Administ rat or 16
AJAX 7, 13
R
Incept ion 3
Interface 9,10,11
RAD 6
Int roduct ion 4
References 7
Analysis 3 Design 18
Report s 4
Rational Unified Process 3
J2EE 5, 13
Client on Int ernet 8
Client on Int ranet 8
Java 6
Scope 4
JSP 5,6
Communicat ion 11
Sequence 30
Complaint s 5
Constraints 11
Soft ware 9
Const ruction 4
Kiosk M anager 4
D
Dat a Base 15
KM 5, 13
Transition 4
Technologies 7
DB2 5, 6
Definitions 5
M edical Expenses 3
Development End 8
M et hodology 4
Drawbacks 8
Use-case 13, 16
Doct or 4,13
UM L 5
O
E
Operating System 6, 8
Our Plan 8
Elaborat ion 4
Overall 9
Virtual M edical Home 4
ER Diagram 12
Overview 8
VM H 4, 5
Exist ing Syst em 8
P
H
WASCE 5, 6
Patient 4, 13
Hardware 10
Precription 4
Healt h Record 10
Product Perspect ive 9
HTM L 8
HTTP 5,8
2009
Page 35
Special Thanks
We convey a special thanks to our department and to

our college. We also convey a special thanks to all
these softwares and websites, they have been helping a
lot in doing the project.
2009
Page 36

SRS Example Libre

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

SRS Example Libre

Caricato da

Copyright:

Formati disponibili

Table of Cont ent s

Virt ual M edical Home

1.4 Definitions, Acronyms and Abbreviations

1.5 Tools Used

1.7 Technologies t o be used

2. Overall Descript ion

2.2 Softw are Interface

2.3 Hardw are Int erface

2.4 Communication Interface

2.5 Const raints

2.7 Use-Case M odel Survey

2.8 Archit ecture Design

2.9 Dat abase Design

3.2 Activity Diagrams

3.3 Sequence Diagrams

4. Support ing Informat ion

Virt ual M edical Home

Fig 1.1:Phases of RUP

Virt ual M edical Home

1.2 Pur pose

1.4 Definitions, Acronyms and Abbreviations

Virt ual M edical Home

Kiosk Manager . He is the ow ner of kiosk and manages appointment s of doctors.

WebSphere Application Server Community Edition. It is an application server t hat runs

Java Server Pages. It is used to creat e dynamic w eb content.

Hypertext Tr ansfer Protocol . Its a service protocol.

Rational Application Developer is a development tool that helps to design w eb pages

1.5 Tools Used

Virt ual M edical Home

Application architecture JAVA, J2EE

Development tool RAD

Database platform DB2

Design tool Rational Softw are M odeler

1.6 Refer ences

Virt ual M edical Home

1.7 Technologies to be used

2. Over all Descr i pt i on

Virt ual M edical Home

Fig 2.1: Pr oduct Per spective

2.2 Software Interface

Data Base Server

2.3 Har dware Interface

Inter net Explor er - 6

Int el Pent ium III or AM D 800 M Hz

Virt ual M edical Home

Int el Pent ium III or AM D 800 M Hz

All Int el or AM D - 1 GHZ

Inter net Explor er - 6

5.0 M egapixel Camera

All Int el or AM D - 2 GHZ

2.4 Communication Interface

Virt ual M edical Home

Limit ed to HTTP/ HTTPS.

2.7 Use Case Model Sur vey

Virt ual M edical Home

Fig2.2 : Use Case Model Survey

2.8 Ar chitecture Diagram

Virt ual M edical Home

Fig2.3: Ar chitecture Diagr am

2.9 Database Design

Virt ual M edical Home

Fig2.4 :Database Design

3.Speci fic Requi r ement s

Virt ual M edical Home