Analysis and Design of a New Access System for Headspace

This report presents a system analysis and design for a new access system intended for the Headspace organization. The analysis begins with a stakeholder map, categorizing stakeholders based on their interest and power within the project, including internal operations, internal executive, external operations, and external executives. The report then details the interests of various stakeholders, such as IT staff, project managers, nurses, doctors, patients, and hospital owners, to understand their perspectives on the system. A questionnaire designed for doctors is included to gather data for system development. The core of the report involves use case diagrams and descriptions, providing a visual and textual representation of the system's functionalities. The use case diagram illustrates actors like patients, doctors, nurses, and the system itself, while the use case descriptions outline processes such as registration, appointment scheduling, treatment, and payment processing. A fully developed use case for payment processing is also provided, detailing pre-conditions, flow of events, and post-conditions. The report concludes with a bibliography of relevant sources. This report provides a detailed overview of the system analysis and design process, offering insights into stakeholder management, system modeling, and use case development.

Running head: SYSTEM ANALYSIS AND DESIGN
System analysis and design
Name of the Student:
Name of the University:
Author Note

1
Internal operations
Nurse, Patients, Doctors
External operations
IT Staffs, Project manager
External executive
Government, Hospital
owners, sponsors
Internal executive
Medical board, Administrator
Interest/ Power
SYSTEM ANALYSIS AND DESIGN
Stakeholder map
The stakeholder map provides the details of the stakeholders in the system. The
stakeholder map is an efficient way for the categorization of the stakeholders who are
associated with the system. The division of the stakeholder map is generally done into four
quadrants and the division is done according to the interest and the power of the stakeholder
in the project. The four quadrants represent the four categories of the system namely the
internal operations, internal executive, external operations and the external executives. The
stakeholder map for the Headspace organization is described below:
Figure 1: Stakeholder Map of New Access System
Source: (created by author)
Stakeholder interest
It is very important to understand the interests of the stakeholders in the system in a
stakeholder analysis. The stakeholder interests in the system has been described in the table
provided below:

2
SYSTEM ANALYSIS AND DESIGN
Stakeholder Interest
IT Staffs The IT staffs would be responsible for the deployment for the
system for the organization and for the maintenance of the
system after the deployment.
Project manager The project manager would be having the maximum interest in
the project during the implementation phase, as they would be
responsible for the procedures that are to be performed in the
deployment process. They would be also assigned with the task
of monitoring the project development process.
Nurses The nurses would be having a great interest in the system as the
system is developed for the nurses to record the details of the
patients in the system.
Doctors The doctors would be able to fetch the details of the patients
form the system and they would be able to update the details of
the patients after treatment as well.
Patients The patients are the ones for whom the system is being
developed and the medical data of the patients are stored in the
system. The system would also be able to reduce the cost of
treatment for the patients.
Medical Board The medical board would not be associated directly with the
system however they would be able to provided feedbacks and
advices during the development of the system. They are the ones
who would be consulted during the development of the system
for the functionalities.
Administrator The administrator would be associated with the system after the

3
SYSTEM ANALYSIS AND DESIGN
system has been developed. The administrator would look over
the functionalities and the procedures of the system. The
administrator would be monitoring the system.
Hospital owners The hospital owners would be interested in the deployment of
the system as they would like to enhance their business
procedure and the implementation would enhance the overall
efficiency of the business of the organization.
Sponsors The sponsors the ones who would be sponsoring the project and
their interest in the project is to make the funding for the project
and obtaining the profits that can be fetched from the
deployment of the project.
Government The government would not like any benefit from the project,
although they would be funding the project as much as in their
scope. The government would be interested in the social benefit
obtained from the project, as they would look to reduce the cost
of treatment for the patients, which would be a great benefit to
the society.
Table 1: Stakeholder Interest for Headspace organization
Source: (created by author)
Questionnaire
The questionnaire are used for the development of the system. The data used for the
analysis and development of the system would be done with the help of the questionnaire.
The doctors are identified as the most important members of the system and hence the

4
SYSTEM ANALYSIS AND DESIGN
questionnaires have been developed for them. The questionnaire developed for the doctors
are provided below:
 What the difficulties in the current system?
 What are the views of the patients about current treatment structure for the
