Guided By:

Miss. Monali Doshi

Ext. Guided By:

Kanzariya

Mr. Dharmesh

Created By:
(12DCE034)

Harsh Sathawara
Jaldip Patel(12DCE041)
Dhruv Patel(12DCE045)

Basic View Of Project Details

Project Title

: E-Clinic System

Project Objective

: To Manage Hospital System

Project Category

: Website

Front End

: Asp.NET

Back End

: SQL Server 2008

Platform

: Windows

Software

: Visual Studio, SQL Server

Management

Technologies to be used

Aim of the Project

Aim of this project E-clinic is to develop a web

application that can be used to keep track of the

patients registering in a hospital.
Also, this system should support features such as-

accessing the previous visit histories of any patient,

search for patients by name and other attributes,
etc.
It also include the appointment and all the activities

included in hospital is managed by Doctor and

Reception side.

Functionalities Of The
Project

In this there are four module

Admin(doctor)
Reception
Patient
Visitor
Here, Visitor can register as a patient. Patient

is managed by reception and doctor.

Reception is managed by doctor and
reception manages patient appointment and
collection of hospital

Functionalities Of The
Project

Doctor manages both reception and patient, he

also manages appointment, health tips, feedback
etc. he is the admin of the site

Visitor can view the health tips and give feedback

in the site

Activity Diagram
Activity diagram is basically a flow chart to represent

the flow form one activity to another activity. The

activity can be described as an operation of the system.

So the control flow is drawn from one operation to

another. This flow can be sequential, branched or

concurrent. Activity diagrams deals with all type of flow
control by using different elements like fork, join etc.

So the purposes can be described as:

Draw the activity flow of a system.

Describe the sequence from one activity to another.
Describe the parallel, branched and concurrent flow of the
system.

Activity Diagram-Login

Activity Diagram-Registration

Activity Diagram-Feedback

Activity Diagram-Patient

Activity Diagram-Reception

E-R Diagram
Using the three schema approach to software engineering,

there are three levels of ER models that may be developed.

The conceptual data model is the highest level ER model in
that it contains the least granular detail but establishes the
overall scope of what is to be included within the model set.
The conceptual ER model normally defines master reference
data entities that are commonly used by the organization.
Developing an enterprise-wide conceptual ER model is useful
to support documenting the data architecture for an
organization.

A conceptual ER model may be used as the foundation for

one or more logical data models. The purpose of the

conceptual ER model is then to establish structural metadata
commonality for the master data entities between the set of
logical ER models. The conceptual data model may be used
to form commonality relationships between ER models as a
basis for data model integration

ER Diagram

Data Flow Diagram

One of the tools of structuring analysis is the Data

Flow Diagram. A Data Flow Diagram is a graphical

representation of the movement, processes and
data stores used in support of an information
system. Data Flow Diagrams serve two purposes:

Provide a graphic tool, which can be used by the

analyst to explain his understanding of the system

to the user.

Can be readily converted into a structure chart,

which is used in design.

DFD(Context Diagram)

DFD(1st level Diagram)

Doctor

DFD(1st level Diagram)

Reception

DFD(1st level Diagram)

Patient

Use case Diagram :

Use case diagrams are behaviour diagrams used to

describe a set of actions (use cases) that some system or

systems (subject) should or can perform in collaboration
with one or more external users of the system (actors).
Each use case should provide some observable and valuable
result to the actors or other stakeholders of the system.

To model a system the most important aspect is to capture

the dynamic behavior. To clarify a bit in details, dynamic

behavior means the behavior of the system when it is
running /operating.

So only static behavior is not sufficient to model a system

rather dynamic behavior is more important than static

behavior. In UML there are five diagrams available to model
dynamic nature and use case diagram is one of them. Now
as we have to discuss that the use case diagram is dynamic
in nature there should be some internal or external factors
for making the interaction.

Usecase Diagram

Class diagram
Hierarchy of UML 2.0 Diagrams, shown as a class

diagram. The individual classes are represented just

with one compartment, but they often contain up to
three compartments.

The class diagram is the main building block of object

oriented modeling. It is used both for general

conceptual modeling of the systematic of the
application, and for detailed modeling translating the
models into programming code.

Class diagrams can also be used for data modeling.

The classes in a class diagram represent both the

main objects, interactions in the application and the
classes to be programmed.

Class Diagram

Data Dictionary
A data dictionary, or metadata repository, as defined in

the IBM Dictionary of Computing, is a "centralized

repository of information about data such as meaning,
relationships to other data, origin, usage, and format." The
term may have one of several closely related meanings
pertaining to databases and database management
systems (DBMS):
a document describing a database

or collection of

databases
an integral component of a DBMS that is required to
determine its structure
a piece of middleware that extends or supplants the
native data dictionary of a DBMS

Table Name: tbl_adminsignup

Table Name: tbl_receptionsignup

Table Name: tbl_patientsignup

Home Page

Conclusion :
E-clinic is a medical site which is useful for all the people

who feel sick. people come here get register and post
appointment and get medicine from doctor. Doctor manage
appointment of patient and manage collection of hospital.
So it is easy way to deal with doctor by patient.

Success Is A Process, Not A Destination.

By project we learned the most precious things, an

experience. It is said that, Experience is the best teacher.

We not only learn how to make a Website but also learn that
how to interact with the person outside the world. This is the
memorable part of our life. And at last we only say that,
To get profit without risk, experience without danger, and
reward without hard work, is as impossible as it is to live
without being born.