Final Documentation for Print Out

8/14/2019 Final Documentation for Print Out

1/69

1. INTRODUCTION

1.1 About the organization

A major healthcare center chain spread across many locations in India

has opened a 200-bed hospital in a coastal town in Andhra Pradesh. There

are no such healthcare centers in 200 km radius and thus this center

became the main hospital to nearly 7 lakh people in and around that town.

Being part of a major chain it has its own software implemented across all

departments. They are outpatient department, inpatient department,

nursing stations, billing counter, pharmacies, central drug stores, diagnostic

center, ambulance, intensive care units, operation theatres, emergency

ward, mortuary, patient room management, staff management and training

departments. Each department has its own manager and few staff given to it

to manage its operations. All staff are trained to use the healthcare software

provided by the management. The staff can never afford to forget data entry

as otherwise they will not be able to fulfill their duties with appropriate

inputs.

1.2 Introduction to project Diagnostic center is used to store the information of the test details in ahospital or a clinic. Here actor is the Lab-Technician or Doctor and he/she

should be registered in the Diagnostic center login account first then only

he/she will do anything. When patient visited Diagnostic center then the

Lab-Technician will register the patient and give appointment to take

prescription from Doctor. Doctor examines the patient and gives the list of

tests to be taken by patient. Lab-Technician gives appointment to the test for

the patient.

Lab-Technician calculates the bill to be paid by the patient and adds 12%

tax to it and specify total amount. Patient pays the bill and Lab-technician

must generate the receipt based on the pay method (cash, credit card, check)

and issue it to the patient. Lab-Technician will then conducts tests to the

patient and specify the time to collect the Reports according to the type of

the test.

1.


2/69

1.2.1 Project Objectives

Computerize the Operations of Diagnostic center.

Diagnostic center provides all test facilities to the patient.

1.2.2 Scope

Lab-Technician can give appointment to patient.

Doctor can recommend tests to the patient.

To specify the Time to collect the reports.

To calculate the amount to be paid by the patient.

To register the patient details in the database.

To print receipt for the patient.

1.3 Literature Survey

1.3.1 Disadvantages of the existing system: -

The present system uses manual methods and the disadvantages of the

present existing system are as listed below: -

There is no protection for the records and files.

Retrieval and storage of information will take much time during

accessing.

Communication between the organization levels is quite less and slow.

Deleting, adding, modifying, updating and inserting of individual

records will take much time.

Security and protection is much less.

2.


3/69

1.3.2 Advantages of the proposed system: -

The advantages of the proposed system are as listed below: -

Easy to maintain the records.

No wastage of time and energy.

Calculations can be performed very accurately and quickly.

Modifications can be done easily.

Data can be retrieved as and when required depending on the

necessity.

Data entry is very easy.

3.


4/69

2. Software Development Life cycle

2.1Phases of Software Development Life cycle

Requirement Specification

Requirement Specification is the first and most important phase of the

SDLC. During this phase our Project Manager is in constant contact with the

Customer to find out requirements of the project in detail. Main tasks in this

phase include Requirement Determination, Risk Analysis, Setting up

Schedules, and deciding Deliverables. Communication with the Customer is

carried out using any of the following means of communication, such as

Instant Messenger, Email, Phone, Voice Chat or personal meeting. A System

Requirement Specification Document is prepared at the end of this phase.

Requirement Analysis and design

Project Manager and System Analyst after reviewing the Customers

requirements analyze the requirement and start designing of the project.

System Architecture, Database Design, Program Specifications and Test

Scenarios are determined. A Detail Design Document is prepared at the end

of analysis that can be used by the programmers to perform the coding.

Coding and Testing

Programmers begin programming in this phase using the Detail Design

Document. As project progress programmer's progresses is monitored by

Project Manager and Project Leader respectively. Project Manager is in

constant contact with the customer and provides updates on the progress of

the project using MS Project. Project Leader helps the programmers with

their coding problems and guides them to the solutions. Testing is done by

the QA Team simultaneously for the finished modules and approval is given

to the modules once they have passed their initial tests before integration.

Deployment and support

This phase starts with Deployment of the Project. Initial hardware and

software setup necessary to run the project is a very critical phase of the

project. After project is completed Project Manager contacts the customer

and prepares for the set-up. Software is handed over to the customer for

acceptance testing only after complete internal testing. Support to the

project is provided for a limited number of days during which any minor

customer changes are finished.

4.


5/69


6/69

Architecture Centric

One of the most important deliverables of the process is the executable

architecture baseline which is created during the Elaboration phase. The

Unified Process insists that architecture sit at the heart of the project team's

efforts to shape the system. Since no single model is sufficient to cover all

aspects of a system, the Unified Process supports multiple architectural

models and views.

Risk Focused

The Unified Process requires the project team to focus on addressing the

most critical risks early in the project life cycle. The deliverables of each

iteration, especially in the Elaboration phase, must be selected in order to

ensure that the greatest risks are addressed first.

Inception:

The inception phase is concerned with establishing the scope of the

