System Analysis and Design for Khoo Teck Puat Hospital

This document provides a system analysis and design for Khoo Teck Puat Hospital, including the organization's main business goals, flow chart of the main business process, identification and description of class, comparison of system acquisition, objectives of the project, feasibility study, system requirements, use case, and conceptual model.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Introduction to the Organization:...........................................................................................2
2. Main Business Goals:.............................................................................................................2
3. Flow Chart of the Main Business Process:............................................................................3
4. Identification and Description of Class:.................................................................................4
5. Comparison of System Acquisition:......................................................................................5
6. Objectives of the Project:.......................................................................................................6
7. Feasibility Study:...................................................................................................................6
8. System Requirements:............................................................................................................7
9. Use Case:................................................................................................................................9
10. Conceptual Model:...............................................................................................................9
10.1 Story Board:...................................................................................................................9
10.2 Hardware, Software and Network Component:...........................................................10
Bibliography:............................................................................................................................11

2SYSTEM ANALYSIS AND DESIGN
1. Introduction to the Organization:
The selected organization is the Khoo Teck Puat Hospital. This hospital is based
located in Singapore. It is a very well-known healthcare organization in its locality. The
hospital was founded in June 2010. Most of the patients of Khoo Teck Puat Hospital are from
northern region of Singapore. The organization provide a very high quality of personalized
care along with the standard medical expertise. Khoo Teck Puat Hospital believes in
maintaining a very healing atmosphere throughout the hospital. Communication with the
patient on frequent basis is considered a very high factor in organization growth in Khoo
Teck Puat Hospital. The best part of the Khoo Teck Puat Hospital is that all the services that
this healthcare organization provides to the patients are hassle-free.
The number of patients of the organization is rapidly increasing every month. The
organization is currently striving to manage the data and internal processes because they use
spreadsheets and paper. The organization is willing to implement a system that can allow
managing back processes automatically. Khoo Teck Puat Hospital also need a database
management system that can run parallel with the management system to store, retrieve and
manipulate data efficiently and accurately.
2. Main Business Goals:
The main business goals of Khoo Teck Puat Hospital are as following.
i. Creating great reputation
ii. Providing better medical services
iii. Making the existing patients more loyal to the hospital
iv. Implementing efficient and accurate processes
v. Continuous improvement in the organization services

3SYSTEM ANALYSIS AND DESIGN
3. Flow Chart of the Main Business Process:
Figure 1: Flowchart of Khoo Teck Puat Hospital Medical Treatment Process
(Source: Created by Author)
The flowchart shows the process of providing medical treatment to the patients. The
flow chart starts and ends by following the conventional method. The flowchart shows that
the general physician will first see the patient and identify the dieses the patient have. If the

4SYSTEM ANALYSIS AND DESIGN
case is critical then the general physician will refer the patient to a surgeon. In other case, the
general doctor will prescribe some medicines to the patient. The general physician will first
prescribe some tests to the patient. If the test results are against patient health and patient
need urgent medical treatment then the patient is admitted to the hospital. On the other hand,
if the case is not under the category of emergency then the patient will be prescribed some
medicines and released. The admitted patients will also get released once the recover,
otherwise surgeon will again prescribe some more tests.
4. Identification and Description of Class:
Person: The person is the superclass of patient class and staff class. The person class
holds the information of the details of any general person can have like the name, gender,
date-of-birth, address, phone and many more.
Hospital: The hospital class is for storing the details of the owner of the system. It
only holds the data like the name, address and phone number.
Department: The hospital has many departments and each department has different
purpose. Class diagrams shows the head of the department who is an employee.
Patient: The person who gets medical assistance from hospital.
Staff: The person who works for the hospital. The staff has doctor, nurse,
administrative staff and technical staff.

5SYSTEM ANALYSIS AND DESIGN
Figure 2: Class Diagram of Khoo Teck Puat Hospital System
(Source: Created by Author)
5. Comparison of System Acquisition:
External Sources: The hospital can acquire a system from outside of the
organization, mainly from a third party organization. The outsourcing of information systems
is becoming more popular because the cost of the development is less and the customer
organization does not have to invest any effort. The outsourcing of the systems are done
through the cloud based environment. In external source acquisition method, the outsourcing
organization provides the human and other resources required for system development. The
client organization signs a service level agreement with the third party organization for
declaring various services related concerns and conditions.
Internal System Development: This acquisition method states that the organization
will develop the system internally. The system is developed by following either by life cycle

