X-20861717509-20861717515 OPD Patient Digitisation Sonia Devi Sunana MSC It 2019

Project Report
On
OPD PATIENT DIGITISATION
Submitted in partial fulfillment of the requirements for the award of degree of
MSC (INFORMATION TECHNOLOGY)
TO
SHANTI DEVI ARYA MAHILA COLLEGE

DINANAGAR
Submitted To:- Submitted By:
Miss. Sanjana SONIA DEVI (20861717515)
Assistant Prof. SUNANA (20861717509)
Dept.Of Computer Science
DEPARTMENT OF COMPUTER SCIENCE

GURU NANAK DEV UNIVERSITY, AMRITSAR
1
ACKNOWLEDGEMENT
With deep sense of gratitude we express my sincere thanks and obligation to our esteemed guide
Assistant Professor Teacher Miss.Sanjana .It is because of her able and mature guidance and co-
operation without which it would not have been possible for us to complete my project.
we would also like to thank Mrs. Deepak Jyoti, HOD, Dept. Of Computer Science in Shanti Devi Arya
Mahila College Dinanagar, for providing the institute with an environment where one can use her
intellect and creativity to develop something fruitful and also for allowing us the opportunity to
experience dynamic professional environment during our Training. This environment facilitated us
in pursuing this project.
It is our pleasant duty to thank all the staff member of the computer Department for their time to
time suggestions.
Finally, we would like to thank the almighty and our parents for their moral support and our friends
with whom we shared our day-to-day experience and received lots of suggestions that improved our
quality of work.
SONIA DEVI (20861717515)
SUNANA (20861717509)
2
CERTIFICATE OF APPROVAL
This is certify that the project report entitled OPD PATIENT DIGITISATION submitted to
SHANTI DEVI ARYA MAHILA COLLEGE,DINANAGAR in partial fulfillment of the
requirement for the award of degree of MASTER OF INFORMATION TECHNOLOGY is
an authention and original work carried out SONIA DEVI (20861717515),
SUNANA(20861717509)under my guidance and supervision. The department of Computer has
accepted the report as the fulfillment of the requirements for the degree of Master of Computer
Science. No part of this report has been submitted to any other College/University for the reward
of any Degree to the best of my knowledge.
MISS. SANJANA
Asst. Prof.
(Project Supervisor)
SDAM COLLEGE, DINANAGAR
3
DECLARATION
We hereby declare that this project report on, “OPD PATIENT DIGITISATION”, which is
being submitted in partial fulfillment of the Tr a i n i n g P r o g r a m o f M A S T E R O F
INFORMATION TECHNOLOGY TO SHANTI DEVI ARYA MAHILA
C O L L E G E , D I N A N A G A R is the result of the work carried out by us , under the guidance
of Asst. Prof. Miss Sanjana Shanti Devi Arya Mahila College, Dinanagar
SONIA DEVI (20861717515)

SUNANA (20861717509)
4
TABLE OF CONTENTS
S.No Topic Page

No
1  Introduction and Objectives of the Project 7-12
 Introduction about Project
 Objectives of the Project
 Advantage
 Drawbacks of the Current Manual System
 Establish the need of the new system
 Proposed System
2  Technologies Used 13-24

 ASP.NET
 What is .NET?
 Web Services
 NET Framework
 ADO.NET
 Visual C#
 SQL Server 2008
3  Hardware And Software Requirements 25

4  Software Development Life Cycle(SDLC) 26-39
 Preliminary Investigation
 Defining a Problem
 Software Requirement
Specification
 Feasibility Study
 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
 Design
 System Design
 Detailed Design
5
5  Modules Description 40-49
TABLE OF CONTENTS
6  Snapshot 50-60
 Screen shot
 Reaches
 Reviews
 Contact us
 Login.aspx
 Login invalid
 Login invalid
 Update
 Check
 report
7  Coding 61-68
8  Testing 69-71
 Acceptance Testing
 System Testing
 Integration Testing
 Unit Testing
9  Implementation 72-78
10  Conclusion 79
11  Bibliography 80
6
INTRODUCTION AND OBJECTIVES OF THE PROJECT
INTRODUCTION
Patient Management System is an application developed in ASP.NET

programming language for effective management of patients in a hospital. The
main aim of project is to provide a computerized service to handle the patients’
details at any hospital. The project generates a kind of hospital management
software which can be installed in any hospital or clinic to keep the records of
patients.
Everyday a large number of patients visit hospitals and clinics to check up;
some of them are prescribed to visit next time. Therefore, it is necessary to keep
record of patients in all health care organizations. But, the traditional system of
storing details of patient is tedious, unsecured and risky. Due to these drawbacks,
the development of computerized patient management system is necessary.
Providing quicker and efficient service is the duty of hospitals.
But, the time of patient registration is longer than time of treatment in the most
hospitals due to use of manual paper-pen system of patient management. The
growing use of computers is becoming the solution to these problems these days.
The proposed Patient Management System Project is the software to maintain the
details of patients in a computerized way. Besides patient management, there are
several other features to manage different branches and departments such as
pharmacy, hospital employees, doctors, etc.
7
Modules Overview:
The proposed ASP.NET project is a four-modules project: patient records

management module, pharmacy module, employee management module and
doctor management module. Each module has different role in effective
implementation of Patient Management System. The modules are briefly
introduced below:
Patient Record Management is the major module of project which describes the
main aim of project. Their module is responsible for keeping the details of patients
in hospital so that they can be accessed at any time.
Pharmacy Management is designed to store the details of medicine regarding batch

number, medicine name, expiry date etc. These details are updated to the system
database by the admin. With the help of their module, the pharmacist can estimate
the available stock of medicine and future requirement in hospital.
Doctors Management Module is developed to maintain the details of doctors and

related information. Their module is also managed by the admin of the software.
Admin has option to add doctor’s details to database using doctor addition module.
The information such as doctor’s name, specialization and timings are available in
their module.
DRAWBACKS OF EXISTING SYSTEM
 More man power.

 Time consuming.
 Consumes large volume of pare work.
 Needs manual calculations.
 No direct role for the higher officials.
 Damage of machines due to lack of attention.
To avoid all these limitations and make the working more accurately the system
needs to be computerized.
8
PROPOSED SYSTEM
The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system. The
system provides proper security and reduces the manual work. The existing system
has several disadvantages and many more difficulties to work well. The proposed
system tries to eliminate or reduce these difficulties up to some extent. The
proposed system will help the user to reduce the workload and mental conflict. The
proposed system helps the user to work user friendly and he can easily do her jobs
without time lagging.
Expected Advantages of Proposed System
The system is very simple in design and to implement. The system requires
very low system resources and the system will work in almost all configurations. It
has got following features
 Ensure data accuracy’s.

 Proper control of the higher officials.
 Reduce the damages of the machines.
 Minimize manual data entry.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.
9
ADVANTAGE
Key Features Are:

 System Connectivity
 No data duplication
 No Paper Work Required
 Time Efficient
 Cost Efficient
 Automatic data validation
 User friendly environment
 Data security and reliability
 Fast data insertion & retrieval
 Maintaining records of Patient
 Crystal Report generation
