Designing+solutions+to+problems

=3.2.1 Designing solutions to problems=

Responsible ||
 * * Design of the input, output and interface
 * Use of structure diagrams to describe the modular nature of a solution
 * Use of program flowcharts and pseudo-code to describe the steps of an algorithm
 * Prototyping and Rapid Application Development (RAD) || Candidates should be able to: || Student
 * ^  || a. discuss the importance of good interface design; || Tolu ||
 * ^  || b. design and document data capture forms, screen layouts, report layouts or other forms of input and output (eg sound) for a given problem; || Kamil ||
 * ^  || c. determine the data requirements of a program (relating to 3.2.3: Data types and data structures); ||   ||
 * ^  || d. explain the advantages of designing a solution to a problem by splitting it up into smaller problems (top-down/modular design); || Sean ||
 * ^  || e. produce and describe top-down/modular designs using appropriate techniques including structure diagrams, showing stepwise refinement; ||   ||
 * ^  || f. produce algorithms to solve problems; ||   ||
 * ^  || g. describe the steps of an algorithm using a program flowchart; || George ||
 * ^  || h. describe the steps of an algorithm using pseudo-code; || Michael ||
 * ^  || i. understand, and implement algorithms and evaluate them by commenting on their efficiency, correctness and appropriateness for the problem to be solved; ||   ||
 * ^  || j. describe the use of Rapid Application Development (RAD) as a design strategy, including prototyping and iterative development, and state its advantages and disadvantages. || Ryan ||