Information System Assignment: New Access System For Headspace

Question

Task: Further Background
Refer to background information provided in Assessments 1 and 2 regarding the Headspace NewAccess project. The project is considering cloud based solutions which should be investigated. Consider various aspects of cloud based solutions such as: data security, which includes data ownership (by Headspace, the young person, medical professionals, the Emergency Department etc). As well as other relevant aspects of cloud solutions.

Complete the Following
Please refer to the marking guide when preparing your response to see what criteria and standards will be used to assess your work and your progress.

Non-Functional Requirements

• This sets out the critical system qualities, system interfaces, user interface requirements, and system constraints.
• Use to ‘FURPS+’ acronym as reference, and ensure that you cover the non-functional aspects of the acronym, Usability,

Reliability, Performance and Security. Review of cloud based.

A review of the strengths and weaknesses of cloud based solutions, taking into consideration the environment in which the solution will be deployed.

SDLC Approach
Write brief description of the Pros and Cons to approaching the project using the ‘Predictive’ SDLC, then the Pros and Cons to approach the project as ‘Adaptive’ SDLC. Then recommend either Predictive or Adaptive to the SDLC for the project and briefly describe why.

Answer

Introduction
Mental health conditions, such as anxiety and depression have become too common for the younger generation of Australia. The issues are impacting the entire Australian population. Headspace is an organization that provides mental health services to the patients. Earlier, the patients were required to share information about their mental health with the professionals of Headspace. The repetition of the information multiple times usually led to the improper coverage after initial rounds. New Access is an automated information recording system that has been proposed to be implemented in Headspace.

Non-Functional Requirements
New Access system will provide various benefits to Headspace along with the patients, medical professionals, and users. The benefits will be realized only when the system is developed as per the user expectations, functional, and non-functional aspects. Non-functional requirements of New Access will have equal significance as the functional aspects. The development of the system shall be done so that the non-functional requirements are incorporated.

Usability
The primary aim of the New Access system is to automatically record the information being shared by the mental health patient. The design and source code of the system must be in accordance with the theme of the healthcare application. The New Access system shall be deisgned so that the users may understand the features and options included in the system on their own. The navigation in the system must be smooth and the element of consistency shall be maintained all throughout the application(Lauesen & Younessi, 2016).

System Reliability
There are various legal and regulatory rules and policies that the health information of the patients is associated with. The security and privacy of the health data is of utmost significance. It is also necessary that the end-system users are provided with the updated and real-time information at all times(Chung, 2016).

System Performance
The system must be designed in such a way that it records the health information of multiple users at the same instance and there is no issue with the response time or throughput time at any point of time(Malan & Bredemeyer, 2010).

System Supportability
The New Access system must be supportable and scalable so that any of the alterations are easy to make(Shaikh & Misbahuddin, 2016). The amount of re-work in the system will minimize with the inclusion of this quality in the system.

System Interfaces
List of User Interfaces

• Responsive web design must be used as the approach for designing the UI aspects of New Access system. The users must feel connected with the system and the system shall respond to the users as per the action performed by them. For instance, if the user switches to the landscape mode then the application shall set its orientation accordingly.
• The end users of the system will include the medical professionals and the theme of the application is mental health services and information collection. The use of colors shall be in accordance with the theme.
• The system shall interact with the users by acknowledging the user actions. For instance, the menu item accessed shall get highlighted in a different color and likewise.
• Personalization and customization shall be made possible on the application (Fosse & Delp, 2016).
• One of the most significant principles of the system shall be consistency of the elements included in the system.
• System navigation must be smooth across all the pages and screens.
• The textual content shall be styled as per the uniform styling principles.
• The users shall be able to customize the reports in terms of their format and properties.

External Systems/Devices Interfaces

• Secure Socket Layer (SSL) and Transport Layer Security (TSL) to ensure the sharing of encrypted and secure mails.
• Integration of File Transfer Protocol (FTP) to allow sharing of files between the medical professional and senior administration.
• Internet Control Message Protocol (ICMP) and Address Resolution Protocol (ARP for routing interface and activities.
• IPSec for security of the information sets
• Automated data analytics tools to analyze the real-time information.
• Interface for health monitoring tools so that the information recorded is compatible with the system database(Conde et al., 2010).
• Secure HTTPS for secure data sharing and communication over the web (Wheatcraft, 2010).

Set of Constraints

• New Access system shall be developed in PHP as the programming language
• Cloud-based database shall be set up at the back end.
• Selenium shall be used as the tool for automation testing of the system (Dettmer, 2016).

Cloud Based Solutions: Review
The New Access system will be deployed using cloud computing as the technology. There are cloud models that will be needed for the implementation of New Access models. There are various cloud delivery models that have been designed. Three primary cloud delivery models include Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS).