DRAWBACKS OF CURRENT MANUAL- SYSTEM
 The current manual system has a lot of paper work
 To maintain the records of Patientmanually, is a Time-consuming job.
 With the increase in database, it will become a massive job to maintain the database.
 Requires large quantities of file cabinets, which are huge and require quite a bit of space
in the office, which can be used for storing records of previous claims.
 The retrieval of records of Patientwillbe a tedious job.
 Lack of security for the records, anyone disarrange the records of your system.
10
ESTABLISH THE NEED OF NEW SYSTEM
1. Problem of Reliability: Current system is not reliable. It seems to vary in quality from one
month to the next. Sometimes it gives good output, but sometimes the output is worst.
2. Problem of Accuracy: There are too Patientmistakes in reports.
3. Problem of timeliness: In the current system the reports and output produced is mostly late
and in most of the cases it is useless because it is not on time.
4. Problem of Validity: The output and reports mostly contains misleading information. The
customer's information is sometimes not valid.
5. Problem of Economy: The current system is very costly. We have to spend lots of Patient to
keep the system up and going, but still not get the desired results.
6. Problem of Capacity: The current system is suffering from problem of capacity also. The
staff for organization is very less and the workload is too much. Few peoples cannot handle
all the work.
PROPOSED SYSTEM
1. Details: The new proposed system stores and maintains all Patientdetails.
2. Calculations: The new proposed system updates tables and other information
automatically and it is very fast and accurate.
3. Registers: There is no need of keeping and maintaining records and information

manually. It remembers each and every record and we can get any report at any time.
4. Speed: The new proposed system is very fast with 100% accuracy and saves time.
5. Manpower: The new proposed system needs less manpower. Less people can do the
large work.
11
6. Efficiency: The new proposed systems complete the work of Patient people in less
time.
7. Reduces redundancy:The most important benefit of ther system is that it reduces

the redundancy of data within the data.
8. Easy statements:Month-end and day-end statement easily taken out without getting
headaches on browsing through the day end statements.
NEED
I have designed the given proposed system in the ASP.NET to automate the process of OPD
Patient digitisation. Ther project is useful for the authorities who keep track of all the system.
The following steps that give the detailed information of the need of proposed system are:
 Performance: During past several decades, the records are supposed to be manually
handled for all activities. The manual handling of the record is time consuming and
highly prone to error. To improve the performance of the system, the computerized
system is to be undertaken.
 Efficiency: The basic need of ther website is efficiency. The website should be
efficient so that whenever a new user submits her/her details the website is updated
automatically. Ther record will be useful for other users instantly.
 Control: The complete control of the project is under the hands of authorized person
who has the password to access ther project and illegal access is not supposed to deal
with. All the control is under the administrator and the other members have the rights
to just see the records not to change any transaction or entry.
 Security: Security is the Patient criteria for the proposed system. Since illegal access
may corrupt the database. So security has to be given in ther project.
12
TECHNOLOGIES USED
ASP.NET
What is .NET?
 A vision of how information technology will evolve
 A platform that supports the vision
 A business model of software as a service
1. A Vision.
 Web sites will be joined by Web services
 New smart devices will join the PC
 User interfaces will become more adaptable and customizable
 Enabled by Web standards
2. A Platform.
 The .NET Framework
 Visual Studio.NET
 .NET Enterprise Servers
o Database, Messaging, Integration, Commerce, Proxy, Security
 Goal: make it incredibility easy to Patient powerful Web applications and Web services
3. A business model.
 Software as a service
 Subscription-based services
 Application hosting
Interoperability: Web languages and protocols must be compatible with one another
independent of hardware and software.
13
Evolution: The Web must be able to accommodate future technologies. Encourages simplicity,
modularity and extensibility.
Decentralization: Facilitates Scalability and Robustness.
Web Services
 A programmable application component accessible via standard Web protocols
 The center of the .NET architecture
 Exposes functionality over the Web
 Patient on existing and emerging standards are HTTP, XML.
The .NET Framework
14
15
What is the .NET Framework?
 A set of technologies for developing and using components to create:

o Web Forms
o Web Services
o Windows Applications
 Supports the software lifecycle
o Development
o Debugging
o Deployment
o Maintenance
 Application Architectures
o The Different types of Applications may vary from single-tier desktop
applications (applications that follow the single-tier architecture) to multi-tier
applications (applications that follow the two-, three, or n-tier architecture)
o Single-tier architecture
 A single executable file handles all functions relating to the user, business,
and data service layers.
o Two-tier architecture
 Divides an application into the following two components:
 Client
 Server
o Three-tier architecture
 All the three service layers reside separately, either on the same machine
or on different machines.
o n-tier architecture
 Uses business objects for handling business rules and data access.
 Has multiple servers handling business services.
16
The .NET Initiative
 The introduction of the Internet and its rapid growth in the recent past has led to the
development of a number of new Technologies.
 One of the most important requirements of such applications is the ability to interchange
information across platforms and to benefit from the functionality provided by other
applications.
 In the current scenario, although applications serve organization-specific requirements,
they are not interoperable. Microsoft has introduced the .NET initiative with the intention
of bridging the gap in interoperability between applications.
 The .NET initiative offers a complete suite for developing and deploying applications,
which consists of the following:
o NET products: Microsoft has already introduced Visual Studio .NET, which is a
tool for developing NET applications by using programming languages such as
Visual Basic, C#, and Visual C++.
o NET services: Microsoft is coming up with its own set of Web services, known
as My Services. These services are based on the Microsoft Passport
Authentication service, the same service that is used in Hotmail.
17
Explanation of the .NET Framework
 Is a collection of services and classes?
 Exists as a layer between .NET applications and the underlying operating system.
 Encapsulates much of the functionality, such as debugging and security services.
 The following figure depicts the components of the .NET Framework:
The .NET Framework Base Classes or the .NET Class Framework
 Consists of a class library that works with any .NET language, such as Visual Basic .NET
and C#.
 Provides classes that can be used in the code to accomplish a range of common
programming tasks.
 Comprises
o Namespaces: Namespaces help you to create logical groups of related classes and
interfaces that can be used by any language targeting the .NET Framework.
o Assembly: An assembly is a single deployable unit that contains all the
information about the implementation of classes, structures, and interfaces.
 The Common Language Runtime
o Provides functionality such as exception handling, security, debugging, and
versioning support to any language that targets it.
o Can host a variety of languages and offer a common set of tools across these
languages, ensuring interoperability between the codes.
 Provides the following features:

o Automatic memory management
o Standard type system
o Language interoperability
o Platform independence
o Security management
o Type safety
18
Advantages of the .NET Framework
Some advantages of the .NET Framework are:

o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment
ADO.NET
 Is a model used by Visual Basic .NET applications to communicate with a database for
retrieving, accessing, and updating data?
 Uses a structured process flow to interact with a database.
ADO .NET Data Access