6SYSTEM ANALYSIS AND DESIGN
model or rapid action development strategy. In this case, the hospital will employ the project
team and provide all the required resources.
6. Objectives of the Project:
The organization wants to achieve efficient and accurate processes that can be tracked
from the beginning to the end. The project will produce a system that will record the data,
process those data to generate information and these information will be used for better and
accurate medical treatment. With the project, the organization can measure the improvement
in the medical procedure. The project will be providing a solution to the Khoo Teck Puat
Hospital that is essential for improving the medical as well as internal processes. The
organization currently needs a solution that can collect all the patient and medical treatment
related information and process those data to generate new patterns. Therefore, the project is
relevant for the situation of Khoo Teck Puat Hospital.
7. Feasibility Study:
Technical Feasibility: Khoo Teck Puat Hospital is currently managing their works
using the spreadsheets. The spreadsheets are very error prone and need a lot of effort for
maintenance. A new technology that can store the data in a structured manner and prevent
storing the repetitive data can allow better investment of effort in core hospital related
processes. The proposed system will have a database management system that can handle the
database. The database will be deployed in the cloud along with the core system. This will
allow the customers and the staff of Khoo Teck Puat Hospital to access the system remotely.
Financial Feasibility: The organization is facing the issue of maintaining the records
of the patients and their treatments. Often the inaccurate data and unnecessary effortful data
management are making the organization loose valuable time. The receptionists are not able
to answer to the queries of the patients because of lack of information and inaccurate data.

7SYSTEM ANALYSIS AND DESIGN
All these are resulting into losing customer base. In such situation, the investment in a new
system is relevant. As the system will be deployed in the cloud, Khoo Teck Puat Hospital will
pay for the system monthly basis.
Operational Feasibility: It is established fact that a system, if implemented
accurately, can allow a healthcare organization to handle operations more effectively. The
current manual paper based works needs to be replaced with a standard and automated
solution. This makes the proposed system a perfect solution for present circumstances of
Khoo Teck Puat Hospital.
8. System Requirements:
Functional Requirements: The functional requirements describes what the system of
Khoo Teck Puat Hospital will do.
i. Patient record storing is the first functional requirement of Khoo Teck Puat
Hospital system. The patient data will be stored in a structured database from
which retrieval of data is efficient. All the data will be stored in a centralized
location. The database will be connected to the core of the main system.
Along with the patient, the treatment process, department and staff details will
also be stored.
ii. The second functional requirement is authentication. Through authentication
process, the system determines whether the user is allowed to access the
system or not. The authentication is done based on the login credentials of the
user. Each user has a unique login id or it can be personal email or staff id.
The password is a vital aspect of authentication. The combination of login id
and password determines the user authentication.

8SYSTEM ANALYSIS AND DESIGN
iii. User interface can be considered as the third most important functional
requirement. The user interface will be the medium between the system and
the user. The user will interact with the user interface of the system.
Non-Functional Requirement: The non-functional requirement will describe how the
system of Khoo Teck Puat Hospital will perform.
i. Most important non-functional requirement of the proposed system is the
availability. As Khoo Teck Puat Hospital operates 24*7, the system also be
available to the user, all the time. The system will be implemented in the cloud
thus the system will be accessible from any location if the internet connection
is appropriate.
ii. Usability can be considered as the second most important non-functional
requirement. The users of the system are not familiar with a system. The staff
must easily understand how they can perform their respective works through
the system. The patients should be able to identify from where they can see
their treatment progress and also request for appointment.
iii. Real-time data flow is another vital aspect of the proposed hospital
management system. The real-time data flow illustrates that if a user inputs a
data into the system, then the other users will be able to see that data instantly.
It happens because the system transfers the data to other authorized users
before storing it into the database.

9SYSTEM ANALYSIS AND DESIGN
9. Use Case:
Figure 3: Use Case Diagram of Khoo Teck Puat Hospital System
(Source: Created by Author)
The use case proposed in the figure 3, shows the dynamic behaviour of the system.
The use case shows that the patient and staff will register to the system. Then the user will
login to the system for using the various functions designed for them. The patient can ask for
an appointment with the doctor through the system. The patient can also request for their own
treatment report. The patient report is also downloaded by the doctor. The difference is that
patient can find their own report and doctor can access every patient’s report.
10. Conceptual Model:
10.1 Story Board:
Eliza Hartley is a patient of Khoo Teck Puat Hospital. She is 35 years old. She is
currently working as a representative in a local café shop. She is not able to travel much so

