Reference no: EM13832294

The business case

Task

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.

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.

Online submission via Turnitin is required for this assignment. Details will be provided by your subject lecturer in the class or by notification in the subject site.

Rationale

This 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

Marking criteria

Criteria High Distinction (HD) Distinction (DI) Credit (CR) Pass (PS) Fail (FL)

Draft project vision Sets out the business case, and summarises other aspects of the project, including ‘needs and features', and other product requirements, in a way that demonstrates breadth and depth of understanding and has insights and awareness of deeper more subtle aspects of the topic content. Evidence of having researched/read more widely beyond the core materials. Sets out the business case, and summarises other aspects of the project, including ‘needs and features', and other product requirements, in a way that demonstrates breadth and depth of understanding and has insights and awareness of many of the deeper more subtle aspects of the topic content.
Evidence of having read beyond the core materials. Sets out the business case, and summarises other aspects of the project, including ‘needs and features', and other product requirements, in a way that demonstrates thorough understanding of material presented in core texts and readings. Sets out the business case, and summarises other aspects of the project, including ‘needs and features', and other product requirements, in a way that demonstrates evidence of having read material presented in core texts and readings. However literature is presented uncritically in a purely descriptive manner.

Content acknowledged but not really taken into account. Sets out the business case, and summarises other aspects of the project, including ‘needs and features', and other product requirements, in a way that demonstrates very little evidence of having read material presented in core texts and readings. Inaccurate or inconsistent acknowledgment of sources.

Limited knowledge of key principles and concepts.

Functional Requirements Specification Use Case Model and descriptions, including a critical core use case. Demonstrates breadth and depth of understanding and has insights and awareness of deeper more subtle aspects of the topic content. Evidence of having researched/read more widely beyond the core materials. Use Case Model and descriptions, including a critical core use case. Demonstrates breadth and depth of understanding and has insights and awareness of many of the deeper more subtle aspects of the topic content. Evidence of having read beyond the core materials. Use Case Model and descriptions, including a critical core use case. Demonstrates thorough understanding of material presented in core texts and readings. Use Case Model and descriptions, including a critical core use case. Demonstrates evidence of having read material presented in core texts and readings. However literature is presented uncritically in a purely descriptive manner. Content acknowledged but not really taken into account. Use Case Model and descriptions, including a critical core use case. Demonstrates very little evidence of having read material presented in core texts and readings. Inaccurate or inconsistent acknowledgment of sources.

Limited knowledge of key principles and concepts.

Presentation, writing style, grammer and references Highly developed skills in expression and presentation of response.

Fluent writing style appropriate to assessment task.

Grammar and spelling accurate. Well-organised. Well-developed skills in expression and presentation of response.

Fluent writing style appropriate to assessment task.

Grammar and spelling accurate. Good skills in expression and clear presentation of response.

Mostly fluent writing style appropriate to assessment task.

Grammar and spelling accurate. Some skills in expression and presentation of response.

Meaning apparent but writing style not always fluent or well organised.

Grammar and spelling contain errors. Rudimentary skills in expression and presentation of response.

Not all material is relevant and/or is presented in a disorganised manner.

Meaning apparent but writing style not fluent or well-organised,

Grammar and spelling contain errors.