Design

• Top-down design: This is where the top-level program (the main steps) are then refined into sub-programs/ modules (functions/ procedures).
• Structure Diagram: A structure diagram is a development tool used in modeling the different parts of a system, from the overview on how the individual parts interact to create the whole, to modeling the details of the smallest parts themselves such as the different objects and classes being used in programming the system.
• Pseudocode: Pseudocode is an artificial and informal language that helps programmers develop algorithms. Pseudocode is a "text-based" detail (algorithmic) design tool. All statements showing

  "dependency" are to be indented (e.g. code in a loop or selection).
• Data-flow: In design, showing data-flow means showing what data is moving from one module to another. These are normally described as “in”, “out” or “in-out”. On a structure diagram, data flow is shown using arrows. In pseudocode, data-flow is normally shown down the right hand side of the top-level design.
• User Interface: The parts of the program that the user will see and interact with.
• Design is the process of working out how the program will work (how all the modules will fit together), how the program will look to the user and how the program will be tested.
• Pseudocode is an English-like description of how the program will work, broken into stages that identify what happens, in what order.
• Pseudocode numbers each line, with refinements of top-level program identified as, for example, 2.1.
• Pseudocode should provide enough detail to the programmer to be able to implement the program.
• In an Iterative/Waterfall approach, the pseudocode should be more or less complete for the entire program prior to commencing implementation.