10SYSTEM ANALYSIS AND DESIGN
she need remote assistance from the organization. As a patient of Khoo Teck Puat Hospital,
Eliza Hartley wants to make appointment from her work place or home so that she does not
need to travel to hospital for every purpose.
10.2 Hardware, Software and Network Component:
Hardware Component: Cloud based system will have a server computer provided by
the host. The system will have a same cloud based database.
Software: The software packages are attendance monitoring application, database
management system, and health record tracking application.
Network: The system will be accessed using open internet connection

11SYSTEM ANALYSIS AND DESIGN
Bibliography:
Ahmad, M., Belloir, N., & Bruel, J. M. (2015). Modeling and verification of functional and
non-functional requirements of ambient self-adaptive systems. Journal of Systems
and Software, 107, 50-70.
de Vasconcelos, J. B., Kimble, C., Carreteiro, P., & Rocha, Á. (2017). The application of
knowledge management to software evolution. International Journal of Information
Management, 37(1), 1499-1506.
Eckhardt, J., Fernández, D. M., & Vogelsang, A. (2015, October). How to specify non-
functional requirements to support seamless modeling? A study design and
preliminary results. In Empirical Software Engineering and Measurement (ESEM),
2015 ACM/IEEE International Symposium on (pp. 1-4). IEEE.
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016). Are" Non-functional" Requirements
really Non-functional? An Investigation of Non-functional Requirements in Practice.
In Software Engineering (ICSE), 2016 IEEE/ACM 38th International Conference
on (pp. 832-842). IEEE.
Eckhardt, J., Vogelsang, A., & Fernández, D. M. (2016). Are" Non-functional" Requirements
really Non-functional? An Investigation of Non-functional Requirements in Practice.
In Software Engineering (ICSE), 2016 IEEE/ACM 38th International Conference
on (pp. 832-842). IEEE.
Idani, A., & Ledru, Y. (2015). B for modeling secure information systems. In International
Conference on Formal Engineering Methods (pp. 312-318). Springer, Cham.
Ilieva-Obretenovaa, M. (2016). Information System Functions for SmartGrid
Management. Sociology, 6(2), 96-103.

12SYSTEM ANALYSIS AND DESIGN
Khan, F., Jan, S. R., Tahir, M., Khan, S., & Ullah, F. (2016). Survey: Dealing Non-
Functional Requirements at Architecture Level. VFAST Transactions on Software
Engineering, 9(2), 7-13.
Marrella, A., Mecella, M., Russo, A., Steinau, S., Andrews, K., & Reichert, M. (2015). Data
in Business Process Models, A Preliminary Empirical Study (Short Paper).
In Service-Oriented Computing and Applications (SOCA), 2015 IEEE 8th
International Conference on (pp. 116-122). IEEE.
Plataniotis, G., Ma, Q., Proper, E., & de Kinderen, S. (2015). Traceability and modeling of
requirements in enterprise architecture from a design rationale perspective.
In Research Challenges in Information Science (RCIS), 2015 IEEE 9th International
Conference on (pp. 518-519). IEEE.
Schlieter, H., Burwitz, M., Schönherr, O., & Benedict, M. (2015). Towards Model Driven
Architecture in Health Care Information System Development.
In Wirtschaftsinformatik (pp. 497-511).
Shiang, C. W., Halin, A. A., Lu, M., & CheeWhye, G. (2016). Long Lamai Community
ICT4D E‐Commerce System Modelling: An Agent Oriented Role‐Based
Approach. The Electronic Journal of Information Systems in Developing
Countries, 75(1), 1-22.
Tran, H. T., & Feuerlicht, G. (2016). Service development life cycle for hybrid cloud
environments. Journal of Software.
Vashisht, V., Lal, M., Sureshchandar, G. S., & Kamya, S. (2015). A framework for software
defect prediction using neural networks. Journal of Software Engineering and
Applications, 8(8), 384.

13SYSTEM ANALYSIS AND DESIGN
Vashisht, V., Lal, M., Sureshchandar, G. S., & Kamya, S. (2015). A framework for software
defect prediction using neural networks. Journal of Software Engineering and
Applications, 8(8), 384.
Wichmann, A., Jäger, S., Jungebloud, T., Maschotta, R., & Zimmermann, A. (2016, April).
Specification and execution of system optimization processes with UML activity
diagrams. In Systems Conference (SysCon), 2016 Annual IEEE (pp. 1-7). IEEE.