Mastering the need process read Note two

Understanding the methods and problems of the requirements process, the next step is to trap the requirements. The work is planned by demand analysts, but to do so requires an analyst, user, and other stakeholders to work together to identify each role's responsibilities. The perceived need is the one that the user first thinks of, which usually indicates something the user wants to improve, that the unconscious need is something that the user is not aware of, and that what is not dreamed of is what is required once the user realizes that it is possible. In the course of the snare, all requirements must be revealed and captured, and the activities of the snare are multi-faceted, using some of the output from the start-up phase activities, and the business events dominate the snare activities.

The first part of the requirement snare is the observation work, any modeling of the current system should be as concise as possible and complete as soon as possible. User interviews are a traditional approach to demand collection and are more effective in conjunction with some techniques. For every business event that has a work response, the business event workshop is an activity. The goal of a business event is to focus on the results that the organization expects when a business event occurs; A scenario is a series of behaviors used to respond to business events; Business rules are rules of management that govern and guide daily business decisions. Innovation is part of the demand process, and brainstorming is a way to generate new ideas that take advantage of the group effect.

Functional requirements indicate what the product must do, and the activities and prototyping activities reveal functional requirements. Non-functional requirements are attributes that a product must have. These properties can be thought of as features or attributes that do not alter the functionality of the product. Functional requirements describe the action of a product from a work perspective, and non-functional requirements describe the user's experience at work, that is, non-functional requirements are the characteristics of the work represented by the condition or functional requirements. Non-functional requirements may be revealed through functional requirements, and prototypes can be used to derive non-functional requirements.

The perception requirement describes the spiritual essence of the product's appearance expectation, the measurement method of the demand is its acceptance target, and as the automation and software products turn to the consumer-oriented field, the perception demand becomes more and more important; The usability requirement takes into account the product's target user and describes the appropriate level of ease of use. The ease of use of the product will have an impact on the user's productivity, error rate, and acceptance of the new product; performance requirements are applied when a product needs to perform certain tasks at a given time or specific precision, primarily from the operating environment, and operational requirements describe the environment in which the product is used, To identify operational requirements, you need to look at the product boundaries defined in the use case diagram and consider the needs of each adjacent system or participant, and security needs must be guaranteed to be correct, or it will bring the greatest risk to the product, which can be considered to have three aspects: confidentiality, which means that the data cannot be accessed by anyone other than the authorized user; The data maintained by the product is consistent with the data that is sent to the product by the neighboring system, and availability refers to the data that the authorized user can access without being blocked.

Once the requirements have been obtained, the requirements are written in the form of a requirement specification. This refers to the task of getting a complete description of the product to be built. The requirements found in collecting requirements or prototyping do not necessarily have a complete form, they are only the idea or intent of the demand, the requirements specification is the basis of the product construction contract, so must contain clear, complete, testable instructions, there are some auxiliary means to help complete a successful requirements Specification-template and requirements framework, One of the Volere Requirements Specification template can be used as a good basis. Volere Requirements Specification template contains four of the majority: constraints (not the real demand, but the demand and the final product has a great impact, including the purpose of the product, the target users of the product, etc.), the product requirements (functional and non-functional requirements), the project problem (also not the product needs, It is the problem that must be faced if the product is to become a reality.

The trap is about collecting demand and listening is the most important requirement gathering skill. Functional requirements should be able to form a complete, as far as possible to avoid ambiguity of the product function description. Non-functional requirements describe the quality of the product-whether it needs to be fast, secure, attractive, etc., which is derived from the functionality required by the product. Writing a requirement specification is not an independent activity, but is done with the rest of the process, it is not a random activity, business events, usage, templates, and requirements framework so that we may at any time measure its degree of accomplishment.

Mastering the need process read Note two