0525 Chapter 8, 9 and 10 of the Law of construction

Eighth Chapter Requirements Analysis

This chapter mainly introduces the requirement analysis. Requirements analysis in a software development process is very important, there is no need for analysis, it can be said that the software does not know which direction to start. The needs of people in today's society are varied, and the project team needs to analyze the software to meet the myriad needs of people. Therefore, in the process of software project development, demand analysis plays an important role.

If analysts fail to correctly recognize the needs of the customer in demand analysis, then the final software is virtually impossible to meet the customer's needs, or the software project cannot be completed in the specified time. This will have an impact on the timely completion of software products and the stakeholders of software products. Through the need analysis to develop the target software, but also through the needs analysis to solve the bug, to meet customer requirements.

Question: Is it time to consider the feasibility of the analysis requirement before the project?

Nineth Chapter Project Manager

The project Manager (PM) will feel good and tall on hearing it. In this chapter, we mainly introduce what PM is, the relevant examples of the origins of Microsoft PM, the role and impact of PM. In the division of our team roles, there are writing code, testing code drawing to design, but one is not within this scope but still very important role-project manager. In project development, not just coding, testing code, drawing and designing, there are many things to do outside of the test development, and these developments and tests are done in PM. So do not think that PM is a power, the position of more comfortable position, behind the pay a lot. He and we work equally, but the hidden task pressure can be said more than the team members.

Question: Does PM need a high standard?

Tenth. Typical users and scenarios

In this section, we can use the examples in the textbook to find out what the typical user is like and what the scene is all about. A typical user's template is

1. Name (the more natural the better).

2. Age.

3. Income

4. Proportion and importance of the users represented in the market

5. Typical scenarios for using software

6. Environment in which the software/service is used

7. Living/Working Conditions

8. Knowledge levels and competencies

9. User Motivation

10. User Preferences.

The scenario is:

1. Typical users

2, the user's needs

3. Assumptions

0525 Chapter 8, 9 and 10 of the Law of construction