The law of construction of software engineering eighth, nine, 10 chapter

Eighth Chapter Requirements Analysis

This chapter focuses on software requirements and user surveys to find software requirements in several steps: acquiring and guiding requirements, analyzing and defining requirements, validating requirements, and managing requirements in the SOFTWARE PRODUCT lifecycle. The need for software is also divided: the need for product functionality, the need for product development, non-functional requirements, and comprehensive requirements.

Common user Research methods are: 1. focus group, 2. In-depth interviews, 3. Card classification, 4. User survey, 5. User log Research, 6. Anthropological survey, 7. Eye tracking Research, 8. Rapid prototyping and 9.a/b testing.

Nineth Chapter Project Manager

The project manager has a lot to do, the responsibility is important, is a team indispensable member of the ability to mobilize subordinates, effective listening, advising and understanding of others behavior, project management is a dynamic management, which requires the project manager must have the flexibility of the ability to respond to adverse situations quickly, and begin to solve. Without the ability to be flexible, you will inevitably be helpless and anxious as hot as a hot cat, and eventually it may lead to the progress of the project, unable to continue the project. Risk is mainly generated from uncertainty, and successful project managers are concerned about risk as a major concern. All issues affecting the purpose are always generated in this way or in that way from the risk. A good project manager can significantly reduce risk, usually by insisting on an open communication policy, to ensure that every important participant has the opportunity to express their opinions and concerns.

Tenth. Typical users and scenarios

。 Typical users can include the following: 1. Name (the more natural the better). 2. Age. 3. Income 4. The proportion and importance of the users represented in the market 5. Typical scenario for using the Software 6. Environment for using the software/Service 7. Life/Work 8. Knowledge levels and competencies 9. User Motivation 10. User Preferences. Use cases require a planning instruction and a functional specification.

The law of construction of software engineering eighth, nine, 10 chapter