Emedical

EMEDICAL CONSULTENCY
A Project Report
Submitted by:

Aeri Panchal
In fulfilment for the Award of the degree
of

SIKKIM MANIPAL UNIVERSITY

SMU

Page 1

Emedical

INDEX
Sr. No
1
1.1
1.2
1.3
1.4
2
2.1
2.2
3
3.1
3.2
4
4.1
4.2
4.3
5
5.1
5.2
5.3
5.4
5.5
5.6
6
6.1
6.2
6.3
6.4
7
7.1
7.2
7.3
7.4
8
8.5
8.6
9
10

SMU

Chapter Name
Introduction
Project Profile
Project Introduction
Company Introduction
Company Profile
Environment Description
H/W & S/W Requirements
Technology used
Existing System
Introduction To Existing system
Drawback of Existing System
Proposed system
Scope
Constraints
Expected Advantages
System Planning
Requirement Specification
Feasibility Study
Life Cycle Model
Effort Distribution Diagram
Task Dependency Diagram
Timeline Chart
System Model Architecture
Use Case Diagram
Sequence Diagram
Activity Diagram
CRC Diagram
System Design
Navigation Map
Table Relationship Diagram
Table Structure
Screen Layout
Software Testing
Testing Introduction
Test Case
Limitation and system Enhancement
References

Page 2

Page No
2
3
4
5
7
8
16
17
19
21
22
23
25
29
32
33
34
37
40
42
51
53
56
57
65
80
83
88
90

Emedical

SMU

Page 3

Emedical

1. INTRODUCTION

1.1 PROJECT SUMMARY

E - Medical Consultancy is web based application. The main aim of project is to manage the
hospital activities such as appointment, patient, medicine, clinical indoor management,
reports of the patient and all etc. It is useful for all the hospitals.
Our project E - Medical Consultancy maintain entire details about doctors, patient, visitor and
manage various functionality such as manage appointments ,searching various data, managing
reports, handling patients histories and allocation of bad and rooms. Our web application has
the facility to give a unique id for every patient and stores the details of every patient and the
staff automatically. It includes a search facility to know the current status of each room and
bed. User can search availability of a doctor and the details of a patient using the id.
1.2 PURPOSE
The main objective of E - Medical Consultancy is to maintain the information about the
patient. It also provides all data in the record manner. In this system we take all the
information about the doctor by just registering/login in the system.
The E - Medical Consultancy web application can be entered using a username and password.
It is accessible either by an administrator or receptionist. Only they can add data into the
database. The data can be retrieved easily. The interface is very user-friendly. The data are
well protected for personal use and makes the data processing very fast.
1.3 SCOPE
System can do:
E - Medical Consultancy is used to search all patientslist by simply fetch the data from the
patient database.It also gives the doctor history to only the authorized person who can access
the doctor data, but doctor list can be seen by any user.
Admin:
Admin is the key user of this web application. All the clinical management is done by the
admin. Admin can edit, delete, update, add patient and doctor data. Admin also provide
authentication to corresponding user.

SMU

Page 4

Emedical

Global Information:
E - Medical Consultancy can provide all the information which issearched by the user in the
application. And user gets the whole information from the system.

User Friendly:
User can easily get the information which they want and can easily use E - Medical Consultancy.
They should be able to understand the clinical information. The E - Medical Consultancy
must be able to guide user properly.

System cannot do:

User which are not registered; they cannot use the clinical service of the application but only
see and view list of doctor and patient review only

1.4 TECHNOLOGY AND LITERATURE REVIEW

The Existence of Multiple Independent Technologies is developed in past that serves the
different facilities but all Technologies were different independent and Separate. And in past it
only work with 32-bit O.S. but in this version it also supported in 64-bit O.S..
Front End Technology: PHP
Back End Technology: MySql
DEVELOPING TOOLS: DreamViewer

SMU

Page 5

Emedical

Front End: PHP

PHP is a server-side web application frame work designed for web development to produce
dynamic web pages.
It was developed by Microsoft to allow programmers to build dynamic website, web
applications and web services.
It was first released in January 2002 with version 1.0 of the .NET Framework, and is the
successor to Microsoft's Active Server Pages (ASP) technology.
PHP is built on the Common Language Runtime (CLR), allowing programmers to write PHP
code using any supported .NET language. IT is a combination of several languages is uses like
c#, j#, c, c++,etc. language.
The PHP SOAP extension framework allows PHP components to process SOAP messages.
After four years of development, and a series of beta releases in 2000 and 2001, PHP 1.0 was
released on January 5, 2002 as part of version 1.0 of the .NET Framework.
Even prior to the release, dozens of books had been written about PHP, and Microsoft
promoted it heavily as part of its platform for Web services. Scott Guthrie became the product
unit manager for PHP, and development continued apace, with version 1.1 being released on
April 24, 2003 as a part of Windows Server 2003. This release focused on improving PHP's
support for mobile devices.
PHP Framework is also support MVC architecture. The PHP MVC Framework is an open
source web application framework that implements the model-view-controller (MVC) pattern.
Based on PHP, PHP MVC allows software developers to build a web application as a
composition of three roles: Model, View and Controller.

A model represents the state of a particular aspect of the application. A controller handles
interactions and updates the model to reflect a change in state of the application, and then
passes information to the view. A view accepts necessary information from the controller and
renders a user interface to display that information.

SMU

Page 6

Emedical

In April 2009, the PHP MVC source code was released under the Microsoft Public
License (MS-PL).
PHP MVC framework is a lightweight, highly testable presentation framework that is
integrated with existing PHP features. Some of these integrated features are master pages and
membership-based authentication. The MVC framework is defined in the System.Web.Mvc
assembly.
The PHP MVC Framework couples the models, views, and controllers using Interface-based
contracts, thereby allowing each component to be easily tested independently.

Apache License 2.0 release

In March 2012, Scott Guthrie announced on his blog that Microsoft had released part of their
web stack (including PHP MVC, Razor and Web API) under an open source license (Apache
License 2.0).
Guthrie wrote that "Doing so will enable a more open development model where everyone in
the community will be able to engage and provide feedback on code checkins, bug-fixes, new
feature development, and build and test the products on a daily basis using the most up-todate version of the source code and test..
The source code now resides on CodePlex. PHP Web Forms was not included in this initiative
for various reasons.

Back End: SQL SERVER

Microsoft SQL Server is a relational database management system developed by Microsoft.
As a database, it is a software product whose primary function is to store and retrieve data as
requested by other software applications, be it those on the same computer or those running

SMU

Page 7

Emedical

on another computer across a network (including the Internet). There are at least a dozen
different editions of Microsoft SQL Server aimed at different audiences and for different
workloads (ranging from small applications that store and retrieve data on the same computer,
to millions of users and computers that access huge amounts of data from the Internet at the
same time). Its primary query languages are T-SQL and ANSI SQL.
Prior to version 7.0 the code base for MS SQL Server was sold by Sybase SQL to Microsoft,
and was Microsoft's entry to the enterprise-level database market, competing against Oracle,
IBM and, later, Sybase. Microsoft, Sybase and Ashton-Tate originally worked together to
create and market the first version named SQL Server 1.0 for OS/2 (about 1989) which was
essentially the same as Sybase SQL Server 3.0 on Unix, VMS, etc. Microsoft SQL Server 4.2
was shipped around 1992 (available bundled with IBM OS/2 version 1.3). Later Microsoft
SQL Server 4.21 for Windows NT was released at the same time as Windows NT 3.1.
Microsoft SQL Server v6.0 was the first version designed for NT, and did not include any
direction from Sybase.
About the time Windows NT was released in July 1993, Sybase and Microsoft parted ways
and each pursued its own design and marketing schemes. Microsoft negotiated exclusive
rights to all versions of SQL Server written for Microsoft operating systems. (In 1996 Sybase
changed the name of its product to Adaptive Server Enterprise to avoid confusion with
Microsoft SQL Server.) Until 1994, Microsoft's SQL Server carried three Sybase copyright
notices as an indication of its origin.
SQL Server 7.0 and SQL Server 2000 included modifications and extensions to the Sybase
code base, adding support for the IA-64 architecture. By SQL Server 2005 the legacy Sybase
code had been completely rewritten.

Since the release of SQL Server 2000, advances have been made in performance, the client
IDE tools, and several complementary systems that are packaged with SQL Server 2005.
These include:

An extract-transform-load(ETL) tool (SQL Server Integration Services or SSIS)

A Reporting Server

