People's Month myth reading notes three

Human Moon Myth The third chapter is about member configuration in team development. In general, a small, lean team of top-notch talent is more efficient than a large team of hundreds of people. But the small and capable team has some limitations and is too slow for the real big system. So this involves a problem- how to create large systems within a meaningful schedule? Small systems are better suited to efficiency and concept integrity requirements, and a large number of manpower is available for large systems.

Here's a model for surgery. This method is proposed by Harlan Mills , the main content is that each part is resolved by a team, the surgical mode of formation, all people are not swarmed. The small project of our introduction to software engineering is that everyone is responsible for a part, and finally a combination.

There are several important roles in a complete surgical model. Lead programmer - with a high talent, ten years of experience and applied mathematics, business data processing or other aspects of extensive system knowledge and application knowledge. second -hand- requires a detailed understanding of all the code and an alternative to the design strategy. Administrator - a professional manager who controls finances, people, workplaces, and office equipment, and serves as an excuse to summarize other regulatory bodies with the organization. Edit - analyze and reorganize, provide a variety of reference information and trees, maintain multiple versions, and oversee the documentation generation mechanism. Secretarial - responsible for the collaborative and non-product work of the project. Program Staff - Receive secretarial training, responsible for the management of machine code files and readable documents. Tool maintenance personnel, testers, and language experts.

To the user, the system is used by one or two people, so the surgical participants are conceptually highly consistent, just as all the doctors and nurses in an operation are working on the same operation. But a surgical model of the team, most people are solving the core problems, the remaining few people are dealing with other things. But the specialization of the remaining members is the key to efficiency, which can make communication between members easier.

These can be achieved under the request of a small project. But extended to large systems. This requires the conceptual integrity of each component to be improved.

Learning the first three chapters of the myth of the human month, I learned that the joys and miseries of software engineering coexist, and that there are many problems, and that we have a comprehensive approach to solving problems, which is the case in both small and large projects.

In a word, the "People's Month myth" this book in the future after we enter the team development will have the important significance, therefore we must in the team development early learning this kind of development pattern, for the future to make a good foundation.

People's Month myth reading notes three