Introduction Background: "headspace" (yes small 'h') is an organization that works with youth aged 12 to 25 who experience mental ill health. In 2014 youth suicide in regional NSW for the age groups 16 to 24 was particularly alarming, especially amongst Indigenous youth. One of the problems identified was that a young person with suicidal ideation might see multiple professionals before getting the help they need. Each time they need to re-tell their 'story'. Soon the young people clam up and say very little, making it even harder for professionals to help them. Initially they might see a headspace case worker, then medical staff in a hospital emergency department, perhaps a General Practitioner, a psychologist, a psychiatrist, and others. Currently funding is being sought to build a system that will capture the 'story' the first time it is told, and give access to successive professionals, so that case notes and the story can become enriched, and the young person can be assisted more appropriately. Further background: Youth assigned to a headspace case worker may subsequently be admitted to the Emergency Department (ED) of the local regional hospital. Currently there is no requirement for the ED staff to notify the headspace case worker when a client has been released. Sometimes case workers are notified, but often not. It means that days and even weeks can transpire before a case worker becomes aware of that release. In the mean time the young person tends to return to the environment and circles of influence that led to the suicidal behaviours in the first place, without the coping and support mechanisms that a case worker can provide. Assignment that need to be done Mobile and cloud based solutions should be investigated. Furthermore, data secuirty also needs to be further investigated, which includes data ownership (by headspace, the young person, the ED, etc), data security in the cloud and who has access permission, and to what level of access, etc. Outputs should include the following: • An updated Project Vision. This should be a revised Vision from previous assignment. Project Vision format is in the uploaded files. Use the format in Vision.docx for project Vision. • Non-Functional Requirements – a System Wide Requirement Specification. This sets out the critical system qualities, system interfaces, user interface requirements, and system constraints. Use the format in the uploaded files, systemwide_req_spec.docx for the non functional requirements. For example you can consider the features like feasibility – can we do it? If yes how can we do it? • Support – how am I providing the support (ex: training, video, FAQ) • Usability – create mockups for app used over phone {how the screen looks, how userfriendly it is} Previous Assignment New Assignment Solution should have the following No.of users scalability of no.of users (how many users?) Results – Reports how accurate these reports are? Defined systems in terms of functionality Reliability of the system (for each system process) User was providing I/P to the system by executing the process of the system . Ex: uploading the patient interview details How do you monitor the performance of the system process How long will it take upload diff types of media (audio/vieo/text) over the cloud Factors to measure performance of the system Watch the video/listen the audio – retrieving patient interbiew Diff plugins required to watch the video. (Plugins – hardware/software constraint) • Validation, and project management issues need to be considered in the response to this assessment item. Validation: In validation take two use cases and consider the authentication permissions need to be given for the system. Project management issues includes • scope • work break down structure : Use software development life cycle to create work breakdown structure • Using work breakdown structure calculate cost and time required to complete the project • Calculate the cost i.e net present value • Risk Management: • Create risk register with below fields. Would consider risks that whose occurrence probability are high and the impact of those risks are high Risk Register Risk id Description Solutions Risk owner Root cause Guidelines to be followed while making the assignment: • This assignment is an enhanced version of Previous Assignment I have already done. So please use the Previous Assignment document in uploaded files to create the solution. The assignment should be done in the one word file. Use the specified format in the documents provided wherever mentioned. • If you have any issues understanding the assignment please feel free to call me or email me. • Contact number: 0470568024 • Please follow the document in uploaded files, Ass 3 Markingguide.docx for the solution.