GCSE ICT Theory - PROBLEM SOLVING USING ICT (FULL COURSE MODULE)

Note: This content is covered by the Full-course Project 2 task.

5.4 PROBLEM SOLVING USING ICT

Content:

• Analysis
• Design
• Development, Testing and Implementation
• Documentation
• Evaluation

5.4.1 Analysis

1. Researching a situation using observation, interviews and/or questionnaires and/or data capture forms
2. Recording information
3. Identifying problems
4. Establishing the information, input, output and processing required
5. Identify suitable hardware and software for developing a new system

Learning Outcomes

Candidates should be able to:

1. identify methods by which to investigate the problem including questionnaires, data capture forms, observation and structured interviews;
2. record information/data;
3. analyse the data and tasks carried out, identifying problems with the current methods and procedures;
4. work out the user and information requirements necessary to resolve the identified problems;
5. specify the required hardware and software;
6. document the system requirements for later reference during evaluation.

5.4.2 Design

1. Designs for documents and files
2. Design forms/inputs
3. Design outputs
4. Validation
5. Use of diagrams to describe system processing

Learning Outcomes

Candidates should be able to:

1. design and document data capture forms and screen layouts;
2. design and document report layouts, screen displays and other forms of output (e.g. audio output);
3. specify any verification and validation required and interactive feedback required if any data is input in error;
4. design the required data/file structures necessary to solve the inefficiencies/problems indicated in the requirements specification;
5. design the new methods/procedures/processing

5.4.3 Development, Testing and Implementation

1. Create the required data/file structures
2. Create inputs/outputs and set up any validation specified in the design
3. Designing test data to test normal, abnormal and extreme circumstances
4. Test the system
5. Specify implementation method: direct changeover, phased implementation or parallel running

Learning Outcomes

Candidates should be able to:

1. develop the data structures of the design using the appropriate features of a software package;
2. develop the input/outputs and validation checks for their user using the appropriate features of the chosen software;
3. identify, develop and document a test strategy for the design, ensuring that normal, abnormal and extreme circumstances are tested;
4. test the new system, illustrating how improvements are carried out as a result of testing;
5. produce detailed and annotated output from the testing to show how the system works;
6. devise a strategy for system implementation.

5.4.4 Documentation

1. The purpose and limitations of the system
2. The hardware and software requirements of the system
3. How to use the system
4. Input and output formats
5. Sample runs
6. Error messages

Learning Outcomes

Candidates should be able to:

1. describe the purpose of the system and its limitations to the user;
2. describe the hardware and software required to run the system;
3. describe how to use the system, illustrating the system in use by providing annotated output;
4. describe the inputs, validation and any outputs from the system;
5. produce a section on troubleshooting errors for the user;
6. produce documented evidence that the system works as part of the project report.

5.4.5 Evaluation

1. Comparing the solution with the original design
2. Conclusions drawn from the testing and any modifications and improvements made

Learning Outcomes

Candidates should be able to:

1. evaluate the final system against the criteria described in the requirements specification;
2. evaluate the users’ responses to testing the system or end results of testing;
3. identify the good and bad points of the final system highlighting any limitations and necessary extensions to the system, indicating how the extensions could be carried out.