Assessment Details and Submission Guidelines Unit Code BN314 Unit Title System Architecture Assessment Type Individual Assignment Assessment Title Assignment 1 Purpose of the assessment (with ULO Mapping) • To identify and understand different types of users who should be involved in investigating system requirements • To investigate the kind of information required to model system requirements • Understand the difference between functional and non-functional system requirements Weight 15 Total Marks 45 Word limit N/A Due Date Submission Guidelines • All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page. • The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings. • Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using IEEE referencing style. Extension • If an extension of time to submit work is required, a Special Consideration Application must be submitted directly to the School's Administration Officer, in Melbourne on Level 6 or in Sydney on Level 7. You must submit this application three working days prior to the due date of the assignment. Further information is available at: http://www.mit.edu.au/about-mit/institute-publications/policies-procedures-and-guidelines/specialconsiderationdeferment Academic Misconduct • Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: http://www.mit.edu.au/about-mit/institute-publications/policies-procedures-and-guidelines/Plagiarism-Academic-Misconduct-Policy-Procedure. For further information, please refer to the Academic Integrity Section in your Unit Description.   Assignment Description Case Study: Mental Health Care Patient Management System (MHCPS) A regional health authority wishes to procure an information system to help manage the care of patients suffering from mental health problems. The overall goals of the system are twofold: 1. To generate management information that allows health service managers to assess performance against local and government targets. 2. To provide medical staff with timely information to facilitate the treatment of patients. The health authority has a number of clinics that patients may attend in different hospitals and in local health centres. Patients need not always attend the same clinic and some clinics may support ‘drop in’ as well as pre-arranged appointments. The nature of mental health problems is such that patients are often disorganised so may miss appointments, deliberately or accidentally lose prescriptions and medication, forget instructions and make unreasonable demands on medical staff. In a minority of cases, they may be a danger to themselves or to other people. They may regularly change address and may be homeless on a long-term or short-term basis. Where patients are dangerous, they may need to be ‘sectioned’ – confined to a secure hospital for treatment and observation. Users of the system include clinical staff (doctors, nurses, health visitors), receptionists who make appointments and medical records staff. Reports are generated for hospital management by medical records staff. Management have no direct access to the system. The system is affected by two pieces of legislation (in the UK, Acts of Parliament). These are the Data Protection Act that governs the confidentiality MHCPMS Case Study 2 of personal information and the Mental Health Act that governs the compulsory detention of patients deemed to be a danger to themselves or others. The system is NOT a complete medical records system where all information about a patients’ medical treatment is maintained. It is solely intended to support mental health care so if a patient is suffering from some other unrelated condition (such as high blood pressure) this would not be formally recorded in the system. As a lead analyst for MHCPS, it is your responsibility is to plan and gather system requirements. Answer the following questions on how you would gather requirements for the proposed system. 1. Who are MHCPS stakeholders? 2. What are the different ways which can be used to gather the requirements for new MHCPS? Explain each of them. 3. How would you determine the system requirements? Why it is important to identify system requirements precisely? 4. What would be the primary functional requirements for the proposed system? (Hint: you can suggest your own functional requirements which are not listed in the scenario) 5. Briefly describe some possible non-functional requirements for MHCPS under following categories: a) Usability b) Safety c) Privacy d) Operational Cost   Marking criteria: Marks are allocated as follows: Section to be included in the Assignment Description Marks Question 1 (stakeholders) Identification of different stakeholders, Reasons for why each group is identified and included in defining system requirements 10 Question 2 (Fact Finding) Determining system requirements questions. At least 3 different types of questions should be listed 7 Question 3 (Identification of Functional Requirements) List of primary functional requirements for the proposed system. At least 5 different functional requirements should be identified from the case study 20 Question 4 (Identification of non-functional requirements) List of non functional requirements of the proposed system. At least 5 different functional requirements should be identified from the case study 5 Reference style Follow IEEE reference style 3 Total 45