Here
ATMC ICT112 Creative Problem Solving with Programming Task 2 Semester 1, 2020 ATMC ICT112 Creative Problem Solving with Programming Task 2 Page 2 of 11 Assessment and Submission Details Marks: 30 % of the Total Assessment for the Course Due Date: 9am Monday, 15th June 2020 Assignments are to be submitted by SafeAssign. DO NOT SUBMIT THE ASSIGNMENT TO THE COURSE CO-ORDINATOR OR TUTOR. Submit your assignment to the link under Assessment -> Task 2 on Blackboard. The submission link will be open a week before the due date. Please follow the submission instructions provided. A draft submission area will be provided for you to check your assignment for academic integrity purposes. Instructions to use the draft submission link and how to read the draft SafeAssign report are in the Task 2 assessment area. After you have made any final edits you will still need to submit the final assignment (via the Task 2 Submission folder) by the due date set for it. The assignment will be marked out of a total of 100 marks and forms 30% of the total assessment for the course. ALL assignments will be checked for plagiarism and/or collusion between individuals. The rubric attached at the end of this document provides detail of the marking criteria. Refer to your Course Outline or the Course Web Site for a copy of the “Student Misconduct, Plagiarism and Collusion” guidelines. Academic Integrity Information. Note: Each student MUST be able to produce a copy of their assignment and this copy MUST be produced within 24 hours of it being requested by the Course Co-ordinator. Failure to produce the second copy of the assignment when requested may result in loss of marks or a fail grade for the assignment. Requests for an extension to an assignment extension MUST be made prior to the date of submission and requests made on the day of submission or after the submission date will only be considered in exceptional circumstances. https://www.usc.edu.au/learn/student-support/academic-and-study-support/online-study-resources/academic-integrity ATMC ICT112 Creative Problem Solving with Programming Task 2 Case Study: Mammal Fauna Rescue Centre Background The Mammal Fauna Rescue Centre (MFRC) is a charity organisation that is dedicated to rescuing mammal fauna, rehabilitating them, and releasing them back to their natural environment. MFRC provide information regarding the location of around 400 wildlife rescue centres across the United Kingdom and therefore offer the opportunity for nationwide mammal fauna rescue. As a charity that is not supported by government funding they rely on donations from the general public for their important work. Due to their lack of funds the organisation you work for has offered to assist in the re-development of their mammal fauna rescue systems. Stage one is the admissions system which stores information on who brought in the mammal fauna, where it was found, suspected injuries, initial triage and/or vet notes and what fauna carer (if any) the animal is assigned to for rehabilitation or care. Animals are brought in for a large variety of reasons and sometimes multiple reasons, and the database is to record these and be able to query them. Each month a report is generated from the data in this database for the charity. Currently the report takes a day to generate which uses time which could be put to better use elsewhere. The report includes the totals and percentages for types of diagnosis, causes of affliction, species, taxons, and regions of the UK. It also includes monthly comparisons of the total number of admissions, yearly comparisons of the total number of admissions and a running total tally. The UK Mammal Fauna Rescue Centre can see thousands of admissions a year, and there is a large database of information (over 35000 entries) that is maintained both for their own record keeping and for regulatory requirements set down by the local and national government regulations. The system requirements are given in Appendix A. The current MFRC system has a very large number of issues and is far from efficient for the charity to use. The more time it takes them to enter their data, the less time and resources they can devote to saving the fauna. Your task is to streamline part of the monthly reporting by processing and generating graphics and summary information for the mammals that have been rescued in a given month. Assignment Requirements and Deliverables You are supplied three .csv data sheets that provide you with the information you need. Two of these sheets are the information on what species are in each taxon group, and what districts and regions are in each part of the UK. The final .csv is the summary of mammals admitted that month, the format of which is the same every month but the data inside will change (including number of rows). ATMC ICT112 Creative Problem Solving with Programming Task 2 PART A DESIGN & RATIONALE (30 marks) • Pseudo code for the problem solutions (15 marks) • Rationale, Discussion & Assumptions (15 marks) Submitted as a MS Word Document: • Pseudo code for the monthly report system. This should include: o what decompositions are made into Functions/Modules and or classes. • Rationale for the system’s design (decomposition) • Discussion of how the System’s test plan (i.e. how did you test your system). • Any assumptions that were made about the data and how to process it. PART B: IMPLEMENTATION (70 marks) • Code solution (50 marks) – at a minimum your code must demonstrate the following: o Import of .csv file (10 marks) o Filtering of data (15 marks) – your code should demonstrate the ability to filter the data, for example by region, by species, by species type, by week, etc. o Graphing with mathplotlib (15 marks) – you should produce 2 pie charts: 1 pie chart for regional results and 1 pie chart for species results ▪ Pass-Credit level, ALL species represented on the pie chart ▪ Distinction- High Distinction – top 10 species only represented on the pie chart o Output to .csv file (10 marks) ▪ 2 files: region-June2018.csv and species-June2018.csv • Format - the formatting of each file should be in line with the following example: Region name, Number in region, Percentage of total cases ‘Severn’, 216, ’63%’ ‘West Scotland’, 97, ’23%’ ▪ For both files: • Pass level output in any order unfiltered, no % • Credit level, output in any order with % • Distinction to High Distinction level, sort into descending order, filter ATMC ICT112 Creative Problem Solving with Programming Task 2 • Documentation and coding style (20 marks) Submitted as a single python notebook with name
_py.ipynb , containing your complete python implementation: • Your Part B MUST work on Anaconda Jupyter Notebook and be able to be demonstrated • Your system MUST have your name and student number included at the beginning of every file/module in the comments. Submission The completed assignment is to be submitted by SafeAssign on or before the due date. The assignment will be assessed according to the online rubric. Late submission of the assignment will result in a late submission penalties as per USC policy: Days Late Marks Deducted 1 day late 5% of the total available marks 2 days late 10% of the total available marks 3 days late 20% of the total available marks 4 days late 40% of the total available marks 5 days late 60% of the total available marks 6 days late 80% of the total available marks 7 or more days late 100% of the total available marks Assignment Return and Release of Grades Assignment grades should be available on the course web site within 10 business days after submission (15 business days after submission at the latest). Electronic feedback on the submission will be made available at this time. Where an assignment is undergoing investigation for alleged plagiarism or collusion the grade and feedback for the assignment will be withheld until the investigation has concluded. ATMC ICT112 Creative Problem Solving with Programming Task 2 Appendix A – System Requirements These requirements and sample reports are provided to assist in you in gaining an understanding of the existing system and the rescue centre’s needs. You do not need to implement these requirements nor all the reports. User Requirements - Every animal brought to a rescue centre is given a unique Admission Number which is found on the top right-hand side of their paper admission form. - Additionally, every admission is a patient. Every patient has a unique patient id. - All animals may be admitted more than once, if they are re-admitted their previous patient number should be re-used, along with the date they were re- admitted – all historical admissions should be maintained (and not overwritten). - The database needs to record, where the animal was found, including the district and region where it was found – reports are generated for particular regions upon request. There should be a link between the district that the animal was found in and the region it belongs to. - Badgers will have also have a badger tag. - Every patient may have a microchip. - Land species animals may have ear tags in one or both ears that uniquely identify them (The tags should have the same number but should be able to tell if one is missing). - Pinnipedia and Cetacea may also have a tag. - Not all tag number formats will be the same - Not all animals will have tags. - In addition to formal tags, some animals will have one or more alternate identifiers, being either a Country identifier, or transfer from or to another rescue facility, such as the RSPCA, these must all be maintained and searchable. - Animals are sorted into taxons and species, of which there are over 100 in the current system. Each species must be associated with exactly one taxon. - The system should be loss-less, no data should be over written. - Aetiology is the term used to describe the diagnosis categories for the mammals. Mammals can and will present with more than one aetiology. In addition, animals may be diagnosed with multiple diagnoses within a category – e.g. an animal may have multiple