8/7/2019 PPSP G1 DOC2

1/59

Introduction

Health care clinic New Delhi is one of the well known medical firms provide medical services to

the patients of Delhi but ever in this era of information technology they are still using manual

method to maintain daily appointment patients task etc. which has now become an arduous task.

So to remove the complexities and improve the quality of services, the management has decided

to adopt computerized online management system.

The online Healthcare clinic management system basically contains four modules.

Online registration and doctor`s appointment, here the patient is required to fill a registration

form containing various detail about himself.

He would be allotted a unique patient id and as per his requirement he would be given an

appointment with an expert doctor at a particular reporting time. There are two separate

appointment modules one for the front office i.e. basically for administrative activities and

another one is online. In the front office the office manager can make on the spot registration for

the patient who visits the clinic for registration.

There is separate module for administrative activities in which Manager can maintain old record

of the patients, reports, and payment and billing details. This module also provides the option of record entry for lab analysis conducted in the clinic.

We have also designed a separate module for Doctors through which they can log into the system

from anywhere though internet or through LAN in the clinic. They can access all the

appointments and comprehensive history of patients. Record of Diagnosis and Auto-Suggestive

Prescriptions is now just one click away from them. Now they can view from their home how

many patients have registered for appointments.

One of the most important modules of system is report generation of various reports such as

patient diagnosis and prescription repots, billing reports, lab analysis reports, comprehensive

history of patients and online customer registration reports. This can be accessed by the doctor

and administrator as per their domain area.

8/7/2019 PPSP G1 DOC2

2/59

S cope of the system

Online Healthcare Clinic Management System can be defined as an online computerized system

that is designed to meet all the information needs within a Health care Clinic. This desired

system involves online availability of information for public view on the internet. They can

access and register for services offered by the clinic. With the help of the system the doctors and

the administrators can efficiently manage the operations of the clinic. The proposed system has

great capability to overcome drawbacks of the existing system by reducing the human errors. It

will help the clinic to improve its goodwill by offering high quality services supported by our

system. It has a great value of scope in meeting the following requirements of the organization:

Operational requirements, which include up-to-date factual information that are

necessary for day-to-day tasks

Planning requirements that comprise of short- and long-term decisions about

patient care and decisions about Clinic management

Documentation requirements such as maintenance of records, accreditation and

legal records.

8/7/2019 PPSP G1 DOC2

3/59

Obj ective of proposed system The main objective of our Online Healthcare Clinic Management System is to overcome the

drawbacks and irregularities of the current system without incurring too much financial burden

on the organization. Its prime objective is to improve the goodwill of the organization by

supporting very high quality services. Our system aims to improve the accuracy and timeliness

of patient care, accounting and administration, record keeping, and management reporting. The

long term goal is to help the clinic to expand its business operations by building and maintain a

patient database for analysis of data to facilitate decision making process.

The objective is to automate the Clinic operations. This project will facilitate the offering world

class health services. Doctors can use the patient data for different kinds of researches. This project will also help in policy making for health in future on the basis of computerized data.

8/7/2019 PPSP G1 DOC2

4/59

P ro bl ems in existing system Ma nu a l entry of D a i l y a ppointments a nd Pa tients Records:

All the records are manually entered, so the current system is error prone as error is

human. Also it is very difficult to manage operations if no. of patients is high.

N o immedi a te retriev a l of d a t a- :

The information is very difficult to retrieve in the current system. If you have to find out

about the patients detail and history, the user has to go through various registers. It

results in inconvenience and wastage of time.

N o P roper stor a ge inform a tion - : The information generated by various transactions is separately stored in various registers

which takes a lot of time and effort. It also results in data redundancy.

E rror m a y in m a nu a l ca l cu l a tion: -

Accounts and billing department is manually run. Calculations are manually done which

is error prone. It also takes a lot of time and results in incorrect information. For example

Calculation of patients bill based on various treatments.

P rep a r a tion of a ccur a te reports: -

It is a very a difficult Task as information has to be gathered from various registers.

P ro bl ems in a ppointments: -

A lot of patients daily visits the Healthcare clinic and are facing problems regarding pre-

appointments and on the spot registrations. The administrative staff of the clinic is not

able to keep and locate the daily appointments and the history record details of the patients manually

8/7/2019 PPSP G1 DOC2

5/59

P roposed S ol utionB asically to overcome the current problems we have proposed the Online Healthcare Clinic

Management System.

Fully computerized operations to ensure the reliability, accuracy and faster services. Provision of online doctors appointments and patient registration to prevent rush. On the

spot registration facility also available.

E fficient management of Clinic as there is proper allocation of expert services and time

scheduling.

Security, services and to improve the patient treatment system and its record . Doctors

can any time view pat ient history to ensure high quality services.

Connect all departments of the clinic to keep a record of all the data.

This system provides online storage/updating and retrieval facility. In this system

everything is stored electronically so very less amount of paper work is required and

information can be retrieved very easily and quickly without searching here and there

into registers.

Maintain online decision support system: the Administrators and Doctors can view the

information as per their requirements which would help them in taking various decisions.

Accounts and billing department are fully computerized which reduces the chances of

error to be minimal.

Report Generation facility is available.

8/7/2019 PPSP G1 DOC2

6/59

S chedu l e P l a nning

1. G a ntt Ch a rt

8/7/2019 PPSP G1 DOC2

7/59

8/7/2019 PPSP G1 DOC2

8/59

S ystem Hier a rchy Ch a rt

8/7/2019 PPSP G1 DOC2

9/59

F ea si bi l ity Report

Feasibility report is the learning about the system function, problem existed and the anticipated

solution. It is an approach to verify the reasonable chance of success of the project. The proposedsystem should be feasible in all regard as economy, technical, schedule and operational. The

objectives of the feasibility report are to find out whether project is feasible or not.

A feasibility study should provide management with enough information to decide:

Whether the project is feasible.

Whether the proposed solution will benefit its projected users.

The alternatives among which other solution can be chosen.

Feasibility study is a management-oriented activity. It is completely determined by managers

that they can precede for the solution or not. There are four types of feasibility such as:

Technical

Operational

Schedule

Economical

T echnic a l fea si bi l ity: -

It is the process of determining whether the organization has the technology resources to develop

or purchase, install, and operate the system. With the help of Technical feasibility we can find

out:-

Whether the required technology is available or not

Whether the required resources are available:-

Manpower- programmers, testers & debuggers

Software and hardware

For developing our system the technical requirements such as hardware, software, and

other accessories are mentioned below:

8/7/2019 PPSP G1 DOC2

10/59

H a rdw a re Requirements: -

Item R equired Available More R equired

Computers 4 0 4

Printers 2 0 2

Server 1 0 1

The configuration of the above mentioned computer should be:

Processor: Core-2-Duo

R AM: 2GB

Hard disk: 320GB

The above mention computers will be implemented at the reception and inventory.

Rest will be used by orders, and billing department.

S oftw a re Requirements: -

Database Manager: MS SQL

Programming Language: ASP.N E T

Operating System: Windows XP

The above mention softwares are required for maintaining the database records

S chedu l e fe a si bi l ity: -

It is the process of assessing the degree to which the potential time frame and completion dates

for all major activities within a project meet organizational deadlines and constraints for

8/7/2019 PPSP G1 DOC2

11/59

affecting change. It basically includes workload matrix, Gantt chart and a work breakdown

structure.

The main part of schedule feasibility report is

Work Load Matrix

Gantt Chart

Pert Chart

E conomic fe a si bi l ity: -

It defines whether the proposed system is economically feasible or not. It consists of 2

tests :

Is the anticipated value of the benefits greater than projected costs of

development? (cost / benefit analysis)

Does the organization have adequate cash flow to fund the project during the

development period?

As our information system is an entirely new set up for the organization, the initial cost of

installation and the training cost will be high. The online Healthcare clinic management System

is a bit costly affair in terms of hardware required because we will be building a network for thorough process. We will be connecting al the computers through LAN so that exchange of data

can be easily done. Also we will be making the website and putting it on internet so the cost

increases but it is a necessary part of this information system.

O per a tion a l F ea si bi l ity: -

Operational feasibility is mainly concerned with issues like whether the system will be used if it

is developed and implemented. Whether there will be resistance from users that will affect the possible application benefits. The essential questions that help in testing the operational

feasibility of a system are following:-

Does management support the project?

Are the users not happy with current business practices?

8/7/2019 PPSP G1 DOC2

12/59

Will it reduce the time (operation) considerably?

If yes, then they will welcome the change and the new system.

Have the users been involved in the planning and development of the project? E arly

involvement reduces the probability of resistance towards the new system.

Will the proposed system really benefit the organization? Does the overall response

increase? Will accessibility of information be lost?

Will the system affect the customers in considerable way?

S el ection of methodo l ogy: -

No any development methodology guarantee success of project but there are the combination of

technologies thats need to implemented for the success of a project.

The various lifecycle models provide as a framework to structure and manage our product

efficiently

For the development of our online healthcare clinic management system we decided to follow

waterfall model which can be considered as traditional and most simple method to develop our

software product.

In this model the project development into divided series of stages which are to be carried out in

sequences. This model is initiated with feasibility analysis if the project is feasible the

requirement analysis and project planning begins.

The design starts after the completion of requirements analysis. When the design is complete

coding begins. Once the programming and the coding part is complete the system is integrated

and tested. After a successful testing, the system is installed at the user end and a regular

operation and management support is provided.

Condition for w a terf a ll mode l : -

1. Define before design and design before code

2. Well understood problem

3. E xpects complete and accurate knowledge of requirement in the beginning

4. No changes at later stage

8/7/2019 PPSP G1 DOC2

13/59

5 . Less user participation

Re a son for se l ection of w a terf a ll mode l : -

B efore the selection of any model for software development we have to consider the following

factors:-

1. Requirements

2. Development team

3. Users

4. Project type and risk

B ased upon the above the factor we selected the waterfall model because of following reason..

Requirement of the project is well know and stable. Requirements are clearly defined and are

not going to change. We have to design and develop the system as per these requirements.

User participation is not possible during the development of project. The guidelines are

clearly set and we have to work to according to that guideline.

This approach is quite simple and easy to understand and usually no special training is

required. The development team is well versed with this technique as they have successfully

used it before in the past project.

The project is of short duration and the product definition is stable. There are very few risks

involved

It is best suited of the automation of a manually existing system.

Comp a rison of mode l s: -

E ach process model is suited for some context. B ut according to our group the w aterfall model

is the optimal process for the current system.

Waterfall model is quite simple and easy to execute than spiral model or time fixing model . It

is quite intuitive and logical for the current scenario than the other two models. In the current

system the requirement are clearly specified i.e. they are stable or frozen.

8/7/2019 PPSP G1 DOC2

14/59

Waterfall model is the best approach to automate an existing manual system. Here we are not

developing completely new system where determining user requirements and user involvement

is essential. The technology requirement for the current system is also not very high. So there is

no such problem in which the chosen technology can become outdated.

Waterfall model is well suited for short duration projects. And we have 8 5 days time to build

the complete project. Other model is well suited for large or real time projects. Development

team consists of only four members so the waterfall model is best approach as compared to other

models as they require large team size. Waterfall model allows proper control and management

of group.

In the current scenario we have to deliver the entire software at end. There is no need to update

the user about the project developments. Most important of all w aterfall models is a documentdriven process that requires formal documentation at the end that helps to produce quality

material.

8/7/2019 PPSP G1 DOC2

15/59

P ROJ E C T PLA NN I N G C O NT RO L Software project management begins with a set of activities that are collectively called project

planning. B efore the project can begin, the manager and the software team must estimate the

work to be done, the resources that will be required, and the time that will elapse from start to

finish. Important area in software planning is user involvement, Risk analysis, standard guideline

and procedures, organization of the project, requirement analysis and design, changes, resource

and quality assurance.

Configuration Management: Whenever we build a computer software, change happens. And

because it happens, we need to control it effectively. Software configuration management (SCM)

is a set off activities that are designed to control change by identifying the work products that are

likely to change, establishing relationships among them, defining mechanisms for managing

different versions of these work products, controlling changes that are imposed, and auditing and

reporting on the changes that are made.

In our project under configuration management we have done following up gradation:

y After development of system we had upgraded our system by giving additional feature for

printing of different reports in the system itself for output generation.

y We had upgraded our system ASP.N E T 32-bit version of ASP.N E T 1.1 to 64-bit version

of ASP.N E T 2.0 because this new version has extra features for users.

y Upgrading the system from lower version to higher version it was necessary to upgrade the

hardware also, therefore we had helped the users to upgrade the hardware.

Software Quality Assurance (SQA): It is defined as a planned and systematic approach to the

evaluation of the quality of and adherence to software product standards, processes, and

procedures. SQA includes the process of assuring that standards and procedures are established

and are followed throughout the software acquisition life cycle.

P ROG AMM I N G S T A N D A RD S : - We have used a uniform coding habit in our software so that

reading, checking, and maintaining code written by our group members becomes easier. The

intent of these standards is to define a natural style and consistency. E veryone has its own style

of witting codes, which makes it difficult to understand for another person. A mixed coding style

8/7/2019 PPSP G1 DOC2

16/59

is harder to maintain than a bad coding style. We have applied a consistent coding style across a

project. Code is more readable when comments are presented in paragraph form prior to a block

of code, rather than a line of comment for a line or two of code. Highlight the comment block in

a manner that clearly distinguishes it from the code. The most important consideration in naming

a variable, constant, or subroutine is that the names fully and accurately describe the entity or

action that the structure represents. Variable and Function naming convention is set, according to

which a relevant name explaining the function of the variable or the function. Go to statement

has been avoided in the coding, and the program has been divided in small modules called

functions by using object oriented programming concept.

Documentation Standards: Documents produced according to appropriate standards have

a consistent appearance, structure and quality. Many a times system documentation is badlywritten, difficult to understand or incomplete. Document structure has a major impact on

readability and usability and it is important to design this carefully when creating documentation.

We have provided the document structure in which the material in the document is organized

into chapters and, within these chapters, into sections and subsections. We have implemented the

IEEE standard for the documentation of our project:

y Font size for heading is 18 & for body text 12

y 1.5 line spacingy Alignment of text Left

y Margin normal (top 1, bottom 1, left 1, right 1)

y Page layout portrait

y Report layout

y Font style Times New Roman

8/7/2019 PPSP G1 DOC2

17/59

C OS T E S T I MA T I O N

Model Used: Constructive Cost Model (COCOMO)

About COCOMO: - It is used for estimating software development costs based on parameters

such as the source line of code of function points.

We have used COCOMO model to estimate the project cost. Since, the requirements were fixed

and well specified and we have a good knowledge about the project. We have used ORGANIC

development mode as it is best suited for the small, well understood and simple project. Also the

system involves the usages of the database which is the heart of the system being developed.

This model has three basic steps to calculate the total cost. They are

1. To obtain an initial estimate of the development effort from the estimate of thousands of

delivered lines of source codes (KLOC).

2. To determine an impact of different attributes of the projects.

3. To adjust the effort estimated by multiplying the initial estimate with all the multiplying

factors.

Function Point cost Estimation (FP)

Decomposition for FP-based estimation focuses on information domain values rather thansoftware functions. The base of the function point analysis is that, computer basedinformation systems comprise of five major components or external user types inAlbrechts (developer of FP). The project planner estimates external inputs, externaloutputs, external inquiries, internal logical files, and external interface files. It is based onan estimate of the functionality of the delivered software. One of the importantadvantages of using the function point metric is that it can be used to easily estimate thesize of a software product directly from the problem specification. Formula for findingthe function point (FP) is:

UFC Unadjusted Function Point Count

T CF Technical Complexity Factor

VAF Value Adjustment Factor

FP = UFC x TCF (VAF*)

8/7/2019 PPSP G1 DOC2

18/59

Function Point for Online Health Care Management System

Information DomainValue

Count Multiplier (Weighting Factor)Simple Average Complex Simple Average Complex Total

E xternal Input Type 6 5 2 3 4 6 5 0E xternal Output Type 5 3 2 4 5 7 49E xternal E nquiry 6 2 - 3 4 6 26Internal Logical File 5 4 - 7 10 1 5 75 E xternal Interface File - - - 5 7 10 -

Total UnadjustedFunction Point Count

200

Notati

on

Contributing Factors NoInfluence

Incidental

Moderate

Average

Significant

E ssential

Weights (0) (1) (2) (3) (4) (5)F1 Data and

CommunicationY

F2 Distributed Functions Y

F3 PerformancesObjectives

Y

F4 Heavily UsedConfiguration

Y

F5 Transaction Rate Y

F6 Online Data E ntry YF7 E nd- user efficiency Y

F8 Online update Y

F9 Complex processing Y

F10

Reusability Y

F11

Installation E ase Y

F12

Operational E ase Y

F13

Multiple sites Y

F14

Facilitate change Y

Total 0 0 6 12 12 5

8/7/2019 PPSP G1 DOC2

19/59

UFC computation UFC= 7 ((Number of items of variety i) x w eight i). Technical ComplexityFactor

Involves 14 contributing factors.

TCF computation TCF=0.6 5+ 0.01 7 Fi. Fi (i=1 to 14) are complexity adjustment values based on responses to questions 1 - 14.

4.

F in a l E stim a tion

FP 200

Average Productivity 5 0 FP/pm at rate of Rs.2 5 ,000 Per MonthCost Per Function Point 25 ,000/ 5 0=Rs. 5 00.00

Total E stimated Project Cost= 5 00*200=Rs.1,00,000.00E stimated E ffort 4 Person-Months

Other Charges

Categorization of Costs

Detail Price PerProduct

T otal Charges(4Persons)

Hard w are cost

Four 2 Mb of RAM 1 5 00 6000

Four Processor Intel Core 2 Due 6000 18 000

Four 80 G B Hard Drive 2000 8000

1024* 768 Pixels color Monitor four

45 00 18 000

Four Keyboards 2 5 0 1000

Four Optical Mouse 200 800

Database server 3 5 000 35 000

Soft w are Cost

Microsoft Visual Studio 2008 5 000 5000

Apache Server & PHP 0 0

SQL Server 5 000 5000

Infrastructure Four Chair and Table areRequired

2000 8000

Travel and Site visit, transportation and 2 5 00 7 500

N et T otal = 35 Thus, TCF= 0 .6 5+0 .0 1*35= 1. 00 Thus, FP = UFC*TCF=2 00 *1. 00 = 200 (approx)

8/7/2019 PPSP G1 DOC2

20/59

training tanning for employees

E mploys Salary Four Person with TwentyThousand Salary each

25 000 100000

Total cost 2,12,3 00

E ffort E stim a tion: -

Description: -

The main goal of the E ffort E stim a tion is to support researchers, practitioners and educators in

software cost and effort estimation through identification of relevant and useful knowledge

(papers, books, journals, conferences, tools, etc). E ffort estimation consists of predicting how

many hours of work and how many workers are required to develop a project. The effortinvested in a software project is most likely one of the most important and most analyzed

variables in recent years in the process of project management. The purpose of the value of this

variable when initiating software projects allows us to plan effectively any forthcoming

activities. As far as estimation and prediction is concerned there is still a number of unsolved

problems and errors. To obtain good results it is essential to take into consideration any previous

projects. E stimating the effort with a high grade of reliability is a problem which has not yet been

solved and even the project manager has to deal with it since the beginning.

Rough E stim a tion: -

Ho w many hours of w ork 4 hours/day

No. of Worker 4

COCOMO II is a well-studied and accepted effort estimation model. The original

COCOMO model was first published by Dr. B arry B oehm in 1981, and reflected the software

development practices of the day. B y expanding the COCOMO model with the proposed

metrics, a new model can build upon the experience inherent in the COCOMO technique.

Co nstructive Co st Mo del II (COCOMO II) is a model that allows estimating the cost, effort, and

schedule when planning a new software development activity. COCOMO II is the latest major

extension to the original COCOMO (COCOMO 81) model published in 1981. It consists of three

sub models, each one offering increased fidelity the further along one is in the project planning

8/7/2019 PPSP G1 DOC2

21/59

and design process. Listed in increasing fidelity, these sub models are called the Applications

Composition, E arly Design, and Post-architecture models.

C OC O M O II c a n be used for the fo ll owing m a j or decision situ a tions: -

Making investment or other financial decisions involving a software development effort

Setting project budgets and schedules as a basis for planning and control

Deciding on or negotiating tradeoffs among software cost, schedule, functionality, and

performance or quality factors.

Making software cost and schedule risk management decisions

Deciding which parts of a software system to develop, reuse, lease, or purchase

Making legacy software inventory decisions: what parts to modify, phase out, outsource,

etc

Setting mixed investment strategies to improve organization's software capability, via

reuse, tools, process maturity, outsourcing, etc

Deciding how to implement a process improvement strategy, such as that provided in the

SE I CMM

The software equation is a multivariable model that assumes a specific distribution of effort

over the life of a software development project. The model has been derived from

productivity data collected for over contemporary project.

E = [LOC* B 0.333 /P] 3 *(1/t 4)

Where,

E =effort in person -months or person-years

t=project duration in months or years

B =Special skill factor

P=Productivity parameter

8/7/2019 PPSP G1 DOC2

22/59

That reflects overall process maturity and management practices, the extent to which good

software engineering practices are used, the level of programming languages used, the state

of the software environment, the skills and experience of the software team and the

complexity of the application.

8/7/2019 PPSP G1 DOC2

23/59

Risk Ma n a gement Risks are those events or conditions that may occur, and whose occurrence, if it does take place,has a harmful or negative effect on a project. Risks should not be confused with events andconditions that require management intervention or action. A risk is a probabilistic eventit mayor may not occur. So project management must be prepared for changes and plan accordingly tohandle such normal events.

So risk management is required to avoid the risk during project .Risk management aims toidentify the risks and then take actions to minimize their effect on the project.During the development of Online Healthcare Clinic Management System we identify thesoftware risk component that can affect the project development process. The software risk components are as given below:

R ISK ASS E SM E NT

Risk assessment basically involves four steps:-1. Risk Identification

2. Risk Analysis

3. Risk Prioritization

4. Risk Control

8/7/2019 PPSP G1 DOC2

24/59

R ISK ID E NTIFICATION

Risk identification is the first step in the risk assessment so as to analyze the different risk factors

which can lead to the software failure.

Sr. No. Risk Identified Description

R 1 B ad Communication Some of the requirements are not clear due to bad communication which can leadto user dissatisfaction & project failure.

R 2 Shortage of Technical Staff It may be possible that all the membersmay not be aware of the technology used.

R 3 Working on New Technology It can be both in terms of hardware andsoftware. Difficult to cope up.

R 4 Member Illness This is uncertain and impact would begreater in the project because of

personnel shortfall.R 5 Hardware Failure and Software Malfunction Failure of hardware or software

malfunction during the development phase

R 6 No Quality control Not able to match the quality policy of the organization and customer needs maylead to quality failure.

R7 Project Size The size of the project may become highor low

R8 Insufficient fund If the fund for the project is not allowedin time, it may cause change in schedule.

R9 Increase in the estimated user If the number of users increases for thesystem, the server requirements and thedatabase efficiency become low.

R 10 Complexity of application It can be complex in functionalities anduser requirements.

R 11 Lack of experienced staff It may be possible that the groupmembers done have any experience insystem development.

R 12 High Work Load Due to the over burden on the groupmembers it may lead to the project failure

R 13 Overall Poor Management Due to the unclear goals and objective inthe high end management levels, maylead to project failure

R 14 Lack Of E fficient Planning Due to lack of efficient planning the project might suffer hard time duringdifferent phases of SDLC

R 15 Inadequate Testing Inadequate Testing during the testing phase may lead to the presence of bugs inthe Software thereby leading to thesoftware failure

R 16 Milestone Not B eing Met Not able to meet the estimated deadlinesduring the implementation phase mayalso lead to the project failure

8/7/2019 PPSP G1 DOC2

25/59

R ISK ANALYSIS

After the Risk Identification the different levels of risk are identified and are categorized as

impact and risk categories. E ach risk in analyzed so as to find the actual risk consequence and its

impact in project.

R ISK P R IO R ITIZATION

After proper risk analysis the risk factors are priority based on their risk exposure level, as higher

the risk exposure the higher the priority it is kept so as to minimize the problem developed in

order to efficiently deliver the system.

R ISK CONT R OL

The counter measures taken so as to control the risk factors having the maximum risk exposure.

Proper planning is initiating so as to derive proper planning to monitor the tasks and avoid the

major risk developing scenarios.

Impact Categories

Level Of Consequences R ange Impact ID

Negligible 0.0-3.0 N E - (0-3)

Marginal 3.0-7.0 MA -(3-7)

Critical 7.0-9.0 CR - (7-9)

Catastrophic 9.0-10.0 CA-(9-10)

Risk Categories

Probability R ange Probability ID

Low 0.0-0.3 LO - (0.0-0.3)

Medium 0.3-0.7 M E - (0.3-0.7)

High 0.7-0.9 HI- (0.7-0.9)

Very High 0.9-1.0 VH- (0.9-1.0)

8/7/2019 PPSP G1 DOC2

26/59

Prioritizing of risks based on their R isk exposure & preparing R isk Management Plan

R isk R isk Management Plan

Increase in the estimated user We are using SQL server as database to handle large no.

of users -data.

Lack of experienced staff We are providing training, User-supported manuals in the

support phase.

Insufficient fund We will be doing initial budget plan/cost analysis & reg.

monitoring.

We are also making application such that it is supported

by generally used technological resources.(H/W & S/W)

Project Size We are avoiding use of unnecessary flash and images.We are also imposing a check on data redundancy.

We are planning ahead for the link load & optimal link

usage by setting a limit.

Overall Poor Management We are ensuring multiple resources are assigned on key

project areas.

Including team-building sessions.

Rotating job among team-members.

We are also maintaining proper documentation of each

individuals work.

Milestone Not Being Met y Work evenly distributed among team-members.

y E ffectively designing the Gantt chart & strictly

following it.

y Regular monitoring to ensure that project milestones

are met with time.

Proper selection of development software (.N E T) for fast

completion.

8/7/2019 PPSP G1 DOC2

27/59

P ro j ect Ma n a gement

It is apprehensive with actions involved in ensuring that software is delivered on time and on

schedule and in accordance with the requirements of the organisations developing and acquiring

the software.

Project Planning

Project planning is the process of quantifying the amount of time and the size of the budget for a

project. The output of the project planning process is a project plan that a project manager can

use to track the project team's progress.

Project Planning process

Analyze the project specification

Make initial assessments of the project parameters

Define project milestones and deliverables

While project has not been completed or cancelled loop

Draw up project schedule

Initiate activities according to schedule

Wait (for a while)

Review project progress

Revise estimates of project parameters

Update the project schedule

Re-negotiate project constraints and deliverables

If (problems arise) then

Initiate technical review and possible revision

E nd if E nd loop

8/7/2019 PPSP G1 DOC2

28/59

Tasks undertaken by the Team Members

Tasks Undertaken Team Member

Project Leader and Business Analyst Anand Kumar

Design coordinator and Tester Anand Raj

Programming coordinator Avinash Kumar

Documentation coordinator Rohit Singh

Milestone R eport

Project Title: Online Healthcare Clinic Management System

Project Leader: Anand Kumar

Project Details:

Project Start date Project E nd Date

10/0 8 /09 14/11/09

Index No. Milestone

Date

Milestones

Achieved

Deliverables

1 14/08/09 Project specificationanalysis

Problems as well as their solutions areidentified

2 20/08/09 Schedule Planning Gantt chart, Workload matrix3 29/08/09 Selection of

Methodology

Purpose, structure and scope of

waterfall model.4 09/09/09 Project Plan and

Control

Configuration Management, Quality

Assurance, Documentation Standards,

Programming Standards etc.

5 09/09/09 Cost estimation E xplanation of techniques used for

8/7/2019 PPSP G1 DOC2

29/59

estimating the cost. Performed cost

estimation to find estimated cost for the

project by Cocomo model

6 15 /09/09 Risk management Risk Assessment, Risk Control, Risk

Identification, Risk Analysis and Risk

Prioritization

7 20/09/09 Project Management

Resources needed for the project , and

their individual roles in the project

8 26/09/09 RequirementAnalysis

Principle of requirement engineering,

elicitation, analysis and validation

techniques

9 05 /10/09 Process Modelling Context diagram, Level 1 DFDs, Level2 DFDs, Structured E nglish

10 10/10/09 Data Modelling E ntity Relationship Diagram, E ntitylife history

11 14/10/09 Designing conceptsand Principles

Design Process, concepts likeabstraction, refinement etc.

12 19/10/09 Architectural design Architecture model followed and its

explanation with the system

architecture

13 23/10/09 Interactive screendesign

Designed Input and Output Screens for

the system.

14 06/11/09 ProgrammingE nvironment

E xplanation and justification of

suitable development tool used to

develop this system.

15 08/11/09 Test plan Testing plan is provided

8/7/2019 PPSP G1 DOC2

30/59

The resources (Hardware & Software) needed for the project, are classified into two parts: theclient terminal and at the server terminal.

Soft w are requirements:

Criteria Server Client

Operating System Microsoft Windows Server 2003 Windows XP or any other OS

Soft w are Technology ASP.N E T Not required

Database SQL Not required

Web bro w ser not required Most appropriate web browser

Hard w are R equirements:

Criteria Server Client

Computer and processor At least two 2 GHz or more 1.8 GHz processor

Memory Minimum 1 G B 25 6 M B RAM

Hard disk 200 G B Free space Available

Drive CD-ROM or DVD drive Available

Display 1024x768 or higher resolution

monitor

Current monitors can operate on this

resolution

Net w orking Device At least 2 Gigabit E thernet NIC (10/100 E thernet Port)

8/7/2019 PPSP G1 DOC2

31/59

Requirement A n a l ysis

Requirement Analysis also known as Requirement E ngineering is the branch of software

engineering concerned with the real-world goals for, functions of, and constraints on software

systems. The major activities like understanding problems, solution determination, and

specification of a solution are the part of requirement analysis. These activities are testable,

understandable, maintainable, and which satisfies project quality guidelines. It is critical to the

success of our project.

R equirements of various users of the online healthcare clinic management system.

1. Patients requirements: The major functionalities which the patients requires from this

system are as follows: The registration procedure should be very easy.

Appointment on his time choice

Patients should get the detailed authentic reports

Another priority of the patients is the detailed medical history.

2. Doctors requirements: The major functionalities which the doctors requires from the

system are as follows:

They can access patients records easily.

They can get detailed patients record.

They can also have the records of the appointments

3. Administrators: The functionalities which the admin staff requires from the system are as

follows.

Administrators can have the privilege of adding or modifying the patients or the

doctors information.

They can easily generate reports.

They can access the patients medical history.

4. System Developers: The requirements of the developer team to make the system are as

follows.

Proper software and hardware availability.

Proper preparation of milestones.

8/7/2019 PPSP G1 DOC2

32/59

Proper work scheduling.

Co-relation between the team members.

Functional requirements from the system: It describes the functionalities and performance of

the online healthcare clinic management system. We have found the requirements based on our software.

Online/ Offline registration for all the patients online.

Old Patient Record History

Record of all the doctors profile and expert allocation time

Instant report Generation for all the functionality

Historical records of visit of patients

Payment and billing records.

Interface Specification: The system which we are developing for this assignment is based on

client server architecture. Following are the hardware and the software requirements for this

system.

Hardware Interface: P4 processor.

Software Interface: ASP.net.

Communications Interface: Screen, Keyboard

Memory Constraints: 128 M B .

Data R equirements:

INPUT- Data input comprises of data being entered in

Patient Registration Input

Doctors Registration Info

Appointment time schedule

8/7/2019 PPSP G1 DOC2

33/59

8/7/2019 PPSP G1 DOC2

34/59

Process Modelling

Context Diagram/Level 0:

8/7/2019 PPSP G1 DOC2

35/59

Level 1:

8/7/2019 PPSP G1 DOC2

36/59

Level 2 (Process 1) DFD

8/7/2019 PPSP G1 DOC2

37/59

Level 2 (Process 3) DFD

8/7/2019 PPSP G1 DOC2

38/59

Level 2 (Process 4) DFD

8/7/2019 PPSP G1 DOC2

39/59

Process Specification :1. Structured E nglish

A ppointment -:

If patient id doesnt exist Then

Doctor id = illness type

And appointment time = current Allotted time + 30 min else

If product id exist and appointment time Then

appointment time = current time + 30 min

Cre a te p a tient profi l e-:

If user Id & mail id doesnt exist Then

create user profile else

Take other user id 2 email addresses

E lse error in creating profile

La b- :

If product id exists

Date = current date

Update diagnosis result else

View report

8/7/2019 PPSP G1 DOC2

40/59

8/7/2019 PPSP G1 DOC2

41/59

D ata Modelling

E ntity R elationship Diagram

E ntity Relationship Diagrams are a major data modelling tool and will help organize the data inyour project into entities and define the relationships between the entities. This process has

proved to enable the analyst to produce a good database structure so that the data can be stored

and retrieved in a most efficient manner. There are basically four components: - entity, attribute,

cardinality, relationship.

8/7/2019 PPSP G1 DOC2

42/59

E ntity Life History

E LHs provide us the dynamic sequence or time-based view. It shows the processing cycle of an

entity from creation to deletion. It models all possible changes to the values of the attributes (or

data items) of the entity during its life and the sequence in which the updates take place. Itanalyses the life cycle of the entities in information systems.

.

Processing cycle -login, profile creates, edit profile, update profile and profile delete

Related Entity - Patient, Doctor

Processing cycle -Hired, profile created, View Appointments & history, Profile Update and Profile

Delete, Treatment of patient.

Related entity- Patient, Administrative Officer

Processing cycle- Register, Take appointments, Treatment of patient, Medical analysis, Medicineprescribed, Detail history maintained, Bill generate and Profile deleted

Related entity -Doctor, Administrative officer

Profile created Profile edited Profile updated Profile deleted

Hired Profile Created Profile Updated Profile Deleted

Register Bill generated

Detail histor maintained

Medical analysisTake appointments

Treatment of patient Medicine prescribed

Profile deleted

Administrative officer

D octor

View Appointments & history

Treatment

Patient

Login

8/7/2019 PPSP G1 DOC2

43/59

Processing cycle- test, reports, delivery of report

Related entity- patient

Pathologist

Perform Medical test Deliver to doctorGenerates report

8/7/2019 PPSP G1 DOC2

44/59

Data Dictionary for Proposed System

PROCESS 1.0

N a me: Log In.

Description : Receives Login Details and login data from Patient in order to provide login details& Response.

Input d a t a f l ows : Login Details, Login Data.

Output d a t a f l ows : Response, Login Details.

P rocess: DO

R E AD Login Details, Login DataWRIT E Response, Login Details

E ND

PROCESS 2.0

N a me: Make Registration.

Description : Receives Patient Details and provides Registration details, and Patient ID. Receiptand stores data about registered member details in Patient Table.

Input d a t a f l ows : Patient Details.

Output d a t a f l ows: Patient ID, Registered Patient Details.

P rocess: DO

R E AD Patient details

WRIT E Patient ID, registered Patient Details, Receipt

E ND

8/7/2019 PPSP G1 DOC2

45/59

PROCESS 3.0

N a me: Make Appointment.

Description : Receives Registered Patient Details and Patient ID and provides Available Time

and Patient ID, Doctor ID, Receipt and stores data about registered Patient details inAppointment Table.

Input d a t a f l ows : Registered Patient Details, Patient ID.

Output d a t a f l ows: Available Time and Patient ID, Receipt.

P rocess: DO

R E AD Registered Patient Details, Patient ID

WRIT E Available Time and Patient ID, Receipt

E ND

PROCESS 4.0

N a me: Generate Report.

Description : Receives Patient Diagnosis Details and Patient Details and provides Report,Receipt and stores data about Patient Details in Appointment Table.

Input d a t a f l ows : Receives Patient Diagnosis Details, Registered Patient Details

Output d a t a f l ows: Diagnosis Report.

P rocess: DO

R E AD Receives Patient Diagnosis Details, Registered Patient Details

WRIT E Diagnosis Report

E ND

8/7/2019 PPSP G1 DOC2

46/59

DATA ST ORE 1

N a me: LogUser Table.

Description : Stores Information about the registered patient details and also provides login

services data detail. Input d a t a f l ows : Registered Member Details, Login Details.

Output d a t a f l ows : Login Data.

Da t a structure: userid, password, usertype, emailid

DATA ST ORE 2

N a me: patient Table.

Description : Stores Information about the registered Patient details and also gives the PatientDetails.

Input d a t a f l ows : Registered Patient Details

Output d a t a f l ows : Registered Patient Details.

Data structure: patientid, patientame, sex, dob, bloodgrp, address, state, nationality, mobile,email_id, emergency_contact, HIprovider, hipphonenumber, insureds_name, photo,

expecteddesease, diseasedescription, treatmentdescription, diagnosis_test, test_result, height,weight, dependents, comp_details

DATA ST ORE 3

N a me: appointment Table.

Description : Stores Information about the Registered Patient ID,Doctor ID and also provides theAppointment Time.

Input d a t a f l ows : Registered Patient ID, Treatment Description, Medicines, Diagnosis,

Appointment Date and time, Payment and Doctor ID.Output d a t a f l ows : Appointment Time.

Data structure: patientid, doctored, present_illness, treatment_description, medicines,diagonosis, diagonosis_result, appointment_date, app_time, emailed,payment.

8/7/2019 PPSP G1 DOC2

47/59

Design P rincip l es a nd ConceptsSoftware design: it is done to produce a solution to the problem given in the software

requirement specification. A good software design is the key to successful product. It is the

process of problem-solving and planning for a software solution.

In the software design phase the customer requirements are perfectly translated into a complete

system.

Design P rincip l es of Our S ystem .

Our design process should not suffer from tunnel vision: We have regarded substitute

approach to complete or system.We had reviewed each module based on the requirements of

the problem, the resources available to do the work and any other constrictions.

Our design should be traceable to the analysis model: It is necessary because a single

element of the design model often traces to multiple requirements, it is necessary to have a

means of tracking how the requirements have been satisfied by the model.

Our design should give minimum surprise to the users: Software design is not a

disorganized process. There are many factors to consider in any design effort. All design

should be as simple as possible, but no simpler.

Our design should minimize the intellectual distance bet w een the soft w are and theproblem as it exists in the real w orld: A software system exists for one reason: to provide

value to its users. All decisions should be made with this in mind.

We should al w ays consider the architecture of the system to build: We are giving

architectural design that illustrates what is the skeleton of the system. The whole program

flow and behavior depends upon the architectural design.

The design of data is as important as important as design of processing functions: In our

system structured data design helps to simplify program flow, which makes the design and

implementation of software component easier, and overall processing more efficient.

The design representation should be easily understandable: The designing of the system

is very simple. It is very easy to understand. A coder and can easily code and tester can easily

test the design.

8/7/2019 PPSP G1 DOC2

48/59

Our design w as revie w ed to minimize conceptual (semantic) errors There is sometimes

the tendency to focus on minute details when the design is reviewed, missing the forest for

the trees.

Design is not coding, coding is not design E ven when detailed designs are created for

program components the level of abstraction of the design model is higher than source code.

Soft w are Design Concepts used in our project

Abstraction - We have used the abstraction concept in our assignment by hiding the

internal working of the system from the users.

R efinement - Patient registration is an information that can be decomposed to patients

name, patients add, patients phone etc. for registration we require all these details

Modularity - These concepts deals with the fact that we have to divide whole of the

software into several modules, this reduces chances of errors as different modules are

developed and tested separately. This also reduces the interference as elements of one

module cant communicate to the elements of other modules. We have designed the

system keeping in view the modularity of it.

Information hiding Since information (data and procedure) contained in our module is

hidden from the elements of other module and one cant directly access the information.Thus it has been made sure that there is proper information hiding done in our project.

Soft w are architecture - overall structure of the software components and the ways in

which that structure provides conceptual integrity for a system

Control hierarchy or program structure - Several modules are divided in sub-modules

and these sub-modules into lower level modules. E very entity has some level of hierarchy

in the application. It is controlled means the level of hierarchy ends after a certain level.

Structural partitioning - horizontal partitioning defines three partitions (input, data

transformations, and output); vertical partitioning (factoring) distributes control in a top-

down manner in our project.

8/7/2019 PPSP G1 DOC2

49/59

Data structure - we have represented the logical relationship among individual data

elements. The system has been designed in such a way that we have mentioned the

relationship between the data elements.

Soft w are procedure - precise specification of processing (event sequences, decision

points, repetitive operations, data organization/structure)

8/7/2019 PPSP G1 DOC2

50/59

8/7/2019 PPSP G1 DOC2

51/59

The system of Online/Offline Healthcare System has been developed using 2 tier, distributed

system model that shows how data and processing is distributed across a range of components.

Clients most often are the web browsers. Servers typically include web servers, database servers

and mail servers.

We have designed system using Abstract machine (layered) model. We have designed 2-tier

architecture, making the first tier i.e. the client architecture & business layer in ASP.N E T and the

database layer as MS SQL.

Application Layer Business Layer Data Layer

Login_UI loginuser

adminlogin_UI adminlogin

doctorlogin_UI Doctorlogin

editprofile_UI edit_profile

view_UI view_profile

make_apointment_UI appointment_user

doctor_view _UI view_doctors

diagnosis_UI diagnosis

Reports_UI Reports

Admin_UI View_profile

Users_login

Patient

Patient_appoint

Doctor

Patient bill

Patient_history

Patient_report

8/7/2019 PPSP G1 DOC2

52/59

Admin_UI Make_appointment Patient_appoint

8/7/2019 PPSP G1 DOC2

53/59

Inter a ctive screen design

Design 1:

8/7/2019 PPSP G1 DOC2

54/59

8/7/2019 PPSP G1 DOC2

55/59

Design 3:

8/7/2019 PPSP G1 DOC2

56/59

P rogr a mming E nvironment

Programming environments provide the basic tools and application programming interfaces, or

APIs, needed to construct programs. A programming environment implies a particular

abstraction of the computer system called a programming model. We have used Dot Net

platform for developing this system.

Technologies used:

Front E nd Asp.Net

Back E nd SQL Server

Documentation Tools:

Microsoft Word 200 7 : Used to write the documentation, designing tables, formatting, etc.

Microsoft Project2003: Used to develop the Gantt chart.

Microsoft Visio 2003: Used to develop E R diagrams, DFDs and Pert chart.

Why w e have used ASP.Net for developing our system?

Since we are making the complete system online so ASP.Net is the best possibletechnology which can be used to easily develop the system.

This Microsoft technology have various features such as easy drag and drop functions

and also we have to write less code while designing the system as the codes are

automatically generated.

ASP.Net also provides flexible and Simple Data Access.

In ASP.Net new features such as automatic control resizing eliminate the need for

complex resize code.

Provides simplicity as ASP.N E T makes it easy to perform common tasks , from simple

form submission and client authentication to deployment and site configuration.

8/7/2019 PPSP G1 DOC2

57/59

The source code and HTML are together therefore ASP.N E T pages are easy to maintain

and write . Also the source code is executed on the server. This provides a lot of power

and flexibility to the web pages.

All the processes are closely monitored and managed by the ASP.N E T runtime, so that if process is dead, a new process can be created in its place, which helps keep your

application constantly available to handle requests.

It is purely server-side technology so, ASP.N E T code executes on the server before it is

sent to the browser.

8/7/2019 PPSP G1 DOC2

58/59

8/7/2019 PPSP G1 DOC2

59/59

ReferencesBooks:

Awad E lias M., (2006) System Analysis and Design. Galgoatia Publications Pvt. Ltd.

Pressman Roger S., (2001) Software E ngineering A practitioners approach .

McGraw-Hill

J alote Pankaj (200 3) An integrated approach to Software E ngineering Addison Wesley

publication Pvt. Ltd.

Sussman David B eginning Dynamic Websites, First Indian Reprint March 2003,[Page No. 55 -95 ]

MacDonald Mathew, The Complete Reference ASP.Net, TMH E dition 2002, TATAMcGraw Hill, [Page No.139, 239, 5 65 ]

Online:

Client server architecture

www.webopedia.com/TERM/c/ client _ server _ architecture .html Accessed on 2 5 thOct.2009.

Testing-types http://www.exforsys.com/tutorials/testing/testing-types.html Accessed on

18 th Oct. 2009.

Requirement analysishttp://www.outsource2india.com/software/RequirementAnalysis.asp Accessed on 10 th

Oct, 2009.

Function point http://davidfrico.com/fpfull.pdf Accessed on 29th August, 2009.

Function point

http://www.codeproject.com/K B /architecture/Calculate_Function_Point.aspx Accessed

on 29th August 2009.

Function point http://en.wikipedia.org/wiki/Function_point Accessed on 29th August

2009.