Third, pay attention to the needs assessment of the integrity of the specification
We often from the following list of questions to guide assessment of needs is "complete."
1, the preparation of all requirements, the level of detail is consistent and appropriate?
2, whether the demand to provide a sufficient basis for the design?
3, all internal references to other requirements correct?
4, whether to include requirements to achieve each priority?
5, is the definition of the functional description of the internal algorithm?
6, whether to include all known customer or system requirements?
7, is missing the necessary information? If you have missed it, mark them as issues to be determined (TBD)?
8, whether all the expected error conditions are generated by the preparation of the document system behavior?
Demand that the integrity of the demand that is mainly reflected in the level of detail, we describe how to determine whether the demand for more? I think requirements need refinement, rather than the mere presentation of refined features, objects to consider all the participants involved, to doWhat, what data, what business rules and conditions subject to restrictions on what the system response, and so on.
Let's look at an example of functional requirements, "FR1: sales shipped to consider credit."
At first glance appear too simple and vague, and we change it into "FR1: 1 sales shipped on the premise that the customer has a credit value of more than shipping, otherwise, the system prompts' the customer credit shortage, no shipping!'2 After the formal system will deduct the shipping line of credit. "
Clearly, the revised shipping and credit needs of the whereabouts of the origins of specific reactions and systems that clear.
Of course, the demand for traditional descriptions to work with actors and use cases in the mapping system response and so on.
Fourth, pay attention to the needs of the feasibility and cost estimates for review
Demand for the feasibility and cost estimates are also requirements review in two important aspects.
Feasibility and needs assessment of the purpose of cost estimates, a number of programs from demand to choose the most optimal or most cost-effective solution.In general, the requirements specification can be given several options with a problem, and gives their advantages and disadvantages and cost differences, by comparison make the final selection by the decision makers.
When we understand the needs that our next step of its analysis of whether there is feasibility.
If feasible, you should also consider what resources it needs and budget.We need to determine whether the technology actually meet the business needs, we must also consider the whole cost of the product, including developers, servers, licensing and upgrade costs, also need to consider the initial hardware, software and support, infrastructure and training costs.
Pay attention to the quality attributes of needs assessment
We need to review requirements specification to determine the reasonableness of all the performance goals, whether it is reasonable to determine the safety aspects of the issue to be taken into account.
The reason why the system performance requirements placed in that at the conceptual stage, because the reality lesson.Do not you see a lot of features the system has been improved because of substandard performance, but shelved by the user - the user is often unbearable or respond too slow to run the system.