statguru
|
University of Derby School of Computing and Mathematics
|
||
|
In-course Assignment Specification
|
||
|
Module Code and Title: 5CC519 Data management and Business Intelligence
|
||
|
Assignment No. and Title: A SAS-based information analysis and presentation system
|
||
|
Assessment Tutor: John Panneerselvam
|
Weighting Towards Module Grade: 100%
|
|
|
Date Set: 25/01/2018
|
Hand-In Deadline Date: Various: Design Justification: 29 March 2018, 11.59pm. Demonstration: 4 May 2018 |
|
|
|
||
|
Penalty for Late Submission Assignments are submitted electronically. The electronic submission area will continue to accept work after the due date. The date and time of submission will be recorded to identify late submissions. Please visit the regulations pages (http://www.derby.ac.uk/regs) for more information. Between the opening of the assignment submission and the deadline date, in most cases, you can submit and overwrite with a resubmission repeatedly. It's important you try to submit as early as you can to take advantage of the plagiarism checking function prior to your final submission. This will also mean that you've submitted something for your lecturer to mark if circumstances beyond your control mean that you can't complete your final submission. For more information on this please see our exceptional extenuating circumstances (http://www.derby.ac.uk/EEC) page. See http://www.derby.ac.uk/esub for more information.
|
||
|
|
||
|
|
Level of Collaboration: None |
|
|
|
||
|
Learning Outcomes covered in this Assignment: 1. Identify and critically evaluate the key requirements for effective data management, analysis and presentation to meet users’ needs 2. Develop a small management information reporting system that meets the users’ needs using a prototyping / Agile approach
|
||
|
Criteria for Assessment: See Portfolio Specification
|
The Task
Overall, you will specify, design and build a small management information analysis and presentation system to analyse the NHS Transparency RTT (Referral to Treatment Time) datasets from the following location https://www.england.nhs.uk/statistics/statistical-work-areas/rtt-waiting-times/rtt-data-2016-17/ and use the XLS spreadsheets for the Admitted Adjusted Commissioner statistics.
The first part of the Portfolio, due on Thursday 29th March 2018 at 11:59 pm in Turnitin, is a justified specification of the Management Information System (MIS).
The second part of the portfolio, which will be assessed on Friday 4th May 2018, will be a demonstration of your SAS based MIS. The demonstration schedule will be published by Week 10.
The relative weightings of the two components is:-
Design Justification 30%
SAS based MIS 70%
Part 1 - Design and Justification - 30%
This will be a short business style report of approximately 1000 words which provides an outline of the MIS and its design. In order to prepare yourself to design the system and write the report, you will need to carry out at the following steps.
You are required to use the template provided for the Outline Design Specification. Please do not remove the section marking criteria. They provide you with a checklist of what you need to achieve for each section.
Step 1
Understand the structure and meaning of the data from the RTT Monthly spreadsheets; you will be able to do this using both Excel and SAS. From this, identify and justify the key stakeholders who have an interest in the data presented in the spreadsheets.
Step 2
Choose one of the stakeholders from the above analysis and identify and fully justify no more than three key questions that can be answered by a suitable selection and presentation of data from up to five of the RTT monthly sets of data.
Step 3
Identify the relevant data and the appropriate selection, summarisation and presentation necessary to allow the stakeholder to pose their question and then gain a suitably presented answer. You may need to consider performance issues in designing a reasonably efficient means of storing your data (this could be done using the Log statistics from the SAS 9.4 system when you experiment with different approaches).
Step 4
Present and justify simple mock-ups of the relevant data entry and presentation interfaces. User interface can be developed using MENU, SELECT, FRAME, PROJECT etc. Select and deploy the appropriate user interface using SAS.
Step 5
Identify and justify how you will prove that the MIS system that will be developed based on this specification and provide suitable test schedule specifications and test conditions.
Report Content
The key aspects that must be addressed in the specification report are:
1) Identification of the Stakeholder chosen for this MIS and justification of up to three types of questions
2) Identification and justification for the chosen Data Architecture to support the selection and presentation of the data necessary to provide answers to the questions
3) Identification and justification for the chosen Systems Logic to support the selection and presentation of the data necessary to provide answers to the questions
4) Identification and justification for the chosen User Interface to support the selection and presentation of the data necessary to provide answers to the questions
5) Identification and justification of the Test Data and Schedule to ensure that the system meets the Stakeholders’ needs
Assessment Criteria for the Design Report
Each of the assessment section will have a weighting of 20%.
|
Section |
100%-70% |
60%-69% |
59%-50% |
49%-40% |
39%-35% |
34%-0% |
|
Stakeholders |
Identifies stakeholder and 3 Key Questions - comprehensive justification |
Identifies stakeholder and 3 Key Questions and good justification |
Identifies stakeholder and 2 Key Questions and some justification |
Identifies stakeholder and 1 Key Question - basic justification |
Identifies either stakeholder or some questions |
Little of merit |
|
Data Architecture |
Justifies best option for RTT data based on SAS Log metrics for best performance |
Justifies SAS structure based on 3rd Normal concepts, i.e. storage efficiency |
Basic justification of the SAS storage structure in relation to questions |
Defines single repository in SAS |
Defines RTT sources as XL |
Little of merit |
|
Systems Logic |
Clearly justified specification of logic, using appropriate techniques such as UML or Flow-charts
|
Clearly justified specification of key logic |
Clear specification of logic |
Basic selection and processing criteria |
Identification of simple criteria |
Little of merit |
|
User Interface |
Fully justified definition of all aspects of the user interface including “criteria” input screens and output reports and graphics |
Justified definition of most aspects of the user interface including output reports and graphics |
Definition of some aspects of the user interface including output reports and graphics |
Definition of a few aspects of the user interface including output graphics |
Identifies types of graphs that might answer a user’s question |
Little of merit |
|
Test Requirements |
Comprehensively defined and justified test schedules and test data |
Justifies test schedules and test data |
Defines test schedules and test data |
Defines testing process |
Identifies need for testing and suggests how it might be done |
Little of merit |
Part 2 - Build MIS in SAS - 70%
Part 2.1 (50%):
Using the Outline Specification from part one of the portfolio, you will develop a small MIS application in SAS that implements the intent of your specification.
Part 2.2 (20%):
Each week you have been given a set of exercises to test your understanding of the material covered that week. You are to demonstrate a selection of the exercises that you have done for marking which will be randomly selected from exercises 1-10. Questions will be asked to test your understanding. The assessment will be based on your understanding and the knowledge of SAS programming.
Part 2.1 and 2.2 will be demonstrated together to your tutor during the last week of the semester. The demonstration schedule will be available on Udo Blackboard.
Assessment Criteria for part 2.1
Out of the 50% in part 2.1, coding and use of SAS will have 30% and data will have 20% weighting.
|
Percentage Band |
Coding and use of SAS |
Data |
|
90%-100% |
Relevant SAS Source code pre-written and stored in SAS system. Code modules chosen and run from a menu system. Data selection menu driven with complex options. Graphic data presentation, good choice of output styles which are menu driven. |
Uses pre-imported data in a saved master file using the PCT detail data and SHA ID data. Optimises SAS storage structures to the types of questions provided. Optimises storage space by use of surrogate keys to natural key tables. Optimises use of permanent and work file structures. |
|
80%-89% |
Relevant SAS Source code pre-written and stored in SAS system. Code modules chosen and run from a menu system. Data selection menu driven with complex options. Graphic data presentation, good choice of output styles. |
Uses pre-imported data in a saved master file using the PCT detail data and SHA ID data. Optimises SAS storage structures to the types of questions provided. Optimises storage space by use of surrogate keys to natural key tables. |
|
70%-79% |
Relevant SAS Source code pre-written and stored in SAS system. Code modules chosen and run from a menu system. Data selection code pre-written with complex options. Graphic data presentation, good choice of output styles. |
Uses pre-imported data in a saved master file using the PCT detail data and SHA ID data. Optimises storage space by use of surrogate keys to natural key tables |
|
60%-69% |
Relevant SAS Source code pre-written and stored in SAS system. Code modules chosen and run manually. Data selection code pre-written but with complex options. Graphic data presentation, good choice of output styles. |
Uses pre-imported data in a saved master file using the PCT detail data and SHA ID data. |
|
50%-59% |
Relevant SAS Source code pre-written and stored in SAS system. Code modules chosen and run manually. Data selection code pre-written. Simple Graphic data presentation, some choice of output styles. |
Uses pre-imported data in a saved master file using the PCT detail data and SHA ID data for several months |
|
40%-49% |
Relevant SAS Source code pre-written and copy / pasted into SAS system. Data selection code pre-written. Simple Graphic data presentation, no choice of output styles.
|
Uses pre-imported data in a saved master file using the PCT detail data for several months |
|
35%-39% |
Relevant SAS Source code pre-written and copy / pasted into SAS system. Data selection code written into programme editor window. |
Uses data for a single month imported at run time from XLS file using the PCT detail data |
|
0%-34% |
Little of merit |
Little of merit |
1