SMU

Page 8

Emedical

An OLAP and data mining server (Analysis Services)

Several messaging technologies, specifically Service Broker and Notification

Services

SQL Server 2005

SQL Server 2005 (formerly codenamed "Yukon") released in October 2005. It included
native support for managing XML data, in addition to relational data.
SQL Server 2008
SQL Server 2008 (formerly codenamed "Katmai") was released on August 6, 2008 and aims
to make data management self-tuning, self-organizing, and self-maintaining with the
development of SQL Server Always On technologies, to provide near-zero downtime. SQL
Server 2008 also includes support for structured and semi-structured data, including digital
media formats for pictures, audio, video and other multimedia data.
SQL Server 2012
At the 2011 Professional Association for SQL Server (PASS) summit on October 11,
Microsoft announced that the next major version of SQL Server (codenamed "Denali"), would
be SQL Server 2012. It was released to manufacturing on March 6, 2012. SQL Server 2012
Service Pack 1 was released to manufacturing on November 9, 2012.
It was announced to be the last version to natively support OLEDB and instead to prefer
ODBC for native connectivity.
SQL Server 2014
SQL Server 2014 promises a new in-memory capability for tables that can fit entirely in
memory (also known as Hekaton). Whilst small tables may be entirely resident in memory in
all versions of SQL Server, they also may reside on disk, so work is involved in reserving
ram, writing evicted pages to disk, loading new pages from disk, locking the pages in ram
while they are being operated on, and may other tasks. By treating a table as guaranteed to be
entirely resident in memory much of the 'plumbing' of disk-based databases can be avoided.

DEVELOPING TOOLS: MICROSOFT VISUAL STUDIO 2010

SMU

Page 9

Emedical

Microsoft Visual Studio is an integrated development environment(IDE) from Microsoft. It

is used to develop console and graphical user interface applications along with Windows
Forms or WPF applications, web sites, web applications, and web services in both native code
together with managed code for all platforms supported by Microsoft Windows, Windows
Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft
Silverlight.

Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The
integrated debugger works both as a source-level debugger and a machine-level debugger.
Other built-in tools include a forms designer for building GUI applications, web designer,
class designer, and database schema designer. It accepts plug-ins that enhance the
functionality at almost every levelincluding adding support for source-control systems (like
Subversion and Visual SourceSafe) and adding new toolsets like editors and visual designers
for domain-specific languages or toolsets for other aspects of the software development
lifecycle (like the Team Foundation Server client: Team Explorer).

SMU

Page 10

Emedical

Visual Studio supports different programming languages by means of language services,

which allow the code editor and debugger to support (to varying degrees) nearly any
programming language, provided a language-specific service exists. Built-in languages
include C/C++ (via Visual C++), VB.NET (via Visual Basic .NET), c# (via Visual C#),
and F# . Support for other languages such as M, Python, and Ruby among others is available
via language services installed separately. It also supports XML/XSLT, HTML/XHTML,
JavaScript and CSS. Individual language-specific versions of Visual Studio also exist which
provide more limited language services to the user: Microsoft Visual Basic, Visual J#, Visual
C#, and Visual C++.
Microsoft provides "Express" editions of its Visual Studio at no cost. Commercial versions of
Visual Studio along with select past version are available for free to students via Microsoft's
Dream Spark program.

SMU

Page 11

Emedical

2. FEASIBILITY REPORT:

It is used to check whether the system is feasible or not, various issues such as technology, cost, time
etc. are to be considered. The project continues only after feasibility study completes successfully.
The project is feasible or not is determine by considering:
1.
2.
3.
4.
5.
6.
7.
8.

Economic feasibility
Technical feasibility
Operational feasibility
Schedule Feasibility
Social Feasibility
Management Feasibility
Legal Feasibility
Time Feasibility
Feasibility study is management oriented activity

1. ECONOMICAL FEASIBLITY:
When assessing the economic feasibility of an implementation alternative the basic question that you
are trying to answer is "does the project make financial sense?" You do this by performing a cost
benefit analysis, which compares the real costs of the application to its real financial benefits. The
alternatives should be evaluated on the basis of their contribution to net cash flow, the amount by
which the benefits exceed the costs, because the primary objective of all investments is to improve
overall organizational performance.
The study should consider the project from two complementing points of view:

Quantitative Cost / Benefit Analysis

A quantitative cost benefit comparison expresses all costs and benefits in monetary terms, compares
costs and benefits by summarizing the ratio of benefits to costs.
Qualitative Cost/Benefits Analysis
The qualitative cost benefit analysis identifies areas for improvement that cannot easily be defined in
monetary terms, such as company image and employee satisfaction. If there is a strong business case
after the cost benefits analysis, the tactical benefits will provide you with a good return on investment
and the strategic benefits can be regarded as a very valuable bonus that should make a compelling
case for investment.
On Economical point of view our project is somehow costly.

SMU

Page 12

Emedical

2. TECHNICAL FEASIBILITY:
In technical feasibility the following issues are taken in to consideration:
Manpower-Programmer
Tester & Debuggers
Software & Hardware
Once it established, it is important to consider the monetary factors also. Technical feasibility is
carried out to determine whether the company has capability, in terms of software, hardware,
personnel, & expertise to handle the completion of project. Also it is based upon current technology,
technology exists or not, available within given resources constraint.
On technical point of view project is technically feasible.
3. OPERATIONAL FEASIBILITY:
Operational feasibility refers to put system in to operation stage. Project should be easy to operate and
interface should be easy to understand.
If interface is difficult to understand than it may possible mistakes takes place. If interface is easy than
with minor training of 2 to 3 days helps staff to use project easily.
While selecting personnel for training, proper care should be taken. Profile and experience of staff
should be taken into consideration with this responsible staff should be invited for training so that
proper training cab be given to every department.
4. SCHEDULE FEASIBILITY:
Schedule feasibility refers to proper installation of project on time. Software should implement and
testing should be done on time without delay. If project is not install on time than importance of
project may not be found.
This may adversely affect the progress of company.

5. SOCIAL FEASIBILITY
Because of better operational accuracy, speed of automate calculation and improved
benefits with improved service level benefits, its easily acceptable by people.
6. MANAGEMENT FEASIBILITY

SMU

Page 13

information

Emedical

First of the entire request proposal was shown to the Management and then after they agreed on
primary proposed project; so we can say that Management is ready to accept the project.
7. LEGAL FEASIBILITY
Proposed project does not infringe on known Acts, Statues, as well as any pending legislations.
8. TIME FEASIBILITY
Proposed project can be implemented within the time frame defined by management. If any
undesired and unexpected event occurs then it may not be possible within time frame.
9. FINAL CONCLUSION OF FEASIBILITY STUDY

Finally, from whole study we can conclude that system is technically feasible. Initially, if we
see, the initial cost is high but by studying economical feasibility with improved level
services, customer may attract towards the HOSPITAL MANAGEMANT SYSTEM and
ultimately which is the aim of E-MEDICAL CONSULATANCY other feasibility aspects are
satisfied, considering certain risky factor, which are always present in any proposed system
project.

After completing the study of feasibility I kindly described the whole study and presented the
report of study and presented to my guide Mr. SOURAV DAS discussed about dates to start
the real specification of system and the designing days and further details and we discussed
roughly about model of actual software system how it could take place and etc.

After that I was very happy because my imagination had got green signal from the above
Feasibility study.

3. SOFTWARE ENGINEERING PARADIGM APPLIED

1. Introduction to Software
Lets first define the term software. Computer software is the product that software
engineers design and build. It encompasses programs that execute within a computer of any size and
architecture, documents that encompass hard copy and virtual forms, and data that combine Varchars
and text but also includes representation of pictorial, video, and audio information.

Software Engineer builds it, and virtually everyone in the industrialized world uses it either
directly or indirectly.

SMU

Page 14

Emedical

Because it affects nearly every aspect of our lives and has become pervasive in our
commerce, our culture, and our everyday activities.

We build computer software like we build any successful product, by applying a process that
leads to a high quality result that meets the needs of the people who will use the product.

We apply a software engineering approach.

From the point of view of a software engineer; the work product is the programs, documents,
and data that are computer software.

But from the users point of view, the work product is the resultant information that somehow
makes the users world, User privileges better.

Software Applications

System software: System software is a collection of programs written to service other

program, e.g. COMPLIER, EDITORS, AND FILE MANAGEMENT UTILITIES, OS
COMPONENTS, DRIVERS, etc.