project and generally defining a vision for the project.

By communicating with the customer & end user

Business requirements for the software are identified.

Rough architecture for the system is prepared.

Plan for the project is developed.

The key activities in the phase are:

Specify the vision for the product

6.
http://en.wikipedia.org/wiki/Image%3AUnifiedProcessProjectProfile20060708.png


7/69

Produce a business case

Define the scope of the project

Estimate the overall cost of the project

Elaboration (communication + modeling)

The purpose of elaboration is to analyze the problem, develop the project

plan further, and eliminate the riskier areas of the project. To eliminate the

risks prototypes will be prepared.

The key activities of this phase are

Refine and expand the preliminary use cases developed in inception

phase.

Expand the architectural representation to include five different views

o Use case model

o Analysis model

o Design model

o Implementation model

o Deployment model

Construction

It is identical to the Construction phase of the Generic frame work

activities. Using the architectural model as input this phase develops the

software components. To accomplish this, analysis & design models that

were started during the Elaboration phase are completed. All necessary and

required features and functions of the software increment are then

implemented in source code. As components are being implemented, unit

tests are designed and executed for each.

Transition (customer delivery + feedback)

The final phase is concerned with moving the final product across to

the customers. Typical activities in this phase include:

Beta-releases for testing by the user community

Factory testing, or running the product in parallel with the legacy

system that the product is replacing

Data take on (i.e. converting existing databases across to new formats,

importing data, etc)

Training the new users

7.


8/69

Marketing, Distribution and Sales

3. INCEPTION PHASE

3.1 Communication

In this phase developer will go to the customer and gathers requirements

by asking some simple questions

Requirements are the descriptions of system structure and behavior.

Requirements are gathered by interacting with the customers or the end

users. They will describe the system from their point of view i.e. at high level

of abstraction or with out including any implementation details. Software

engineers will convert these requirements, which are relatively at lower level

of abstraction. These requirements can be divided under three heads

depending on what they describe

User Requirements:

These are the requirements specified by customer or the end user.

Generally they will be natural language sentences. They did not include

implementation details, because their inclusion may lead to confusion of

non-technical people. So they will be at high level of abstraction.

System Requirements:

User requirements, which are in natural language, will be taken by the

system analyst and are converted to system requirements. They prescribe

the implementation details of the User Requirements; hence, they are the

certain extent related to them; but at the same time they are more detailed

than them. The data with in the system requirements should be complete as

well as consistent.

Domain requirements:Before entering into a project, the software team should have some

knowledge about the domain in which they are working. Requirements of

8.


9/69

that domain are Domain Requirements. The user will specify these

Requirements. In this project our domain is Diagnostic Center. The domain

requirements for the Diagnostic Center are

What are the tests available in that Diagnostic Center?

What are the test timings in that Diagnostic Center?

Requirements for Diagnostic Center:

O1: The diagnostic center has facilities and personnel to conduct all

common tests and provide test reports within minimum time periods as

mentioned below:

1. blood report (8 hr)

2. urine report (8 hr)

3. lipid profile (8 hr)

4. Thyroid test (16 hr)

5. Ultra sound test (2hr)

6. x ray (2 hr)

7. ECG (0.5 hr)

8. EEG (1 hr)

02: Test facilities for conducting 1-4 tests are available for only 16 hr (6 am

10 pm) in a day. But, 5-8 tests are available for 24 hr every day. It normally

receives requisitions for various test reports from nursing stations and out

patients and it manages its operations through its own software module.

03: A doctor orders certain specific reports for his patient and then the tests

are conducted on him after noting

Patient name

AgeTests to be done

Referred by doctor

Reports required immediately

04: Once the payment for the tests is done, the patient (or his caretaker) is

duly examined and samples are collected within a maximum time of 1 hr.

05: Then the patients caretaker / nursing station is informed of the time to

collect reports that are required immediately, and those others at a differenttime.

9.


10/69

06: The diagnostic center then provides the same at the given time precisely.

3.2 Planning

Effective management of a software project depends on thoroughly

planning the progress of the project. The project manager must anticipate

problems which might arise and prepare tentative solutions to those

problems. A plan, drawn up at the start of a project, should be as the driver

for the project. The initial plan should be the best possible plan given the

available information. It evolves as the project progresses and better

information becomes available.

The project plan sets out the resources available to the project, the work

break down and a schedule for carrying out the work. The project plan is

solely concerned with the development process. The details of the project

plan vary depending on the type of project and organization. The project plan

structure is as shown

Introduction: In this we will set out the constraints (budget, time etc) which

effect the project management.

Project Organization: This describes the way in which the development

team is organized, the people involved and their roles in the team.

Risk Analysis: This describes possible project risks, the likelihood of these

risks arising and the risk reduction strategies which are proposed. A risk is

defined as the probability of missing a cost, schedule, future extendibility,

quality.

Hardware and software resource requirements: This describes the hard

ware and software requirements. If hardware is to be purchased estimates

the prices and delivery schedule.

10.


11/69