organization?
 Are there any financial crisis faced by the patients?
 What are your views on the system that is being proposed for the system?
 What are the functionalities that you are looking forward to in the current system?
 Are you happy with the financial structure of the proposed system?
 Do you expect any financial benefit from the system that is to be developed?
 What are the type of data security that you would like to be implemented on the
system?
 Are there any administrative constraints, which you would like to handle?
 Would you like any administrative rights to be stored in the system for you?
Use case diagrams and description
Use case diagram
Use case diagram is very important modelling tool, which can help the users and the
developers in understanding the details of the system such as the actors involved in the
system, and the functions to be performed for each the actors in the system. The use case
diagram for the New access system to be developed for the Headspace organization would
provide the designers of the system an excellent insight to the procedures that are intended to
be implemented in the system. In addition to this, the model provided below would help them
the stakeholders of the system to understand the detailed functionalities of the system.

5
SYSTEM ANALYSIS AND DESIGN
Figure 2: Use case diagram for New Access system
Source: (created by author)

6
SYSTEM ANALYSIS AND DESIGN
The above designed use case has been used for the description of the functionalities
that are available in the New Access system developed for the Headspace organization. The
main actors identified for the system with the help of the above designed diagram are
patients, doctors, nurses and system. The patients are the primary actors for several of the use
cases and the other secondary actors of the system are doctor, nurses and system.
Use case description
The use case descriptions are provide in the table included below:
Use Case Description
Registration The registration of the patients are done in the system by the
staffs.
Record Details The details of the patients are stored in the system after the
patients have completed the registration process so that the
doctors can fetch the required details at point of time.
Fixing Appointment The staffs fixes an appointment with the doctor for the patient.
Treatments The doctor provides the treatment for the patients.
Select Doctors The staff selects a doctor for the treatment of the patient.
Prescribe The doctor provides a prescription after performing the
treatment procedure.
Fetch details The doctor fetches the details of the patients from the system.
Make Payment The patient makes the payment after the completion of the
treatment.
Store details The details of the patient are updated in the system after the
treatment has been performed.
Payment processing The system processes the payments made by the patients
Invoice sent The invoice of payments made by the patients are sent to them

7
SYSTEM ANALYSIS AND DESIGN
from the system.
Table 2: Use case description of New Access
Source: (created by author)
Fully developed use case description
The fully developed use case for the payment processing function has been described
in the table provided below:
USE CASE ID UC10
USE CASE NAME Payment processing
PRIMARY ACTORS Patients
SECONDARY ACTORS System
DESCRIPTION The patients make the payments. On
making the payments, the system delivers
the invoice to them. Before the invoice is
being delivered the system processes the
payments received from the patients.
PRE-CONDITION Make payment
FLOW User System

8
SYSTEM ANALYSIS AND DESIGN
1. Receive
treatment
2. Make
payment
3. Receive
invoice
1. Calculate
payment
2. Validate
payment
3. Send invoice
POST-CONDITION Send invoice
EXCEPTIONS An exception occurs in case the payment
made by the user is not validated by the
system.
Table 3: Fully developed used for Payment processing
Source: (created by author)

9
SYSTEM ANALYSIS AND DESIGN
Bibliography
Arnott, D., & Pervan, G. (2016). A critical analysis of decision support systems research
revisited: the rise of design science. In Enacting Research Methods in Information
Systems (pp. 43-103). Palgrave Macmillan, Cham.
Dennis, A., & Wixom, B. H. (2018). Systems analysis and design. Wiley.
Gupta, A. K. (2017). Response spectrum method in seismic analysis and design of structures.
Routledge.
Lessard, L., Recht, B., & Packard, A. (2016). Analysis and design of optimization algorithms
via integral quadratic constraints. SIAM Journal on Optimization, 26(1), 57-95.
Montgomery, D. C. (2017). Design and analysis of experiments. John wiley & sons.
Rajaraman, V. (2018). Analysis and design of information systems. PHI Learning Pvt. Ltd..
Taranath, B. S. (2016). Structural analysis and design of tall buildings: Steel and composite
construction. CRC press.