Real-Time software: Software that monitors/analyzes/controls real-world events as they

occur is called real time. Elements of real-time software include a data gathering component
that collects and formats information from an external environment, an analysis component
that transforms information as required by the application, a control/output component that
responds to the external environment and a monitoring component that coordinates all other
components so that real response can be maintained

SMU

Page 15

Emedical

Business software: Business information processing is the largest single software application
area. Discrete systems (e.g. PAYROLL, ACCOUNTS RECEIVABLE/PAYABLE,
INVENTORY, SMBS)

Engineering and scientific software: Engineering and scientific software have been
characterized by Varchar crunching algorithms. Application range from astronomy to
vocanology, from automotive stress analysis to space shuttle orbital dynamics, and from
molecular biology to automated manufacturing.

Embedded software: Intelligent products have become commonplace in nearly every

consumer and industrial market. Embedded software resides in read-only memory and is used
to control products and systems for the consumer and industrial markets, e.g. keypad control
for a microwave oven, so we can say that they can perform very limited and esoteric
INOXctions.

Personal computer software: The personal computer software market has burgeoned over
the past two decades. Word processing, spreadsheets, computer graphics, multimedia,
entertainment, personal and business financial applications, external network, and database
access are only a few of hundreds of applications.

Web-based software: The web pages retrieved by a browser are software incorporates
executable instructions (e.g. CGI, HTML, PERL, JAVA, ASP), and data (e.g. hypertext and a
variety of visual and audio formats)

Artificial intelligence software: Artificial intelligence (AI) software makes use of nonnumerical algorithms to solve complex problems that are not amenable to computation or
straightforward analysis. Expert systems, pattern recognition (image and voice), artificial
neural networks, theorem proving, and game playing are representatives of applications
within this category.

This proposed project could be put in the category of BUSINESS APPLICATION

SOFTWARE.

SMU

Page 16

Emedical

2. SOFTWARE DEVELOPMENT LIFE CYCLE

In any project, the development process revolves around a life cycle that begins with the
recognition of user needs.

The key stages of the cycle are an evaluation of the present system, information gathering, a
cost/benefit analysis, a detailed design, and the implementation of the project.

The life cycle is not a procedure that deals with hardware and software. Instead, it deals with
building computer-based systems to help the users to operate a business or make decisions
effectively and manage an enterprise successfully.

The System Development Life Cycle (SDLC) encompasses all the activities required to
define, develop, test, deliver, operate, and maintain a software system. Different models
emphasize the different aspects of the Life Cycle and no single Life-Cycle model is
appropriate for all the software systems.

It is important to define various activities required to develop and maintain a software system.

A Life Cycle model is that which gives understandability to manageability, resource

allocation, cost control, and system quality.

The process of building, delivering, and evolving a software system from the inception of an
idea to the delivery and final retirement of the system is called a Software Production Process.

The Software Production Process may follow different methods of software development.
Three frequently used Software Production Process models are:
o

The Spiral Model or Phased Model or Linear Sequential Model.

The Evolutionary Model or Prototyping Model.

The Spiral Model.

I explained them that our whole project is very big and to complete the first phase
very successfully we have to study the SDLC of our system.

Here, I have used THE SPIRAL MODEL to describe the whole Software
Development Life Cycle.

SMU

Page 17

Emedical

3. MEANING OF SPIRAL MODEL

The spiral model, also known as the spiral lifecycle model, is a systems development lifecycle
(SDLC) model used in information technology (IT). This model of development combines the
features of the prototyping model and the waterfall model. The spiral model is favored for large,
expensive, and complicated projects.
This model can be considered as the model, which combines the strengths of various other models.
Conventional software development processes do not take uncertainties into account. Important
software projects have failed because of unforeseen risks. The other models view the software process
as a linear activity whereas this model considers it as a spiral process. This is made by representing
the iterative development cycle as an expanding spiral.

The following are the primary activities in this model :-

Finalizing Objective: The objectives are set for the particular phase of the project.

Risk Analysis: The risks are identified to the extent possible. They are analyzed
and necessary steps are taken.

Development: Based on the risks that are identified, an SDLC model is selected
and is followed.

Planning: At this point, the work done till this time is reviewed. Based on the
review, a decision regarding whether to go through the loop of spiral again or not
will be decide. If there is need to go, then planning is done accordingly.

Advantages:
Following are the advantages of Spiral Model.

Emphasis on alternatives and constraints supports the reuse of existing solutions.

Targets testing by treating it as a risk, which has to be addressed.

Maintenance is just another phase of the spiral model. It is treated in the same way as
development.

Estimates (budget and schedule) get more realistic as work progresses, because important
issues are discovered earlier.

It is more able to cope with the (nearly inevitable) changes that

generally entails.

SMU

Page 18

software development

Emedical

Software engineers, who can get restless with protracted design processes, can get their hands
in and start working on a project earlier.

Disadvantages:
Following are the disadvantages of Spiral Model.

Only intended for internal projects (inside a company), because risk is assessed as the project
is developed. Hardly suitable for contractual software development.

In case of contractual software development, all risk analysis must be performed by both
client and developers before the contract is signed and not as in the spiral model.

Spiral model is risk driven. Therefore it requires knowledgeable staff.

Suitable for only large scale software development. Does not make sense if the cost of risk analysis is
a major part of the overall project cost.

In the spiral model, these phases are followed iteratively.Figure1.1 depicts the Boehms Spiral Model
(IEEE, 1988).

SMU

Page 19

Emedical

3. System Requirement Study

3.1 User Characteristics

SMU

Page 20

Emedical

User:
User can create their account free and use only visit facilities provided by clinical system.
This application has different facilities as follow:

Creating user profile

Find doctor

Search doctor according to diseases.

Check entire information of management.

Askingqueries about appointment, timing etc.

Give e-mail or contact no.

Take appointment from doctor.

Get latest updates from the system via email on selected criteria.

Registered user:
Register user can use all services provided to visitor user and have also following services:

SMU

Take appointment from doctor.

Change appointment if doctor give permission.

Give previous report to the doctor.

Take emergency appointment.

Page 21

Emedical

Admin:
Admin manages user& registered user profile. Admin is responsible for managing this site or
supporting the system to be worked. Admin also manages fallowing:

Manage & Update Application

Manage Registered User

Update Doctor schedule

Update patient report.

Manage all appointment of doctor through schedule.

Solve problem of patient & doctor.

Manage clinical system.

3.2 Hardware and Software Requirement

NOTE: These requirements of system are minimum. So to run this application on system this is
minimum required to execute application efficiently.
Software Requirements:

Application Software

: Browser (Mozilla Firefox, Internet Explorer, Google

Chrome etc.)

Operating System

: Window 2007,Window XP.

Table 2.2.1: Software Requirement

SMU

Page 22

Emedical

Hardware Requirements:

Graphic Card

256 MB

Processer

Pentium and above.

[Ram]

512 MB

[Hard disk]

40 GB

Minimum Memory Required

Table 2.2.2: Hardware Requirement

3.3 Constraints
3.3.1 Regulatory Polices
It is a document that describes philosophy, principles and fundamental factors used by the
system in its regulatory program. Regulatory documents are policies, standards, guides,
notices, procedures and information documents supports and provide information on legally
enforceable instruments. These documents do not create those instruments.
3.3.2

Hardware Limitation

System integration, the process of putting hardware, software and people related to the system
together for making a system. It is done incrementally so that sub systems (modules) area
integrated one at a time.
Interface problem between sub system and actual system usually found at the stage of
integration which causes the hardware limitation.
Problems of uncoordinated system components also lead to a hardware limitation.

SMU

Page 23

Emedical

3.3.3 Interface to other Applications

This constraint describes the applications relationship to other systems. For example,
Does the application is independent?
This application does integrate different to provide some of the user friendly functions.
Is it a component of larger application?
Not really but it is a large application which include other application into single
system which designs the best site for travelling world.
Is it replacement of another system?
No it does not replace any system.
3.3.4

Parallel Operations

This system is parallel processing so, system is parallel to update existing user profile and all
effects will be shown. E.g. If user delete a profile from this system then the stored personal
information, Queries, Favorite destinations will also deleted from the system database where
it is actually stored.
3.3.5

Higher Order Language Requirement

In my service I have used PHP as higher order language. It uses 3-tier architecture which
follows pure MVC structure for implementation or maintenance.
3.3.6

Reliability Requirements

