Thoughts on 8, 9 and 10 chapters of the Law of construction

The 8th chapter of 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 9th chapter of the project manager's Reading

This chapter focuses on the origin and requirements of the project Manager (PM) and the importance of the project manager. PM works equally with everyone, pushing the team to complete the functionality of the software. A group can have more than a number of PM, and other team members often form a resolution, steward regardless of people, but also to do specific work. 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.

10th Chapter

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.

Thoughts on 8, 9 and 10 chapters of the Law of construction