"Mastering the demand Process" reading notes (II.)

"Mastering the demand Process" reading notes (II.)

The project starts. We should make some preparations for the project and make sure that it is feasible before the action is made, and that the start-up meeting is a joint application development (Joint Application Development,JAD meetings, participants put themselves together and work together until the goal of the start-up meeting is to gather enough facts to ensure that the project has a worthwhile goal, that the goal may be met, and that the risk-holders ' commitment to the obligations is achieved.

Network knowledge. After the start of the project, we should begin to recruit knowledge and start the conference activities to provide a basis for the need. The start-up meeting identified the scope of work to be studied and the business events that had an impact on the work. The stakeholders identified by the initiation meeting provide demand to the demand collector, and the output of the activity is a potential demand that needs to pass through quality checks.

Do prototypes and scene modeling. Prototypes are a quick and incomplete version of a potential product. The intent of a prototype is a simulation of the need to express to the user. There are two ways to build demand prototypes: High fidelity (using certain automated techniques) and low fidelity (mainly using pencil-box paper, or some other similar way).

Write down the requirements. At this stage of the demand process, all requirements are called "potential requirements" because, so far, the requirements have not passed the test and passed the quality pass. Requirements are business requirements, and the business language must be used so that users can understand these requirements and verify the correctness of these requirements, as well as the need to ensure that designers are able to accurately build the products they want. To meet this need, an analyst will add an acceptance criteria for each requirement. Acceptance criteria are a measure of demand, which is designed to quantify requirements so that testers can pinpoint whether the product being implemented meets the requirements. Analysts used two mechanisms to make it easier to write the requirements specification. The requirements Specification template is an outline of the requirements specification, which the analyst uses to know how to write the requirements document. The second mechanism is the requirements framework, with a number of components for each requirement, and the requirements framework is a convenient way to ensure that each requirement has the right elements.

Quality clearance. Quality clearance is a single point that each requirement must pass before it becomes part of the requirements specification. By testing the completeness, correctness, scalability, ambiguity and some other quality attributes of each requirement before each requirement is added to the requirements specification, quality assurance is ensured by a stringent requirements specification.

Reuse requirements. The requirements for any of your projects will never be completely unique, so you can leverage your previous projects with important requirements.

Identification requirements Specification. This process examines missing requirements, ensures that all requirements are coordinated, and there is no unresolved conflict between demand and demand.

Post-mortem analysis. For this process we should ask the following questions about all the people involved in the process: "What have we done right?" "What have we done wrong?" "If we have to do it again, where do you do it differently?" ”。

The clipping process.

With:

The project starts ----- Find out what we really know about the project and begin to measure the project as early as possible.

The start phase determines the work that the product is to be part of and determines the exact goals that the product is intended to achieve. Other products provided during the start-up phase are useful for qualifying the product range and will be used as input for subsequent requirements collection activities. The product of the initiation phase provides the basis for the products: The purpose of the product, the customer, the customer, the stakeholder, the user, the restrictions, the name, the facts and assumptions, the scope of the work, the estimated cost, risk, continuation or termination of the decision.

The product objective describes the reason for building the product ----- What will the product do to help the job? The product goal is the business need. All other requirements collected must contribute in some form to that goal. We will review all requirements in the future based on this statement of purpose. Product objectives should pay attention to several aspects:

Target ----- A description of what the product will do

What are the advantages-----products can offer?

How do metrics ----- measure the benefits?

Rationality ----- Does the workload of building products outweigh the business advantages?

Can the feasibility --- product reach the measurement standard?

Can it be achieved ---- the organization has (or can acquire) the skills to build the product and can operate it after it has been built?

Develop a product who will pay for the development?

Know your customers, and your customers (if appropriate);

Know what they want?

Understand the customer's problem;

Understand customer's expectations;

Know what is acceptable and unacceptable to customers and customers.

"Mastering the demand Process" reading notes (II.)