PRJ/2013/IT/13 System Analysis

C.S.P.I.T 34 Department of Information-Technology

System
ANALYSIS






4
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 35 Department of Information-Technology




4.1 Study of Current System
The current system lacks some of the features which are necessary for providing additional
functionalities in improving the Health-Care System.
Currently, different departments in the health-care center have their own separated System,
leading to the lack of communication in the hospitals and the inefficient data sharing to the
government.

While each system serves a distinctive purpose, there is no coordinating, assimilating and
representing of data.

The systems may have duplicate data which is a waste of space. The different systems also
may have different application programs which cause incompatible files.

Existing Systems are not based on the UNIQUE ID (i.e Aadhar Card) System. The Doctors
cannot view the patient history in the current system and the government is not being
provided proper health-care data so that it can take required steps to improve the health-care
in the country.

4.2 Weakness of Current System
Hardware Constraints
The system requires a database in order to store persistent data. The database should have
backup capabilities.
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 36 Department of Information-Technology



Software Constraints
The development of the system will be constrained by the availability of required software
such as servers, database and development tools.
User Side, will need internet explorer 7.0 or above and Mozilla Firefox
Also the following two are major usage constraints:
There will be training involved in using Server Management Studio and Microsoft Visual
Studio 2010, and someone (usually at least one person, but sometimes more) in Users
organization must become the webmaster who operates the system, understands it, and
carves time in their workload to manage it.
Non-technical members can view content on the website. No HTML experience or
graphics experience is necessary. If some error may occur in system, Non-technical
members may not find out or judge the faults.

4.3 Feasibility Study
A feasibility analysis usually involves a thorough assessment of the operational (need),
financial and technical aspects of a proposal. Feasibility study is the test of the system
proposal made to identify whether the user needs may be satisfied using the current software
and hardware technologies, whether the system will be cost effective from a business point of
view and whether it can be developed with the given budgetary constraints. A feasibility
study should be relatively cheap and done at the earliest possible time. Depending on the
study, the decision is made whether to go ahead with a more detailed analysis.

When a new project is proposed, it normally goes through feasibility assessment. Feasibility
study is carried out to determine whether the proposed system is possible to develop with
available resources and what should be the cost consideration. Facts considered in the
feasibility analysis were.
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 37 Department of Information-Technology




4.3.1 Technical Feasibility
Technical Feasibility deals with the hardware as well as software requirements. Technology
is not a constraint to type system development. This evaluation determines whether the
technology needed for the proposed system is available or not. The technical feasibility
issues usually raised during the feasibility stage of investigation includes these

Can the work for the project be done with current equipment existing software technology
& available personnel?

The answer is yes. This system can be developed in Windows 7, the current operating system
used by the developers.

Can the system be upgraded if developed?

If new technology is needed then what can be developed?

Yes. The system can be expanded.

This is concerned with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable front-end and
back-end. When user decided to develop the project user went through an extensive study to
determine the most suitable platform that suits the needs of the organization as well as helps
in development of the project.

PRJ/2013/IT/13 System Analysis


C.S.P.I.T 38 Department of Information-Technology








The aspects of our study included the following factors.


Front-end selection:

1. It must have a graphical user interface that assists users that are not from IT background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Front end must support some popular back end like MS SQL Server.

According to the above stated features user selected Visual Studio 2010 as the front-end for
developing our project.

Back-end Selection:
1. Multiple user support.
2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 39 Department of Information-Technology



7. Operating System compatible.
8. Easy to install.
9. Easy to implant with the Front-end.

According to above stated features user selected MS SQL Server 2008 as the backend.
4.3.2 Economical Feasibility
This feasibility study presents tangible and intangible benefits from the prefect by comparing
the development and operational cost. The technique of cost benefit analysis is often used as
a basis for assessing economic feasibility. This system needs some more initial investment
than the existing system, but it can be justifiable that it will improve quality of service.

Thus feasibility study should center along the following points:
Improvement resulting over the existing method in terms of accuracy, timeliness.
Cost comparison.
Estimate on the life expectancy of the hardware
Overall objective
Our project is economically feasible. It does not require much cost to be involved in the
overall process. The overall objectives are in easing out the requirement processes.

