Limited-time offer! Save up to 50% Off | Solutions starting at $6 each  

Cloud Computing Assignment Solution (doc)

Added on - 11 May 2020

Trusted by 2+ million users,
1000+ happy students everyday
Showing pages 1 to 4 of 12 pages
Running head: HEADSPACE CASE STUDYHeadspace Case StudyName of the StudentName of the UniversityAuthor’s Note:
1HEADSPACE CASE STUDYTable of ContentsIntroduction......................................................................................................................................2Discussion........................................................................................................................................31. Non-Functional Requirements of the System..........................................................................31.1 Functionality......................................................................................................................31.2 Usability.............................................................................................................................31.3 Reliability..........................................................................................................................41.4 Performances.....................................................................................................................41.5 Security..............................................................................................................................42. Functional Requirements of the System vs Non Functional Requirements............................53. Cloud Based Solution..............................................................................................................53.1 Cloud Environment Strength.............................................................................................63.2 Cloud Environment Weakness..........................................................................................64. SDLC Approach......................................................................................................................74.1 Predictive Approach..........................................................................................................74.2 Adaptive Approach............................................................................................................8Conclusion.......................................................................................................................................8References......................................................................................................................................10
2HEADSPACE CASE STUDYIntroductionHeadspace is a recognized and renowned organization that works with various youthgeneration, whose ages vary between twelve to twenty-five, who are experiencing mental illnessand ill health (Pearce & Bainbridge, 2014). Anxiety and depression are the most common mentalhealth problems, although there are many other mental illnesses as well. Every time thesepatients need to tell their problems again. The young people discussed little and even stoppedtalking about their problem. This makes it harder for the professionals to help them for theirproblems. Initially, a social worker of Headspace, then the medical staff in a hospital, maybe apsychiatrist, a psychologist, and a general practitioner watches them.Recently, funds are beingraised for the formation of a system, which will record the patient’s story in the very first time(Steele, Min & Lo, 2012). This will give authority to the distinct professionals, so that thespecific case studies and their stories can improve, and the young patient can be facilitated moreprecisely and appropriately. This particular organization has considered opting for a cloud-basedoption for their project. This particular report focuses on the type of cloud, which should beundertaken by Headspace for their business.This report outlines a specific description on the requirement for the implementation ofcloud in the Headspace organization(Chen & Zhao, 2012). This report outlines the various non-functional requirements of the system and the type of cloud Headspace should be opting for theirbusiness. The report further mentions about the recommended software development life cycleapproach, which would be the best for the organization.
3HEADSPACE CASE STUDYDiscussion1. Non-Functional Requirements of the SystemThe requirement of a project or system, which deals with the several and variousattributes of a particular system, is known as non functional requirements. These non functionalrequirements help in the recognition of all types of critical qualities of a particular system, therequirements of a particular system and the constraints of particular system (AlZainet al., 2012).The several non-functional requirements of the system are the FURPS or Functionality,Usability, Reliability, Performance and Security. All of the above-mentioned requirements areextremely important for any system.1.1 FunctionalityFunctionality is the most beneficial criteria for the Headspace project, namely My HealthRecord system. This particular system will be storing all the information of the patients(Kulkarni et al., 2012). Therefore, it is required for the My Health Record system to enable aspecific option for accessing and updating the data from any device according to therequirements of the user. The most important functional requirement of the system isadaptability.1.2 UsabilityUsability is another main criterion for the recognition of the non-functional requirementsof the My Health Record system. The main benefit of this software is that it can be learnt easilywithout much complexities and this particular requirement is the most important under usability(Balaji & Murugaiyan, 2012). The interface that will be between the user and the software mustbe friendly to the users and can be easily used by all the users.
desklib-logo
You’re reading a preview
Preview Documents

To View Complete Document

Click the button to download
Subscribe to our plans

Download This Document