These requirements means to specify the numerical reliability targets for the application based
on system level reliability targets and known reliability of other components.
User is ensured that the system would be reliable at the time of Power Failure.

3.3.7

SMU

Criticality of the Application

Page 24

Emedical

The main criticality of this system is if the server goes down then this system wont work. Or
else in case of traffic increasing the server would not able to control the traffic system goes
down.
3.3.8

Safety Security Consideration

The system is providing basic security to users profile. All users profiles are secure by
password mechanism. Unauthorized user cannot login to this system.
3.3.9

Assumption And Dependencies

The system will be using E-MAIL API, MAP API for notifying users which is another system
and assume that it will be working properly.

SMU

Page 25

Emedical

Assumption and Constraint

The Assumptions of the Project are:

The staff of the project is consisting of two (2) people. Project Leader will work
(2hours) a week and other person will work forty two (42) hours a week.

The programming language PHP and SQL server is decided for the project.
However, according to the customers demand it can be changed.

The Constraints of the Project are:

The schedule of the project is predefined by the customer.

Since user are from within the training institute, the E-MEDICALCONSULTANCY will be
Client-server but platform independent.
The project is being developed as part of the training project for Master in Computer
Application.
The software development processes and any kind of documentation will be in
compliance with the IEEE Standards [1, 2,3and4].
Functions of Project :
According to initial meetings done with customers, the users of the EMEDICAL CONSULTANCY consists of system groups. These are users and
administrator (this will be referred as root from now on).

The function root:

Define users on the E-MEDICAL CONSULTANCY

Assign each user a unique user-id

Assign each user a password
The function of administrator:
Use the user control function
The function of customer:
Use the registration, giving order, checking etc.
The Function of Employee:
Use for employee management.

SMU

Page 26

Emedical

Project deliverables

Initial Plan: The document will be prepare and submitted to Client-mail address until Nov 15 th,
2013.
SRS: The document will be prepared and submitted to Client-mail address until Nov 28 th, 2013.
SPMP: The document will be prepared and submitted to BIT BARODA.com address until Feb
10th, 2014.
SDD: The document will be prepared and submitted to BIT BARODA.com address until Feb
25th, 2014.
Delivery of Product: The product will be delivered on March 25 th,2014.
User Manual: The document will be prepared by March 28 th,2014.
Demonstration of Product: The demonstration of the product will be done on March 30 th, 2014.
Delivery of Final Product: The final product will include the software, the software source code
and the user manuals. The delivery will be on March 30th, 2014.

Schedule and Budget Summary

Date Due

Document/Activity Name

15th Nov2013

Initial Plan

28thNov2013

SRS

10th DEC 2013

SPMP

28th DEC 2013

SDD
Table 1- Schedule of the Project

As explained in Subclass 1.1.2,no real budget is associated with BIT NETWORK [SOCIAL
NETWOKING].For hardware and software needs, existing resource of Bit & own resources of student
will be used.

Evaluate of Plan
This is the initial version of the software project management plan.
Due Date

Document

Status

15th Nov2013

Initial Plan

Created

28thNov2013

SRS

Created

10th DEC 2013

SPMP

Created

REFERENCES

SMU

Page 27

Emedical

[1]IEEE STD 1128-1998, IEEE standard for management plans

[2] IEEE STD 830-1998. IEEE recommended practice for software requirements specifications
[3] IEEE STD 1066-1998, IEEE recommended practice for software design descriptions
[4] IEEE STD 1111-1987, IEEE standard software user documentation.
[5] Sommerville, Ian , software engineering, sixth edition , pearson education, 2006.
[6] Wrox publication
[7]Black book

DEFINITION & Abbreviations

IEEE: Institute of Electrical & Electronics Engineering
BIT INFOTECH: will be referred to software development team.
PC: Personal Computer
SRS: Software requirement Specification
Admin: The administrator is a person who has privileges to control server as well as
responsibilities to manage the running system.
Member: The user who is signed up before.
Project Deliverable: A work product to be delivered to the acquirer. Quantities, delivery dates,
and delivery location are specifying in a project agreement.
User: refers to people who will see the routes.
User Id: A set of characters that identifies the user.
The Acquiring Organization: Is the organization that will receive the final product.
The Quality control Manager: is responsible from controlling the product whether it satisfies
the customers demand and provide consultancy in this project quality control manager refers to
Mss. Mr. Jagdish Shah.
Work Product: Any tangible item produced during the process of developing or modifying
software.
Sign-up: refer to recording user information to the system at first time to have a chance to use
the system.
Software Project: is the set of work activities both technical and management requirement to
satisfy the terms and conditions of a project agreement.
Contract: A legally binding document agreed upon by the customer and the supplier. This
includes the technical and organizational requirements, and schedule for a product.
Customer: The person or persons who pay for the product and usually[but not necessarily]
decide the requirements. In the context of thisrecommended practice the customer and the
supplier may be members of same organization.
User Interface: The interface that the user will see while using online.
SPMP: Software Project Management Plan. The controlling document for managing the
software project.

PROJECT ORGANIZATION
External Interface
BIT INFOTECH
|
Mr. SOURAV DAS

SMU

Page 28

Emedical

Figure 1: External interface ofEMEDICAL CONSULTANCY

List Responsible People to contact:

The quality control manager: BIT INFOTECH Trainer ( Mr. Sourav Das)

Internal Structure
The project responsibilities and authority line are separated among Bit Infotech. Thus, the project is a
matrix organization. The internal structure of the project is given bellow:

Project
Leader
Requiremen
Desig
Codin
t Analysis
n
g
Team
Team
Figure 2: The Internal Structure
of the Project Developing
Team Organization

Documentatio
n Team

Role and Responsibilities

External Entities:
Acquiring Organization: It is the person who defines the requirements for the project both
approves and accepts the product deliverable and final product.

Quality Control Manager: It is the person who carries out the quality assurance of the project.
Therefore, manager is responsible from the preparation of review report for the project
documentation.

Internal Entities:

SMU

Page 29

Emedical

Name

E-maile address

Role

Mr. Sourav Das

[email protected]

Project manager
System analyst & designer
Customer relations representative

Table 3: Roles and Responsibilities of BIT

The risk management process is comprised four parts:
Table 13: Details of Software Process

Methods, tools and techniques that shall be for the E-MEDICAL CONSULTANCYsite
project are explained below.

Software process model: Waterfall model

Software programming language: Php
Software design methodology: Object-oriented analysis & design technique
Software documentation: Open office 3.1, planner v0.14.4
To store and retrieve the user and customer information: Progress-SQL
Slander for software requirement specification documentation: IEEE std. 1830-1998[2]
Slander for software project management plan documentation: IEEE std. 1128-1998[1]
Slander for software designing description documentation: IEEE std. 1066-1998[3]
Slander for user manual development: IEEE std. 1830-1998[4]
Infrastructure plan
There is no interface between the SN evaluation system and the hardware on which it shall
operate. So, the hardware configuration specified below shall not be taken either as a hardware
interface of the SN or as a minimum requirement configuration. The hardware configuration
specified below indicates resources, which are already available to BIT INFOTECH and which
shall be allocated to the SN.
Develop software. Planner shall be use be used as project management software. Microsoft
window must be installed Flash player for the operating systems.
The development environment for the SN is represented below. The specified infrastructure is
already available and shall be provided to each individual, who is allocated to the SN project in
the Sntech.

Hardware Configuration

A microprocessor having 866 MHZ clock speed

128 MB RAM
10 GB total hard disk space
8 MB graphics card memory
A network interface card supporting 100 MBPs connections

Operating System

SMU

Window 7

Page 30

Emedical

Network Connection

100 MBPs network connection

Software Configuration

PHP standard Edition visual studio 2004 Microsystems

SQL Server
Firefox v3.6
Progress-SQL
Table 14: Details of Infrastructure Plan

Product Acceptance Plan:

The acquirer acceptance of the delivered work products generated shall be as follows:

Any deliverable work product shall satisfy 100% of the requirement specified in the software
requirements specification, where each requirement specification shall be weighted equally.
If it is proven that a work product delivered to the customer within its schedule time period
satisfies more than 90% of the requirements, BIT INFOTECH shall be give an additional one
week time to modify the work product.
If it is proven that a work product delivered to the customer within its scheduled time period
satisfies less than 90% of the requirements, BIT INFOTECH shall pay RS100 for each working
day passed to the delivery of the modified version, satisfying 100% of the requirements
specification in the software requirements specification.

Supporting Process Plans

Configuration Management Plan

