"Quest for demand-quality before design" read Note three

The first step in getting information is to define the function, at which point the product is described for what it is doing. The hypothesis is the root of the decision tree, so the customer says that what is needed is the issue statement. And the customer said that the product can achieve what function is refers to his test function. In describing functionality, it is necessary to document the functionality that all users want, and then to understand it, not to record features that the user does not want. Doing this requires some skill, first documenting all the potential features, understanding the obvious hidden and decorative features, and identifying unnoticed features. Practical function to inspire the way to identify functions, to create a return function of the processing method.

Attributes are characteristics that customers want, and to differentiate between attributes and functionality, products with different properties may be functionally similar or identical. The same attribute may qualify more than one attribute, and the attribute is classified as required, required, and ignored at the time of analysis, so that the user's expectations can be effectively judged. A constraint is a mandatory condition placed above an M-type attribute, and every constraint must be met in order for the final design to be accepted by others. Every system will have his boundaries, and we have to take that into account when considering constraints.

Preference is a desire attached to an attribute, but it is a selectable condition. In demand, this factor of preference allows developers to choose the best and most qualified solution from the alternatives, which is better for our solution. Often when the designer delivers the product to the user, users will find their preference. But preference should not be overused. When determining this factor, it is important to distinguish each preference clearly, otherwise it is difficult to distinguish between two or more preferences. In order to make the numbering quantifiable, it is possible to use the multi-sensory information display to quantify the proportion of people who can receive all the information. Constrained preferences tend to be value, and value maps can help designers analyze each of the preferred forces to make their work more directional.

The difference between disappointment and satisfaction is not in the outcome of electricity tariffs, but in the degree to which the deliverables and expectations are matched. Because people are not perfect, people are not all logical, people have different understanding of things, such as a series of factors, need an additional step to limit expectations. To calculate the impact of a factor, you can use the method you want to limit: Generate a specific list of expectations, generate a list of expectations, limit expectations, and keep the possibilities open.

Then the project requirements phase comes to an end, after a few stages of measuring ambiguity, conducting technical review, measuring satisfaction, testing cases, learning existing products, and reaching agreement. First of all, the method of voting can be used for ambiguous measurement, the participants can be investigated according to different problems, the ambiguity of three ambiguous problems, the ambiguity of the design process and the ambiguity of the final product are clarified and processed. The review phase, the technology attached as a project review to provide information, the project review should also consider non-technical topics of information; The results of the body can be adjusted to match the requirements of the resource, or adjust the resources to match the requirements. The review report is also written to be complete and accurate, as a reliable basis for related work, measurable for the purpose of tracking processes, since a review is required to provide a reliable measure of work progress.

The user satisfaction test can then be done, in order to avoid user dissatisfaction, we need to measure user satisfaction from the beginning of the design. In addition, the test itself can be used as a tool to find properties, and a tool for designers to communicate with users, which can be used as a cross-cutting content to help designers work. The next black-box test can be used to obtain what the project can and does, and the results of the black-box test can be used as a basis for subsequent system and product testing, so this step is necessary to test the completeness, accuracy, and conciseness of any requirements that are developed to the present.

Almost no "new" product is entirely new, because all of the products that are designed are almost always compared to what is already there. To compare their products with existing products, to see what features are missing in the product, whether there is a corresponding part of the implementation of their products. Compare products put forward a list of features that might be omitted from the new requirements, and then interview the users of some of the older products, present a feature that is missing from the current system, and then correct their own product requirements. At the time of decision-making, it is necessary to make choices, assumptions and forced acceptance, and to convert the decision into an agreement without false assumptions. The demand process begins with a vague line and ends with an agreement.

"Quest for demand-quality before design" read Note three