Reference no: EM13304187
Question:
You are required to analyse the effectiveness of the Qantas Online Air Ticketing system. To do this you are required to employ at least two data gathering techniques, one of which must be observation. You will need to research the existing online ticketing system and other information you can find about the airline. You also need to observe how at least three (3) users interact with the system. Suppose the 3 users want to travel to different cities. You need to script two or more scenarios for these users, and then observe their interaction. For instance, two possible scenarios might be as follows:
(A) You want to travel to the Whitsundays next Friday. Before reserving your seat, you want to be sure that you can finish packing without rushing it, and reach the airport on time. You therefore want to find out when your flight is departing on that day.
(B) You want to check-in online, so that you don't have to queue at the airport, but can go straight to the boarding gates. Without going through to finalising the payment, see if your participants can check-in.
Amongst the information sought are answers to the following questions.
Questions you need to address are:
1. What are the major business objectives and processes (operations) that the airline company carries out?
2. List the information systems and subsystems that are used to support their portal and describe how they are related to the overall business objectives and processes.
3. Detail the scenarios you developed and how the users you observed interacted with the system, when carrying out the tasks of those scenarios.
4. Recommend improvements to the system and describe the analytic consequences. For instance, not all airlines provide systems for online check-in. If the company were to add such functionality, what do the analysts need to consider?
5. Describe the stakeholders involved. Who are they? Why do analysts need to consider their interests?
6. Discuss, in detail, the data collection techniques you used to answer the above questions.
7. Develop a high level DFD and domain model class diagram for the online booking system.
Rationale
This assessment task covers topics 1 to 8 and has been designed to ensure that you are engaging with the subject content on a regular basis. More specifically it seeks to assess your ability to:
develop and test your skill to research the role of information systems in solving business problems
describe the purpose of systems analysis and design in the development of information systems and identify the list of stakeholders
identify some data gathering techniques you will also learn about the role of the system analyst in the development of information systems.
CRITERIA STANDARDS
The major business objectives and processes
The overall goals of the business are clearly expressed to show all the major business objectives and processes. The overall goals of the business are clearly expressed to show most of the major business objectives and processes. The overall goals of the business are clearly expressed to show some of the major business objectives and processes. The overall goals of the business are clearly expressed to show few of the major business objectives and processes. The overall goals of the business are not clearly expressed and show none of the major business objectives and processes.
A listing of the information systems
At least 7 information systems are explicitly described and there is a clear discussion and analysis of the relationships to the processes they automate. At least 6 information systems are described with relationships to the processes they automate clearly discussed. 4 to 5 information systems are described and relationships to the processes they automate are clearly discussed. 2 to 3 information systems are described with relationships to the processes they automate Less than 2 information systems are described with few or no relationships identified.
Justification for the scenario choices and results
3 scenarios presented including a well-defined justification for each user's choice; and in-depth discussion and analysis of the user''s attempts to carry out the tasks is clearly presented. At least 3 scenarios presented, with some justification for the user's choice, and clear description of the user''s attempts to carry out the tasks included. At least 3 scenarios presented, with some justification for the user's choice, and a description of the user''s attempts to carry out the tasks included. At least 3 scenarios presented, with little justification for the user's choice, and some description of the user''s attempts to carry out the tasks included. Less than 3 scenarios presented, poor or no justification for the choices made by the user, and description of the users'' attempted to carry out the task provide little information.
Improvement recommendations
The recommended improvements logically follow from the data gathered. Analytical considerations are in-depth, organized evidence that reveal insightful patterns, differences or similarities of systems. The recommended improvements logically follow from the data gathered. Analytical considerations are organised evidence that reveal important patterns, differences or similarities of systems. The recommended improvements logically follow from the data gathered. Analytical considerations are organised evidence that provide insight into possible patterns within systems. The recommended improvements follow from the data gathered. Analytical considerations states a general conclusion that provides a broad application of the recommendation that may or may not be useful. The recommended improvements do not follow from the data gathered. There is no clear analytical considerations discussed or presented.
Stakeholder identification
More than five stakeholders from each major category (client, user, technical support) is identified and their interests are explicitly defined and discussed in relation to the scenario. Five stakeholders from each major category (client, user, technical support) is identified and their interests are clearly explained in relation to the scenario. At least four stakeholders from each major category (client, user, technical support) is identified and their interests are listed in relation to the scenario. At least three stakeholders from each major category (client, user, technical support) is identified but their interests are not identified in relation to the scenario. No stakeholder from each major category (client, user, technical support) is identified and their interests are not explained in relation to the scenario.
Detailed description of the data gathering techniques used
More than two data gathering techniques used are discussed in detail and information obtained is analysed, synthesized with concepts of systems analysis and clearly presented in a report. At least two data gathering techniques used are discussed and information obtained is analysed and reported with some reference to systems analysis concepts. Less than two data gathering techniques used are clearly discussed and information obtained is analysed and reported. Less than two data gathering techniques used are discussed in detail and information obtained is not analysed and reported No data gathering techniques used are discussed in detail and information obtained is ineffectively explored.
Develop a high level DFD and domain model class diagram for the online booking system.
All elements of the diagram are skillfully developed. Appropriate methodology synthesized from across the concepts covered in this subject, as well as reference to external research is evident. Critical elements of the diagram are appropriately developed, with evidence that some concepts covered in this subject have been applied to the diagram development. Critical elements of the methodology are developed and included in the diagram. Diagram presents information from relevant concepts representing limited points of views or approaches. Diagram presents incorrect information and from irrelevant sources.