Case Study: Headspace (Cloud-based solution)
Headspace organization is one of the organizations trialing a new information system under NewAccess program. NewAccess is a mental health intervention targeted youth aged between 17 to 25 initially. Further, it is trying to expand the age limit to as young as 12, and also to indigenous youth. Particularly, NewAccess targets anxiety and depression. One of the major issues identified was that that a young person having mental illness might go to multiple professionals before getting the assistance they require. Each and every time they need to tell their story again and again. Further, in order to help the young people, the professional faces difficulties, as the young people clam up and say very little. First of all, they might see a case worker of Headspace, then medical staff in an emergency department of hospital, perhaps, a psychologist, a general practitioner, a psychiatrist and others. The project is considering a cloud-based solution that should be investigated.
As per the case study, the project will consider various aspects of cloud-based solutions i.e. data security including data ownership (by young person, headspace, medical professionals, and the emergency department). Besides this, it will consider other relevant aspects of cloud solutions- the non-functional requirements, reviewing of cloud-based solution, SDLC approach to integrate the cloud-based solutions. Further, some outcomes related to the information system after adopting the cloud based solution will be discussed in this case study. The non-functional requirements of the developed system are the system qualities, user interface requirements, system requirements and system constraints are considered in this project. The overall non-functional requirements such as FURPS that refers to Functions such as, capability, reusability; Usability such as, Human factors, consistency, responsiveness; Reliability such as, availability, accuracy predictability; Performance such as, scalability, capacity, throughput, resource consumption, speed and efficiency; and Supportability such as, localizability, portability, flexibility and testability must be considered in this project, as per the case study. A review of weakness such as downtime of system, security and privacy issues, vulnerability to attack, limited flexibility and control, vendor lock-in, and strengths such as, expenditures for deployment and maintenance, Reliability, effective manageability of data, strategic edge of the cloud-based solutions must be considered in the deployment of the new cloud-based solutions. Further, a brief description of the drawbacks and benefits of using the ‘Adaptive’ SDLC approach, and ‘Predictive’ SDLC approach are provided in this case study. The ‘Adaptive’ SDLC is an approach in which the first phase is required to complete before going to the next phase and ‘Predictive’ SDLC is an approach in which the development of project and evaluation of client are carried out side by side. Where the example of an adaptive SDLC model is Waterfall model in which the development phases and process is carried out sequentially. On the other hand, the example of Adaptive SDLC approach is an agile methodology which is based on iterative development, where the solutions and requirements evolve thorough collaborating between the self-organizing cross-functional team. The SDLC approach for developing the project will be provided in this case study.
Moreover, one of the mentioned SDLC approaches also will be recommended for the project. Besides this, the reason for recommending a particular approach will also be provided as per the case study. Some of the learning outcomes also mentioned in the case study which must be gained from the deployment of the cloud-based solution. The formulated project must have different factors to satisfy the requirements of the case study. The project must be able to contrast and compare the different approaches of system evaluation and analyze the appropriateness of complex and different situations.
Furthermore, it must be able to differentiate between techniques of requirement gathering, i.e. questionnaire and interviews and also combine these techniques in an appropriate manner to apply to the actual scenario. The project must be able to combine the elements of a requirement approach by using techniques and tools of structured or object-oriented systems modelling. Along with this, it must be able to justify and formulate the requirement models of a system based on the evaluation of given situations, and also evaluate the requirement development and prepare a feasibility proposal based in the multi-disciplinary such as, technological, human resource and financial analyses.
The case study concluded with providing an analysis of a cloud-based solution for Headspace organization to maintain the data of young patients effectively. Headspace is an organization that mainly deals with the mental health of persons by providing services based on meditations, and mental health management. Currently, the organization adopted an information system of NewAccess organization which works same as that of Headspace organization. In order to deploy the cloud-based solution within the new information system, this case study analyzes the system on aspects of non-functional requirements based on FURPS and also recommend a SDLC approach to carry out the deployment process in an effective manner.