1.4 drafting: minimum method
[Comparison of programmers and writers]. The same point of use of text is expressed, and the expression of the expression can determine the success of the product. Different writers are generally independent behavior, involving time limit requires very economical use time, abandonment Methods to bring important results 1.4.1 premise
[Two important premise or some historical lessons and new demands]
Different from process language, C has many protection, programmers can build their own protection to create procedures to destroy its structure, whether during creation or during maintenance. Division: Regardless of the analysis, facing constantly Developing affairs, even if there is a matter of development in the post-development, it may not be discovered. It is important to test the test system to achieve the target system.
【display method】
The language is the best way to express things. Mistortion because it is too clear and limited. Good description tool should establish code and documentation. It is very important to use familiar tools and thinking.
1.4.2 High Concept
Description and necessity】
Established system, no matter how complicated, there is a basic purpose, which industry is serving which industry and what basic needs should be met. High concept is maintained, it is very important. The description of the high concept does not require very accurate
1.4.3 Discussion (TREATMENT)
The discussion of the story, the outline of the story, that is, the high concept. The best way to develop high concepts and discussions in computer systems is to form a group, which has a write-capable aid. In the collective discussion It is possible to establish, assist tools are responsible for expressing their respective ideas, not given evaluation, just trying to maintain these ideas clear and smooth * Discussion becoming the first prototype of the starting point and design of the shot, and can also have auxiliary Tools completed
1.4.4 Structured
For the system, the structure is the key.
[Organization System]. The first layer: "High Concept", "Discussion", "Object", "Design" starting point. Layer 2: Objects found to the first floor. Layer 3: Added object interface
Use descriptive language, do not use pictures, the meeting discussion process is not subject to the speed limit of this description
[Feature: Discover Initialization]
Discussion: Name verb noun ==> Class verbs ==> Class method or system design process √ This is a procedure that constantly repeat, does not expect the program to fully understand the problem
If a class is inherited from another class, the second layer of subsections should be placed in its base class as close as possible, and its subsequent name should show this inheritance relationship. Occam's razor method: Choose a most Simple class constructs because it is very easy to add an element to a class, but if you lose your element, you will be difficult [plot: Initialization System Design]
Episode: System Activity. According to the possible system activities proposed by the team, it is not required to establish and systematically link them. Participants can be very wide, designers, market staff, and management personnel can attend. The purpose is to "Communication" - For the consensus of the entire system, you can improve your enthusiasm. You can summarize the basic conditions transition description for each sub-plot, and these will become the initial code implementation goals.
1.4.5 development
From the initial conversion of the coarse design to compile code, compile code can be proved or reverse design. This is a procedure for repeated. By re-generating documents for the structure in the code or related text. Design document becomes a report tool for project progress.
[Initial translation]
Document First, Object Description - Generates a file header according to the object, that is, the system program header file, each object is through some types of implementation. - Split the document into several parts, working on every part Layer 2, Type Abstraction - Automatically generates class declaration - the corresponding secondary description is a member function and variable declaration
The fourth layer of the document, the plot - Each sub-plot produces an independent full-end function, the supply port function main () is used, or the main paragraph.
[Code generation]
. Generate a separate class declaration header file for each class of the object section. Generate system processes for each child plot. Use summary headings to mark each sub-plot, classes, and methods, such as: file: // # [1] .... Interface and plot should be compiled but unconnected, because there is no code implementation, just for syntax check. Additional supplementary documentation, if class or sub-plot finds changes
1.4.6 rewriting
【purpose】
Perfect procedures, update documents
【opportunity】
Because software development is an appointment service, it is inevitable that the release is required to release
1.4.7 logic
【responsibility】
Reasonability and maintenance design documentation is the responsibility of project leaders or managers. The project group or individual is responsible for a small part of the document (code and notes)
〖Personal understanding〗
This section can mainly put forward two views, language roles and script methods. In fact, since I started to engage in programming, I have a tendency to use graphic or picture language, it seems that I am wrong, I originally Because of the unclearness of language, I hope to use more intuitive and formal language description system. Obviously I ignore a little understanding of people's understanding of people and the limitations of things cognition, the charm of language is actually reading Different, constantly cognitive and modification is the correct process of collective cognitive systems, simple illustrations, often easily give reading readers' first-in-one main and dependencies.
The system design is to write scripts. I have previously designed too stylized, in fact, this is a common problem of process design, always hopes to close the door after complete understanding of the system requirements, clearly commit non-identified problems.