Most applications need data access at one point of time making it a crucial component when
working with applications. Data access is making the application interact with a database, where
all the data is stored. Different applications have different requirements for database access.
VB.NET uses ADO.NET (Active X Data Object) as it's data access and manipulation protocol,
which also enables us to work with data on the Internet. Let's take a look why ADO.NET came
into picture replacing ADO.
Evolution of ADO.NET
The first data access model, DAO (data access model) was created for local databases with the
Patient-in Jet engine which had performance and functionality issues. Next came RDO (Remote
Data Object) and ADO (Active Data Object) which were designed for Client Server architectures
but soon ADO took over RDO. ADO was a good architecture but as the language changes so is
the technology within it. With ADO, all the data is contained in a record set object which had
problems when implemented on the network (Internet) and penetrating firewalls. ADO was a
connected data access which means that when a connection to the database is established the
19
connection remains open until the application is closed, which raises concerns about database
security and network traffic. And also as databases are becoming increasingly important and as
they are serving more people a connected data access model makes us think about its use. For
example, an application with connected data access may do well when connected to two clients,
the same may do poorly when connected to 10 and might be unusable when connected to 100 or
more. Also, open database connections use system resources to a maximum extent making the
system performance less effective.
Why ADO.NET?
To cope up with some of the problems mentioned above, ADO.NET came into existence.
ADO.NET addresses the above mentioned problems by maintaining a disconnected database
access model which means that when an application interacts with the database the connection is
opened to serve the request of the application and is closed as soon as the request is completed.
Likewise if a database is updated, the connection is opened long enough to complete the Update
operation and is closed. By keeping connections open for only a minimum period of time
ADO.NET conserves system resources and provides maximum security for databases and also
has less impact on system performance. Also, ADO.NET when interacting with database uses
XML by converting all the data into XML and using it for database related operations making
them more efficient.
Features of ADO.NET
 Disconnected data architecture — Applications connect to the database only while
retrieving and updating data.
 Data cached in datasets — ADO.NET is based on a disconnected data structure.
Therefore, the data is retrieved and stored in datasets.
 Data transfer in XML format — ADO.NET uses XML for transferring information from
a database into a dataset and from the dataset to another component.
 Interaction with the database is done through data commands.
20
ADO.NET Object Model
Key Components of the ADO.NET Model
 Data Provider
o Is used for connecting to a database, retrieving data, and storing the data.
 Is of two types:
o OLE DB data provider
o SQL Server data provider
Components of a Data Provider

 Connection
o Used to establish a connection with a data source
o Some commonly used properties and methods:
 ConnectionString property
 Open()method
 Close()method
 State property
 Data adapter
o Creates a dataset and updates the database.
o Handles data transfer between the database and the dataset through its properties
and methods.
o Displays the data through the process of table mapping.
o Are of two types:
 SqlDataAdapter
 OleDbDataAdapter
 Data command
o Is a SQL statement or a stored procedure that is used to retrieve, insert, delete, or

modify data from a data source?
o Is an object of theSQLCommandclass?
 Data reader
21
o Is used to retrieve data from a data source in a read-only and forward-only mode.
o Stores a single row at a time in the memory.
o Commonly used methods:
 Read()
 Close()
 NextResult()
 Dataset
o Is a disconnected, cached set of records that are retrieved from a database.

o Is present as a DataSet class in the System.Data namespace.
o Has its own object model.
VISUAL C# (Language Used for coding)

Microsoft Visual C# is Microsoft's implementation of the C# specification, included in the
Microsoft Visual Studio suite of products. It is based on the ECMA/ISO specification of the C#
language, which Microsoft also created. While multiple implementations of the specification
exist, Visual C# is by far the one most commonly used. In most contexts, an unqualified
reference to “C#” is taken to Patient “Visual C#.”
C# (pronounced "C-sharp") is an object-oriented programming language from Microsoft that
aims to combine the computing power of C++ with the programming ease of Visual Basic. C# is
based on C++ and contains features similar to those of Java.
C# is designed to work with Microsoft's .Net platform. Microsoft's aim is to facilitate the
exchange of information and services over the Web, and to enable developers to Patient
highly portable applications. C# simplifies programming through its use of Extensible Markup
Language (XML) and Simple Object Access Protocol (SOAP) which allow access to a
programming object or method without requiring the programmer to write additional code for
each step. Because programmers can Patient on existing code, rather than repeatedly duplicating
it, C# is expected to make it faster and less expensive to get new products and services to market.
22
SQL SERVER 2008
SQL Server is an SQL-compliant RDBMS. SQL-compliant means it use the ANSI (American
National Standard Institute) version of Structured Query Language or ‘SQL’. Structured Query
Language is a command that allow us to modify or retrieve information from the database.
Client server means that SQL Server is designed to store data in the central location (the server)
and deliver it on demand to numerous other locations (the client). SQL Server is also a
Relational Database Management System (RDBMS).
FEATURES OF SQL SERVER 2008:

 Information representation
 Unique definition of rows
 Systematic treatment of Null values
 Guaranteed access
 High level Update, Insert, and Delete
ENTERPRISE MANAGER
SQL Server Enterprise Manager is a graphical tool that allows easy configuration and
management of Microsoft SQL Server and SQL 2008program group.
SQL Server Enterprise Manager can also be used to:
 Manage logins, permission and users.
 Create a database
 Take Patient-up of database and transaction logs.
 Manage tables
QUERY ANALYZER
The SQL Server Query Analyzer allows us to create adhoc queries and run them interactively.
We may also execute Transact-SQL statements stored in text file and view the result in result
plane or result grid. The Query Analyzer also has a color-coded editor to assist the user with
checking of syntax. It also has context sensitive help.
Queries are processed in two steps:
 Interpret- First the Queries are checked for syntax.
23
 Execute- Then the processing take place.
 SQL Stored Procedures
A precompiled collection of Transact-SQL statements stored under a name and processed as unit
.SQL SERVER supplies stored procedures for managing SQL SERVER and displaying
information about databases and users. SQL SERVER supplied stored procedures are called
System stored procedures. A stored procedure is a group of Transact-SQL statements compiled
into a single execution plan.
DATABASE
Ther tier of the architecture is mainly related to the database that is required in the project. The
database is used for storing data as a set of records and is used for performing Data Manipulation
upon ther data stored. Ther is the job of the Database team within an organization. The database
tier design consists of the following elements:
 TABLES
The data in the database is stored in the form of tables where each column is the set of attributes
that describes data, and each row represents each record of data stored. We study the whole
project and find out what all tables will be required during the project, and then we develop the
tables and their attributes with a naming convention followed.Each unique attribute within each
table is set as the primary key.
 STORED PROCEDURES
In database we use stored procedures for each table defined in the tables section. These are
compiled objects and are used for achieving the advantages of reusability, better security and
performance.These are stored aswell as executed in the database. We have defined 5 stored
procedures for each table for performing insert, update, delete, search and display operations on
the data of the database.
24
HARDWARE AND SOFTWARE REQUIREMENTS
HARDWARE REQUIREMENTS FOR SERVER:
 Processor 500MHz (minimum)
 RAM 4GB
 Hard Disk 1000 GB
HARDWARE REQUIREMENTS FOR CLIENT:

 Processor 4 (minimum)
 RAM 2GB
 Hard disk 500 GB
SOFTWARE REQUIREMENTS:
 . NET Framework 4
 Visual Studio 2010
 SQL Server 2008 R2
 Browser like Internet Explorer, Mozilla, Opera
OPERATING SYSTEM
 WINDOWS 8.1 or higher