All the project deliverables are to be considered as configuration items. The configuration item
as 1.1,2.1..Documentation files will be in open office v3.1 format and project plan schedule
files will be in planner v0.14.4 format.

Verification and Validation Plan

The details of the verification and validation plan shall be done by testing activities and they are
depicted in Table 15. Testing of the SN site shall be done by the BIT INFOTECH testing team.
However the programmer and the testing engineer shall not be the same person.

The testing activities shall be composed of the verification of the correctness of the requirement
specified in the software requirement specification of the SN site. No special method will be used by
San tech members will do testing activities since there is not enough time to do so.

SMU

Page 31

Emedical

Table 15: Details of verification and validation plan

Documentation plan
The IEEE standards would be followed for all documentation purposes. All the documents
would be discussed with BIT before their baseline versions are issued and distributed.
Moreover before submitting the major milestones, a meeting will be done with customer .All
the documentation plans will be prepared by Sahishna Nair.

QUALITY ASSURANCE PLAN

Verification, validation, reviews and configuration management are the methods that using for
quality assurance. Design team is responsible for both verification and validation. Work
products are ensured right and align with the requirements set in SRS after internal reviews and
review meeting with BIT INFOTECH.

Review plan
N/A

Problem Resolution Plan

Scheduled problems which arise from the deviations of the actual planning will be solve and updated
by the project manager. The project manager will reassign the team members to the work activities in
order to resolve the scheduled problems. Technical problems will be solved by the BIT INFOTECH
group members. The member, who identified the problem in the BIT INFOTECH group, will
communicate to the other group members.

SMU

Page 32

Emedical

5. SYSTEM ANALYSIS
5.1 STUDY OF THE CURRENT SYSTEM
In current scenario, all doctor leaves are recorded manually, that is using paper .When a doctor
has to take a leave, he has to write an application. That application is forwarded to admin head
and then the leave is granted.
Due to their job there was an urgent need to make an application called as E-Medical
Consultancy which would increase the efficiency of the system.
The E-Medical Consultancy is an Intranet based web application that can be accessed
throughout the admin or a doctor/patient. The main objective of this project is to give
information of all doctors according to diseases.
This application can be used to find doctor according to disease. There are features like email
notifications, cancellation of appointment, approval of appointment, report generators etc. in
this system.
5.2 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM
i.
ii.

Required internet connection for appointment.

It runs only on 32-bit operating system.

5.3 REQUIREMENTS OF NEW SYSTEM

To solve the problems of the current system, the proposed system had its focus mainly on the
computerization of the existing manual system, which will also suffice the expectations and
eliminate the problems of the existing system.

Computerized system:As an Expected outcome we will get a smart and fast Computerize soft
clinical system with which any doctor can access anywhere and anytime within a few seconds.
Fast information access: if a doctor has to check his/her hospital job time then, it can be
checked easily using World Wide Web.

No paper work: In this process the doctor see status from the system,he/she does not have to
worry about any paper application.
Notification via email: If doctor/patient appointment has been approved then he/she will be
notified via an email.

SMU

Page 33

Emedical

Appointment report generation: If any long time disease patient come then the report of the
total number of patient who have long time disease, then report will be produced in PDF format.
Then the user can take a print of it if needed.
Faster information access: All doctor/patient information will be stored in the system itself.
Therefore doctor/patient can edit, update, and delete his information if required.
Faster communication:since soft clinical system is an intranet based application, therefore,
communication between the doctor and the patient will be faster.
5.4 FEASIBILITY STUDY
A feasibility study is undertaken to determine the possibility or probability of either improving
the existing system or developing a completely new system. It helps to obtain an overview of the
problem and to get rough assessment of whether feasible solution exists.
Need for Feasibility Study:

The feasibility study is needed to:

Define the problems and objective involved in a project.
Improve the existing system.
Determine the potential of the existing system.
Give Answer of the question whether a new system is to be installed or not?
Avoid costly repairs at a later stage when the system is implemented.
Avoid the Hardware Approach i.e. getting a computer first and then decide how to use it
Know what should be embedded in the new system.
There are three aspects in feasibility study portion of the preliminary investigation.

(1)
(2)
(3)

Technical feasibility.
Schedule feasibility and
Implementation feasibility of the project.

1) Technical Feasibility:
We are going to be implemented our system in PHP. Technical feasibility studies is the study of
the hardware and software requirements i.e. technical requirement of the system on order to
inform admin and user that for particular system designing this much technical are required. In
order to know the users and admin views regarding the technical resource
the software requirements are needed. We have defined all software requirements in project
profile.
After an initial feasibility study, and scanning through some of the resources and study material
available on the Internet, I gained confidence that even this part was technically feasible, and will
not present any serious obstacles to the realization of the project.

SMU

Page 34

Emedical

2) Schedule Feasibility:
The important thing to be considered in making this project is the time duration and the time
required for making this project is 10 months.
I have enough time to complete and understand the System. I have divided the work evenly
according to the months and it will provide more time to finish the work as the work load reduces.
That means our System seams to be feasible with Time. All the issues arising during the making
of the software would be solved and encountered with the help of the faculties and some external
guide.
3) Implementation Feasibility:
We are going to design our system in Windows Xp or Windows 7 or Windows 8. So all we need is
a computer with Windows Operating System which is supporting Microsoft visual studio. My
software seems to be feasibly implemented.

5. 5 REQUIREMENTS OF VALIDATION
The patient who has taken an appointment must first login into the system if he is a member.
Otherwise he has to first register himself as a new user then login. This is basically done so as to
maintain the security of the system.
The second validation is that if an patient has taken the appointment and later if he wants to
forward this appointment to another patient , then he has perform this task before 24 hours
otherwise his leave will be considered.

5.6 FUNCTIONS OF SYSTEM

5.6.1 USE CASE DIAGRAM
1) DOCTORS USECASE

SMU

Page 35

Emedical

2) PATIENTS USECASE

SMU

Page 36

Emedical

3) ADMINS USECASE

SMU

Page 37

Emedical

E-Medical
Consultancy

SMU

Page 38

Emedical

4) SYSTEMS USECASE

E-Medical
Consultancy

SMU

Page 39

Emedical

5.7 DATA MODELING

5.7.1 E-R DIAGRAMS
Symbols

Meaning
Entity

Relationship

Attribute

Key Attribute

E1

SMU

Cardinality Ratio N: 1 for E1: E2 in R

E2

Page 40

Emedical

E-R Diagram for system:

SMU

Page 41

Emedical

5.7.2 System Activity or Object interaction Diagram

SMU

Page 42

Emedical

5.7.3

DATA DICTIONARY

1) Table Name : Doctor

SR
No.

Field Name

Data
Type

Data
Size

Constraints

Description

1
2

doctor_id
doctor_name

Int
Varchar2

6
30

Primary Key
Not null

Doctornumber
doctor name

Address1

Varchar2

30

Not null

Address of doctor

Address2

Varchar2

30

Not null

Another address of doctor

5
6
7
8

Contact
Email
City
Pincode

15
20
10
10

Not null
Not null
Not null
Not null

Contact number
Email
City
Pin-code of city

Bdate

10

Not null

Birth date

10

Age

Not null

Age of doctor

11

doctor_doj

10

Not null

Date of joining

12

doctor_dol

Varchar2
Varchar2
Varchar2
Varchar2
Date
time
Int
Date
time
Datetime

10

Not null

Date of leaving

13

Des_no

Int

Referencing
table

14

Specialization
id

Varchar2

10

Not null

Doctor specialization

15

User id

Varchar2

20

Foreign key

Login id for doctor id

account

16

Dept_id

Varchar2

20

Foreign key

Dept_id

2) Table Name: login

SMU

Page 43

des_mst

Designation of Doctor

Emedical

Sr NO.
1
2
3
4
5

Field Name
User id
Password
Recovery question
Answer
User type

Data Type
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2

Data size
10
10
50
50
20

Constraints
Primary key
Not null
Null
Not null
Not null

Description
Username of admin
Password of admin
Difficulties of user
Solution of user
Types of user

Data Type
Varchar2
Varchar2

Data Size
20
20

Constraints
Primary key
Not null

Description
Department no
Department name

Data Type
Int
Varchar2
Varchar2

Data Size
6
30
30

Constraints
Description
Primary key
Designation no
Not null
Designation name
Foreign key ofDepartment name
dept_mst

Data Type
Int

Data Size
6

Constraints
Primary key

Description
Registration no

Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2

30
30
50
20
15
10
20
20
5

