Stakeholder Analysis for Headspace Project

As per analysis of the case study of Headspace project, the stakeholders are identified along with their individual role based segmentation. The role wise specification of stakeholder is performed under four different quadrants such as ‘external-executive’, ‘internal-operation’, ‘external-operation’, and ‘internal-executive’. Stakeholder map is prepared and shown as underneath:

Figure 1: Headspace Project Stakeholder Analysis Map

(Source: Created by author)

The map states some internal and external stakeholders in this case study of Headspace project. Categorization and identification of stakeholder is performed under tabular format as shown following:

Stakeholder Types	Internal	Headspace staffs, Information System Manager, workers, Headspace project authority
External	Medical Personnel, Doctors and Physicians, Government of Australia, and Patients across Australia

Areas of interest identification is the way of realizing individual stakeholder roles so that individual stakeholder can be involved with their work intentions. Their individual responsibilities are addressed in the following table in detail:

Stakeholder Roles	Areas of Interest
Medical Personnel	Medical personnel can be benefitted from system once the system can store appointments and medicine details. The personnel can collect the patient applications and review them so that applications can be sent to doctors.
Doctors and Physicians	Doctors and physicians are interested for viewing patient case and update the patient case details once diagnosis is completed. The appointment is allowed for individual patients.
Government of Australia	Australian government will be incorporated in the system for their area of interest on system applications. Government personnel can easily overview entire details about medical staffs, Australian patients, and supplier of medicines.
Patients across Australia	Patients are part of the system as they can check availability of doctors and can view his/her treatment description and details.
Headspace staffs	Headspace staffs are incorporated in the system as they can operate the system along with databases with proper efficiency. Personnel can modify, update, delete, and select stored data.
Information System Manager	Information system manager will be responsible for developing the entire system; therefore, he or she will be responsible as well.
Workers	Workers are responsible for viewing the patient status, their updated details, patient case scenario, and appointment as well.
Headspace project authority	Headspace project authority can perform their activity with patient information stored into database. Newly designed system could be useful for obtaining profit, additional cost for treatment, medicinal requirements, and booking appointment, and others.

Headspace authorities need to identify the patient and staff overview of the system and new system implementation. Henceforth, the questionnaire is prepared with all questions regarding collection of opinions. The feedback and opinions are for reviewing in later so that new system can be improved along with recommended settings and functionalities. The questionnaire is shown as following:

1. Inform us about system experience; share us whether you are experiencing it for first time or you have used the system before.
2. What do you require the system to do or what will be expectations from the system?
3. Identify what are the advantages and disadvantages of system.
4. Identify the ways to remove disadvantages in the system; provide suggestions for removing the disadvantages.
5. Identify what will be benefits from the system.
6. Provide some suggestions about the functionality that should be included in the new system.
7. Tell us how you will be affected by the system.
8. Tell us whether the staff performance is improved or not after the system is implemented.
9. Inform us what glitches that you have faced or bugs that you have experienced till now.
10. Provide rating on the system performance with including overall feedback as well.

This particular use case is designed with scenario of identifying specific yet appropriate functionalities regarding the system. Use case of the system included some different actors, such as Headspace personnel, doctors, and patients. The doctors are identified as other, Headspace personnel are identified as primary, and patients are identified as secondary actors. Workers take responsibility of registering the patients, update patient information, include their individual cases, and viewing treatment status. The physicians will update the patient information when the patient diagnosis is completed. Medical personnel can complete booking of appointment along with individual doctors while checking doctors’ availability, reviewing staff details, and teenager case. The medical personnel can insert medical treatment details and can update the booking details. The patients can view individual information, check the appointment details, detailed diagnosis, and medicine records. The use case diagram is essential for adding specific functionalities in order to make system useful to database.

Figure 2: Headspace Project for Use Case Diagram

(Source: Created by author)