4.3.3 Operational Feasibility

It is mainly related to human organizations and political aspects. The points to be
considered are:
What changes will be brought with the system?
What organization structures are disturbed?
What new skills will be required? Do the existing staff members have these
skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the end users to operate it.
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 40 Department of Information-Technology



Besides, the new proposed system is very much useful to the users and therefore it
will be readily accepted by its targeted market.

4.3.4 Schedule Feasibility

Time evaluation is the most important consideration in the development of project.
The time schedule required for the developed of this project is very important since
more development time effect machine time, cost and cause delay in the
development of other systems.

A reliable Health-Care System can be developed in the considerable amount of
time.
Time-Line chart for the proposed system is as follows:




Figure 4.1 Time-line Chart (in weeks)
0.0 0.5 1.0 1.5 2.0 2.5 3.0
Documentation
Implementing
Testing
Coding
Design
Analysis
Understanding
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 41 Department of Information-Technology



4.3.5 Requirement Validation:


Requirement validation checks a requirements document for Completeness and consistency,
conformance to standards, requirements conflicts, technical errors and ambiguous
requirements. Here the key question to be asked was, Whether the requirement user got was
right?


The outputs and inputs which were analyzed during the requirement gathering stage was
again validated for no ambiguity.

The user requirements include the following things:
1. The application should be collaborative and cost effective.
2. The application should be able to run upon high traffic.
3. The application should display the selected column of the selected grid view in
different color.
4. The application should display error message in the form of label.
5. The additional information of the application and its know-how should be accessible
to the user.
6. The application should provide information regarding how to generate reports of
Patient.

PRJ/2013/IT/13 System Analysis


C.S.P.I.T 42 Department of Information-Technology




4.4 SystemStudy


Start
Login
Master-Admin
Institute-
Admin
Doctor
View,register
,Delete
Citizen
Add,update,
Delete
Institute
End
Register,View,
Delete
Doctor
View Patient
Report
Treat Patient
and
View Pat-Details
Generate
Patient
Reort

Figure 4.2 Flow-chart of the System
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 43 Department of Information-Technology



4.5 Features of New System.

Based on Aadhar Card:
Whole Registration Process can be done through the Aadhar-card.
Patients Previous Medical history can also be viewed.
Government is provided proper medical data about citizen so that it can take
efficient steps in improving health care of the country.


User Management (admin):
Easily manage existing and new users and assign them user credentials by
accessing the main user database.

Medical-Report Generation:
Medical report of the patient can be generated after its treatment which is
helpful for further medical treatment of patient.












PRJ/2013/IT/13 System Analysis


C.S.P.I.T 44 Department of Information-Technology



4.5.1 Modules of the System.

Master-Admin
Register, View, Update and Delete Citizen.
Register, View Update and Delete Institute.
Sort out Reports based on date, month, year and institute.

Institute-Admin:

View Patient.
Register, View, Update and Delete Doctor.
Sort out Reports based on date, month and year.

Doctor:

View Patient Report and its Previous Medical History.
Generate Patient Report.

Report-Generation:

Efficient Development of Patients Medical Report.







PRJ/2013/IT/13 System Analysis


C.S.P.I.T 45 Department of Information-Technology





4.6 Data Flow Diagrams :

1. Context- Level Diagram:



0.0
Health-Care System
0.0
Health-Care System
Uname
Password
Doctor
Services,
Report-Generation
Matser-
Admin
Controls n
Manages Data
Institute
Admin
U-name
Password
Add,update,delete
Institute and citizen


Figure 4.3 Context Diagram




PRJ/2013/IT/13 System Analysis


C.S.P.I.T 46 Department of Information-Technology



2. Level-1 Diagram:
0.1
Login
Master_Login
Password
Username User-Type Select
user type
0.3
Inst-Admin
Type=Inst-admin
Login details
0.4
Doctor
Type=Doctor
Citizen_Reg
Patient-info
Inst-info
Institue_master
0.5
Report-
Generation
Doctors prescription
Patient-Report
Report-details
0.2
Master-
Admin
Type=Master-Admin
Inst-info
Add,update,
View institute
Add,update,delete
Citizen-info
Add,Update,
View Citizen
Add,update,view
Register,View,
Delete
Doctor
Register,view,delete

