Data Service Algorithm Design

Task Overview

• Students must design a solution, which involves creating a plan of action rather than physically implementing it.
• The activity must be completed during a specified time and date provided by Pearson.
• A 3-hour time limit is given to produce the required outcomes.
• The task must be completed under supervised conditions and no internet access is allowed.
• The data file "task3or_data.csv" is provided for use during the task.
• All work and materials must be kept secure at all times.

Task Brief

• A company must develop a data service to transform raw data into meaningful information for data-driven decisions.
• Developers need to design a solution based on requirements agreed upon with the client.

Activity Requirements

• Produce algorithm designs (pseudo code or flowcharts) to demonstrate how the system and user requirements will be implemented; 17 marks available.
• Algorithm designs should communicate the intended solution effectively.
• The designs should enable the client to make informed decisions.
• A third party should be able to use the design documents to create the proposed solution.
• The "task3or_data.CSV" file should be used to aid in the design of the solution.
• Completed design documents must be saved as PDF files using the specified naming convention.
• The solution must allow users to select a destination and compare flight prices from different airlines for a specified period.
• The solution should be easy to use.
• Information should be displayed in a meaningful way.
• The solution should use appropriate textual, numerical, and graphical output.

Assessment Focus

• There are three assessment sections: decomposition of the problem (8 marks), application of logical thinking and conventions (6 marks), and communication of the design (3 marks).
• Examiners will be looking for specific indicative content and marker guidance within each section.

Decomposition of the Problem

• Decomposition of the problem can be represented using a decomposition diagram instead of a flowchart.
• A decomposition diagram shows what needs to be done without traditional flowchart symbols.
• Basic decomposition includes only some of the work that needs to be done for the solution.
• Mostly detailed decomposition includes most of the criteria and requirements that need to be completed for the solution.
• Thorough and detailed decomposition should include inputs, processes, and outputs but does not necessarily have to be a flowchart.

Application of Logical Thinking and Conventions

• This section requires a flowchart or pseudo code, but not both.
• Pseudo code involves describing what needs to be done, and is an acceptable answering format.
• Break down your algorithm into smaller steps and differentiating them
• Pseudo code includes detailed direction such as where to get data, send data, display data, and save data.
• Precise logic: the pseudo code or flowchart should make sense and provide sensible output when traced.
• Efficient structure: avoid repetition by creating functions that can be referenced multiple times.
• Convention: use appropriate symbols or names (input, process, output, etc.) with descriptors.

Communication of the Design

• Effective communication uses technical language appropriate for the audience such as developers
• The symbols, words, and shapes used should clearly convey information.
• The description provided (flowchart or pseudo code) should enable a developer to follow the instructions