System Analysis, Design, and Development (PDF)

Running: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student;
Name of the University:
Author Note

1
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction......................................................................................................................................2
Stakeholder Analysis.......................................................................................................................2
Stakeholder Map..........................................................................................................................2
Stakeholder Interests....................................................................................................................3
Targeted Stakeholder Group............................................................................................................5
Questionnaires Introduction Statement........................................................................................5
Questionnaire...............................................................................................................................5
Use Case and Description................................................................................................................6
Use Case Actors...........................................................................................................................6
Use Case Description...................................................................................................................7
Fully developed Use Case Description........................................................................................8
Bibliography....................................................................................................................................9

2
SYSTEM ANALYSIS AND DESIGN
Introduction
The report is used for the description of the My Health Record System. The system is to
be implemented in Australia which would help the people in Australia to receive treatment with
a reduced expense (Phillips, Nagle & Chakraborty, 2015). Additionally, the system would also
help the health organization is reducing the response time for the clients (Kingni et al., 2014).
The stakeholder analysis and the use case description has been done in the report.
Stakeholder Analysis
This part of the report consists of the analysis of the stakeholders of the system for my
health record (Dennis, Wixom & Tegarden, 2015). According to the power and association with
the systems the stakeholders of the system can be divided into Internal-Operation, Internal-
Executive, External-Operation, and External-Executive.

3
SYSTEM ANALYSIS AND DESIGN
Stakeholder Map

4
SYSTEM ANALYSIS AND DESIGN

5
SYSTEM ANALYSIS AND DESIGN
Figure 1: Stakeholder Map
Source: (created by Author)
Stakeholder Interests
The stakeholder descriptions have been provided in the table below:
Stakeholder Description
Government of
Australia
The government of Australia is the main stakeholder of the system,
they would directly linked with the development of the system of
the healthcare and the health of the area would be depending on the
development of the system. However the government would not be
involved with the systems and hence they are categorized as the
external executive stakeholders of the information system (Shao et

6
SYSTEM ANALYSIS AND DESIGN
al., 2015).
Hospital Owners The owners of the hospitals would be external executive
stakeholders as the owners are the ones that would be responsible
for the business of the hospital. The business would also affect their
reputation. Hence they are very in context of the system design.
However they do not have any direct involvement with the system
and hence they are the external executive stakeholders of the
system.
Investors The investors would also invest in the system to incur some type of
benefits from the investment they are making for the deployment of
the system. Hence, the system deployment would be affecting the
investor as well. However the investor would be not associated
with the system directly and they would be considered as the
external executive of the systems.
Board of directors The board of directors would be executive stakeholders of the
systems. They would be taking all the major decisions of the
system and also would be controlling the major operations of the
system. Hence they are internal executive stakeholders of the
system.
Medical Board The medical board would be taking all the important decisions
about the medical operation and also update the medicine
information for the hospitals individually. They would be linked
directly to the systems and hence they can be considered as the
internal executive stakeholders of the system.
System administrator The system administrator would be an internal stakeholder of the
system. He would be responsible for handling and monitoring all
the major operations of the system. Hence the system
Administrator is considered as the main internal executive
stakeholder of the system.
Customer The customers of the system would be main stakeholders for whom
the system is being implemented. The customers would be served

7
SYSTEM ANALYSIS AND DESIGN
by the system directly. All the information of the customers would
be stored in the system. Hence, they are one of the main external
operational stakeholders for the system.
Doctors The doctors would also be associated with the system. The doctors
would be fetching information from the system about the patients.
Hence they can also be considered as the external operational
stakeholders for the system.
Medical Staffs The medical staffs would be entering the data of the customers in
the system and hence they would be the external operational
stakeholders for the system as they are connected directly to the
system.
Nurses The Nurses would be updating the data of the customers in the
system and hence they would be the external operational
stakeholders for the system as they are connected directly to the
system.
Technicians The technicians would be used for the implementation of the
system. They would be responsible for the development of the
system. The technicians would be categorized as the internal
operational stakeholders of the system.
Technical staffs The technical staffs would be supporting the staffs of the system
and they would only be required when the staffs would face
difficulty in accessing the systems. However they too have to be
categorized as the internal stakeholders of the systems.
Targeted Stakeholder Group
Questionnaires Introduction Statement
The questionnaires are directed to the doctors in the system (Missonier & Loufrani-
Fedida, 2014). The feedback from the system would provide an efficient insight to the possible
updating required by the system (Chitchyan et al., 2015).