Figure 4.4 1
st
Level Diagram
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 47 Department of Information-Technology



3. Level-2 for Institute:

0.2
Master-
Admin
Add,Update,Delete
0.2.1
Add
institute
0.2.2
Update
institute
0.2.3
Delete
institute
Update
Add
Delete
Institue_Master
Institute-Info
Institute-Info
Institute-Info


Figure 4.5 2
nd
Level DFD for Institue



PRJ/2013/IT/13 System Analysis


C.S.P.I.T 48 Department of Information-Technology



4. Level-2 for Citizen:



0.2
Master-Admin
Add,Update,View
0.2.4
Add
citizen
0.2.5
Update
citizen
0.2.6
View
Citizen
Update
Add
view

Citizen_Reg
citizenr-Info
Citizen-Info
Citizen-Info


Figure 4.6 2
nd
Level DFD for Citizen
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 49 Department of Information-Technology




5. Level-2 for Doctor:

0.3
Institute-Admin
Add,Update,View
0.3.1
Add
Doctor
0.3.2
Update
Doctor
0.3.4
View
Doctor
Update
Add
view
Doctor_Master
Doctor-Info
Doctor-Info
doctor-Info



Figure 4.7 2
nd
Level DFD for Doctor
PRJ/2013/IT/13 System Analysis


C.S.P.I.T 50 Department of Information-Technology




6.Level- 3 Add Institute:



0.2.1
Add institute
Institue-
info
0.2.1.2
Verification
0.2.1.2
Verification
Verify
Institute
Institute_master
Verified
Institute
Institue-Id
Already
Exists


Figure 4.8 3
rd
Level DFD for Institute Add





PRJ/2013/IT/13 System Analysis


C.S.P.I.T 51 Department of Information-Technology




7.Level-3 institute Update:


0.2.2
Update
Institute
0.2.2.1
Verification
0.2.2.1
Verification
Institute_master
Verify
Updatable-info
Institute-info
Not-Verified
Updatable-info
Retrieve
Institute-info
Verified



Figure 4.9 3
rd
Level DFD for Institute Update




PRJ/2013/IT/13 System Analysis


C.S.P.I.T 52 Department of Information-Technology



8.Level-3 Add Citizen:



0.2.4
Add
Citizen
0.2.4.1
Verification
0.2.4.1
Verification
Verify
Citizen
Citizen
Info
Citizen_Reg
Citizen-info
Verified
Not-Verified




Figure 4.10 3
rd
Level DFD for Citizen Add




PRJ/2013/IT/13 System Analysis


C.S.P.I.T 53 Department of Information-Technology




9. Level-3 Update Citizen:



0.2.5
Update
Citizen
0.2.5.1
Verification
0.2.5.1
Verification
Citizen_Reg
Verify
Updatable-info
Verified
Updatable-info
Retrieve
Citizen-info
Citizen-info
Not-Verified


Figure 4.11 3
rd
Level DFD for Citizen Update





PRJ/2013/IT/13 System Analysis


C.S.P.I.T 54 Department of Information-Technology





10. Level-3 Add Citizen :




0.3.1
Add
Doctor
0.3.1.1
Verification
0.3.1.1
Verification
Verify
Doctor
Doctor
Info
Doctor_Master
Doc-info
Verified
Not-Verified



Figure 4.12 3
rd
Level DFD for Doctor Add


PRJ/2013/IT/13 System Analysis


C.S.P.I.T 55 Department of Information-Technology




11. Level-3 Update Doctor :



0.3.2
Update
Doctor
0.3.2.1
Verification
0.3.2.1
Verification
Doctor_Master
Verify
Updatable-info
Verified
Updatable-info
Retrieve
Doctor-info
Doctor-info
Not-Verified


Figure 4.13 3
rd
Level DFD for Doctor Update