Read Note 05

Reading the Nineth to tenth chapter of the Law of construction

Today, I read the contents of chapters Nineth and tenth of the Law of Construction, chapter Nineth, from the perspective of the developer, the development of the project manager; Tenth chapter mainly introduces a good software design tail How to describe the user scene.

The Nineth chapter is about the function of the "project manager" position and the relationship with other departments. The PM is abbreviated to PM, but it's not just the project manager's meaning. Product Manager, Project Manager, Program Manager abbreviations are PM. The meaning is Product manager, Project Manager, Microsoft Project Manager in turn. Program Manager: Microsoft's job title, responsible for everything except product development and testing. PM to manage risk throughout the project lifecycle. It's not that easy to be PM. PM to be able to understand the user, can stand in the perspective of the user to consider the problem, observe the user is not good at expressing the demand, understand the implication of the team members, listen to the boss/client/stakeholder implication. PM to be able to analyze the focus, find priorities, make judgments, make decisions.

The 10th chapter is mainly about qualitative users and typical scenes. First introduced the typical user knowledge, we have to learn to define a typical user, we must first divide the typical users into popular typical users and unpopular typical users, and typical users need to include: name, age, income, the proportion and importance of the users represented in the market, using this software typical scenario, using the software /service environment, living/working conditions, knowledge levels and abilities, user motivation, purpose and difficulty, user preferences. And what is a typical user to do? is to make sure that our software is not designed for everyone, but only for the typical users we have identified. Once a typical user is identified, the scenario is determined, and the scenario is defined to describe what the user is going to achieve with the system and the process that must be experienced to achieve the goal. Once the scene has been identified, the architect and the owner of each module will divide the scene into subsystems and different modules. Then the use case is also a common requirement analysis tool. It requires us to determine the following elements: Title, role, main success scenario, step, extended scene. Next we introduce what is the specification, it can be divided into software function manual and software specification. The function specification mainly describes some functions of the software, and the technical specification describes how the developer should implement it, and then the function-driven design, mainly includes: The first step: constructing the overall model the second step: Constructing the Function List step three: Making a development plan the fourth step: Functional design phase This section is mainly called How we implement the function.

Software is to serve the user, we should design the software at the beginning of the use of the software should be more consideration of the situation and as far as possible to achieve the convenience of the function, so that users can really feel our excellent work.

Read Note 05