25
26
SYSTEM DEVELOPMENT LIFE CYCLE
SDLC is an acronym for System Development Life Cycle, a methodology that consists of
development activities that have a prescribed order. Once a problem or opportunity for a new
system is recognized a request for developing a new system is forwarded for approval. If it is
approved, a study is carried out to ensure that the proposed system is feasible. If it is feasible,
then the system’s requirements are specified and are followed by phases of system analysis,
system design, system implementation, and post implementation. A recycling of development
may occur again following system evaluation if the system still requires modification or
redevelopment.
To understand system developmentwe need to recognize that candidate system that has a life
cycle. System analysis and design are keyed to the system life cycle.
The stages of system development life cycle are:
 Preliminary investigation
 Determination of software requirement
 Design of software
 Development of software
 System testing
 System implementation, evaluation and maintenance
PRELIMINARY INVESTIGATION
System development, a process consisting of two major steps of system analysis and design, start
when management or sometimes system development personnel feel that a new system or an
improvement in the existing system is required. The system development life cycle is classically
thought of as the set of activities that analysts, designers and users carry out to develop and
implement an information system. The system development life cycle consists of the following
activities:
 Preliminary investigation
 Determination of system requirements
 Design of system
 Development of software
 System testing
27
 Implementation, evaluation, and maintenance
DEFINING A SYSTEM
A collection of components that work together to realize some objective forms a system.
Basically there are three major components in every system, namely input, processing and
output.
In a system the different components are connected with each other and they are
interdependent. For example, human body represents a complete natural system. We are also
bound by Patient national systems such as political system, economic system, educational
system and so forth. The objective of the system demands that some output is produced as a
result of processing the suitable inputs.
28
PRELIMINARY
INVESTIGATION
REVIEW RUNNING DETERMINATION OF

SYSTEM AND REQUIREMENTS
SYSTEM
MAINTENANCE
DEVELOPMENT OF
PROTOTYPE SYSTEM
SYSTEM DESIGN OF SYSTEM

IMPLEMENTATION
DEVELOPMENT OF
SYSTEM TESTING SOFTWARE AND
CODING
FIG: SYSTEM DEVELOPMENT LIFE CYCLE
29
SYSTEM REQUIREMENT SPECIFICATION
The System Requirement Specification & Development Life Cycle Analysis is a common
methodology for any Application development, whether it is a website project which may run on
a network or enterprise level or an standalone project which might be even Multi user. It marks
the phases or steps of information that will be used by the system to decide to acquire the
necessary resources required for it. A careful study is done of how the organization currently
handles the work and how the new system should work. Professionals develop a strategy for
designing a new system, which is then either Patient or purchased. Once complete, the system
can be installed on the server, and after proper testing, the user begin to incorporate the new
system into their daily work.
The requirement analysis is the process of discovery and refinement. The hardware required,
software scope initially established during system engineering is refined in detail. Alternative
solution are analyzed and allocated to various elements. It is software engineering task that
bridges the gap between system level software allocation and design. Requirement analysis
enables the system engineering to specify software function and performance, indicates software
interface with other system.
FEASIBILITY STUDY
A feasibility study is a test of a system personal according to its workability, impact on

organization, ability to meet user needs, and effective use of resources. It focus on three major
questions:
1. What are the user’s needs and how does a system meet them?
2. What resources are available for given system? Is the problem worth solving?
3. What are the likely impacts of the system on the organization? How well does it fit within
the organization’s?
Each of these questions may be answered. They resolve around investigation and evaluation of
the problem, identification and description of candidate system, and final selection of the best
system.
30
To, solve all these problems a detail study of the present system is done. Finally it is seen that the
new system could be implemented as it takes less time comparatively to the existing system. So,
the needed system was feasible enough to be uploaded
A proper feasibility study for the project was carried out and it includes the following three types
of feasibility studies:
 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
1. TECHNICAL FEASIBILITY
Technical Feasibility centers on the existing computer system (hardware, software etc.) and to
what extent it can support the proposed addition. For example, if the current computer is
operating at 80 percent capacity-an arbitrary ceiling-then running another application could
overload the system or requires additional hardware. Ther involves financial considerations to
accommodate technical enhancements. If the budget is a constraint, then the project is judged not
feasible.
2. ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system. More commonly known as cost/benefit analysis, the procedure is to determine
the benefits and savings that are expected from a candidate system and compare them with costs.
If benefits outweigh costs, then the decision is made to design and implement the system.
Otherwise, further justification or alterations in the proposed system will have to be made if it is
to have a chance of being approved. Ther is an ongoing effort that improves in accuracy at each
phase of the system life cycle.
In today’s world the two important factors that judge the success of an online project is the data
security and speed of data access
31
3. OPERATIONAL FEASIBILITY
People are inherently resistant to change, and computers have been known to facilitate change.
An estimate should be made of how strong a reaction the user staff is likely to have toward the
development of a computerized system.
Ther study gives us a very clear picture of the existing system as well as the proposed system.
Further with the help of ther study one can clearly understand the difference between the two
systems clearly specifying the merits, which shall be attained from the proposed system.In most
cases, the introduction of new system requires special effort to educate, sell, and train the staff on
the new ways of conducting business.
32
33
SYSTEM ANALYSIS
A system analysis is a separation of a substance into parts for study and their implementation
and detailed examination.Before designing any system it is important that the nature of the
business and the way it currently operates are clearly understood. The detailed examination
provides the specific data required during designing in order to ensure that all the client's
requirements are fulfilled. The investigation or the study conducted during the analysis phase
is largely based on the feasibility study. Rather it would not be wrong to say that the analysis
and feasibility phases overlap. High-level analysis begins during the feasibility study. Though
analysis is represented as one phase of the system development life cycle (SDLC), ther is not
true. Analysis begins with system initialization and continues until its maintenance. Even after
successful implementation of the system, analysis may play its role for periodic maintenance
and up gradation of the system.
One of the Patient causes of project failures is inadequate understanding, and one of the Patient
causes of inadequate understanding of the requirements is the poor planning of system
analysis.
Analysis requires us to recall the objectives of the project and consider following three
questions:
 What type of information is required?

 What are the constraints on the investigation?
 What are the potential problems that may make the task more difficult?

IMPORTANCE OF COMPUTERIZED OPD Patient digitisation
There are several attributes in which the computer based information works. Broadly the
working of computer system is divided into two Patient groups:
 Transaction System
 Decision Support System
