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

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

The eighth chapter: Demand Analysis

Software development team is for the sake of the user, so always in the program project before the development of the project needs analysis

This section covers 4 steps for software requirements, (1) acquiring and directing requirements (2) analyzing and defining requirements (3) validating requirements (4) managing requirements in the SOFTWARE PRODUCT lifecycle. Analyzing software requirements in software engineering requires consideration of stakeholder relationships, such as the relationship between users, customers, market analysts, regulators, software engineers, etc.

9 User research methods are described: (1) focus Group (2) in-depth interview (3) card category (4) User survey (5) User log Research (6) Ethnographic/Anthropological survey (7) Eye Tracking Research (8) Rapid Prototyping (9) A/B testing

We use these methods to develop software, so as to meet the needs of users as much as possible.

The Nineth Chapter: Project manager

This chapter describes the project manager's origins and requirements, the difference between project manager and other managers, and PM's professional competence. The ability to act as a pm,pm is important. PM is a good pm that has the ability and is approved by everyone. In this section, the project manager is simply the leader of the project team, and the project manager's primary responsibility is to lead the project team to complete the project work and satisfy the customer in a timely and high-budget manner. 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

1. Typical scenarios and typical users

User awareness, such as the value of the user, how to define the user, the combination of users and scenes, from the scene to the task, as well as the user's template or story.

2. Specification Sheet

(1) Function manual

Define related concepts--specification good hypothesis--avoid misunderstanding, define some of the user/software interaction steps-----some good features and side effects---quality of service

(2) Function specification template

(3) Technical manual

(4) Function-driven design

Build the overall model, build a feature list, develop a development plan, feature design phase, to achieve specific functions

This section teaches us how to define a typical user and provide a template for defining typical users and scenarios that can help us imitate.

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