Monitoring and reporting mechanisms: This describes the management

reports which should be produced, when these should be produced and the

project monitoring mechanisms used.

The project plan should be regularly revised during the project. Some

parts, such as the project schedule will change frequently; other parts will be

more stable.

11.


12/69

4. ELABORATION PHASE

4.1 Communication

Initially in the inception phase requirements will be gathered by

communicating with the customer. After analyzing the requirements the

software team will again go to the customer and they will finalize the

requirements. After this stage the project will be moved to the modeling

phase.

4.2 Modeling

In this the finalized requirements will be modeled using two models. They

are

Analysis Modeling

Design Modeling

12.


13/69

4.2.1 Analysis Model

The Analysis model is the first technical representation of the system.

Analysis modeling uses a combination of text and diagrams to represent

software requirements in an understandable way. Building analysis model

make it easier to uncover requirement inconsistencies and omissions.

Analysis models represent the customer requirements by depicting the

software in three different domains.

Requirements Documents

In this all user requirements are written in a specified format, which will

be very easy for the designers, coders and testers to understand. This can be

divided into two parts basing on how they are described.

URD (User Requirement Document): In this the requirements are at

high level of abstraction. No technical words are used here. This

document will be given to the customer who validates that. Here each

requirement will be given an ID.

SRS (System Requirement Specification): After getting conformation

from the customer the URD will be converted to SRS. It contains the

technical details which makes the software engineer comfortable

13.


14/69

4.2.1.1 User Requirement Document (URD)

Introduction

This section mainly briefs about who is the customer and what is

customer business and the problems customer is facing in the existing

business. It also gives information on business aspects considered for

automation, goals of the project.

Target audience

Customer

Developers

Lab-Technician

Doctor

Project manager and project leader

Project guide

Look-up table

S.No Requirement

ID

Requirement Name Source

(Customer/Vendor)

Stable

(Y/N)

1. DC-UC01 Login Customer Y

2. DC-UC02 Configure Test Customer Y

3. DC-UC03Appointment for

testCustomer Y

4. DC-UC04Generate Test

ReportsCustomer Y

5. DC-UC05 Generate Bill Customer Y

6. DC-UC06 Payment Customer Y

14.


15/69

Requirement description

15.

Requirements ID DC-UC01

Title Login

Description The purpose of this use case is to authorize usersbefore they access features of applications

Actor Lab-Technician, Doctor

Input: LoginID, password

Behavior

--Verify ID exists or not--If ID exists retrieve password--Compare password--If password match then allow user to access theapplication--Else display error message

Output Home page

Pre-conditions Lab Technician registered

Post-conditions ----nil---

Use-case

Login

Lab Technician

Special

Instructions

--nil--


16/69

16.

RequirementsID

DC-UC02

Title Configure Test

DescriptionThis usecase is used to specify the test details and storethe details in the database

Actor Lab-Technician

Input: Test name, Duration, cost, Regular or fulltime

Behavior Store test details in the application

Output Success or failure message

Pre-conditions

Lab-Technician login

Post-conditions

--nil--

Use-case

Configure test

Lab Technician

Login

uses

SpecialInstructions

Regular(6AM-10PM hours) , Full time(24 hours)


17/69

17.

RequirementsID

DC-UC03

Title Appointment for test

Description This usecase is used to specify the date and time for theappointmentand calculate the time for collecting reports


Input: Patient ID, Test name, Date and time

BehaviorStore test details in the application and calculate thetime to collect the reports

Output Specifying the time to collect the reports

Pre-

conditions


Post-conditions

--nil--

Use-case

Appointment for

Test

Lab Technician

Login

uses

SpecialInstructions

Regular(6AM-10PM hours) , Full time(24 hours)


18/69

18.

RequirementsID

DC-UC04

Title Generate test reports

DescriptionThis usecase is used to store the test details andgenerating test reports


Input: Patient name, age, Test name, Doctor name, Test details

BehaviorStore test details in the application and generating thereport format

Output Printing reports

Pre-conditions Lab-Technician login

Post-conditions

--nil--

Use-case

Generate Test Reports

Lab Technician

Login

uses

Generate report format

Special

Instructions --nil--


19/69

19.

Requirements

IDDC-UC05

Title Generate Bill

Description This usecase is used to calculate the cost of all details


Input: Patient ID

Behavior Calculate the cost of all details

Output Amount

Pre-conditions


Post-conditions

--nil--

Use-case

Generate Bill

Lab Technician

Login

uses

SpecialInstructions

--nil--


20/69

4.2.1.2 System requirement specification (SRS)

20.

RequirementsID

DC-UC06

Title Payment

Description This usecase is used to record payment details andgenerating reports


Input: Payment type(DD or Cheque or cash)

Behavior Record Payment details and generate receipt

Output Print receipt

Pre-

conditions


Post-conditions

--nil--

Use-case

payment

Lab Technician

Login

uses

Print reciept

SpecialInstructions --nil--


21/69

Introduction

This section mainly briefs about giving appointment for the test,