8
SYSTEM ANALYSIS AND DESIGN
Questionnaire
The following questionnaires would be used:
1. How would rate the system?
2. What according to has been the best aspect of the system?
3. Has the implementation of the system accelerated the process of treatment of the patient?
4. Has the system benefited the organization financially?
5. Has the system put any effect on the cost of treatment for the patients?
6. How do your patient respond to the system that has been implement?
7. What are major drawbacks of the system?
8. What possible solution would you suggest for the systems?
9. Has the new system improved the situation?
10. What were the main drawback of old system?

9
SYSTEM ANALYSIS AND DESIGN
Use Case and Description

10
SYSTEM ANALYSIS AND DESIGN

11
SYSTEM ANALYSIS AND DESIGN
Figure 2: Use case of My Health Record
Source: (created by Author)
Use Case Actors
Use case Use Case Actors
Register to the system System Administrator
Staff Log in Staffs
Register patient Staffs
Register patient medical story Staffs
View patient information Doctors
View medical history Doctors
Maintain hospital information Staffs
Log in to the medical system Patients
Fix appointment Patients

12
SYSTEM ANALYSIS AND DESIGN
Provide treatment Patients, Doctors
Make payment Staffs, Patients
Use Case Description
Use case Brief Use Case Description
Register to the
system
The staffs would be registered to the system by the system administrator.
Staff Log in The staffs can log in to the system by using the log in credentials stored
in the system.
Register patient The patients are registered to the system by the staffs
Register patient
medical story
The details of the medical history would be stored in the system by the
staffs as the medical story of the users.
View patient
information
The information about the patient would be available to the doctors from
the system.
View medical
history
The medical history of the patients would provide the doctors with the
information about the medical perspective of the patients to diagnose the
patients successfully.
Maintain hospital
information
The information about the hospitals would be edited and updated by the
staffs of the hospitals regularly.
Log in to the
medical system
The patients would also be allowed to log into the system by using their
individual systems.
Fix appointment They would able to fix appointments with the doctors to express their
concern.
Provide treatment The doctors would be able to provide treatment to the patients for those
who have booked appointment with the particular doctor.
Make payment The patient would be making the payment through the system.
Fully developed Use Case Description

13
SYSTEM ANALYSIS AND DESIGN
Scenario: Fix Appointment
Event Trigger: The patient selects the doctor and fixes an appointment with the doctors.
Brief Description: The patients would able to fix appointments with the doctors to express
their concern.
Actors: Patients, Doctors
Related Use case: Patient Log in
Stakeholders: System, Staffs
Precondition: The patient have to be logged into the system to be able to view the
available doctors for their check-up.
Post conditions The post condition is the patient would be receiving treatment.
Flow of activities: Actor System
1. Log in to the system
2. Check doctors
3. Select doctor
4. Fix appointment
1. The system would check the
user credentials
2. The system would provide the
list of available doctors
3. Redirect to the fix appointment
option.
4. Confirm appointment
Exceptions: 1. The user details are not registered into the system
2. No doctor is available.

14
SYSTEM ANALYSIS AND DESIGN
Bibliography
Chitchyan, R., Rashid, A., Sawyer, P., Garcia, A., Alarcon, M. P., Bakker, J., ... & Jackson, A.
(2015). Survey of aspect-oriented analysis and design approaches.
Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Kingni, S. T., Jafari, S., Simo, H., & Woafo, P. (2014). Three-dimensional chaotic autonomous
system with only one stable equilibrium: Analysis, circuit design, parameter estimation,
control, synchronization and its fractional-order form. The European Physical Journal
Plus, 129(5), 76.
Missonier, S., & Loufrani-Fedida, S. (2014). Stakeholder analysis and engagement in projects:
From stakeholder relational perspective to stakeholder relational ontology. International
Journal of Project Management, 32(7), 1108-1122.
Phillips, C. L., Nagle, H. T., & Chakrabortty, A. (2015). Digital Control System Analysis &
Design. Pearson Prentice Hall.Phillips, C. L., Nagle, H. T., & Chakrabortty, A. (2015).
Digital Control System Analysis & Design. Pearson Prentice Hall.
Shao, S., Khreishah, A., Ayyash, M., Rahaim, M. B., Elgala, H., Jungnickel, V., ... & Freund, R.
(2015). Design and analysis of a visible-light-communication enhanced WiFi system.
IEEE/OSA Journal of Optical Communications and Networking, 7(10), 960-973.