Transaction System:
34
A transaction is a record of some well-defined single and usually small occurrence in a system.
Transactions are input into the computer to update the database files. It checks the entering data
for its accuracy. Ther means that numeric data appears in numeric field and character data in
character field. Once all the checks are made, transaction is used to update the database.
Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are
entered and updated into the database almost instantaneously. In batch mode, transactions are
collected into batches, which may be held for a while and inputted later.
Decision Support System:
It assists the user to make analytical decision. It shows the various data in organized way called
analysis. Ther analysis helps in making decisions.
Computer system works out best with record maintenance. It will tell you which customer would
get how much pending/reports statements. It will also help to search the information about a
particular person by simply entering her telephone number. User can store information as per
requirement, which can be used for comparison with other reports.
PRINCIPLES OF SYSTEM ANALYSIS
Principles:
1. Understand the problem before you begin to create the analysis model.
2. Develop prototypes that enable a user to understand how human machine interaction will
occur.
3. Record the origin of and the reason for every requirement.
4. Use multiple views of requirements like building data, function and behavioral models.
5. Work to eliminate ambiguity.
35
36
SYSTEM DESIGN
The design of an information system produces the details that clearly describe-how a system will
need the requirement, identified during the system analysis. System specialist often refers to ther
stage or logical design, in contrast to process of developing program software, which is referred
to as physical design. The system design describes the data to be input, calculated or stored,
individual data items and calculations procedures are written in detail designer’s select file
structure and storage devices. Designers are responsible for providing programmers with
complete and clearly outlined software specifications. Design is essentially the bridge between
requirement specification and the final solution for satisfying the requirement DESIGN PHASE.
The design document that we will develop during ther phase is the blueprint of the software. It
describes how the solution to the problem is to be Patient. Since solution to complex problems
isn’t usually found in the first try, iterations are most likely required. Ther is true for software
design as well. For ther reason, any design strategy, design method, or design language must be
flexible and must easily accommodate changes due to iterations in the design. Any technique or
design needs to support and guide the partitioning process in such a way that the resulting sub-
problems are as independent as possible from each other and can be combined easily for the
solution to the overall problem. Sub-problem independence and easy combination of their
solutions reduces the complexity of the problem. Ther is the objective of the partitioning process.
Partitioning or decomposition during design involves three types of decisions: -
Define the boundaries along which to break;

Determine into how Patient pieces to break; and
Identify the proper level of detail when design should stop and implementation should start.
Basic design principles that enable the software engineer to navigate the design process suggest a
set of principles for software design, which have been adapted and extended in the following list:
Free from thesuffer from "tunnel vision." A good designer should consider alternative
approaches, judging each based on the requirements of the problem, the resources available to do
the job.
37
The design should be traceable to the analysis model. Because a single element of the design
model often traces to multiple requirements, it is necessary to have a means for tracking how
requirements have been satisfied by the design model.
The design should not repeat the same thing. Systems are constructed using a set of design
patterns, Patient of which have likely been encountered before. These patterns should always be
chosen as an alternative to reinvention. Time is short and resources are limited! Design time
should be invested in representing truly new ideas and integrating those patterns that already
exist.
The design should "minimize the intellectual distance" between the software and the problem as
it exists in the real world. That is, the structure of the software design should (whenever possible)
mimic the structure of the problem domain.
The design should exhibit uniformity and integration. A design is uniform if it appears that one
person developed the entire thing. Rules of style and format should be defined for a design team
before design work begins. A design is integrated if care is taken in defining interfaces between
design components.
The design activity begins when the requirements document for the software to be developed is
available. Ther may be the SRS for the complete system, as is the case if the waterfall model is
being followed or the requirements for the next "iteration" if the iterative enhancement is being
followed or the requirements for the prototype if the prototyping is being followed. While the
requirements specification activity is entirely in the problem domain, design is the first step in
moving from the problem domain toward the solution domain. Design is essentially the bridge
between requirements specification and the final solution for satisfying the requirements
The goal of design process is to produce a model or representation of a system on the basis of
which a system can be designed. The design process for software can be divided into 2 different
phases.
 System Design
 Detailed Design
38
SYSTEM DESIGN
At the first level focuses on deciding which module are needed for ther system, the specification
of these modules, and how the modules should be interconnected so that combination of these
provides the desired output. That is what is called System Design. Modules are designed that
they have least interactions between them so that changes in one module can take place with a
negligible effect on other.
DETAILED DESIGN
The internal logic and working of each module described in system design is decided in ther
phase. And the modules logic is described in a high level language. Data structure and
algorithmic design of each and every module is also defined in ther phase.
39
MODULES DESCRIPTION
1. ADMIN
Ther module is very important from security point of view. Administrator has the power to add
Patient, edit the information of the Patient, store the feedback of the Patient, prepare the crystal
reports of the student results.
2. MEMBER
Ther module is for the Patient. The username and password assigned by the admin to the Patient. user
can login with their username and password and can have access to home page, post the feedback, and
see their results .
Because the detailed design is an extension of system design, the system design controls the
major structural characteristics of the system. The system design has a major impact on the
testability and modifiability of a system, and it impacts its efficiency. Much of the design effort
for designing software is spent creating the system design.
A design can be object-oriented or function-oriented. In function-oriented design, the design

consists of module definitions, with each module supporting a functional abstraction. In object-
oriented design, the modules in the design represent data abstraction (these abstractions are
discussed in more detail later). In the function-oriented methods for design and describe one
particular methodology the structured design methodology in some detail. In a function- oriented
design approach, a system is viewed as a transformation function, transforming the inputs to the
desired outputs. The purpose of the design phase is to specify the components for ther
transformation function, so that each component is also a transformation function. Hence, the
basic output of the system design phase, when a function oriented design approach is being
followed, is the definition of all the major data structures in the system, all the major modules of
the system, and how the modules interact with each other.
Once the designer is satisfied with the design he has produced, the design is to be precisely
specified in the form of a document. To specify the design, specification languages are used.
Producing the design specification is the ultimate objective of the design phase. The purpose of
ther design document is quite different from that of the design notation. Whereas a design
40
represented using the design notation is largely to be used by the designer, a design specification
has to be so precise and complete that it can be used as a basis of further development by other
programmers. Generally, design specification uses textual structures, with design notation
helping in understanding.
DETAIL AND WORKING OF THE PROJECT
DATABASE TABLES
In a project database tables are the most important component. It is where the data is actually
stored. These tables are not shown to the user. The user has access to the data stored in these
tables through the forms made in the front-end tool by the programmer. In ther project Oracle is
used as a backend tool. The database used in our project consists of the following tables:
1. tbusr- to store login details of the administrator.
Field Name Type Constraints Description

Userid Int Primary Key Userid
Userpwd Varchar (50) Not Null Password
41
2. tbreg: To store details of the Patient .
Pid P Name Age Address Case Follow Follow Follow
History Up1 Up2 Up3
101 Rajbir 25 Gurdaspur Fever
102 Rajat 26 Batala Fever
103 Manat 34 Dinanagar Headache
3.tbfeedback: To store feedback
Patient Name Mobile No Email Comment

Onakr 9814556700 one@gmail.com Good
Manik 9878654522 manik@gmail.com Good
Manoj 9876677556 manoj@gmail.com Good
42
DATA FLOW DIAGRAM
A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through an
information system. A data flow diagram can also be used for the visualization of data
processing (structured design). It is common practice for a designer to draw a context-level DFD
first which shows the interaction between the system and outside entities. Ther context-level
DFD is then "exploded" to show more detail of the system being modeled.
Data flow diagrams were invented by Larry Constantine, the original developer of structured
design, based on Martin and Estrin's "data flow graph" model of computation. Data flow
diagrams (DFDs) are one of the three essential perspectives of Structured Systems Analysis and
Design Method SSADM. The sponsor of a project and the end users will need to be briefed and
consulted throughout all stages of a system's evolution. With a dataflow diagram, users are able
to visualize how the system will operate, what the system will accomplish, and how the system
will be implemented. The old system's dataflow diagrams can be drawn up and compared with
the new system's dataflow diagrams to draw comparisons to implement a more efficient system.
Dataflow diagrams can be used to provide the end user with a physical idea of where the data
they input ultimately has an effect upon the structure of the whole system from order to dispatch
to restock. How any system is developed can be determined through a dataflow diagram.
The dataflow diagram (DFD) was first developed by Larry Constantine as a way of expressing
system requirements in a graphical from. A DFD also known as a bubble chart has a purpose of
clarifying system requirement and identifying major transformation that will become the
program in the system design.
DFD Symbols
1. A SQUARE defines a source or destination of system data
43
2. An ARROWidentifies dataflow or data in motion. It is pipeline through which information
flows.
3. A CIRCLE or a bubble represents a process transform in coming dataflow into outgoing

