Recent Question/Assignment

ICT115
Introduction to Systems Design
Task 2
ATMC
Semester 2, 2019
Assessment and Submission Details
Marks: 35% of the Total Assessment for the Course
Due Date: 11:59pm Monday, Week 12
Submit your assignment to Blackboard Task 2. Please follow the submission instructions in Blackboard.
The task is an individual assignment and will be marked out of a total of 100 marks and forms 35% of the total assessment for the course. ALL assignments will be checked for plagiarism by SafeAssign system provided by Blackboard automatically.
Refer to your Course Outline or the Course Web Site 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 and requests made on the day of submission or after the submission date will only be considered in exceptional circumstances.


Case Study: Ryanair
Founded in Ireland in 1985, Ryanair took advantage of deregulation to commence Europe’s first low cost airline. Operating in a very competitive industry with rivals such as the Irish national carrier Aer Lingus and British Airways, Ryanair pursued a low-cost but profitable strategy of offering heavily discounted services to regional UK and European destinations. Ryanair is no stranger to technology having built a cutting-edge website in 1999. In the last four years has reinvented its technology strategy with the launch of its technology arm Ryanair Labs.
Ryanair Labs ambition is to become a ‘technology company with an airline attached’ primarily focused on increasing passenger numbers from 130m / year to 220m by 2024. This ‘Customer first’ strategy includes plans to create wearable technology apps to improve and simplify passenger experience. ‘RyanAssist’ is one such app Ryanair is aiming to develop to help passengers navigate to the right airport, though the check-in process, and then to the correct gate, or between gates for transfers. The app would also guide passengers as to flight timings such as check-in and boarding times as well as being a direct communication with them re flight delays and other useful information before and during the passenger’s journey.
End of Case Study
Assignment Task
Ryanair has asked you provide the following Analysis and Design requirements. However, you are free to design and include any process and design components into RyanAssist’ you feel important to Ryanair. Keep in mind there are many possible answers - 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 Major Outcomes
1 Introduction
2 Data Flow
Diagram (DFD) Create a 3 level DFD (pages 143-160 Tilley & Rosenblatt 2017) of the new RyanAssist app. Ryanair require:
• a Context diagram,
• Level 0 Diagram including the three areas of RyanAssist
functionality, and
• three Lower Level Diagrams one each for:
o navigation to and around airports processes, o flight schedule assistance processes, and o flight communication processes
Ryanair would like to understand the principle behind DFDs including advantages and disadvantages, and how you have applied the DFD to modelling RyanAssist.
3 User Persona • Ryanair would like you to identify at least 2 different user types who will use RyanAssist.
• Choose one of these users and create a one-page (two-page at most) persona based on the five steps in Week 7 Tutorial material.
• Along with the persona Ryanair have asked for an explanation of your reasonings behind each persona creation step for your particular 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 the reasoning behind the summary quote?
o Step 3 - …..
4 User Storyboard Imagine a RyanAssist 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 persona as the lead actor using the app, or
• Human Computer Interface Storyboard (HCI) – a storyboard modelling the device displaying the sequence of interaction with the app.
Ryanair 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 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 recognized 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 submission 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 in two weeks after the submission. An electronic assignment marking sheet will be available at this time.
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 1
ICT115 Task 2 – Analysis and Design Report
Criteria Distinction (75-84%) Credit
(65-74%) Pass
(50-64%) Fail
High Distinction
(85-100%)
(10%) Format
report to clearly communicate case study design requirements 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 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 Satisfactory Satisfactory report format with title page, headings, page numbering, introduction, report body, conclusion, recommendations and adequately referenced. Good communication to
executive audience
Adequate
Basic report format and adequately referenced. Adequately appropriate communication to executive audience Inaccurate Poorly formatted and unclear report. poor referencing
(30%) Create 3 levels of DFD. Explain DFD principles and their application
to the case study
Systematic and skillful Skillful 3 level DFD and insightful analysis applied to the case study. Thorough and clear Thorough 3 level DFD and clear analysis applied to the case study. Effective
Effective 3 level DFD and analysis applied to the case study. Sound
Basic 3 level DFD and basic application to the case study. Simplistic No or very little organization and relationship to the case study.
ATMC ICT115 Introduction to Systems Design Assignment 2
Criteria High Distinction (85-100%) Distinction
(75-84%) Credit
(65-74%) Pass
(50-64%) Fail
(30%) Identify case study users and Create one case study related persona and explain reasonings behind persona
creation steps
Perceptive and polished Insightfully identified users and a perceptive and empathetic persona with insightful application to the case study. Proficient
Good representative users identified and a well-constructed persona with clear application to the case study. Deeper understanding Relevant users identified and a soundly identifiable persona with application to the case study Essential Relevant users identified and a basic but identifiable persona with basic application to the case study Superficial Little or no relationship between persona and case study
(30%) Create Case study related Storyboard (UX or
HCI)
Skillful and proficient Insightful storyboard from the case study with skillfully directed story and identifiable as either UX or HCI.
Proficient and effective
Clearly themed storyboard from the case study with clear logic and flow and identifiable as either UX or HCI.
Clear and coherent Clear case study related storyboard with good logic and flow and identifiable as either UX or HCI. Coherent Basic storyboard from the case study with basic logic and flow and identifiable as either UX or HCI Imprecise and vague
No or little logic,
flow or relationship with the case study.
Page 8 of 8