generating test reports, generating bill, printing the receipt to the patient .

Software and Hardware Requirements

Hardware environment

The minimum server configuration includes

HDD-160GB

RAM-1GB

Processor- AMD Athlon

The minimum Client Configuration includes

HDD-80GB

RAM-512MB

Processor- Pentium - 4

Software environment

At Server Side : : Operating System(Windows server 2003),One Web

Browser, Oracle 9i, Jdbc, Odbc Drivers

At Client Side : : Operating System(Windows XP),One Web Browser(Internet

Explorer, Morzilla Firefox..Etc)

Look up table

S.no System Feature ID Title

1. SF 01 Login

2. SF 02 Configure Test

3. SF 03 Recommend Test

4. SF 04 View Reports

5. SF 05 Appointment for the test

6. SF 06 Generate Test reports

7. SF 07 Generate Bill

8. SF 08 Payment

System features

SRS ID DC-SF01TITLE Login

21.


22/69

DESCRIPTIONThe purpose of this is to authorize users before they

access features of applications

INPUT ID , password

LOGIC

Click login link in home page

Display login form

Enter input data

Submit form

Perform data validations

If errors found display error messages

Else call server program

Read from data

Connect to Database

On successful connection, retrieve password for

given login ID from database

If resultset is empty then display loginID does

not exist

Else compare password

If password matches with the password entered

in the form then display user home page

Else display error message that the password is

incorrect

Close resultSet

Close database.

OUTPUT User home page/ error message

CONDITIONS

TO CHECK

User ID should be atleast 4 characters long and

_ is only the special symbol allowed

Password should be more than 6 characters

long

SRS ID DC-SF02

TITLE Configure Test

DESCRIPTIONThe purpose of this is to store test details and

displaying success or failure message.

22.


23/69

INPUTTname, Duration, cost, Test timings(Regular or

fulltime)

LOGIC

Click configure test link in home page

Display form with Test name, Duration, cost,

Test timings(Regular or fulltime)

Enter input data

Submit form



If cost is not in the floating point format then

display error message.


Read from data

Connect to Database

Execute insert operation on database to store

the details entered

Check return value of insert operation

If it is 0 then the insertion is failed and

display error message

Else display message Test details stored

successfully and click OK to return to user

home page.

Close database.

OUTPUTMessage: Test Details stored successfully/ error

messageCONDITIONS TO

CHECK

Duration should be in between 0.5 hours and

16 hours

SRS ID DC-SF03

TITLE Recommend test

DESCRIPTIONThe purpose of this is to store recommended test

by doctor, Patient ID in the database.

23.


24/69

INPUT Sno, PID, Tname

LOGIC

Click Recommend Test link in home page

Display form with Test name, Sno, Patient

ID

Enter input data

Submit form




Read from data

Connect to Database

Retrieve the Doctor ID from the login details

through which the doctor logged in.

Store the details of the Sno, Test name given

by doctor, Patient ID, Doctor ID by using

insert operation.

If the return value for the insert operation is

0 then display error message

Else display message Details registered

successfully

Close database.

OUTPUTMessage: Details stored successfully/ error

message

CONDITIONS TOCHECK

---nil---

SRS ID DC-SF04

TITLE View Reports

DESCRIPTIONThe purpose of this is to retrieve report details from

database and Display details in the form.

24.


25/69

INPUT Rno

LOGIC

Click View Reports link in home page

Display form with Report no field

Enter input data

Submit form




Read from data

Connect to Database

Retrieve the Report details by using Report no

If result set is empty then display error message

Else Display the report details in the format

Close database.

OUTPUT Message: Details stored successfully/ error message

CONDITIONS TO

CHECK---nil---

SRS ID DC-SF05

TITLE Appointment for the test

DESCRIPTIONThe purpose of this is to store appointment details

and calculate time to collect reportsINPUT PID, Tname, date and time

25.


26/69

LOGIC

Click Appointment for test link in home page

Enter input data

Submit form



If Date and time are invalid then display error

message in that form itself.


Read from data

Connect to Database


details entered


If it is 0 then the insertion is failed and display

error message

Else calculate time to collect reports based on

Test timings in a day.

Display that calculated time to collect reports

Close database.

OUTPUT Specifying time to collect reports/ error message

CONDITIONS TO

CHECK

We have to check whether the test is regular or

full time from the test details table

If the test is from 6:00 AM to 10:00 PM then

check whether the current time is in that limitand give the appointment.

SRS ID DC-SF06

TITLE Generate Test reports

DESCRIPTION

The purpose of this is to store test report details and

generating report format

26.


27/69

INPUT Pname, Age, Tname, Dname, TestDetails

LOGIC

Click Generate Test reports link in home page

Display the form with the details such as

Patient name, Age, Test name, Doctor name,TestDetails etc.

Enter input data

Submit form




Read from data

Connect to Database


details entered



error message Else Prepare the form with the details entered

in the database in the report format

Print the reports and take printout.

Close database.

OUTPUT Print reports/ error message