Use Case	Description
Patient Registration	This particular option can be utilized for registering the patient for first time, the registration process require patient details.
Insert patient case	Staffs can enter individual case and health problem scenario from this option.
View patient status	The option can be utilized for viewing the patient status when they are under appointment schedule.
Update patient status	The update patient status option can be used for updating patient status when the diagnosis and treatment is completed from doctors. The update option is available from medical staffs and Headspace personnel.
Update patient information	Doctors are responsible for updating patient information as per individual appointment is completed. The doctors can add details regarding patient information along with medical records such as medicine, patients’ case as well.
Book doctor appointment	Medical staffs can use this particular option with individual doctor appointment so that individual patient details can be included. The book appointment option can add patient information with detailed steps and necessary routine of work.
View patient information	This option is typically used from staff side showing patient information with details of patient treatment details and medicines.
Update treatment of patient	When the diagnosis and treatment is completed; the doctor can update treatment details to assure consistency in stored data for the system.

Figure 3: Use case diagram for insertion of patient cases into the system

(Source: Created by author)

Description: The use case is relevant for using from staffs, doctors, and patients side. The use case is a part of the system for insertion of patient case into the system; the option can allow staffs to view the patient details. The patient can check their appointment details when staffs have stored the details in the stored information tab. Doctors can be able to view the patient scenario as they discussed about it to the staffs. The doctors can easily identify the disease with earlier diagnosis with offering appropriate treatment for the patients. The patient can easily book as per the doctor appointment status and availability.

Use Case Name:	Insertion of the Patient cases into the system
Primary Actor:	Headspace Staffs
Secondary Actors:	Patients
Other Stakeholders:	Doctors
Business Goal:	The business goals are as following: 1. Reduction of treatment cost 2. Faster response to treatments   3. Record storing for individual patients
Prerequisites:	The prerequisites were: A. Portal sign-in B. Applicable for registered patients
Success Condition	Success criteria and condition is flawless registration for each patient.
Main Path	In the Use Case flow path, the patient first starts conversation with staffs to initiate the activity. Once, the patient has provided their health details. Then the staffs can store the collected information from patients into the system.
Post condition:	The patient case is inserted and doctors can review the patient case as well.

References

Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-oriented approach with UML. John Wiley & Sons.

Faitelson, D., & Tyszberowicz, S. (2017, May). UML diagram refinement (focusing on class-and use case diagrams). In Proceedings of the 39th International Conference on Software Engineering (pp. 735-745). IEEE Press.

Hossain, S., Karim, R., & Sarma, D. (2014). Designing a Task Management System for a Banking System by Combining Relational Model with Use Case Diagram. International Journal of Computer Applications, 108(8).

Jovic, A., Kukolja, D., Jozic, K., & Cifrek, M. (2016, May). Use case diagram based scenarios design for a biomedical time-series analysis web platform. In Information and Communication Technology, Electronics and Microelectronics (MIPRO), 2016 39th International Convention on (pp. 310-315). IEEE.

Khurana, N., Chhillar, R. S., & Chhillar, U. (2016). A Novel Technique for Generation and Optimization of Test Cases Using Use Case, Sequence, Activity Diagram and Genetic Algorithm. JSW, 11(3), 242-250.

Mondal, B., Das, B., & Banerjee, P. (2014). Formal Specification of UML Use Case Diagram-A CASL Based Approach. International Journal of Computer Scienceand Information Technologies, 5(9), 2113-2717.

Seidl, M., Scholz, M., Huemer, C., & Kappel, G. (2015). The Use Case Diagram. In [email protected] Classroom (pp. 23-47). Springer International Publishing.

Singh, A., & Sharma, E. S. (2014). Functional Test Cases Generation Based on Automated Generated Use Case Diagram. International Journal of Innovative Research in Advanced Engineering (IJIRAE), (8).

Singh, M., Sharma, A. K., & Saxena, R. (2016). Formal Transformation of UML Diagram: Use Case, Class, Sequence Diagram with Z Notation for Representing the Static and Dynamic Perspectives of System. In Proceedings of International Conference on ICT for Sustainable Development(pp. 25-38). Springer Singapore.

Vemuri, S., Chala, S., & Fathi, M. (2017, April). Automated use case diagram generation from textual user requirement documents. In Electrical and Computer Engineering (CCECE), 2017 IEEE 30th Canadian Conference on(pp. 1-4). IEEE.