Myth of man and month-tailored to suit and outline

Best Practice-Focus on the space scale and space control skills of the program

What is the topic in this chapter? We often consider the running time and efficiency of programs when developing programs, but seldom consider the running space of programs. Currently, the storage space is getting cheaper and we seldom consider these issues. In the classic DOS version, the legend of xianjian Qixia is less than 20 m, but now a big game is 2, 3G or even bigger. Due to the continuous upgrading of computers and the improvement of performance, we do not place special emphasis on the space issue, but we will still emphasize the space issue for the underlying programs of some operating systems.

At the beginning, I first talked about the scale control of software products. This scale refers to space storage. The scale of software products should be budgeted from top to bottom, it is decomposed into subsystems and modules. This is a general idea starting from the system as a whole. After such decomposition, every developer must consider how to achieve the expected scale goal and try to design the program as much as possible, algorithms and other aspects to optimize the program scale.

The skills of scale control are clearly explained. There are two common methods. One is to exchange space by providing the number of functional points, and the other is to exchange space by sacrificing performance and time. But how can we make a good compromise between space and time? On the one hand, it is necessary to strengthen training to improve developers' programming skills (the core may be data structures and algorithms). On the other hand, it is necessary to carry out long-term technical accumulation, it advocates reuse and development of more public components.

The manifestation of data is the foundation of strategy. In many cases, the improvement of skills and the reexpression of strategic images come from tables and data. Due to lack of space, programmers can often break away from their own code, review and analyze the actual situation, think carefully about program data, and finally get very good results. In fact, the representation of data is the foundation of programming.

Outline-roles and management of documents

In the vast ocean of documents, a few documents form a key hub, and each project's management work revolves around them. They are the main personal tools of managers. (Documentation is an important auxiliary means of communication. It is effective instead of being effective)

Here we have read and described three types of documents. We only analyze the product-level documents and project documents. Documents at the computer product level are the basis for subsequent project version plans and the product-level plans at the previous level of the project plan. It must include:

• Product Positioning and objectives
• Detailed product features and technical specifications (the initial source may be sow, which can be further refined into product requirements)
• Product Cycle and budget
• Product feasibility analysis (constraints and balances on the three elements of prediction, price, and quotation)
• Organization chart

For software project-level documents, the most important thing is to start the project plan. I have described the original blog in detail. The core content in this book includes:

• Project objectives and scope (detailed Requirement Description)
• Schedule (milestones and detailed schedules)
• Budget (capital budget, human resource demand and budget)
• Workspace allocation
• Organization chart

Why is there a small number of necessary documents? On the one hand, written documents can reduce differences, and on the other hand, asynchronous communication is a good way. The task of the project manager is to develop a plan and implement it according to the plan. However, only the written plan is accurate and can be communicated. The plan includes the time, place, people, what to do, and funds. These few key documents encapsulate the work of some project managers. If we first realized their universality and importance, we could utilize the document as a tool in a friendly manner without making it an annoying task. By following the document, the Project Manager can set his/her own direction more clearly and quickly.