Headspace is a recognized and renowned organization that works with various youth generation, whose ages vary between twelve to twenty-five, who are experiencing mental illness and ill health (Pearce & Bainbridge, 2014). Anxiety and depression are the most common mental health problems, although there are many other mental illnesses as well. Every time these patients need to tell their problems again. The young people discussed little and even stopped talking about their problem. This makes it harder for the professionals to help them for their problems. Initially, a social worker of Headspace, then the medical staff in a hospital, maybe a psychiatrist, a psychologist, and a general practitioner watches them. Recently, funds are being raised 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 the specific case studies and their stories can improve, and the young patient can be facilitated more precisely and appropriately. This particular organization has considered opting for a cloud-based option for their project. This particular report focuses on the type of cloud, which should be undertaken by Headspace for their business.
This report outlines a specific description on the requirement for the implementation of cloud 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 their business. The report further mentions about the recommended software development life cycle approach, which would be the best for the organization.
Non-Functional Requirements of the System
The requirement of a project or system, which deals with the several and various attributes of a particular system, is known as non functional requirements. These non functional requirements help in the recognition of all types of critical qualities of a particular system, the requirements 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 are extremely important for any system.
Functionality is the most beneficial criteria for the Headspace project, namely My Health Record 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 a specific option for accessing and updating the data from any device according to the requirements of the user. The most important functional requirement of the system is adaptability.
Usability is another main criterion for the recognition of the non-functional requirements of the My Health Record system. The main benefit of this software is that it can be learnt easily without 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 must be friendly to the users and can be easily used by all the users.
Reliability is the most essential requirement under the non-functional requirements (Galibus & Vissia, 2015). When the system will not be reliable, it is evident that the data and information will be unsafe. The information that is related to the patients is extremely confidential and under no circumstances, it should be lost. The information system will also be updating the information automatically. Hence, the reliability is mandatory for the My Health Record system (Li et al., 2015). A cloud-based infrastructure brings extreme reliability in any system.
Performance is again one of the most important criteria under the non-functional requirements (Jain & Nandakumar, 2012). When the performance of the system will not be up to the mark, it is baseless for implementing that particular system. The performance of the system should be perfect and the system must be flexible.
The data or information that is to be stored in the My Health Record system is absolutely sensitive and confidential in nature. The fifth criterion for the non-functional requirement is the security of the information. The security is extremely important for all information (Balaji & Murugaiyan, 2012). Any type of unauthorized or unsanctioned access must be prohibited at every aspect. Biometric authentication is the best option for My Health Record system. It will prevent all types of unauthorized access of information.
Functional Requirements of the System vs Non Functional Requirements
The functional requirements of a system calculate the probable functions of a particular system, which is to be implemented. In simple words, the functional requirements refer to the typical functions, which are estimated to be coming out of the system (Chung et al., 2012). The difference between the functional and the non-functional requirements lie here. The non-functional requirements only deal several qualities, which are evident to be present in the system. This is the main difference between two of them.
Cloud Based Solution
Headspace is suffering from some of the major problems and has taken the decision to opt for cloud-based solution in their business (Galibus & Vissia, 2015). There are normally four main types of clouds present in market. These four types of clouds include private, public, hybrid and community clouds. The type of private cloud is a closed cloud and only particular group of customers is able to access the data. There are no such restrictions in public cloud. All customers can access public cloud easily. Hybrid cloud is the amalgamation of both the private and public clouds (Rittinghouse & Ransome, 2016). Community cloud is a fixed group of clients. However, these clients should have same requirements.
The recommended cloud for the My Health Record system of Headspace is the Hybrid cloud. Hybrid cloud is the amalgamation of both the private and public clouds (Jain & Nandakumar, 2012). This particular characteristic of hybrid cloud means that a typical hybrid cloud has various features of public cloud and also many characteristics of private cloud. The selection of public cloud will be the worst option for Headspace as security is highly threatened in that case. Private cloud will also not be a good option as it allows only registered clients. Therefore, hybrid cloud would be the best solution for this case (Li et al., 2015). The access is not restricted and the security is high. The moment a hybrid cloud will detect an intrusion or attack, the cloud will block the entire system.
Cloud Environment Strength
Hybrid cloud has various advantages or strengths, which make it popular for any organization (Chen & Zhao, 2012). The main benefits of hybrid cloud are as follows:
i) Security: This is the major advantage of hybrid cloud. The security of this particular type of cloud is extremely high and attacks are almost impossible here (Li et al., 2014). Moreover, it contains almost all the features of public and private clouds and thus, it is extremely popular amongst all organizations.
ii) Cost Effective: This is another main advantage of a hybrid cloud (Kulkarni et al., 2012). Although, hybrid cloud contains the features of both public and private clouds, it is absolutely cost effective and is affordable for all organizations.
Cloud Environment Weakness
Hybrid cloud has several advantages. However, there are few disadvantages as well (Rittinghouse & Ransome, 2016). The weaknesses or the disadvantages of a hybrid cloud are as follows:
i) Movement of Data: The data in hybrid cloud is continuously moved or shifted from public and private clouds (Li et al., 2012). The intruder gets easy access to the confidential data during this time and the data is hacked.
ii) Implementation Cost: The cost of implementation in a hybrid cloud is higher than the public or private cloud. This cost is even more if it is implemented in a large organization (AlZain et al., 2012). Thus, it sometimes becomes problems for smaller organizations to implement this cloud.
SDLC or software development life cycle divides the entire software development lifetime into a number of phases, successful completion of which ensures a project’s success (Balaji & Murugaiyan, 2012). These phases are named as requirement analysis, feasibility study, project implantation , testing and so on. There are two types of approaches. They are the predictive approach and adaptive approach.
The predictive approach of the SDLC or software development life cycle means the entire life cycle of a project while initiating the project (Tuteja & Dubey, 2012). This approach is only possible if the project schedule and scope are clear. The pros and cons of the predictive approach in SDLC are as follows:
i) The planning of the particular project is completed smoothly.
ii) The scope and the schedule of the project are clear to all the members of the project.
iii) The requirements of the project are absolutely clear to all the members of the project (Mahalakshmi & Sundararajan, 2013).
iv) The progress of the project is tracked throughout the project.
i) Improvisation is not possible at any part of the project.
ii) The feedback cannot be taken as everything is previously planned.
The adaptive approach is not same as the predictive approach. The entire planning of the project is not done in the beginning of the project (Mahalakshmi & Sundararajan, 2013). At every stage of the project, proper deliverables are sent and proper acknowledgement is taken. The pros and cons of adaptive approach are as follows:
i) Improvisation is possible in every phase.
ii) Feedback is taken into consideration for improvement of the project.
i) The cost is extremely high.
ii) Scope and the schedule time are not clear (Tuteja & Dubey, 2012).
It is recommended and suggested for Headspace organization to opt for the predictive approach of SDLC because of the benefits of the approach.
Therefore, from the above discussion, it can be concluded that Headspace is a recognized and renowned organization that works with various youth generation, whose ages vary between twelve to twenty-five, who are experiencing mental illness and ill health. Anxiety and depression are the most common mental health problems, although there are many other mental illnesses as well. Every time these patients need to tell their problems again. The young people discussed little and even stopped talking about their problem. This makes it harder for the professionals to help them for their problems. Initially, a social worker of Headspace, then the medical staff in a hospital, maybe a psychiatrist, a psychologist, and a general practitioner watches them. Recently, funds are being raised for the formation of a system, which will record the patient’s story in the very first time. This will give authority to the distinct professionals, so that the specific case studies and their stories can improve, and the young patient can be facilitated more precisely and appropriately. This particular organization has considered opting for a cloud-based option for their project. This particular report focuses on the type of cloud, which should be undertaken by Headspace for their business. This report outlines a specific description on the requirement for the implementation of cloud in the Headspace organization. The above report outlines the various non-functional requirements of the system and the type of cloud Headspace should be opting for their business. The report further mentions about the recommended software development life cycle approach, which would be the best for the organization. This recommendation will be beneficial for Headspace.
AlZain, M. A., Pardede, E., Soh, B., & Thom, J. A. (2012, January). Cloud computing security: from single to multi-clouds. In System Science (HICSS), 2012 45th Hawaii International Conference on (pp. 5490-5499). IEEE.
Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30.
Chen, D., & Zhao, H. (2012, March). Data security and privacy protection issues in cloud computing. In Computer Science and Electronics Engineering (ICCSEE), 2012 International Conference on (Vol. 1, pp. 647-651). IEEE.
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2012). Non-functional requirements in software engineering (Vol. 5). Springer Science & Business Media.
Galibus, T., & Vissia, H. E. R. M. (2015). Cloud storage security. Proc NSCE, 2014, 123-127.
Jain, A. K., & Nandakumar, K. (2012). Biometric Authentication: System Security and User Privacy. IEEE Computer, 45(11), 87-92.
Kulkarni, G., Gambhir, J., Patil, T., & Dongare, A. (2012, June). A security aspects in cloud computing. In Software Engineering and Service Science (ICSESS), 2012 IEEE 3rd International Conference on (pp. 547-550). IEEE.
Li, J., Li, Y. K., Chen, X., Lee, P. P., & Lou, W. (2015). A hybrid cloud approach for secure authorized deduplication. IEEE Transactions on Parallel and Distributed Systems, 26(5), 1206-1216.
Li, Q., Wang, Z. Y., Li, W. H., Li, J., Wang, C., & Du, R. Y. (2013). Applications integration in a hybrid cloud computing environment: Modelling and platform. Enterprise Information Systems, 7(3), 237-271.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A Comparative Study. International Journal of Emerging Technology and Advanced Engineering, 3(6), 192-196.
Pearce, C., & Bainbridge, M. (2014). A personally controlled electronic health record for Australia. Journal of the American Medical Informatics Association, 21(4), 707-713.
Rittinghouse, J. W., & Ransome, J. F. (2016). Cloud computing: implementation, management, and security. CRC press.
Steele, R., Min, K., & Lo, A. (2012). Personal health record architectures: technology infrastructure implications and dependencies. Journal of the Association for Information Science and Technology, 63(6), 1079-1091.
Tuteja, M., & Dubey, G. (2012). A research study on importance of testing and quality assurance in software development life cycle (SDLC) models. International Journal of Soft Computing and Engineering (IJSCE), 2(3), 251-257