The book of People's Month myth

The book of People's Month myth

Not reading this book How can not be linked to the name of the software engineering, the total feeling of human moon myth more like a fairy tale or also associated with some of the space things, and finally began to study the book in the holiday, but also slowly by the content of the book to be impressed. During the reading of the book through the "Software engineering-theory, methods and practice" only to know that the month is the development of the unit in the system. Did not read before I heard it is software developers must read, is the myth of the software industry, after reading let me feel deeply, although I have not really engaged in the software development industry, as a student I may not understand the main ideas in the book is very comprehensive, The book is mainly described in the Software Development project on the project schedule and increase personnel can not be interchangeable, the book of a number of points of view has given me a lot of help.

People's Month Myth This book explores the difficulties and solutions of achieving consensus in many problems of software crisis, and explores other aspects of software engineering management, and puts forward many practical viewpoints, this book has a lot of thought-provoking views, and a lot of software engineering practice, For the managers of each complex project to give their own insights.

The beginning of the book on the image of the software crisis compared to tar pits, the image of the software development process to express many difficulties, but also write out how difficult these difficulties to solve. As the book is carried out each chapter has elaborated the very practical viewpoint, the human month myth this part tells the human and the time does not reflect the linear relation. It is pointed out that the development of software can not be shortened with a large number of people and short time. Swarm's operation is not conducive to software production, and will create trouble, resulting in worse software. The addition of manpower to lagging projects will only make progress more backward. Because the new people need time to understand the whole project, and increase the additional communication consumption. The book contains the following: the surgical team. With the same training and two years of seniority, a good professional programmer is 10 times times more productive than a bad programmer. The dapper team is the best-use the fewest people possible. A two-person team, one of whom is a leader, is usually the best way to employ people. It's too slow to develop a really big system with a short team. The vast majority of large software systems experience shows that using a bunch of people to act recklessly is the most cost-effective, the slowest, the least efficient, and the system that makes it is conceptually the most incomplete. The second systematic effect of the myth of Man and month the second system is the most dangerous system in terms of what one has done, and in general, tends to be over-engineered.  

In the book, we can see project estimation, organizational structure and personnel role arrangement, team building and communication, historical data accumulation and modeling, software development methodology, risk and problem management, etc., and in software engineering, we can see that the architecture design guarantees the conceptual integrity, the whole and the part, The relationship between space skills and program structure, the method of product integration and the design idea of eliminating defects; In the process of support we can see the construction of documents and processes, software development tools for software development process support and efficiency improvement and tool selection and other related content, back to see, Found in the book still most of the content involved in the team, people and communication. For large-scale software engineering projects still emphasize the importance of people, at the beginning of the development of the professional fun, followed by the importance of communication through Babel, in the surgical team to talk about team formation and division of labor. These involve people and interactions in the team, and only a communication team with a positive mindset and passion can make a great team. From the last no silver bullet, again affirmed that the development work is a high intellectual mental work.

Develop a software, we must have the reasonable time progress, the developer must be few but good, the concept integrity has to take into account, should try to be able to communicate as soon as possible and continuous communication. At the same time, documents form a key hub, and each project management work revolves around them, which are the main personal tools of managers. For computer hardware development projects, key documents are targets, manuals, schedules, budgets, organizational charts, spatial allocations, and pricing, forecasts, and prices for the machine itself; for us university students, key documents are similar: Objectives, course descriptions, degree requirements, research reports, schedule and course arrangements, budget, classroom assignments, Assignment of teachers and graduate assistants; For software projects, the requirements are the same: goals, user manuals, internal documentation, progress, budgeting, organizational chart, and workspace assignments. Even for a small project, we will require writing related documents, providing status monitoring and early warning mechanisms for the maintenance of each critical document, and can be used as a checklist or database. A good work manual and organizational structure can be developed to better meet the needs of users. manuals, or written specifications, are a very necessary tool, although the documentation is not enough. The manual is the external specification of the product, which describes and prescribes every detail that the user sees, and, similarly, the main work product of the architect.

There are so many things in the book that are very inspiring to us, whether they are already working or are going to school, the ideas in the book are very helpful to those of us who are dealing with software development, and it gives us a lot less detours in the software development process, which inspires us to be more efficient in software development.

The book of People's Month myth