"Railway Management System": Submitted in Partial Fulfillment For The Award of The
"Railway Management System": Submitted in Partial Fulfillment For The Award of The
"Railway Management System": Submitted in Partial Fulfillment For The Award of The
SYSTEM”
Submitted in partial fulfillment for the award of the
1
1. INTRODUCTION
2
1.2 Organizational profile
3
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.
4
2.2.1 LIMITATIONS OF EXISTING SYSTEM
To avoid all these limitations and make the system working more
accurately it needs to be computerized.
5
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.
6
FEASIBILTY STUDY
Technical Feasibility
Economic Feasibility
Behavioral Feasibility
7
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.
8
3. SOFTWAREREQUIREMENT SPECIFICATIONS
Monitor : VGA/SVGA
9
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.
10
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.
11
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.
12
3.3.2 MICROSOFT ACCESS
Microsoft Access
13
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.
14
SYSTEM DESIGN
INTRODUCTION
15
4.1 INPUT DESIGN
In the input design, user-oriented inputs are converted into a computer
based system format. It also includes determining the record media, method
of input, speed of capture and entry on to the screen. Data entry accepts
commands and data through a keyboard. The major approach to input design
is the menu and the prompt design. In each alternative, the user’s options are
predefined. The data flow diagram indicates logical data flow, data stores,
source and destination. Input data are collected and organized into a group of
similar data. Once identified input media are selected for processing.
16
4.2 OUTPUT DESIGN
17
and flexible for other users. During database design, the following objectives
are concerned:-
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.
This table stores the details about the admin .Admin registration table
contains the fields username and password.
18
Table Name: User Registration
This table stores the details about the user registration. The User
Registration table contains the fields.
This table stores the details about the doctor registration. The Doctor
Registration table contains the fields.
19
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.
This table stores the details about the discharge. The Discharge Sheet table
contains the fields.
20
Field Name Data Type Description
Patient id Double Patient id
Name Text Name
Doctor Text Doctor
Remark Text Remark
Totbill Double Total Bill
Date Date/Time Date
This table stores the details about the Blood donors. The Blood Bank table
contains the fields.
This table stores the details about the eye donors. The Eye Bank table
contains the fields.
21
4.4 DATA FLOW DIAGRAM
CONTEXT DIAGRAM
Advanced Hospital Management System
Controls Overall Data Add/Edit/Delete Data
Administrator User
Administrator
Login
22
Level 1 DFD User
Patient Registration
User
User
IP/ OP Search
Login Details IP/OP
Hospital Management Process
Hospital Database
Login Details
Login Doctor Search
Doctors
Login
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
24
4.5 SYSTEM STRUCTURE CHART
Login
Digital Signage
System Tray
Bill
25
4.7 GANTT CHART
System
study
Design
database
part
Design forms
Code for
application
Code database
part
26
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.
7.IMPLEMENTATION AND MAINTENANCE
27
System Implementation
Careful planning.
28
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.
8.CONCLUSION
29
computerization of the system has sped up the process. In the current
system, the front office managing is very slow. The hospital managing
system was thoroughly checked and tested with dummy data and thus is
found to be very reliable.
30
9.FUTURE ENHANCEMENT
31
10.BIBLIOGRAPHY
Books
www.associatedcontent.com
www.members.tripod.com
www.vbcodesource.com
32