Professional Documents
Culture Documents
INTRODUCTION
1
1.2 Organizational profile
2
2. SYSTEM ANALYSIS
2.1 Introduction
. Existing system refers to the system that is being followed till now.
Presently all the hospital functionalities are done manually. That is if a
patient want to consult a doctor he can visit their till his chance called. This
is make the person very difficult. Out_Patient and In_Patient tickets are
distributed directly. The main disadvantage is time consuming.
3
2.2.1 LIMITATIONS OF EXISTING SYSTEM
To avoid all these limitations and make the system working more
accurately it needs to be computerized.
4
is very simple in design and to implement. The system requires very low
system resources and the system will work in almost all configurations.
The main objectives of the proposed system can be enumerated as follows:
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.
Security of data.
5
FEASIBILTY STUDY
Technical Feasibility
Economic Feasibility
Behavioral Feasibility
6
2.4.1 TECHNICAL FEASIBILITY
This analysis involves how it will work when it is installed and the
assessment of political and managerial environment in which it is
implemented. People are inherently resistant to change and computers have
been known to facilitate change. The new proposed system is very much
useful to the useful to the users and there for it will accept broad audience
from around the world.
7
3. SOFTWAREREQUIREMENT SPECIFICATIONS
Monitor : VGA/SVGA
8
3.3 LANGUAGE REQUIREMENT
Visual Basic 6.0 is more than just a programming language; the secret
to Visual Basic is in its name” Visual”. With to days Windows Operating
System, a program must be able to interact with the screen. Keyboard,
mouse and printer graphically.
9
Hence a Visual Basic application is a combination of object like forms and
controls, procedures that can respond to Events and other general-purpose
procedures.
10
Following is the sequence of events in an event driven applications.
b) The form (or a control on the form) receives an event. The event
might be caused by the user (For example, a key stroke), by the
system (For example, a timer event), or indirectly by your code.
5. Data Management
6. Online Help
7. Data Access.
11
3.3.2 MICROSOFT ACCESS
Microsoft Access
12
develop application software. Relatively unskilled programmers and non-
programmer "power users" can use it to build simple applications. It
supports some object-oriented techniques but falls short of being a fully
object-oriented development tool.
13
(file-based database engine, used in Access by default), Microsoft SQL
Server, Oracle, and any other ODBC-compliant product.
Features
Unlike a modern RDBMS, the Access and the Jet Engine implements
database triggers and stored procedures in a non-standard way. Stored
Procedures are implemented in VBA, and Triggers are only available from
embedded Forms. Both Triggers and Stored procedures are only available to
applications built completely within the Access database management
system. Client applications built with VB or C++ are not able to access these
features. Starting in MS Access 2003 (Jet 4.0), there is a new syntax for
creating queries with parameters, in a way that looks like creating stored
procedures, but these procedures are still limited to one statement per
procedure. Microsoft Access does allow forms to contain code that is
triggered as changes are made to the underlying table (as long as the
modifications are done only with that form) and it is common to use pass-
14
through queries and other techniques in Access to run stored procedures in
RDBMSs that support these.
SYSTEM DESIGN
INTRODUCTION
15
Design of a system can be defined as a process of applying various
techniques and principles for the purpose of defining a device, a process or a
system in sufficient detail to permit its physical realization. Thus system
design is a solution to “how to” approach to the creation of a new system.
Thus important phase provides the understanding and the procedural details
necessary for implementing the system recommended in the feasibility
study. The design step provides a data design, architectural design, and a
procedural design.
16
Also the important input format is designed in such a way that
accidental errors are avoided. The user has to input only just the minimum
data required, which also helps in avoiding the errors that the users may
make. Accurate designing of the input format is very important in
developing efficient software. The goal or input design is to make entry as
easy, logical and free from errors.
17
4.3 DATABASE DESIGN
Controlled redundancy
Easy to learn and use
More information and low cost
Accuracy
Integrity
The database file used in the system is :
This table stores the details about the login .User login table contains the
fields username and password.
18
Table Name: Admin Registration
This table stores the details about the admin .Admin registration table
contains the fields username and password.
This table stores the details about the user registration. The User
Registration table contains the fields.
19
Table Name: Doctor Registration
This table stores the details about the doctor registration. The Doctor
Registration table contains the fields.
20
Table Name: Patient Details
This table stores the details about the Patient. The Patient Details table
contains the fields.
This table stores the details about the medicine. The Medicine table contains
the fields.
21
Table Name: Discharge Sheet
This table stores the details about the discharge. The Discharge Sheet table
contains the fields.
This table stores the details about the Blood donors. The Blood Bank table
contains the fields.
22
Table Name: Eye Bank
This table stores the details about the eye donors. The Eye Bank table
contains the fields.
23
4.4 DATA FLOW DIAGRAM
CONTEXT DIAGRAM
Administrator User
24
Level 1 DFD Administrator
Administrator
Login
25
Level 1 DFD User
User
Login
26
Patient Registration
User
IP/ OP Search
Login Details IP/OP
Report Generation
Add Medicine
Medicine
Change Password
User
TPL
TPL
Login Details
Add/Edit /View Doctor
Doctor
Login
Add /Edit/ View New Departments
Departments
Rooms
TPL
TPL
Eyebank
28
4.5 SYSTEM STRUCTURE CHART
Login
Digital Signage
System Tray
Bill
29
4.7 GANTT CHART
System
study
Design
database
part
Design forms
Code for
application
Code database
part
30
6. SYSTEM TESTING
The first level of test is unit testing. The purpose of unit testing is to
ensure that each program is fully tested.
The second step is integration testing. In this individual program units
or programs are integrated and tested as a complete system to ensure that the
software requirements are met.
Acceptance Testing involves planning and the execution of various
types of tests in order to demonstrate that the implemented software system
satisfies the requirements. Finally our project meets the requirements after
going through all the levels of testing.
31
7.IMPLEMENTATION AND MAINTENANCE
32
System Implementation
Careful planning.
33
System Maintenance
After the installation phase is completed and the user is adjusted to the
changes created by the new system,evaluation and maintenance is to
continue to bring the new system to the standards. If the new information is
consistent with the design specification,changes have to be
made.Maintenance is actually the implementation of the post
implementation review plan.
34
8.CONCLUSION
35
9.FUTURE ENHANCEMENT
36
10.BIBLIOGRAPHY
Books
www.associatedcontent.com
www.members.tripod.com
www.vbcodesource.com
11. APPENDIX
37
11.1 Screen layouts
Login
Doctor Registration
38
39
Edit Doctor
40
Add Rooms
41
Room Allocations
Patient Registration
42
43
Doctor Search
44
IP Billing
OP Billing
45
Lab Billing
46
Pharmacy Billing
47
48