Not null

Registration date
patient name
Address of patient
City of patient
Contact no of patient

Data Size
6
30
30
50

Constraints
Primary key
Foreign key

3) Table Name: department

Sr No.
1
2

Field Name
Dept_id
Dept_name

4) Table Name: designation

Sr No
1
2
3

Field Name
Des_no
Des_name
Dept_id

5) Table Name: patient_detail

Sr No
1
2
3
4
5
6
7
8
9
10

Field Name
Registration
no
Registration date
name
Address
City
Contact no
Marital status
Gender
User id
Age

Not null
Not null
Not null
Not null
Not null
Foreign key
Not null

Patient user name

6) Table Name: patient_diagnosis

Sr No
1
2
3
4

SMU

Field Name
diagnosis no
Registration no
Diagnosis date
Remark

Data Type
Int
Varchar2
Varchar2
Varchar2

Page 44

Not null

Description
Diagnosis no for patient
Registration no
Date
Describe diagnosis

Emedical

5
6
7
8
9
10
12
13
14

Biochemistry
blood
colonoscopy
gastroscopy
urine
xray
Advise date
Final diagnosis
Ecg

Boolean
Boolean
Boolean
Boolean
Boolean
Boolean
Varchar2
Varchar2
Boolean

20
15
10
20
20
10
30
20
20

null
Null
Null
Null
Null
Null
Null
Not null
Null

Data Type
Int
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2
Varchar2

Data Size
6
30
30
50
20
15
10
20
20
5
20

Constraints
Primary key
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Foreign key
Not null
Null

7) Table Name: Appointment

Sr No
1
2
3
4
5
6
7
8
9
10
11

SMU

Field Name
Appointment no
Appointment date
Name
Address
City
Contact no
Marital status
Gender
User id
Age
App_history

Page 45

Description
Registration no
Registration date
patient name
Address of patient
City of patient
Contact no of patient

Patient user name

History of patient
Appointment

Emedical

5.8 FUNCTIONAL AND BEHAVIORAL MODELING

5.8.1 CONTEXT DIAGRAM

3.8.2 DATA FLOW DIAGRAM

SMU

Page 46

Emedical

DFD: Level 1

SMU

Page 47

Emedical

DFD: Level 2

SMU

Page 48

Emedical

DFD: Level 3

SMU

Page 49

Emedical

5.9 MAIN MODULES OF NEW SYSTEM

Registration module

Clinical module

Appointment scheduler

Indoor management

Reporting module

5.10SELECTION OF HARDWARE AND SOFTWARE

JUSTIFIACTION

Hardware Technology Used:

To run the application software of the system in the computer the minimum configuration required
is as below:

768 MHz Pentium processor or other compatible.

Intel Chipset Motherboard.
256 MB-RAM.
10 GB Hard-Disk.
Monitor. [640 * 60 Display]
Keyboard.
Mouse.
Laser Printer.

Figure 3.11.NET Platform

in it can be manipulated and updated independent of the database. When the use of this

SMU

Page 50

Emedical

Data Provider: The Data Provider is responsible for providing and maintaining the connection to
the database. A Data Provider is a set of related components that work together to provide data in
an efficient and performance driven manner. The .NET Framework currently comes with two Data
Providers:
1. The SQL Data Provider ,
2. The OleDb Data Provider
This allows us to connect to other types of databases like Access and Oracle. Each Data
Provider consists of the following component classes:
TheConnection object which provides a connection to the database
The Command object which is used to execute a command
The Data Reader object which provides a forward-only, read only, connected record set
The Data Adapter object which populates a disconnected Dataset with data and performs update.

SMU

Page 51

Emedical

6. System Design
6.1 DATA STRUCTURE DESIGN
1) Sequence diagram for doctor:

SMU

Page 52

Emedical

2) Sequence diagram for patient:

E-Medical

3) Sequence diagram for admin:

SMU

Page 53

Emedical

4) Sequence diagram for system:

SMU

Page 54

Emedical

6.2 INPUT/OUTPUT AND INTERFACE DESIGN

6.2.1 Access Control and Security

SMU

Page 55

Emedical

List of forms accessed by administrator

1.
2.
3.
4.
5.
6.

Patient request appointment

Patient get appointment
Patient appointment approval
Add Patient appointment
Registration of new patient
Authenticate the patient

List of forms accessed by employee

1.
2.
3.
4.
5.

Patient view approved appointment

Patient view history
Forget password
Update password
Update own detail in patient history

Security In Project:
1) The user has to enter username and password in order to login
2) In case if user has forgotten his password, it can be retrieved using the question which he
had answered during registration (FAQ).

6.2.2 SCREEN SHOTS:

Main Page

SMU

Page 56

Emedical

Description:This page its to search the Doctor....................

SMU

Page 57

Emedical

Patients Viewed Screens:

Login Page

Description:-

SMU

Page 58

Emedical

Registration Page :

Description:This page is used to registration on paitents................

SMU

Page 59

Emedical

Patient Welcome Page :

Description:-

SMU

Page 60

Emedical

Update Patient Details :

Description:-

SMU

Page 61

Emedical

Doctors List :

SMU

Page 62

Emedical

Take Appointment :

SMU

Page 63

Emedical

Change Password :

SMU

Page 64

Emedical

Doctors Page :
Signup Page :

Description: This page shows details.

Registration Page :

SMU

Page 65

Emedical

Description: This page shows patients registration details.

SMU

Page 66

Emedical

Welcome Page :

Description: This page shows main page.

SMU

Page 67

Emedical

Change Password :

Description: Every patients can change password.

SMU

Page 68

Emedical

Patient List :

Description: This page shows patients full details.

SMU

Page 69

Emedical

View Appointment :

Description: This page shows patients appointments details.

SMU

Page 70

Emedical

Patient History :

Description: This page shows patients history list.

SignOut :

SMU

Page 71

Emedical

On clicking on the Login Link, the main page will be displayed again.

SMU

Page 72

Emedical

6.3 CODE EFFICIENCY

Reviewing of Code efficiency for a module is carried out after the module is successfully compiled
and all the syntax errors eliminated. Code efficiency review is extremely cost-effective strategies
for reduction in coding errors in order to produce high quality code. Normally, two types of
efficiency are carried out on the code of a module - code optimization and code inspection. The
procedure and final objective of these two efficiency techniques are very different as discussed
below.
6.4 OPTIMIZATION OF CODE
Code optimization is an informal code analysis technique. In this technique, after a module has been
coded, it is successfully compiled and all syntax errors are eliminated. Some members of the
development team are given the code a few days before the optimization meeting to read and
understand the code. Each member selects some test cases and simulates execution of the code by
hand (i.e. trace execution through each statement and function execution). The main objectives of
the optimization are to discover the algorithmic and logical errors in the code. The members note
down their findings to discuss these in an optimization meeting where the coder of the module is
also present.

Even though a code optimization is an informal analysis technique, several guidelines have evolved
over the years for making this nave technique more effective and useful. Of course, these
guidelines are based on personal experience, common sense, and several subjective factors.
Therefore are based on personal experience, common sense, and several subjective factors.
Therefore, guidelines should be considered as examples rather than as rules to be applied
dogmatically. Some of these guidelines are the following:

The team performing the code optimization should not be either too big or too small. Ideally, it
should consist of three to seven members.

SMU

Page 73

Emedical

7. TESTING
7.1 TestingPhase
One of the purposes of the testing is to validate and verify the system. Verification means checking
the system to ensure that it is doing what the function is supposed to do and Validation means
checking to ensure that system is doing what the user wants it to do.
No program or system design is perfect; communication between the user and the designer is not
always complete or clear, and time is usually short. The result is errors and more errors.
Theoretically, a newly designed system should have all the pieces in working order, but in reality,
each piece works independently. Now is the time to put all the pieces into one system and test it to
determine whether it meets the user's requirements. This is the best chance to detect and correct
errors before the system is implemented. The purpose of system testing is to consider all the likely
variations to which it will be subjected and then push the system to its limits. If we implement the
system without proper testing then it might cause the problems.
1. Communication between the user and the designer.
2. The programmers ability to generate a code that reflects exactly the system specification.
3. The time frame for the design.
Theoretically, a new designed system should have all the pieces in working order, but in reality,
each piece works independently. Now is the time to put all the pieces into one system and test it to
determine whether it meets the requirements of the user.The process of system testing and the steps
taken to validate and prepare a system for final implementation are:

SMU

Page 74