CONDITIONS TO

CHECK---nil---

SRS ID DC-SF07

TITLE Generate Bill

DESCRIPTIONThe purpose of this is to calculate the amount of test

to be done and

27.


28/69

INPUT PID

LOGIC

Click Calculate Bill link in home page

Display the form to enter patient ID

Enter input data

Submit form



If invalid ID is entered then display error

message


Read from data

Connect to Database

Retrieve the test name from the database

From that test name retrieve cost of the test

Add service tax to it

Display the amount and specify to patient to

pay it

OUTPUT Calculating bill/ error message

CONDITIONS TO

CHECK

Add 12% service tax to the cost of the test and

calculate bill

SRS ID DC-SF08

28.


29/69

TITLE Payment

DESCRIPTIONThe purpose of this is to record payment details and

generate receipt

INPUT Payment type(DD, cheque, cash), details

LOGIC

Click print receipt link in home page

Display the Payment form which consists of

payment details

Enter input data

Submit form




Read from data

Connect to Database


details entered



error message

Else print receipt and issue to patient.

Display that calculated time to collect reports

Close database.

OUTPUT Print receipt/ error message

CONDITIONS TO

CHECK

Check whether the payment type is cash or DD

or cheque

4.2.2 Design Model

Software design is a meaningful engineering representation of the

software product that is to be built. A design can be traced to the customers

29.


30/69

requirements and can be assessed for quality against predefined criteria.

During the design process the software requirements model is transformed

into design models that describe the details of data structures, system

architecture, interfaces and components. Each design product is reviewed

for quality before moving to the next software engineering action.

Design can be classified into two parts. This Classification is based on

the things to be modeled.

4.2.2.1 High Level Design

Architectural Design

It is derived from

o Information about application domain relevant to software

o Relation ships and collaborations among specific analysis model

elements

o

Availability of architectural styles and patternsUsually depicted as asset of interconnected systems that are often

derived from the analysis packages

30.

User with personal computer

Client User interface (Web Browser)

