Use the notes within this page to help structure the Design section of your programming project. There are no set determined number of pages for this section.

3.2 Design the solution

Structure and Description of content needed for Programming Project
Design

3.2.1 The Problem – Describe the problem in small parts. Identify where the problem must be broken into individual solvable parts. Discuss how each solvable part of the problem will be achieved using different computational elements (see list on Analysis section).

3.2.2 The Solution – What is your intended solution? How many parts are there to this solution? GUI, STORAGE, PROCESSING, DATA. Why have you designed each part listed above? Why not do it a different way?

Show how your solution will function using flowcharts and pseudocode. Each diagram should have annotation to support what content the diagram shows. After identifying all the individual parts of your design you should create an overall STRUCTURE diagram showing how all the algorithms LINK together to form your solution. Provide a justification as to why and how it works. 

Describe all the key usable features of your solution? Explain why these were needed in order to meet the requirements set out in the analysis section. 

Create a table to identify All variables, data structures and classes. Explain why they are needed in the different parts of your solution.

3.2.3 Testing the solution – Explain and design your testing strategy.

Explain the use of ITERATIVE TESTING in your DEVELOPMENT PHASE and explain the use of FINAL TESTING at the end of DEVELOPMENT. Explain how these will differ from each other and the reason for this? Explain how testing will link to your success criteria. What TYPES of data will you use?

Identify what specific methods of testing will be used in your project? BLACK BOX, WHITE BOX what is the difference between the two?