Assessment item 3
Due date: 01-Oct-2017
Return date: 24-Oct-2017
Submission method options Alternative submission method
Refer to background information provided in Assessments 1 and 2 regarding the Headspace 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.
This sets out the critical system qualities, system interfaces, user interface requirements, and system constraints.
Use to ‘FURPS+’ acronym as reference, and ensure you at cover the non-functional aspects of the acronym, Usability, Reliability, Performance and Security.
In your answer, critically compare and contrast these non-functional requirements from the functional requirements for this system.
Review of cloud based.
A review of strengths and weaknesses of cloud based solutions. Taking into consideration the environment which the solution would be deployed.
Given the sensitive nature of mental health data, discuss how the data will be kept secure, particularly if third party products are involved which may not be subject to Australian legislative protections regarding the storage of such data.
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.
This assessment aligns with learning outcomes
be able to describe the context of an information system;
be able to compare and contrast the different methodologies of systems analysis and evaluate their appropriateness for different and complex situations;
be able to distinguish between requirement gathering techniques and combine these appropriately to apply to a real scenario;
be able to evaluate development requirements and prepare a feasibility proposal based on multidisciplinary (financial, human resource, technological) analyses;
be able to formulate and justify system requirement models based on evaluation of given situations; be able to assemble the components of a requirements model using the tools and techniques of object oriented or structured systems modelling.