dataflow.
4. AN OPEN RECTANGLEis a data source or Data at rest.
44
Context Level Diagram For OPD Patient digitisation
2.
1.
Reach Us
OPD Patient Form
3.
5. OPD PATIENT
DIGITISATION Reviews
Sign in
4.
CONTACT US
45
Context Level Diagram For OPD Patient digitization admin panel
2.
CHECK
1. 3.
OPD PATIENT
REDACT DIGITISATION REPORT
ADMIN PANEL
46
DATA FLOW DIAGRAMS
Context Level Diagram for modules of OPD Patient digitisation
USER
Log in
user Administrator
Can get
Home Add Patient Details
About us Edit Records
Contact us
Search Patient
Show Patient
detail
Give
Prepare Crystal
Feedback & Reports
complaints
47
Report Generation
'Crystal Reports' is a popular third party package that is included with ASP.NET, which allows
you to create reports for your application. The package consists of a designer - where you can
design and test the reports, Crystal Reports API calls and Crystal Report Viewer control. The
reports generated by the administrator are
 MenuWise Result
48
TOOLS / PLATFORM, HARDWARE AND SOFTWARE REQUIREMENT
SPECIFICATION
 The project is based on The three tier architecture where the application is divided into three
logical constituents-
 User Services – Provide services such as user interface. (Asp.Net, C#application in
ther case).
 Business services – Implement business rules
 Data Services – Provide handling and validation of data. (SQL-SERVER in ther
case)
 Minimum Hardware requirements

Pentium IV Processor
60 GB hard Disk
512 MB RAM
Optional
Hardware (LAN, Switches, Routers etc)

