ICT115
Introduction to Systems Design
Task 2
ATMC
Semester 3, 2019
Assessment and Submission Details
Marks: 35% of the Total Assessment for the Course Due Date: 11:59pm Monday, Week 12
Students must submit the assignment through Blackboard using SafeAssign
Submit your assignment to Blackboard Task 2. Please follow the submission instructions in Blackboard.
Note: Each student MUST make a second copy of the 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.
The task is an individual assignment and will be marked out of a total of 100 marks. It forms 35% of the total assessment for the course. ALL assignments will automatically be checked for plagiarism by the SafeAssign system provided by Blackboard.
Refer to your Course Outline or the Course Website for a copy of the ‘Student Misconduct, Plagiarism and Collusion’ guidelines. Academic Integrity Information.
Assignment submission extensions will only be made using the official USC Guidelines.
Requests for an extension to an assignment MUST be made to the course coordinator prior to the date of submission. Requests made on the day of submission or after the submission date will only be considered in exceptional circumstances.
Case Study: TFW Logistics
Founded in the UK in 1989, TFW Packages started as a small delivery service that gave fast and personal courier options for the delivery of small to medium packages within a 100 mile radius of London. Operating in a very competitive industry with various national and international competitors, TFW Packages pursued a strategy with personalised pick-up and delivery options, fast-tracking the transfer of packages using a variety of transport modes and communication devices.
Taking advantage of the increase in eCommerce, TFW Packages set up franchise opportunities in various international destinations. As they expanded their operation it became necessary to focus more on supporting their franchisees. To achieve this they instigated a technology strategy to develop wearable device apps that could give accurate and up to date advice on various aspects of the journey required for each parcel. Staying true to their original policy of always putting the customer first, TFW Packages now want to develop an app through which each of the franchisees’ customers can track the exact position of their package and share that with the person to whom the package is being sent.
By incorporating Google Maps the app would allow users to be able to identify the exact position of the parcel at any one point in time whether it was stationary at a collection point or moving in transit between destinations. It is planned that the app will show an estimated delivery time with no more than a 10 minute window. The app will also enable each package sender and receiver to know the exact time of delivery and where the parcel has been left (if the delivery location is unattended). Finally, the app is planned to allow direct communication between the sender, the receiver and the TFW Packages franchisee as well as providing other useful information.
End of Case Study
Assignment Task
TFW Packages has asked you to provide the following analysis and design requirements. You are free to design and include any process and design components into the app that you feel are important to TFW Packages. There are many possible answers so be aware that the key is to make your design, logic and explanations clear.
Use the accompanying report template to complete your assignment with the following outline. Refer to the Rubric attached at the end of this document for marking guidelines.
Analysis and Design Report outline
Title
1 Introduction
2 Data Flow Diagram (DFD) Create a 3 level DFD (pages 143-160 Tilley & Rosenblatt 2017) of the new app that TFW Packages require:
· a Context diagram
· a Level 0 Diagram including 3 areas of functionality, and
· 3 Lower Level Diagrams, one for each of the areas of functionality.
TFW Packages would like to understand the principle behind DFDs including the advantages and disadvantages, and how you have applied the DFD to modelling the new app.
3 User Persona · TFW Packages would like you to identify at least 2 more different user types who will use the new app
· Choose one of these users and create a one-page (two page at most) user persona based on the five steps in the Week 7 Tutorial material
· Along with the user persona TFW Packages have asked for an explanation of your reasonings behind each persona creation step for your particular user persona. For example:
o Step 1 – Build Empathy, how did you (hypothetically) go about building empathy with your persona?
o Step 2 – Create Header, why did you choose the name and what was the reasoning behind the summary quote?
o Step 3 - etc.
4 User Storyboard Imagine a TFW Packages user scenario and create a Storyboard based on the Week 6 Tutorial material.
· You may like to create a User Experience Storyboard (UX) – a storyboard with your user persona as the lead actor using the app,
or a
· Human Computer Interface Storyboard (HCI) – a storyboard modelling the device displaying the sequence of interaction with the app.
TFW Packages are not quite as interested in the graphic quality, but they are very interested in the clarity, logic and flow of the Storyboard.
5 Conclusion
6 Recommendations
Report Format
Your report should be no less than 1,500 words and it would be best to be no longer than 2,000 words.
The report MUST be formatted using the following guidelines:
· Paragraph text – 12 point Calibri single line spacing
· Headings – Arial in an appropriate type size
· Margins – 2.5cm on all margins
· Header – Report title
· Footer – Page number (including the word “Page”)
· Page numbering – roman numerals (I, ii, iii, iv) up to and including the Table of Contents, restart numbering using Arabic (conventional) numerals (1, 2, 3, 4) from the first page after the Table of Contents
· Title Page – Must not contain headers or footers. Include your name as the report’s author
· The report is to be created as a single Microsoft Word document (version 2007, 2010, 2013, 2016 or Office 365). No other format is acceptable and doing so will result in the deduction of marks.
Please follow the conventions detailed in:
· Summers, J. & Smith, B., 2014, Communication Skills Handbook, 4th Ed, Wiley, Australia.
Referencing
The report is to include appropriate references and these references should follow the Harvard method of referencing. Note that ALL references should be from reputable web sources, journal articles, conference papers, technical papers or a recognised expert in the field. DO NOT use Wikipedia as a reference. The use of unqualified references will result in the deduction of marks.
Submission
The completed assignment is to be submitted to Blackboard Task 2 by the due date of 11:59pm Monday of Week 12.
The assignment will be assessed according to the marking sheet. Late submissions will be penalised according to the policy in the course outline. Please note Saturday and Sunday are included in the count of days late.
Assignment Return and Release of Grades
Assignment grades will be available on the Blackboard course site in accordance with the university policy.
Where an assignment is undergoing investigation for alleged plagiarism or collusion the grade for the assignment and the assignment will be withheld until the investigation has concluded.
Assignment Guidelines
It is imperative that students take heed of the following points in relation to doing this assignment:
1. Ensure that you clearly understand the requirements for the assignment – what has to be done and what are the deliverables.
2. If you do not understand any of the assignment requirements – Please ASK the lecturer or your tutor.
3. Each time you work on any aspect of the assignment reread the assignment requirements to ensure that what is required is clearly understood.
End of Assignment
ICT115 Task 2 Rubric
Rubric Detail
Criteria
Levels of Ach ievement
High Distinction
Format report to clearly communicate case study design requirements
Weight
10.00%
Create 3 levels of DFD. Explain DFD principles and their application to the case study
Weight
30.00%
Identify case study users and Create one case study related persona and explain reasonings behind persona creation steps
Weight
30.00%
Create Case study related Storyboard (UX or HCI)
Weight
30.00%
85.00 to 100.00 %
Perceptive -Very well set out report format with title page, headings, page numbering, introduction, report body, conclusion, recommendations and well referenced. Polished, clear and logical communication to executive audience
85.00 to 100.00 %
Systematic and skillful - Skillful 3 level DFD and insightful analysis applied to the case study.
85.00 to 100.00 %
Perceptive and polished - Insightfully identified users and a perceptive and empathetic persona with insightful application to the case study.
85.00 to 100.00 %
Skillful and proficient - Insightful storyboard from the case study with skillfully directed story and identifiable as either UX or HCI.
75.00 to 84.00 %
Accurate - Nicely set out report format with title page, headings, page numbering, introduction, report body, conclusion, recommendations and well referenced. Good clear and logical communication to executive audience
75.00 to 84.0046
Thorough and clear- Thorough 3 level DFD and clear analysis applied to the case study.
75.00 to 84.00 %
Proficient - Good representative users identified and a well-constructed persona with clear application to the case study.
75.00 to 84.00 VD
Proficient and effective - Clearly themed storyboard from the case study with clear logic and flow and identifiable as either UX or HCI.
65.00 to 74.00 %
Satisfactory - Satisfactory report format with title page, headings, page numbering, introduction, report body, conclusion, recommendations and adequately referenced. Good communication to executive audience
65.00 to 74.0046
Effective - Effective 3 level DM and analysis applied to the case study.
65.00 to 74.00 %
Deeper understanding- Relevant users identified and a soundly identifiable persona with application to the case study
65.00 to 74.00 %
Clear and coherent - Clear case study related storyboard with good logic and flow and identifiable as either UX or HCI.
50.00 to 64.00 %
Adequate - Basic report format and adequately referenced. Adequately appropriate communication to executive audience
50.00 to 64.0046
Sound - Basic 3 level DFD and basic application to the case study.
50.00 to 64.004+0
Essential - Relevant users identified and a basic but identifiable persona with basic application to the case study
50.00 to 64.00 %
Coherent- Basic storyboard from the case study with basic logic and flow and identifiable as either UX or HCI
0.00 to 49.00 %
Inaccurate - Poorly formatted and unclear report. poor referencing
0.00 to 49.00 35
Simplistic - No or very little organization and relationship to the case study.
0.00 to 49.00 %
Superficial - Little or no relationship between persona and case study
0.00 to 49.00 %
Imprecise and vague - No or little logic, flow or relationship with the case study.