Emedical

7.2 LEVELS OF TESTING:

Different types of testing are as follows:

1. UnitTesting:
Thisisthe smallesttestableunit ofacomputer systemandis normallytested using the white box
testing.Theauthor of theprogramsusually carriesoutunit tests.
2.IntegrationTesting:
In integration testing, the different units of the system are integrated together to form the
complete system and this type of testing checks the system as whole to ensure that it is doing
what is supposed to do. The test in go fan integrated system can be carried out top-down,
bottom-up, or big-bang. Inthistypeof testing, some parts will be tested with white box test in
gandsome with blackbox testing techniques.This type of testing plays very important role in
increasing the systems productivity. We have checked our system by using the integration
testing techniques.

3. SystemTesting:
A part from testing the system to validate the functionality of Software against the requirements,
it is also necessary to test the non-functional aspect of the system. Some examples of nonfunctional tools include tests to check performance, data security, usability/user friendliness,
volume, load/stress that we have used in our project to test the various modules.

SMU

Page 75

Emedical

System testing consists of the following steps:

1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.

4. Field Testing:
This is a special type of testing that may be very important in some projects. Here the system is
tested in the actual operational surroundings. The interface with other systems and the real
world is checked. This type of testing is very rarely used. So far our project is concerned; we
haven't tested our project using the field testing.
5. Acceptance Testing:
After the developer has completed all rounds of testing and he is satisfied with the system, then
the user takes over and re-tests the system from his point of view to judge whether it is
acceptable according to some previously identified criteria. This is almost always a tricky
situation in the project because of the inherent conflict between the developer and the user. In
this project, it is the job of the bookstores to check the system that whether the made system
fulfils the goals or not.

SMU

Page 76

Emedical

8. VERIFICATION AND VALIDATION (V&V)

Theobjectivesof verification,validityactivitiesareto assessand improvethequality ofthe work
productsgeneratedduring

developmentand

modificationofthesoftware.

Quality

dependsupon

thevariousattributeslikecorrectness, completeness, consistency, reliability, usefulness,

usability,

efficiency and conformance to standards.

Thetermsverificationandvalidationare used synonymously. These aredefinedas under:Verification:Are we buildingtheproductright?
Validation:Are we buildingtherightproduct?
Verificationactivitiesincludeproving,testing,and
evaluatingsoftware

atthe

endof

the

reviews.
software

Validationistheprocess
developmentto

withthesoftwarerequirements.Testingisacommonmethodofvalidation.Clearly,

of

ensurecompliance
forhighreliability

weneedtoperform bothactivities.Together,theyareoftencalled V&Vactivities.

ThemajorV&Vactivitiesfor

softwaredevelopmentareinspection,reviews,

and

testing(bothstaticanddynamic).TheV&VplanidentifiesthedifferentV&Vtasks
forthedifferentphasesand specifieshowthese taskscontributetothe projectV&V goals. The methods
to

be

used

for

performing these V&V activities, the responsibilitiesandmilestonesfor

eachoftheseactivities,inputsandoutputsfor each V&Vtask, andcriteriafor evaluatingtheoutputsare

alsospecified.
The

twomajor

V&Vapproachesare

testingandinspections.Testingis

anactivitythat

canbegenerallyperformedonlyoncode.Itisanimportantactivityandisdiscussed
indetailinalaterchapter.Inspectionisa

moregeneralactivitythat

canbe

appliedto

any

work

product,includingcode.Many oftheV&Vtasksaresuchthatfor them,an inspectiontypeofactivityisthe

onlypossiblewaytoperformthe

tasks(e.g.trace

abilityanddocumentevaluation).Due

tothis,inspectionsplaya significantrolein verification.

9. POST IMPLEMENTATIONMAINTENANCE AND REVIEW

As weknow,creatingsoftwareisonethingand theimplementationofthecreated software is another.The

SMU

Page 77

Emedical

process

ofimplementingsoftwareismuchdifficultas

wehavetoimplementthesoftware

comparedtothetaskofcreatingtheproject.First

onasmallscaleforremovingthebugsandothererrorsintheproject

andafter removingthemwe canimplementthe software on alargescale.

Before we think intermsof implementingthe Softwareon a largebasis, we must considerthe

Hardware requirements.
Wheneverwe developsoftware orproject acertainhardware andsoftwareis beingusedby
theprogrammerfordevelopingtheproject.Thehardwareandsoftware
programmerfordevelopingthe

projectshouldbe

resultinthedevelopmentofaproject,which
whichtheprojecthasbeencreatedby

usedbythe

suchthatit

would

theprogrammer.The

tobe

satisfyall
Hardware

would
thebasicneedsfor

shouldbesuch

thatcost

constraintsoftheClientshouldalsobetakenintoaccountwithoutaffecting theperformance.

9.1 Hardware EvaluationFactors

When we evaluate computer hardware, we should first investigate specific physical and
performance characteristics for each hardware component to be acquired. These specific questions
must be answered concerning many important factors. These hardware evaluation factors questions
are summarized in the below figure.
Notice that there is much more to evaluating hardware than determining the fastest and cheapest
computing device. For e.g. the question of possible obsolescence must be addressed by makinga
technology

evaluation.

The

factor

of

ergonomics

important.Ergonomicsisthescienceandtechnologythattriestoensure
andothertechnologiesare"user-friendly",thatissafe,comfortableandeasytouse.

SMU

Page 78

is

also

very

thatcomputer

Emedical

Connectivityisanotherimportantevaluationfactor,sincesomanycomputersystems
arenowinterconnectedwithinwideareaorlocal areatelecommunicationsnetworks.

The hardware evaluation factors are as follows:

1)Performance
2)Cost
3)Reliability
4)Availability
5)Compatibility
6)Modularity
7)Technology
8)Ergonomics
9)Connectivity
10)Environmentalrequirements
11)Software
12)Support

9.2 Software Evaluation Factors

Softwarecanbe evaluatedaccordingtomanyfactorssimilarto the hardware evaluation.Thus the
factorsofperformance,cost, reliability,compatibility, modularity, technology, ergonomics,

and

support should be used to evaluate proposed software acquisitions. In addition, however, the
software

evaluationfactorsare

summarizedinbelow

figure.

For

packagesrequiretoo much memory capacity and are notoriously slow,

e.g.somesoftware
hard to use,

or

poorly documented.They arenot agoodselectionformostendusers, even ifoffered at attractiveprices.

SMU

Page 79

Emedical

SoftwareEvaluationFactors:
1. EFFICIENCY: is t h e s o f t w a r e a w e l l -written
s y s t e m o f c o m p u t e r instructionsthatdoesnotuse muchmemorycapacity or
CPUtime?
2. FLEXIBILITY:canithandleitsprocessingassignmentseasilywithout
majormodifications?
3. SECURITY:doesitprovidecontrolproceduresforerrors,malfunctions andimproperuse?
4. LANGUAGE: do ourcomputerprogrammersanduserswriteitina
programminglanguagethatisused?
5. DOCUMENTATION: is the s/w we lldoc ume nt ed ? Does itinclude helpfuluser
instructions?
6. HARDWARE:doesexistinghardwarehavethefeaturesrequiredtobest use thissoftware?
7. Othercharacteristicsofhardwaresuchasitsperformance,whataboutthe
cost,howmuchisreliableand etc.

9.3 ConversionAnd Training

An

important aspect of is to make sure

that the new design is implemented to

establishstandards.Thetermimplementationhasdifferentmeanings,rangingfrom
theconversionofabasic
Implementationisused

applicationtoa

completereplacementofa

computer

heretomeantheprocessofconvertinganeworrevise

system.
system

intoanoperationalone.Conversionis one aspect ofimplementation.Conversion meanschangingform

onesystemtoanother.Theobjectiveistoputthetested system intooperationwhileholding costs, risks,
and personnelirritationto a minimum.It involves c r e a t i n g c o m p u t e r -compatible

files,

t r a i n i n g t h e o p e r a t i o n s t a f f , a n d installingterminaland hardware. Acriticalaspectof

conversion isnotdisrupting the functioningof the organization.

SMU

Page 80

Emedical

When a new system is used over and old, existing and running one, there are always compatibility
errors. These errors are caused because of the lack of equipment or
Personneltoworkthenewsystem.Runninganyspecifiedsystematanorganization doesrequire someor
otherhardware or, inthiscase, softwarerequirementas well.
Conversion i s o n e aspect of implementation review &software maintenance.

Thereare threetypesof implementation:

