Software engineering Sixth Chapter Knowledge Point Summary _ software project

Sixth chapter Detailed design

1. Detailed design, the fundamental goal of detailed design is to determine how the specific implementation of the required system. Detailed design phase of the task is not how to specifically write the program, but to design the "blueprint" of the program, the programmer in accordance with the "blueprint" to write the actual code, so the detailed design results basically determine the final program code quality.

2. Structure detailed design, sequential structure selection structure cycle structure

3. Man-machine Interface Design

(1) Design problems: System response time, user assistance facilities, error information processing, command interaction

(2) design process, iterative process, that is, usually first create the design model, and then use the prototype to implement the design model, and the user trial and evaluation, and then according to the user's comments modified.

4. Human Interface Design Guide

(1) General interaction Guide: Maintain consistency, require user confirmation before performing a larger destructive action, allow most operations to be canceled, reduce the amount of information that must be memorized between two operations, and minimize the number of user keystrokes

(2) Information Display Guide: Only display information related to the current work content; instead of drowning users with data, you should represent data in a way that makes it easy for users to absorb information quickly, use consistent tags, standard abbreviations, and predictable colors, allow users to maintain a visual context, produce meaningful error messages, and use case, Indents and text groupings to help understand, use Windows to separate different types of information, display information in a way that is "simulated", and use the display efficiently

(3) Data Entry guide: Minimize user input, maintain consistency between information display and data, allow user to customize input, interact should be flexible, and can be adjusted to the user's favorite input method, so that commands that do not apply in the context of the current action do not work; Let the user control the interaction flow ; Help with all input actions; eliminate redundant input.

5. Process Design Tools

(1) Program flow chart

(2) Box diagram

(3) Pad map

(4) Decision table

(5) Decision tree

(6) Process design language (PDL), also known as Pseudocode, is a "mixed" language that uses the vocabulary of one language (usually a natural language) while using the syntax of another language (a structured programming language). The fixed syntax of the keyword, which provides the characteristics of structured control structure, data description and modularity.