Reference no: EM13836121

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 their previous environment and circles of influence, without the coping and support mechanisms that a case worker can provide.

Outputs should include the following:
• A draft Project Vision.
This sets out the business case, and summarises other aspects of the project, including 'needs and features', and other product requirements.

• Functional Requirements Specification.
  This should involve a Use Case Model, backed up by short use case descriptions. There should be at least one full use case description for a critical core use case; this could be an Emergency Department admission, or inter-agency communication, such as between a public hospital psychiatrist and a headspace case worker. (Identifying critical core use cases allows us to address the issue of project risk).
• Please note: Prior to the mid session break further information will be released in the Interact subject site. This is to mirror what often happens in real life. It will further build up the case study.

RationaleThis assessment has been designed to allow students to test and demonstrate their topic understanding related to:

• describe the context of an information system;
• compare the range of requirements gathering techniques;
• describe and apply feasibility study methods and approaches;
• develop system requirements models