1.

Implementation of a computer system to replace a manual system.

problemsencounteredareconvertingfiles,trainingusers,creatingaccurate

The
filesand

verifyingprintoutsfor integrity.
2.

Implementationofanewcomputersystemtoreplaceanexistingone.Thisis

usually

adifficultconversion.Ifnotproperlyplannedtherecanbemany
problems.Somelargecomputersystemshavetaken aslongasyearto convert.
3.

Implementationofamodifiedapplicationtoreplaceanexistingone,usingthe samecomputer.This
typeof conversion isrelatively easy to handle,provided thereareno majorchangesin thefiles.

9.4 TrainingNeeds
Trainingneedsrefer to thegainingof knowledge requiredfor runningthe system.
First

ofallthesystemisacomputerbasedsystemthereforethepersonshouldhave

good

knowledgeaboutcomputerand its working. He should knowhowto use software'son thecomputer.

Fora betterusageand workingof the softwaretheorganizationshouldappointa person who hasgood
knowledgeof

alltherequiredsoftware.The

persontrainedthroughdifferentinstitutespresentinthemarket.Thetrainingshould
aboverequirements.

SMU

Page 81

organizationgetsa
beasperthe

Emedical

9.5 Limitations of the Project

1.Theprojectwehavecreated is single user & does notsupportthe multiuser environment
i.e.client/server.
2. Theprojectiswindowsbased&notthewebbasedasrequiredinmostof the companies now a days.
3. The projectcanbeused only by a person whohas completeknowledgeof visual basic.
4. Afterthe completion of theapplicationsoftware,the memoryneeded by it should be available on
the harddisk.

SMU

Page 82

Emedical

10. Scope Of Future Application

This

websitewillbedevelopedfor

theOnlineusers

(employees)toget

informationabouttheclaimsthatthey canapply.Utmostcareandback-up procedures mustbe established

to ensure100% successfulimplementation of the
failure,theorganizationshouldbeina

E-Medical Consultancy. In case of system

positiontoprocessthetransactionwith

anotherorganizationorif

theworstcomestotheworst,itshouldbeina position tocomplete itmanually.

Thedecisiontoautomategenerally

dependsontheneeds

tohaveaccurate,

consistentandtimely

datainavarietyofreportingformats.Butthemost importantfactorthatshould be considered is

Besuretotakefuturegrowthintoconsiderationandevaluate
whetherthesoftwarepackagecouldbemodifiedif

theorganization

expands

in

the

futureoryouneedto revisethe system.

ThenextgenerationofWindows-basedcomputerizedsystems

wouldbechangingtheway

ownersandmanagementthink about runningtheir businesses.Itwouldapowerfultoolthatgivesthem

morewaystoget theirfinancialInformationsothat theycanbetter manage and growtheir business.

SMU

Page 83

Emedical

Thenextgenerationofsystemswouldtakeadvantageofthe

latest

technologies,includingMicrosoftWindowsXPandOrcale11i tooffer access andintegrate withall

aspectsofabusiness.Keeping

thisinviewwecoulddevelopsystemsthatwouldworkefficiently

andintegrateseamlessly invirtually any industrysetting,evenupto mid-sized corporations

anddivisions oflarger organizations.
Consideranothersetting,wheretheusersarenotcomfortable

on

computers,forsuch

users

wecandevelopsystemswherethe users can have their own personalized menu setup in the
accountingsoftwaresothattheynolongerhavetosearcharound tofindwhattheyneed.
Now

consider

the

exchangenetworkcomeswithmany

Internet.

This

wide

benefitsforbusinesses,

open
including

information
breaking

downphysicalbarriers asto wherehe/shecan consultto the companies.

Adding other capabilities can be added time totime. These are Applicationmaybeinstalled
clientserver. Application

can

upgraded

Requirementswithlittle

according
changes

to

Employees
made

ApplicationmaybetransferredtolatestRDMBSlikeOraclewith little changes in currentcode.Use

forSecurity purpose
NOTE:Inanutshellwehavealotofscopetofurtherenhancethe futuresand functionalitiesof the proposed
Solution.

SMU

Page 84

Emedical

11. GANTT & PERT CHART

GANTCHART
Ganttcharts

mainly

usedtoallocateresources

toactivities.The

resourcesallocated

toactivitiesinclude staff,hardware,andsoftware.Gantt charts (namedafter itsdeveloper Henry

Gantt)areusefulfor resource planning.AGanttchart isspecialtypeofbarchartwhereeach barrepresents
anactivity.Thebars aredrawnalongatimeline.Thelengthofeachbaris proportionalto the duration
ofthetime planned forthe corresponding activity.
Ganttchart is aprojectscheduling technique. Progress can be represented easily ina Ganttchart, by
coloring eachmilestone when completed. Theproject willstart in the monthof January and end after 4
months at the endofApril.

PertChart

SMU

Page 85

Emedical

PERT(Project

EvaluationandReviewTechnique)chartsconsist

ofanetwork

ofboxesand

arrows.Theboxesrepresentactivitiesandthe arrowsrepresent taskdependencies.

PERT chart represents the statistical variations in the project estimates assuming a normal
distribution. Thus in a PERT chart instead of making a single estimate for each task, pessimistic,
likely, and optimistic estimates are also made. The boxes of PERT charts are usually annotated with
the pessimistic, likely, and optimistic estimates for every task. Since all possible completion times
between the minimum and maximum durations for every task have to be considered, there are many
critical paths, depending on the permutations of the estimates for each task. This makes critical path
analysis in PERT charts very complex. A critical path in a PERT chart is shown by using thicker
arrows. The PERT chart representation of the National Eye Bank Management System problem of
Figure A. is shown in Figure B.
Task
SpecificationPart

ES
0

EF
115

LS
0

LF
15

ST
0

DesignDatabase Part

15

60

15

60

DesignGUI Part

15

45

90

120

75

Code DatabasePart

60

165

60

165

CodeGUIPart
Integrate andTest

45
165

90
285

120
165

165
285

75
0

Write UserManual

15

75

225

285

210

Figure A:DifferentTasksfortheE-MedicalConsultancyshown inabovetable.

SMU

Page 86

Emedical

FIGURE B : PERT Chart representation of the E-Medical Consultancy.

PERTchartsareamoresophisticatedformof

activitychart.Inactivity

diagrams

only

theestimatedtask durations arerepresented. Sincetheactual durations might vary

fromtheestimateddurations, theutility oftheactivity diagrams is limited.

SMU

Page 87

Emedical

12.SECURITY AND VALIDATION CHECKS

Inthisprojectwehaveusedfollowingvalidationchecks.
W h i l e enteringthedataintotheformitwillcheckforthenameofthe
&itshouldnotbenull.

clientisproperly

filled

Wheneverweenterthedataforthenewcustomer,company,oruser willautomatically check the

details fromthe database tablesand also generate theconnection number automatically.
Similarlyinthecomplainttablecomplaintnumberwillgenerate automatically.
E n t e r e d text/numbershouldnotexceed the limit(width).
Almostforallfieldswehaveusedthevalidationforexampleifname
of
thefieldsrequires
thetexttypeofdatathenitwillcheck forthestring and ifthedataisnumericthenitwillcheckif
thenumberenteredis propernumeric or not.

PHPProvidesSecurity
Evidence-based security (authentication) Based
onuseridentity andcode identity Configurable policies
Imperativeanddeclarativeinterfaces

SMU

Page 88

Emedical

13. CONCLUSION

Thisprojectisdesignedtomeettherequirementsofthehospital.Ithasbeen developedin PHP,keepingin

mind the specifications of thesystem.
Fordesigning

the

systemwehaveused

simpledataflow

diagrams.

Overallthe

projectteaches us the essential skillslike:

Usingsystemanalysisanddesigntechniqueslikedataflowdiagramin designing thesystem.
Understandingthedatabase handlingandqueryprocessing usingSQL Server.

SMU

Page 89

Emedical

14. BIBLIOGRAPHY

1.SennJamesA: AnalysisandDesignofInformationSystems, McGrawHill, InternationalEd,1989.

2.O'Brien Jamea A: Management Information Systems, Galgotia
PublicationsPvtLtd,NewDelhi,1998.
3.Laudon&Laudon:ManagementInformationSystems,Organisationand
Technology,PHI,NewDelhi,1998.
4. WetherebeJames:SystemsAnalysisandDesign,GalgotiaPublicationsPvt Ltd,
NewDelhi,1990

SMU

Page 90