Networking ((LAN & WAN, Different Components of networking)
 Minimum Software requirements
.Net is used for front end application (ASP.NET, C#, AJAX, JAVA-SCRIPT, J-QUERY and
CSS)
49
50
SCREEN SHOTS
1. OPD Patient Form
51
2. Reach Us
52
3. Reviews
53
4. Contact Us
54
5. Login.aspx
55
6. Login invalid
56
7. Login admin
57
8. Redact
58
9. Check
59
10.Report
60
CODING
61
Patient.aspx.cs
using System;
usingSystem.Configuration;
usingSystem.Data;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.Security;
usingSystem.Web.UI;
usingSystem.Web.UI.HtmlControls;
usingSystem.Web.UI.WebControls;
usingSystem.Web.UI.WebControls.WebParts;
usingSystem.Xml.Linq;
usingSystem.Data.SqlClient;
publicpartialclasspaitent :System.Web.UI.Page
{
SqlConnection con = newSqlConnection();
protectedvoidPage_Load(object sender, EventArgs e)
{
con.ConnectionString = ConfigurationManager.ConnectionStrings["cn"].ConnectionString;
if (con.State == ConnectionState.Closed)
{
con.Open();
}
}
protectedvoid Button1_Click(object sender, EventArgs e)
{
SqlCommandcmd = newSqlCommand();
cmd.CommandText = "insert into paitent values(@pid,@name,@age,@add,@cs,@fu1,@fu2,@fu3)";
cmd.Connection = con;
cmd.Parameters.Add("@pid", SqlDbType.VarChar, 50).Value = pid.Text;
cmd.Parameters.Add("@name", SqlDbType.VarChar, 50).Value = name.Text;
cmd.Parameters.Add("@age", SqlDbType.Int).Value = age.Text;
cmd.Parameters.Add("@add", SqlDbType.VarChar,200 ).Value = address.Text;
cmd.Parameters.Add("@cs", SqlDbType.VarChar, 500).Value = cs.Text;
cmd.Parameters.Add("@fu1", SqlDbType.VarChar, 200).Value = fu1.Text;
cmd.Parameters.Add("@fu2", SqlDbType.VarChar, 200).Value = fu2.Text;
cmd.Parameters.Add("@fu3", SqlDbType.VarChar, 200).Value =fu3.Text;
cmd.ExecuteNonQuery();
cmd.Dispose();
pid.Text = "";
name.Text = "";
age.Text = "";
address.Text = "";
cs.Text = "";
fu1.Text = "";
fu2.Text = "";
fu3.Text = "";
}
62
protectedvoid TextBox4_TextChanged(object sender, EventArgs e)
{
}
}
Aboutus.aspx.cs
using System;
usingSystem.Collections.Generic;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclassAboutus :System.Web.UI.Page
{
{
}
}
Feedback.aspx.cs
using System;
usingSystem.Data;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclassfeedback :System.Web.UI.Page
{
{
63
if (con.State == ConnectionState.Closed)
{
con.Open();
}
}
protectedvoid TextBox4_TextChanged(object sender, EventArgs e)
{
}
{
}
{
cmd.CommandText = "insert into feedback values(@name,@mno,@email,@comment)";
cmd.Parameters.Add("@name", SqlDbType.VarChar, 50).Value = name.Text;
cmd.Parameters.Add("@mno", SqlDbType.VarChar, 200).Value = mno.Text;
cmd.Parameters.Add("@email", SqlDbType.VarChar, 50).Value = email.Text;
cmd.Parameters.Add("@comment", SqlDbType.VarChar, 50).Value = comment.Text;
cmd.Dispose();
name.Text = "";
mno.Text = "";
email.Text = "";
comment.Text = "";
}
}
Contactus.aspx.cs
using System;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclasscontactus :System.Web.UI.Page
{
{
}
}
64
Login.aspx.cs
using System;
usingSystem.Data;
usingSystem.Collections;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclass_Default :System.Web.UI.Page
{
{
}
{
if (TextBox1.Text == "admin"&& TextBox2.Text == "admin")
{
Response.Redirect("edit.aspx");
}
else
{
Label3.Text = "Invaild user name password";
}
}
}
Review.aspx.cs
using System;
usingSystem.Collections;
usingSystem.Data;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
65
publicpartialclassreview :System.Web.UI.Page
{
{
rep_bind();
}
privatevoidrep_bind()
{
SqlDataAdapteradp = newSqlDataAdapter("select * from feedback",
ConfigurationManager.ConnectionStrings["cn"].ConnectionString);
DataSet ds = newDataSet();
adp.Fill(ds);
DataList1.DataSource = ds;
DataList1.DataBind();
}
}
Edit.aspx.cs
using System;
usingSystem.Data;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclassedit :System.Web.UI.Page
{
{
if (Page.IsPostBack == false)
{
grdbind();
}
}
privatevoidgrdbind()
{
SqlDataAdapteradp = newSqlDataAdapter("select * from paitent",
ConfigurationManager.ConnectionStrings["cn"].ConnectionString);
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
66
protectedvoid GridView1_SelectedIndexChanged(object sender, EventArgs e)
{
}
protectedvoid GridView1_RowEditing(object sender, GridViewEditEventArgs e)
{
GridView1.EditIndex = e.NewEditIndex;
grdbind();
}
protectedvoid GridView1_RowCancelingEdit(object sender, GridViewCancelEditEventArgs e)
{
GridView1.EditIndex = -1;
grdbind();
}
protectedvoid GridView1_RowUpdating(object sender, GridViewUpdateEventArgs e)
{
Int32 age;
Stringpid, name, address, cs, fu1, fu2, fu3;
pid = ((Label)(GridView1.Rows[e.RowIndex].FindControl("Label2"))).Text;
name = ((TextBox)(GridView1.Rows[e.RowIndex].FindControl("TextBox1"))).Text;
age =
Convert.ToInt32(((TextBox)(GridView1.Rows[e.RowIndex].FindControl("TextBox2"))).Text);
address = ((TextBox)(GridView1.Rows[e.RowIndex].FindControl("TextBox3"))).Text;
cs = ((TextBox)(GridView1.Rows[e.RowIndex].FindControl("TextBox4"))).Text;
fu1 = ((TextBox)(GridView1.Rows[e.RowIndex].FindControl("TextBox5"))).Text;
con.Open();
cmd.CommandText = "update paitent set
name=@name,age=@age,address=@address,ch=@cs,fu1=@fu1,fu2=@fu2,fu3=@fu3 where pid=@pid";
cmd.Parameters.Add("@pid", SqlDbType.VarChar, 50).Value = pid;
cmd.Parameters.Add("@name", SqlDbType.VarChar, 50).Value = name;
cmd.Parameters.Add("@age", SqlDbType.Int).Value = age;
cmd.Parameters.Add("@address", SqlDbType.VarChar, 200).Value = address;
cmd.Parameters.Add("@cs", SqlDbType.VarChar, 500).Value = cs;
cmd.Parameters.Add("@fu1", SqlDbType.VarChar, 50).Value = fu1;
cmd.Dispose();
GridView1.EditIndex = -1;
grdbind();
}
protectedvoid GridView1_RowDeleting(object sender, GridViewDeleteEventArgs e)
{
stringpid;
pid = ((Label)(GridView1.Rows[e.RowIndex].FindControl("Label1"))).Text;
con.Open();
cmd.CommandText = "delete from paitent where pid=@pid";
cmd.Parameters.Add("@pid", SqlDbType.VarChar, 50).Value = pid;
cmd.Dispose();
67
grdbind();
}
}
Search.aspx.cs
using System;
usingSystem.Data;
usingSystem.Linq;
usingSystem.Web;
usingSystem.Web.UI;
publicpartialclasssearch :System.Web.UI.Page
{
{
}
privatevoidgrdbind()
{
SqlDataAdapteradp = newSqlDataAdapter("select * from paitent where name='" +

TextBox1.Text + "'", ConfigurationManager.ConnectionStrings["cn"].ConnectionString);
adp.Fill(ds);
GridView1.DataSource = ds;
GridView1.DataBind();
}
{
grdbind();
}
}
68
TESTING PHASE
69
The basic goal of the software development process is to produce software that has no errors or
very few errors. In an effort to detect errors soon after they are introduced, each phase ends with
verification activity such as a review.
As testing is the last phase before the final software is delivered, it has the enormous
responsibility of detecting any type of error that may in the software. A software typically
undergoes changes even after it has been delivered. And to validate that a change has not
affected some old functionality of software regression testing is performed
LEVELS OF TESTING
The basic levels of testing are unit testing, integration testing and system and acceptance testing.
These different levels of testing attempt to detect different types of faults.
Figure: Table Of Level Of Testing
Client Needs Acceptance Testing

Requirements System Testing
Design Integration Testing
Code Unit Testing
ACCEPTANCE TESTING
Acceptance Testing is system testing performed by the customer to determine whether or not to
accept the delivery of the system.
SYSTEM TESTING
System tests are designed to validate fully developed system with a view to assuring that it meets
its requirements. There are essentially two kinds of system testing.
 Alpha Testing: Alpha Testing refers to the system testing that is carried out by the team
within the organization.
 Beta Testing: Beta Testing is the testing performed by the group of friendly customer.
INTEGRATION TESTING
70
During integration testing, different modules of a system are integrated using an integration plan.
The plan specifies the steps and the order in which the modules are combined to realize the full
system. After each integration step, the partially integrated system is tested. The primary
objective of the integration testing is to test the module interfaces. An important factor that
guides the integration plan is the module dependency graph. Various approaches to the
integration testing are given below:
 Top Down Approach
 Bottom Up Approach
Top Down Integration Testing: Top-down integration testing starts with the Patient routine i.e.
the root module, and one or two sub module are added. After the top level skelton has been
tested, the subroutine of the skelton are immediately combined and tested. Ther type of testing
requires the use of program stubs to simulate the effect of lower-level routines that are called by
the routines under test. A disadvantage of ther approach is if the sub-module is not ready than the
whole process slow down.
Bottom-Up Integration Testing:In bottom-up testing each subsystem is tested separately and
then the full system is tested. A subsystem might consist of Patient modules which communicate
among each other through well defined interfaces. The primary purpose of the each subsystem is
to test the interfaces among various modules making up a subsystem. Both control and data
interfaces are tested.
UNIT TESTING
Unit testing is the testing of the different modules in the isolation. Testing a program consists of
providing the program, a set of test inputs and observing the working of the program. If the
program fails to behave as expected, then the condition under which a failure occur are noted for
debugged and corrected.
71
72
SYSTEM IMPLEMENTATION
As we know, creating software is one thing and the implementation of the created software is
another. The process of implementing software is much difficult as compared to the task of
creating the project. First we have to implement the software on a small scale for removing the
bugs and other errors in the project and after removing them we can implement the software on a
large scale.
Before we think in terms of implementing the Software on a large basis, we must consider the
Hardware requirements.
Whenever we develop software or project a certain hardware and software is being used by the
programmer for developing the project. The hardware and software to be used by the
programmer for developing the project should be such that it would result in the development of
a project, which would satisfy all the basic needs for which the project has been created by the
programmer. The Hardware should be such that cost constraints of the Client should also be
taken into account without affecting the performance.
HARDWARE EVALUATION FACTORS
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 Patient 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 making a
technology evaluation. The factor of ergonomics is also very important. Ergonomics is the science
and technology that tries to ensure that computer and other technologies are "user-friendly", that is
safe, comfortable and easy to use. Connectivity is another important evaluation factor, since so
Patient computer systems are now interconnected within wide area or local area telecommunications
networks.
73
Hardware Evaluation Factors:-
1) Performance
2) Cost
3) Reliability
4) Availability
5) Compatibility
6) Modularity
7) Technology
8) Ergonomics
9) Connectivity
10) Environmental requirements
11) Software
12) Support
SOFTWARE EVALUATION FACTORS
Software can be evaluated according to Patient factors similar to the hardware evaluation. Thus
the factors of performance, cost, reliability, compatibility, modularity, technology, ergonomics,
and support should be used to evaluate proposed software acquisitions. In addition, however,
the software evaluation factors are summarized in below figure. For e.g. some software
packages require too much memory capacity and are notoriously slow, hard to use, or poorly
documented. They are not a good selection for most end users, even if offered at attractive
prices.
74
SOFTWARE EVALUATION FACTORS
1. EFFICIENCY: is the software a well-written system of computer instructions that
does not use much memory capacity or CPU time?
2. FLEXIBILITY: can it handle its processing assignments easily without major
modifications?
3. SECURITY: does it provide control procedures for errors, malfunctions and
improper use?
4. LANGUAGE: do our computer programmers and users write it in a programming
language that is used?
5. DOCUMENTATION: is the s/w well documented? Does it include helpful user
instructions?
6. HARDWARE: does existing hardware have the features required to best use ther
software?
7. Other characteristics of hardware such as its performance, what about the cost, how
much is reliable and etc.
CONVERSION AND TRAINING
An important aspect of is to make sure that the new design is implemented to establish standards.
The term implementation has different meanings, ranging form the conversion of a basic
application to a complete replacement of a computer system. Implementation is used here to
Patient the process of converting a new or revise system into an operational one. Conversion is
one aspect of implementation. Conversion means changing form one system to another. The
objective is to put the tested system into operation while holding costs, risks, and personnel
irritation to a minimum. It involves creating computer-compatible files, training the operation
staff, and installing terminal and hardware. A critical aspect of conversion is not disrupting the
functioning of the organization.
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 personnel to
work the new system. Running any specified system at an organization does require some or
other hardware or, in ther case, software requirement as well.
75
Conversion is one aspect of implementation review & software maintenance.
There are three types of implementation:

