What Is Demand Management?

Demand management (demand management) refers to marketing management, which refers to the level, timing and composition of the need to help companies in order to achieve their goals. ^[1]

Demand management

Requirement management is a part of the complete management model. It is inseparable from other features such as integrity and consistency, and is related to each other. A set of requirements management should be a complete reflection of known system requirements. Each part of the solution is to satisfy (or even fully meet) a certain percentage of the overall requirements, and it is not meaningful to address only part of the requirements. An oversight of critical requirements is likely to be catastrophic. Imagine the consequences of an aircraft's failing safety design. The combination of different requirements constitutes a complete set of requirements models. User requirements determine the problems to be solved in the system design and the results they bring. It can be said that requirements management indicates everything that system development must and must do, and it indicates the functions and constraints that all designs should provide. The process of requirements management, from the acquisition of requirements throughout the entire

Avoiding failures is a very good reason. It is also a reason to increase the success rate of projects and other benefits brought by demand management. The CHAOS report of the Standish Group further confirms that the biggest factor related to successful projects is good demand management.

The first step to understanding requirements management is to reach a consensus on what is requirements management. Rational defines requirements as "conditions or functions that a system (under construction) must meet". The Institute of Electrical and Electronics Engineers uses a similar definition. famous

Simply put, the reason why system development teams manage requirements is because they want to make the project successful. Meeting the project requirements lays the foundation for success. If the requirements cannot be managed, the chances of achieving the goal will be reduced. The evidence recently collected is Persuasive: The CHAOS Reports of the Standish Group from 1994 to 2001 confirmed that the most important cause of project failure is related to demand. In 2001, the CHAOS Reports of the Standish Group reported a study of the company, After investigating each project, it was found that 74% of the projects failed, that is, these projects could not be completed on time and on budget. Among them, the most cited cause of project failure was "change user requirements".

Needs are not always obvious, and they can come from all aspects. Needs are not always easy to express clearly in words. There are different kinds of needs, and their levels of detail are different. Without control, the number of needs will be difficult Management. Requirements are related to each other and to other deliverables of the process in multiple ways. Requirements have unique characteristics or characteristic values. For example, they are not equally important, and the difficulty of processing is also different. Requirements involve many related interest

In the process of requirements management, the means of capturing requirements is important, but in the process of capturing requirements and finalizing the requirements, we will face a variety of requirements-related information and materials (this information can also be collectively referred to as " Requirements "), how to discover the relationship between these information and organize it effectively is more critical. The type of requirements is

By defining the type of requirements and the relationship between them, we have established a framework for a demand management model. Of course, we have established such a model to facilitate our use of requirements, and in order to achieve this, we also need to be here Corresponding content is added on the basis. Various attributes need to be added with their attributes, in order to query the requirements and other management methods. For example, according to user needs, you can determine the needs of the need, priority, certainty and other attributes. In an actual project, you can determine the values of these attributes, and then schedule the project according to these actual attribute values. Or, when the project is urgent, determine which requirements can be postponed and which must be completed. ,and many more.

Requirement traceability Secondly, according to the derivation of different requirements, a tracking relationship can be established between different requirements. For example, the user needs to determine the characteristics of the product to be built, and the characteristics of the product determine the software requirements of the product. Establish an association between these different types of requirements.Once some of these requirements change, you can determine the impact it may have and develop a corresponding strategy.

Workflow details

It can be said that demand is a model and an early prototype of the product. By performing a demand analysis, we can optimize the final product. It is important to keep in mind that demand is always changing. The tasks that need management needs to complete include:

Define needs and reach consensus;

Establish associations;

Design corresponding solutions according to different needs;

Go

The tools used for requirements management must be able to process and apply to the various requirements mentioned in this article, which should help us analyze the requirements, determine the corresponding development and support tools to process related information, and then process the corresponding modules of the system. System engineers are always committed to visualizing requirements with simple tools, commonly used tools such as system publishing tools with annotations and related databases.

Requirements management involves a series of complex objects, and its tasks are very broad, and are related to all aspects of the entire design and development. The tools used should provide some of the functions listed in the figure:

This article deals with requirements management engineering. Requirements management is a testament to the effectiveness of development. It is clear that requirements management is a high-level system behavior that involves the entire development process and the product itself.

Requirements management must first analyze the needs, then apply them to the product and propose a solution. The model of demand analysis is the prototype sample of the product. Excellent demand management increases the possibility that it brings the final product closer to solving the demand, improves user satisfaction with the product, and makes the product a truly high-quality qualified product. . In this sense, demand management is the foundation of product quality.