New Access system for Headspace must be delivered using PaaS as the cloud model. One of the major concerns with the cloud models is the security and privacy issues and risks. However, the security of the health information will be enhanced with the use of PaaS model. The occurrence of data breaches and network-based attacks will be avoided and mitigated with the use of PaaS model. Maintenance of the system will also get easier by delivering the system using the PaaS model. Ownership issues will also be avoided. There are various security risks that the cloud networks and applications are exposed to. Some of the common risks include malware attacks, data breaches, man in the middle attacks, data manipulation issues, denial of service attacks, distributed denial of service attacks, eavesdropping attacks, and many others. The involvement of PaaS model will provide enhanced security and the integration of the security controls will also get easier. Similarly, there are several cloud deployment models to choose from. The deployment can be done using the cloud model as private cloud, public cloud, or combination of the two referred as hybrid cloud. The New Access system will have varied set of functionalities. Some of these may benefit using the private cloud model while there may be some that will be suitable to be carried out on the public cloud. Therefore, hybrid cloud model shall be used for the deployment of New Access system.

SDLC Approach
A software development approach shall be determined in advance for the New Access system. The approach may belong with the predictive or adaptive family of methodologies.

Predictive Methodologies for System Development
The predictive approach of system development is a traditional approach in which the development activities and their order are determined in advance. There is a pre-defined cycle that is to be followed by the development team for developing a system. There are various methodologies that are defined under predictive set of methods. One of the most widely used is the Waterfall model for system development. In this methodology, system development is done in a sequential set of steps that are known in advance.

Adaptive Methodologies for System Development
The second category is the adaptive methodology in which the steps to be followed are not known in advance. A methodology in this category may involve different steps for different projects. There is a no pre-defined list and the methodology works on an ad-hoc basis. The most common adaptive approach is the agile methodology that works in a series of sprints. These are iterations in which the sub-set of the overall requirements are involved and executed to achieve the final goal (Ccsu, 2011). The requirements of the system will be put in a product backlog and the working set will be obtained from the backlog and will be placed in the sprint backlog. The methodology will provide working product at the end of every sprint and the customer feedback will also be asked for.

Recommendations & Conclusions
The recommended cloud model for New Access system is Platform as a Service (PaaS) model. The recommendation has been given as the PaaS model will make sure that the security of the system is enhanced and easy to maintain. The overall maintenance will also be easier. The deployment model recommended is the hybrid model. The recommendation is made on the basis of the varied nature of the operations and information sets involved with the application. The system development methodology that is recommended for the system is Agile Scrum methodology. It is an adaptive methodology that will make sure that the customers have a sub-set of the final product at a gap of 2 to 4 weeks. The customers will be asked to review the modules to provide their comments and feedback. The improvement activities will be made as per the comments from the customers.

Project management is another significant discipline and it is necessary that the project management approach is also determined in advance. The one that is recommended for the New Access system is Project Management Body of Knowledge (PMBoK) (Csbdu, 2004). The methodology is recommended as the management of all the project knowledge areas will be done. The management process will involve several phases so that the short-term goals are defined. These goals will be easy to track and achieve as compare to an overall project goal. The estimations and calculations for the project will be made in the planning phase of the methodology.

References
Ccsu. (2011). Agile Software Development. Retrieved 02 October 2018, from http://www.cs.ccsu.edu/~stan/classes/cs530/slides11/ch3.pdf
Chung, L. (2016). Non-Functional Requirements. Retrieved 02 October 2018, from https://www.utdallas.edu/~chung/SYSM6309/NFR-18-4-on-1.pdf
Conde, J., De, S., Hall, R., Johansen, E., Meglan, D., & Peng, G. (2010). Telehealth Innovations in Health Education and Training. Telemedicine And E-Health, 16(1), 103-106. http://dx.doi.org/10.1089/tmj.2009.0152
Csbdu. (2004). A Guide to Project Management Body of Knowledge. Retrieved 02 October 2018, from http://www.csbdu.in/csbdu-old/pdf/A%20Guide%20to%20the%20Project%20Management%20Body%20of%20Knowledge.pdf Dettmer, H. (2016). Systems and Constraints: The Concept of Leverage. Retrieved 02 October 2018, from http://goalsys.com/systemsthinking/documents/Part-6-SystemsandConstraints.pdf
Fosse, E. & Delp, C. (2016). Systems Engineering Interfaces: A Model Based Approach. Retrieved 02 October 2018, from http://www.omgsysml.org/System_Engineering_Interfaces-IEEE_2013.pdf
Lauesen, S. & Younessi, H. (2016). Six Styles for Usability Requirements. Retrieved 02 October 2018, from http://www.itu.dk/~slauesen/Papers/SixStyles.pdf
Malan, R. & Bredemeyer, D. (2010). Defining Non-Functional Requirements. Retrieved 02 October 2018, from http://www.bredemeyer.com/pdf_files/NonFunctReq.PDF

McAtee, M. (2016). A good compliance system takes the administrating out of managing. Qualitydigest.com. Retrieved 02 October 2018, from http://www.qualitydigest.com/nov01/html/paperless.html Shaikh, A. & Misbahuddin, M. (2016). A system design for a telemedicine health care system. Retrieved 02 October 2018, from https://gupea.ub.gu.se/bitstream/2077/10498/1/gupea_2077_10498_1.pdf

Wheatcraft, L. (2010). Everything you wanted to know about interfaces, but were afraid to ask. Retrieved 02 October 2018, from http://spacese.spacegrant.org/uploads/images/UserContributedFiles/WheatcraftInterfaces110909.pdf

Wick, S. (2016). User Stories and Use Cases - Don’t Use Both!. Batimes.com. Retrieved 02 October 2018, from https://www.batimes.com/articles/user-stories-and-use-cases-dont-use-both.html