Web Server authenticationWeb UI (HTML, JSP, Java Script)Web Application server (Classes,

interfaces

App server runtime environment

containers, JRE

Database providers (ADODB, ODBC,

JDBCDatabase AuthenticationDatabase logical layer


31/69

Flow Charts

1. Login

31.

Database

physical layer


32/69

Start Click Login link

Enter ID,password

Submit form

Perform validtions

IS Data OK?

Call Server

Read from data

Connect to Database

IS Connection OK?

Retrieve password for given IP

IS Result empty?

IS password matches?

Display home page

Close database

connectionStop

No

yes

No

yes

NoError ID incorrect

Error ID incorrectYes

Yes

No

D

ata

base

2. Appointment for test

32.


33/69


34/69

StartClick Generate

reports link

Enter the patient

ID,Test name

details

Submit form

Perform validtions

IS Data OK?

Call Server

Read from data

Connect to Database

IS Connection OK?

Retrieve Test for given

patient ID

IS Result empty?

Yes

ErrorNo

Yes

Yes NoError

Patient ID not exists

IS test name selected in result?

Retrieve patient details for

given patientID and other

report details

Yes

Da

ta

ba

se

Display the report

details in new page

Stop

No

34.


35/69

4.2.2.2 Low Level Design

ER Diagrams

Doctor checks Patient

Tests

Recommends

Lab Technician

conducts

Reportsgenerates

Billgenerates

pays

StaffID

StaffID

Test name

Patient ID

Bill no

Report no

password

Address

Phone no

dept

password dept

Address

Phone no

Report name

Details

E-mail

name

Phone no address

cost

type

Duration

Details

Payment method

amount

35.


36/69

Database Tables

Table for Login Information

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

loginID varchar 30 n 1.Should not

be null

2.Should be

unique

Primary Key

password varchar 20 n 1.Should not

be null

2.Should be

minimum

6characters

N/A

Confirm

password

varchar 20 n 1.Should not

be null

2.Should be

minimum

6characters

N/A

Name varchar 30 n N/A N/A

RoleCode varchar 20 n Should be anyone of the role

code given by

the developer

N/A

Table for patient Registration

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

PID number 10 n 1.Should not be

null

2.Should be

unique

Primary Key

Name varchar 30 n N/A N/A

address varchar 40 y N/A N/APhno number 12 n Should be in any

one of the format

N/A

36.


37/69

given by the

developer

Age number 3 n Should not be a

negative number

N/A

Email varchar 25 n Should be in any

one of the format

given by the

developer

N/A

Table for Test details

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

Tname varchar 20 n 1.Should not

be null

2.Should be

unique

Primary Key

Cost Float 10 n N/A N/A

address varchar 40 n N/A N/A

type varchar 20 n Should be

any one of

the test type

given by the

developer

N/A

Email varchar 25 n Should be in

the format

given by the

developer

N/A

Table for Bill details

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

bno number 10 n 1.Should not be

null

2.Should be

Primary

Key

37.


38/69

unique

amount float 10 n Should not be a

negative number

N/A

date date 20 n Should be in

any of the

format of date

N/A

PID varchar 30 n N/A Foreign Key

Payment

details

varchar 20 n Should be any

one of the role

code given by

the developer

N/A

Table for Reports

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

Rno number 10 n 1.Should not

be null

2.Should be

unique

Primary Key

name varchar 20 n N/A N/A

PID number 10 n Should be

foreign key for

PID of Patient

table

Foreign Key

Tname varchar 20 n Should be

foreign key for

Tname of Test

table

Foreign Key

details varchar 50 y Should be in

the format

given by the

developer

N/A

Table for Patient-Test details

Column

name

Data

type

Size Nulls

(y/n)

Constraints Remarks

Sno number 10 n 1.Should not be Primary

38.


39/69


40/69

vertical line. A role is a slot for an object within a collaboration that

describes the type of object that may play the role and its relationships to

other roles. However, a sequence diagram does not show the relationships

among the roles or the association among the objects. An object role is

shown as a vertical dashed line, the lifeline.

An arrow between the lifelines of two objects represents each message.

The Order in which these messages occur is show top to bottom on the page.

Each message is labeled with the message name. The label also can include

the argument and some control information and show self-delegation, a

message that an objects sends to it, by sending the message arrow back to

the same lifeline. The horizontal ordering of the lifelines is arbitrary. Often,

call arrows are arranged to proceed in one direction across the page, but this

is not always possible and the order conveys no information.

Sequence diagrams are an easy and intuitive way of describing the

behavior of a system by viewing the interaction between the system and its

environment. A sequence diagram shows an interaction arranged in a time

sequence. It shows the objects participating in the interaction by their life

lines and the messages they exchange, arranged in a time sequence.

Sequence Diagram for Diagnostic Center

40.


41/69

4.3.2 Class design:Class design provides complete overview of the Diagnostic center.

The class diagram is core to object-oriented design. It describes the types of

objects in the system and the static relationships between them.

Classes:-The core element of the class diagram is the class. In an object

oriented system, classes are used to represent entities within the system;

entities that often relate to real world objects. Classes are divided into three

sections: Top: The name, package and stereotype are shown in the uppersection of the class. You can optionally assign a stereotype to a class.

41.


42/69

Centre: The centre section contains the attributes of the class.

Bottom: In the lower section are the operationsthat can be performed on the

class.

Attributes: An attributeis a property of a class. It is generally understood

that when implementing the class, functionality is provided to set and

retrieve the information stored in attributes. Methods to set and retrieve

attribute data are often called accessormethods and need not be shown in

your model as they are usually inferred.

Operations: The operations listed in a class represent the functions or tasks

that can be performed on the data in the class.

Class description

Class id DC-class01

Class name Staff

Description This class is used to login into their own home pages

Attributes LoginID, password, name, rolecode

Methods register(), login()

Class id DC-class02Class name Tests

Description This class is used to configure tests include adding,

deleting, updating

Attributes Tname, cost, duration, type

Methods add(), delete(), update()

Class id DC-class03

Class name Doctor

Description This class is used to recommend tests to patient and

viewing reports of the particular patient

Attributes ID, pwd, name, rolecode

Methods recommendTest(), viewReports()

Class id DC-class04

Class name Lab Technician

Description This class is used to give appointment to patient for tests

and generating reportsAttributes ID, pwd, name, rolecode

42.


43/69

Methods appointment()

Class id DC-class05

Class name Reports

Description This class is used to generate the reports and print thereport

Attributes Rno, name, PID, tname, details

Methods generateReport(), printReport()

Class id DC-class06

Class name Bill

Description This class is used to store bill details into the database

and print recieptAttributes Bno, amount, date, PID, paymentType

Methods generateBill(), printReciept()

Class id DC-class07

Class name Patient

Description This class is used to store patient details into the

database

Attributes PID, name, address, phno, email

Methods N/A

Class Diagram

43.


44/69

Patient

PID

NameAddress

Phno

emailStaff

ID

pwd

name

rolecode

register()login() Reports

Rno

name

PID

tname

details

generateReport()

printReport()

Doctor

ID

pwd

name

rolecode

recommendTest()

viewReports()

Tests

Tname

cost

duration

type

add()

delete()

update()

Bill

Bno

amount

datePID

paymentType

generateBill()

printReciept()

LabTechnician

ID

pwd

name

rolecode

appointment()

pays

recommends

conducts

undergoes

generates

generates

checks

5. CONSTRUCTION

44.


45/69

public class Staff

{

char lid,password;

char name,rolecode;

public void login(char lid,char password)

{

}

public void register(char lid,char password)

{

}

}

public class LabTechnician

{

char lid,password;

char name,rolecode;

public void appointment(int pid,char tname)

{

}

}

public class Doctor

{

char lid,password;

char name,rolecode;

public void recommendTest(int pid,char tname)

{

}

public void viewReports(int pid,char tname)

{

}

}

public class Report

{

45.


46/69

int Rno,pid;

char name,tname,details;

public void generateReports(int pid,char tname)

{ }

public void printReport()

{ }

}

public class Tests

{

char Tname, type;

float cost;

int duration;

void add(){ }

void update(){ }

void delete(){ }

}

public class Bill

{

int Bno;

float amount;

Date date;

char pid,paymentType;

public void generateReport(){ }

public void printReport(){ }

}

6. TESTING

6.1 Introduction

46.


47/69

Testing begins at the component level and works out ward to ward the

integration of entire computer based system. The software testing Life cycle

consists of the following phases.

Planning consists of analyzing the features of the product to be tested

and detailing the scope of the test effort.

Design includes documenting and detailing the tests that will be

necessary to validate the product.

Development involves creating or modifying the actual tests that will be

used to validate the product.

Execution is concerned with actually exercising the tests against the

product.

Analysis or review consists of evaluating the results and effectiveness

of the test effort; the evaluation is then used during the planning stage

of the next testing cycle. Reuse is focused on improving the

development, and to a lesser extent the design, portions of the testing

cycle.

6.2 Unit test cases

In computer programming, unit testing is a method of testing that

verifies the individual units of source code are working properly. A unit is

the smallest testable part of an application. In procedural programming a

unit may be an individual program, function, procedure, etc., while in

object-oriented programming, the smallest unit is a method, which may

belong to a base/super class, abstract class or derived/child class. In this

section write the test cases to test each of the methods in a class.

Concentrate on whether those methods are created as per their pseudo code

specification or not.

47.


48/69

Test case for Login ID

Test Case ID: Input Expected Result

1. minivja_cseValid

2. 864789 Invalid

3. #@er143 Invalid

4. raghukishore Valid

5. Administrator@ Invalid

6. Invalid

7. >30 characters Invalid

8. vivek.reddy537 valid

Test case for Patient name, Doctor name, Lab Technician name

Test case for E-mail ID

48.

Test Case ID: Input Expected Result

1. B. Srinivas valid

2. Ramesh123 Invalid

3. M S S V R valid

4. Arjun_panday Invalid

5. Rajesh@ Invalid

6. 23vivek Invalid

7. San^tosh Invalid

8. 5763 Invalid

9. >30 characters Invalid

10. Vivek reddy valid


49/69

Test case for Phone Number

49.

Test case ID Input Expected Result

1. [email protected] Valid

2. [email protected] Valid

3. A123@ Valid

4. A%B@ Error

5. Blank Error

6. Spaces Error

7. A [email protected] Error

8. AB@c Error

9. [email protected] Accept

11. AB@c. Reject

12. [email protected]

m

Accept


50/69

7. SCREENS

50.

Test case ID Input ExpectedResult

1. Ch99598868 Error

2. 9959886840 Valid

3. 995988684 Error

4. 1298853074 Error

5. 99661435sa Error

6. 1234567892 Error

7. 000995988689 Error

8. 08662531712 valid


51/69

User interface

Screen id: Login(S1)

Figure:7.1 Screen for Login

51.


52/69

Screen id: Register(S2)

Figure:7.2 Screen for Register

Screen id: About us(S3)

Figure:7.3 Screen About their Diagnostic center

52.


53/69

Screen id: Tests(S4)

Figure:7.4 Screen for Test details

Screen id: cost(S5)

Figure:7.5 Screen for cost of tests

53.


54/69

Screen id: Contact Us(S6)

Figure:7.6 Screen for contact information

Screen id: Lab Technician Home page(S7)

Figure:7.7 Screen for Lab-Technician home page

54.


55/69

Screen id: Patient Registration(S8)

Figure:7.8 Screen for patient Registration

Screen id: Configure Test(S9)

Figure:7.9 Screen for configuring test details

55.


56/69

Screen id: Add Test details(S10)

Figure:7.10 Screen for adding test details

Screen id: Update Test details(S11)

Figure:7.11 Screen for updating test details

56.


57/69

Screen id: Appointment to test(S12)

Figure:7.12 Screen to give appointment for test

Screen id: Report generation(S13)

Figure:7.13 Screen for generating reports

57.


58/69

Screen id: Print reports(S14)

Figure:7.14 Screen for printing reports

Screen id: Bill generation(S15)

Figure:7.15 Screen for Generating Bill

58.


59/69

Screen id: Print receipt(S16)

Figure:7.16 Screen for Print reciept

Screen id: Doctors Home page(S17)

Figure:7.17 Screen for Doctors Home page

59.


60/69


61/69

8. CONCLUSION

The DIAGNOSTIC CENTER is an efficient tool which handles all the

difficulties and complexity described above. Here no paper work will be

alone. All the work will be handled by the Lab-Technician and Doctor. So

this software is easy to use by a Lab-Technician and Doctor. But Lab-

Technician or Doctor should have minimum knowledge about the browsing,

how to handle the errors and form submission.

61.


62/69

9. APPENDICES

9.1 AN OVERVIEW OF SERVLET AND JSP TECHNOLOGY

The Java Database Connectivity (JDBC) API is the industry standard for

database-independent connectivity between the Java programming language

and a wide range of databases SQL databases and other tabular data

sources, such as spreadsheets or flat files. The JDBC API provides a call-

level API for SQL-based database access.

JDBC API OVERVIEW:

The JDBC API makes it possible to do three things:

Establish a connection with a database or access any tabular data

source

Send SQL statements

Process the results JDBC has been part of the Java Standard Edition

since the release of JDK 1.1. The JDBC classes are contained in the Java

package java.sql. Starting with version 3.0, JDBC has been developed underthe Java Community Process.

JDBC allows multiple implementations to exist and be used by the same

application. The API provides a mechanism for dynamically loading the

correct Java packages and registering them with the JDBC Driver Manager.

The Driver Manager is used as a connection factory for creating JDBC

connections.

JDBC connections support creating and executing statements. Thesemay be update statements such as SQL's CREATE, INSERT, UPDATE and

DELETE, or they may be query statements such as SELECT. Additionally,

stored procedures may be invoked through a JDBC connection. JDBC

represents statements using one of the following classes:

Statement the statement is sent to the database server each and

every time.

62.


63/69


64/69


65/69


66/69

Summary

HTML is a markup language to describe hypertext document on the

www.html describes the structure and the content of a document. It can also

be used to include links and multimedia.

Markup tags: HTML documents are made of pieces of code within

markup tags. Most tags have attributes that allow better formatting basic

tags consist of tags that define the body on the whole. Text formatting tags

are of two types: logical and physical. These are used to enhance the

appearance of the text in the documents.

9.3 INTRODUCTION TO JAVA SCRIPT

Java Script is a new scripting language for web pages. Scripts written

with Java Script can be embedded into your HTML pages. With Java Script

you have many possibilities for enhancing your HTML pages with interesting

elements. For example, you are able to respond user-initiated events quite

easily. Some effects that are now possible with Java Script were some time

long ago only possible with CGI. So you can create really sophisticated pages

with the help of Java Script scripts on the internet. Best you have a look at

some Java Script enhanced pages. You can find many links at Gamelan (in

the Java Script section).

Java Script is an object based scripting language that has its roots in a

joint development program between Netscapes web scripting language. It is

very simple programming language that allows HTML pages to include

functions and scripts that can recognize and respond to user implement

complex web page behavior with a relatively small amount of programming

effort.

The Java Script language resembles Java, but without Javas static

typing and strong type checking. Java Script supports a runtime system

based on small number of data types representing numeric, Boolean, and

string values. Java Script complements Java by exposing useful properties of

Java applets to script developers. Java Script statements can get and set

exposed properties to query the state or alter the performance of an applet or

plug in.

66.
http://www.html/http://www.html/


67/69

Java Script is compiled into byte codes and interpreted by the Live wire

Pro server extension running in conjunction with the Netscape server. In this

role, Java Script essentially replaces or extends CGI.

On the server side, Java Script can accomplish many of the tasks usually

associated with retrieving and working with information from a database,

including:

Connecting to and disconnecting from the database.

Beginning, committing, and rolling back an SQL transaction.

Displaying the results of an SQL query.

Creating updatable cursors for viewing, inserting, deleting, and

modifying data.

Accessing binary large objects for multimedia content such as images

and sounds.

9.4 INTRODUCTION TO ORACLE DATA ORGANIZATION

In Oracle, all data is stored in tables. A table consists of columns (also

called fields) and of rows a single row of data is called a record or a tuple, a

subset of rows or columns might be selected.

A view is derived table that you can create for purpose of display

although it looks like a real table, within the database a view is only store as

a definition. Therefore, views are referred to as virtual tables, and the tables

they are derived from are called database. A view can be combination of two

base tables or subset of one base table.

Because oracle is relational system, the stored in various tables can be

connected to increase its usefulness and to avoid duplication selection is

the process of producing a ne table consisting of a set of rows from another

table match certain specified criteria a join produces a new table that is the

union of all rows table, less any duplicate rows.

At the core of oracle is SQL which stands for structured query language

IBM sponsored research in relational theory resulted in SQL has emerged as

the standard and has been adopted by the American national standard

institute. In consists of a set of common English words which can be

67.


68/69


69/69

10. BIBILOGRAPHY

Web Programming |2nd Edition |Chris Bates

PL/SQL Programming by Scott Urman

SQL complete reference by Livion

Software Engineering by Roger Pressman

References

http://www.manateediagnostic.com

http://www.dnacenter.com/

http://www.dcn-cde.ca.gov/

http://vieradiagnosticcenter.com/
http://www.manateediagnostic.com/http://www.dnacenter.com/http://www.dcn-cde.ca.gov/http://vieradiagnosticcenter.com/http://www.manateediagnostic.com/http://www.dnacenter.com/http://www.dcn-cde.ca.gov/http://vieradiagnosticcenter.com/

Final Documentation for Print Out

Documents

Transcript of Final Documentation for Print Out