table of Contents
It is elaborated from three aspects: demand side, demand acquirer and business itself.
Demand side (customer side):
Issues generated:
- Incomplete description: only the requirements under normal circumstances are considered in the description, and some requirements that are considered common sense are ignored. The
solution: the demand acquirer can properly guide and mine - Inaccurate terminology , may be clear in the heart but lack of expressive ability
Solution: Try to understand the thinking process that users use to express their needs. Fully study the decision-making process made by users when performing tasks, and extract potential logical relationships. Flow charts and decision trees are good ways to describe these logical decision paths. - Limited knowledge ability : Interlacing like mountains, and limited knowledge, resulting in incomplete and inconsistent requirements.
Solution: Try to ask customers more questions to better obtain the demand. - Insufficient user participation : There are too many actual users to effectively select customers; users do not cooperate with demand acquisition; there is no clear user
solution: the demand acquirer should make effective choices for users, initiate demand acquisition, or try multiple acquisition methods to acquire demand.
Demand acquirer:
Issues generated:
- The strength of professional competence : an acquirer needs to understand the needs of a variety of methods acquired (such as interviews, questionnaires, prototyping, simulation scenarios to observe, document review, etc.)
solution: with a strong professional capacity-person needs of the acquirer, or team At least one of the more experienced software requirements engineers - Difficult
to understand customer needs Solution: Try to explain clearly the assumptions held by customers, especially those that conflict - Always stand on the technical point of view, unable to understand the customer's business needs
Solution: The demand acquirer understands the software implementation technology, but the premise of the software is to meet the customer's needs, rather than being limited to technology. Technology obey the demand, should try our best to solve the customer's demand - Effective demand extraction
during requirements acquisition Solution: Analyze the model during the requirements acquisition process, screen graphics and prototypes can make the concept expression clearer, and then provide a way to find errors and omissions - Effective selection of users
Solution: When the demand is obtained, it is best to control the number of teams in the seminar from 5 to 7 - When demand is acquired, tools are carried and personnel arrangement is insufficient, and the demand cannot be acquired and processed in time
- The scope of the project is too small or too large
- Demand collection cannot be comprehensive
The business itself:
- The actual business is more complicated than expected
