Ask a question from expert

Ask now

Headspace | Case Study

12 Pages2840 Words382 Views
   

Added on  2020-03-16

Headspace | Case Study

   Added on 2020-03-16

BookmarkShareRelated Documents
Running head: HEADSPACE CASE STUDYHeadspace Case StudyName of the StudentName of the UniversityAuthor’s Note:
Headspace | Case Study_1
1HEADSPACE CASE STUDYTable of ContentsIntroduction......................................................................................................................................2Discussion........................................................................................................................................31. The Non-Functional Requirements of the System...................................................................31.1 Functionality......................................................................................................................31.2 Usability.............................................................................................................................31.3 Reliability..........................................................................................................................41.4 Performances.....................................................................................................................41.5 Security..............................................................................................................................42. The Functional Requirements of the System vs The Non-Functional Requirements.............43. Cloud Based Solution..............................................................................................................53.1 Cloud Environment Strength.............................................................................................53.2 Cloud Environment Weakness..........................................................................................64. SDLC Approach......................................................................................................................64.1 Predictive Approach..........................................................................................................74.2 Adaptive Approach............................................................................................................7Conclusion.......................................................................................................................................8References......................................................................................................................................10
Headspace | Case Study_2
2HEADSPACE CASE STUDYIntroductionHeadspace is a popular organization, which works with youth generation aged twelve totwenty-five, who experience mental illness and ill health. Anxiety and depression are the mostcommon mental health problems, although there are many other mental illnesses as well. Everytime these patients need to tell their problems again (Pearce & Bainbridge, 2014). The youngpeople discussed little and even stopped talking about their problem. This makes it harder for theprofessionals to help them for their problems. Initially, a social worker of Headspace, then themedical staff in a hospital, maybe a psychologist, a psychiatrist, and a general practitioner seesthem.Currently, funds are raised to form a system that will record the patient’s story in the firsttime. This will provide authority to the specific professionals, so that the case studies and theirstory can improve, and the young patient can be facilitated appropriately and more precisely(Steele, Min & Lo, 2012). This particular organization has considered opting for a cloud basedsolution for their project. This report focuses on the cloud that should be undertaken byHeadspace for their business.The following report outlines a brief description on the need for the implementation ofcloud in Headspace organization. The report covers the non functional requirements of thesystem and the type of cloud Headspace should opt for their business (Chen & Zhao, 2012). Thereport further mentions about the recommended software development life cycle approach,which would be the best for the organization.
Headspace | Case Study_3
3HEADSPACE CASE STUDYDiscussion1. The Non-Functional Requirements of the SystemThe non functional requirements of a particular system deals with the attributes of asystem for performing the functions optimally (Chung et al., 2012). The main advantage of theserequirements is that they help in identifying the critical qualities of the systems, the requirementsof the system and the constraints of the system. These features are taken into consideration forthe implementation of any project. These non functional requirements has an important impacton the success factors of the project (Balaji & Murugaiyan, 2012). The various non functionalrequirements for the Headspace case study with respect to FURPS or functionality, usability,reliability, performance and security are given below.1.1 FunctionalityThis is the most important criteria for this particular project of My Health Record system.The information system would be having all the necessary information related to the patients(Chen & Zhao, 2012). Hence, it is extremely important for the system to enable a particularoption for updating and accessing the information according to the needs of the user. The mainfunctional requirement of this particular system is the adaptability.1.2 UsabilityThis is the second most important criteria for the non functional requirements of thisproject. The software can be easily learnt and this is the main requirement under usability(Galibus & Vissia, 2015). The interface between the software and the user should b user friendlyso that it can be easily accessed by all users.
Headspace | Case Study_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Cloud Computing Assignment Solution (doc)
|12
|2889
|341

System Analysis and Design
|11
|2447
|356

System Analysis and Design for Headspace's New Access Project
|11
|2781
|87

System Analysis and Design
|11
|2761
|336

System Analysis & Design : Assignment
|13
|2664
|92

System Analysis and Design Headspace Organization Assignment
|12
|2711
|38