System Analysis for Headspace Project

Added on - 08 Nov 2019

  • 12

    pages

  • 1970

    words

  • 105

    views

  • 0

    downloads

Showing pages 1 to 4 of 12 pages
Running head: ASSESSMENT ITEM 2System Analysis for Headspace Project: Assessment Item 2Name of the StudentName of the UniversityAuthors’ Note
1ASSESSMENT ITEM 2Table of Contents1. Stakeholder Map..........................................................................................................................21.2 Stakeholder Categorization........................................................................................................31.3 Stakeholder and their Areas of Interest.....................................................................................32. Questionnaire...............................................................................................................................43. Use Case Diagram.......................................................................................................................63.1 Use Case Description of each use case......................................................................................73.2 Detailed Use case description..................................................................................................10References......................................................................................................................................12
2ASSESSMENT ITEM 2Information System ManagerHeadspace staffsWorkersMedical PersonnelDoctors and PhysiciansGovernment of AustraliaPatients across AustraliaHeadspace project authorityInternal-Operation StakeholdersInternal-Executive StakeholdersExternal-Executive StakeholdersExternal-Operation StakeholdersHighHighLow1. Stakeholder MapAs per analysis of the case study of Headspace project, the stakeholders are identifiedalong with their individual role based segmentation. The role wise specification of stakeholder isperformed under four different quadrants such as ‘external-executive’, ‘internal-operation’,‘external-operation’, and ‘internal-executive’. Stakeholder map is prepared and shown asunderneath:Figure 1: Headspace Project Stakeholder Analysis Map
3ASSESSMENT ITEM 2(Source: Created by author)1.2 Stakeholder CategorizationThe map states some internal and external stakeholders in this case study of Headspaceproject. Categorization and identification of stakeholder is performed under tabular format asshown following:StakeholderTypesInternalHeadspace staffs, Information System Manager, workers,Headspace project authorityExternalMedical Personnel, Doctors and Physicians, Government ofAustralia, and Patients across Australia1.3 Stakeholder and their Areas of InterestAreas of interest identification is the way of realizing individual stakeholder roles so thatindividual stakeholder can be involved with their work intentions. Their individualresponsibilities are addressed in the following table in detail:StakeholderRolesAreas of InterestMedicalPersonnelMedical personnel can be benefitted from system once the system can storeappointments and medicine details. The personnel can collect the patientapplications and review them so that applications can be sent to doctors.Doctors andPhysiciansDoctors and physicians are interested for viewing patient case and update thepatient case details once diagnosis is completed. The appointment is allowedfor individual patients.Government ofAustraliaAustralian government will be incorporated in the system for their area ofinterest on system applications. Government personnel can easily overviewentire details about medical staffs, Australian patients, and supplier ofmedicines.Patients acrossAustraliaPatients are part of the system as they can check availability of doctors andcan view his/her treatment description and details.Headspace staffsHeadspace staffs are incorporated in the system as they can operate thesystem along with databases with proper efficiency. Personnel can modify,update, delete, and select stored data.
desklib-logo
You’re reading a preview
card-image

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Download This Document