Chapter 8, 9 and 10 of the Law of construction

The eighth chapter: Demand Analysis

This chapter mainly introduces the types of software requirements, stakeholders, the common methods and steps to obtain user demand analysis, the framework of competitive demand analysis, the four-quadrant approach, and the NABCD of project planning and estimating techniques. Demand analysis is to determine the scope of the use of a software, only one meeting the needs of the public software, to obtain revenue. In this case, demand analysis is particularly important. The software requirements are divided into the following steps: 1. Acquiring and directing requirements. 2. Analyze and define requirements. 3. Verification Requirements 4. Manage requirements in the SOFTWARE PRODUCT lifecycle. Software PRODUCT stakeholders include: User surveys, in-depth interviews, card classification, user surveys, user log studies, anthropological surveys, winter tracking studies, rapid prototyping, and A/B testing. The framework of competitive demand analysis NABCD the use of better solutions, making it easier for us to develop good software.

The Nineth Chapter: Project manager

Project manager, refers to the establishment of the project manager responsibility system as the core, the implementation of the project quality, safety, progress, cost management of the responsibility to ensure that the overall improvement of project management level of the important management positions. The project manager is the person who is responsible for the successful planning and execution of the project. PM's ability is important. PM is a good pm that has the ability and is approved by everyone. Here PM is an important role in promoting a team to work quickly and efficiently, but also need to be able to work with others, equal. A good PM requires strong requirements and capabilities: 1. Ability to observe, understand and learn quickly, 2. Ability to analyze 3. A certain professional ability, 4. A certain professional ability 5. Ability to introspect. These are key to the team's success and very important. The project manager is the leader of the project team, and the primary responsibility of the project manager is to lead the project team to complete the project work and satisfy the customer in time and within budget. For this purpose, the project manager must lead in a series of project planning, organization and control activities to achieve the project objectives.

The tenth chapter: typical Users and scenarios

This chapter focuses on typical users and scenarios. Typical users can include content: 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. Provides templates that define typical users and scenarios to help us emulate. The performance test case design begins with the analysis of typical scenarios in the user's reality, and then is designed with reference to typical scenarios. There are three types of common user scenarios: Usage scenarios for different time periods within a day the usage of most systems changes over time on the same date. The scene of the system running in different periods is the basis of the design of the large data volume performance test case. Scenarios in different business modes the same system may be in a different business model.

Chapter 8, 9 and 10 of the Law of construction