The fifth chapter draws snake
1. Targets in this chapter: Structural designers should avoid adding a lot of unrepatched features to the system (avoid painting snakes).
2. Early exchange and continuous communication can make the structural staff have a good cost awareness, and make developers to design confidence, and will not confuse their division of responsibility.
3. Facing a problem that is too high, the structural staff has two options: cutting the design or recommended costs - the result of the estimation of the estimate. The latter is an inherent subjective sensor reaction. At this time, the structural staff challenged the developer's work. I want to succeed, the structural staff must
Keep in mind that developers bear the achievement of creativity and inventive achievement, so structs can only recommend them, but cannot dominate;
Time is prepared for the specified description, it is recommended to implement any other way to meet any objective method;
Keep low-key and calm for the above recommendations;
Prepare to abandon the improvement suggestions made.
4. A criterion that can open the horizon of the interface is to assign a value for each small function: each improvement, the function x does not exceed the M-byte memory and N microseconds. These values will be a warning of the physical implementation during the start of the decision and a warning to everyone during the decision.
5. The project manager must adhere to the decision of the structural staff with two systems and above. At the same time, maintain a warning to special temptation, he can constantly propose the correct question to ensure that the concept and goals of principled are complete in detailed design.
Chapter 6 implementation
1. Problem: How does the project manager ensure that everyone is listening, understanding and implementing structural decisions? How to keep the system conceptual integrity for multiple structs.
2. Manual, or written specification, is a very necessary tool. The manual is an external specification of the product, which describes and specifies every detail you have seen by the user; the same, it is also the main working product of the structural staff.
The manual must not only describe everything that is visible, including all interfaces, but it also describes what users can't see. The latter is a scope of programming to achieve personnel, and the design and creation of personnel should not be restricted. The architecture designer must prepare a method for any characteristics described by himself, but he should not try to give a specific implementation process.
Specifications must be clear, complete and accurate. Users often refer to some definition, so each description must repeat all basic elements, so all texts are consistent.
3. In the specification, formal definition is accurate, and they tend to be more complete; differences are more obvious, can be completed faster. But the shortcomings of formal definitions are not easy to understand. The narrative text can display structural principles, describe the structures on the stage or on the hierarchy, and provide examples. Two ways should be included in the formation and narrative definitions.
4. Through the way of meeting, developers communicate and discuss issues.
5. Strict requirements between different implementations are compatible with each other. If there are at least two implementations, then the definition will be harder and specific.
6. For those who have questions, they should encourage them to call asked the corresponding structural staff instead of guessing while guessing.
A useful mechanism is to save the phone log by the structuralist. In the log, he recorded every question and the corresponding answer. We will merge, reinitely, and publish it to users and implementation people every week. This mechanism is very unfair, but very fast and easy to understand.
7. In the final analysis, the user is an independent supervisor. In a cruel real-world use environment, each subtle defect will not be informable. The product test team is a customer's agent, specializing in defects. From time to time, the careful product tester will always find some parts that do not implement, design decisions do not have correctly understood or accurately. For this reason, the establishment of the test team is the necessary means to implement design decisions, and it is also necessary to start as soon as possible, and design simultaneously.
