Case Study Assignment - Part 2 (Report and Presentation Slides)
Case Study Assignment - Part 2 (due 9th October 2015 @ 11:55pm)
This is the second part of your case study assignment. If you have not completed part 1 of your case study assignment, you need to do this now as it is a critical requirement for completing this part of the assignment. Note that when you submit this assignment, you should include part 1 (corrected if necessary) to show your completed work that informs this second part of the study.
Assignment Part 2 should not exceed 25 pages. This page count includes coversheet, tables, diagrams and references, but excludes your revised assignment 1 (including your revised event table with activities).
If you are not clear how to cite and reference your research consult the unit outline or search for referencing on the UC website.
You might treat the list of required assignment components below as a check list. Omitting one or more of them will have a negative effect on your assignment grade. Consult the notes you have been taking during lectures and tutorials combined with the research you have been conducting each week to fully understand the assignment. You should also refer to your textbook and other resources.
1. Update Part 1 of the assignment
Apart from what you see appropriate, you should note the feedback that you have received during your presentation as well as in your written report on part 1 of the case study and adjust as necessary. (Please allow at least couple of weeks before your tutor returns marked part-1 assignment to you. So, it is suggested that you start doing part 2 of the assignment earlier rather than later, and do not wait for part-1 of assignment to be marked because it might be too late to complete part-2 of the assignment by the time you get your marks back from your tutor. Remember, you can always revise part-1 as well as your part-2 of the the assignment when you have a draft submission ready).
2. Develop a Context Diagram for your system
If you are not clear what a context diagram might be, then revise the lecture slides from week 5 and 6.
3. Develop a top level Data Flow Diagram (DFD 0) for your system
This diagram should capture the high level features of the system.
4. Develop lower level DFDs for the core components of your case
Level 1 and perhaps level 2 diagrams for your system's core components. The number of levels may vary based on the complexity of your case study and your design decisions. It is also your judgment call.
5. Design and develop a Data Dictionary for your core system to data elements level
These data dictionary entries should be for your DFD diagrams.
6. Develop Process Specifications for the core components of your system
These specifications should be for lowest level of processes that appear on your DFDs. You should specify three different processes using one of each types - structured English, decision table and decision tree. In other words, you will provide three pSpecs in total - one of each type.
7. Develop an Entity Relationship Diagram (ERD) for your system
It's up to you to decide whether you want to attempt normalisation or not.
8. All assumptions must be documented
9. List of references (Harvard style)
We will be looking for evidence of research and reasoning.
Note on Presentation
Every student should upload his/her presentation slides in this dropbox with the report.
Each student will get strictly 4 minutes to present his/her work, followed by Q&A for a minute. Students can't cover every aspect of the assignment and may be asked to present only couple of models assigned in random during the presentation, such as one DFD, ERD, partial Data Dictionary, pSpec etc. Hence, students should not be surprised by random allocation of models to present and should prepare for it.
Submission status
This assignment will accept submissions from Saturday, 3 October 2015, 12:55 PM