The method of construction read Note 04
Today, read the "Construction of the law" of the 第九、十、十 chapter, the Nineth chapter mainly on the project manager, after reading, I initially understand the project manager's work content and should have the basic ability, software team project manager is divided into many kinds, but always called PM,PM is the development of software with the emergence of a profession, Because of the increasing number of software team members, communication between them becomes a major problem in the software development process. And the project manager is to solve the same project to develop different functions of the team communication intermediary, the same project manager also shoulder the need to accurately express the user's needs in detail to the development team, this task is particularly important, even to determine the success of the project is an important factor. Therefore, an important requirement for the ability of project managers is to have the ability to understand the situation, psychology, and motivation of others, even if he does not develop projects. The project manager also has an important responsibility-project risk management. That is, outside of the normal software life cycle events, events that can affect the success of the project, such as the resignation of a team, changes to national regulations, and the release of new software versions, have been introduced in the book on how to avoid risk. A good project manager, even without writing any code, wins the respect of everyone in the team and positively affects the project and the product.
The tenth chapter mainly introduces typical users and typical scenes. Typical users should be the analysis of each user's information, in order to recommend the user he may need software products, or according to some of his needs to develop the corresponding software products, for the typical scenario I am not very understanding of the introduction of the book, but also do not express any feelings. The tenth chapter also introduces the function specification, which is to describe the function, input, output, interface, function boundary problem, function efficiency (to the user), internationalization, localization and abnormal situation from the user's angle, which does not involve the implementation details of the software. Let me also understand part of the software documentation.
The 11th chapter-Analysis and Design methods, the book with a classic math problem vividly explained the software development process in the analysis and design concepts and processes. In the "Demand analysis" phase, we need to figure out what entities are in the real world in the problem domain, how to abstract the attributes that we really care about, what the relationship between entities is, and on this basis, what the user needs and how the software solves the user's needs. In the design and implementation phase, we need to figure out how the software solves these requirements. In the "Testing" and "release" phases, do we have to figure out if the software really solves these requirements? All relevant personnel of the software team need to process and understand this information, if the process of misunderstanding and loss, it will lead to problems in the development process, and ultimately the product can not meet the needs of users. This shows how important the analysis in the software development process is, and the 11th chapter introduces the concrete steps from spec to implementation and the daily management of the development and the timing of the bug fixing. All of this has taught me a lot.
The law of Construction read Note 04