1. Implementation of a computer system to replace a manual system. The problems
encountered are converting files, training users, creating accurate files and verifying
printouts for integrity.
2. Implementation of a new computer system to replace an existing one. Ther is usually a
difficult conversion. If not properly planned there can be Patient problems. Some large
computer systems have taken as long as year to convert.
3. Implementation of a modified application to replace an existing one, using the same
computer. Ther type of conversion is relatively easy to handle, provided there are no
major changes in the files.
76
77
SYSTEM MAINTENANCE
Once the website is launched, it enters the maintenance phase. All systems need maintenance.
Maintenance is required because there are often some residual errors remaining in the system
that must be removed as they are discovered. Maintenance involves understanding the effects of
the change, making the changes to both the code and the documents, testing the new parts and
retesting the old parts that were not changed. Maintenance is mainly of two types:
1. Corrective Maintenance
2. Adaptive Maintenance
CORRECTIVE MAINTENANCE
Almost all software that is developed has residual errors or bugs in them. Patient of these
surfaces only after the system have been in operation, sometimes for a long time. These errors
once discovered need to be removed, leading to the software to be changed. Ther is called
Corrective Maintenance.
ADAPTIVE MAINTENANCE
Even without bugs, software frequently undergoes change. The software often must be upgraded
and enhanced to include more features and provide more services. Ther requires modification of
the software. Ther type of maintenance is known as the Adaptive Maintenance
78
CONCLUSION
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. Ther results in errors. The number and nature
of errors in a new design depends on several factors:
 Communication between the user and the designer.

 Personal prejudice on the part of users in disclosing information.
 The programmer’s ability to generate code that reflects exactly the system specifications.
 The time frame for the design.
In the “OPD PATIENT DIGITISATION”,I have tried my best to cover successfully and
accurately all the requirements of the project.
79
BIBLIOGRAPHY
 ASP.NET 4 in C# By Anshuman
 C# Development by Rob Miles
 Beginning SQL Server 2008 R2 for developers by Robin Dewson
 C# for Dummies by Stephen Randy Davis and Chuck Sphar
 Beginning with ASP.NET by ImarSpaanjaars
 Software Engineering By Roger S. Pressman
 ASP.NET Bible by MridulaParihar
 SQL for Dummies By Allen G. Taylor
 The Complete Reference Visual Basic .NET by Jeffery R. Shapiro
80

X-20861717509-20861717515 OPD Patient Digitisation Sonia Devi Sunana MSC It 2019

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

X-20861717509-20861717515 OPD Patient Digitisation Sonia Devi Sunana MSC It 2019

Uploaded by

Copyright:

Available Formats

Project Report

OPD PATIENT DIGITISATION

Submitted in partial fulfillment of the requirements for the award of degree of

MSC (INFORMATION TECHNOLOGY)

SHANTI DEVI ARYA MAHILA COLLEGE

Submitted To:- Submitted By:

Miss. Sanjana SONIA DEVI (20861717515)

Assistant Prof. SUNANA (20861717509)

Dept.Of Computer Science

DEPARTMENT OF COMPUTER SCIENCE

SONIA DEVI (20861717515)

SDAM COLLEGE, DINANAGAR

SONIA DEVI (20861717515)

S.No Topic Page

2  Technologies Used 13-24

3  Hardware And Software Requirements 25

Patient Management System is an application developed in ASP.NET

The proposed ASP.NET project is a four-modules project: patient records

Pharmacy Management is designed to store the details of medicine regarding batch

Doctors Management Module is developed to maintain the details of doctors and

DRAWBACKS OF EXISTING SYSTEM

 More man power.

The aim of proposed system is to develop a system of improved facilities. The

Expected Advantages of Proposed System

 Ensure data accuracy’s.

Key Features Are:

 No Paper Work Required

 Automatic data validation

 User friendly environment

 Data security and reliability

 Fast data insertion & retrieval

 Maintaining records of Patient

 Crystal Report generation

DRAWBACKS OF CURRENT MANUAL- SYSTEM

 The current manual system has a lot of paper work

 To maintain the records of Patientmanually, is a Time-consuming job.

 The retrieval of records of Patientwillbe a tedious job.

2. Problem of Accuracy: There are too Patientmistakes in reports.

3. Registers: There is no need of keeping and maintaining records and information

7. Reduces redundancy:The most important benefit of ther system is that it reduces

Decentralization: Facilitates Scalability and Robustness.

The .NET Framework

 A set of technologies for developing and using components to create:

The .NET Framework Base Classes or the .NET Class Framework

 Provides the following features:

Some advantages of the .NET Framework are:

ADO .NET Data Access

Components of a Data Provider

o Is a SQL statement or a stored procedure that is used to retrieve, insert, delete, or

o Is a disconnected, cached set of records that are retrieved from a database.

VISUAL C# (Language Used for coding)

FEATURES OF SQL SERVER 2008:

HARDWARE REQUIREMENTS FOR SERVER:

 Processor 500MHz (minimum)

 Hard Disk 1000 GB

HARDWARE REQUIREMENTS FOR CLIENT:

 Hard disk 500 GB

 Visual Studio 2010

 SQL Server 2008 R2

 Browser like Internet Explorer, Mozilla, Opera

REVIEW RUNNING DETERMINATION OF

SYSTEM DESIGN OF SYSTEM

FIG: SYSTEM DEVELOPMENT LIFE CYCLE