EN 
DE If only it weren't for the customers. Or the project manager. Or my own boss. Everyone finds something to criticize about my beautiful embedded solution. One function is difficult to use, another is missing entirely, the input field should have a blue background, the response time is too long, the memory fills up too quickly, and so on and so forth.
The more complex the module, the more extensive and complex the requirements and the well-intentioned suggestions for extensions and improvements. Especially with embedded systems, complexity is constantly increasing, and with it, the number of requirements.
The following image illustrates the situation:
Figure 1: Requirements management – a challenge with requirements
Limited resources no longer allow us to implement most, let alone all, of the requirements. Filtering requirements inevitably leads to frustration. Who would accept having their own requirement rejected while another colleague's or client's is accepted? Add to that the constant time pressure. Ignoring the problem and waiting it out isn't an option either. The problem won't solve itself – the project manager is calling, and so is the competition.
The good news is: there is a suitable solution for this, and it is called Requirements management. The principle is quite simple and is outlined in the next image:
Figure 2: Principle of requirements management
The task is to process the requirements and ultimately determine whether a requirement must be implemented, can be implemented, or should be discarded. From the "Yes" and "Maybe" containers, the remaining requirements are transferred to the requirements backlog, in the exact order required for implementation. This completes the essential task for a requirements manager.
The advantages of good requirements management are compelling:
- The important requirements are implemented, the unimportant ones discarded. The process separates the wheat from the chaff using a defined procedure.
- The process generates a priority-ordered list of requirements. The requirement at the top is addressed first. As many requirements are implemented as resources and time allow. Alternatively, resources or time are adjusted.
- The process is transparent. For each requirement, there is a status report and an objective explanation for the decisions.
- The procedure prevents "management by noise". Demands made in an intrusive and loud manner are treated exactly the same as those made in a reserved and quiet manner.
Author:
Alfred Ressenig is a speaker for the training course "Product Management for a Modern Company" formerly offered at MicroConsult and brings 18 years of professional experience as a product manager in renowned international technology companies.
Requirements Management: Training & Coaching
Requirements Engineering and Requirements Management for Embedded Systems
With the knowledge acquired in the Requirements Engineering training, you can introduce, evaluate, optimize, understand and implement a requirements process in your company.
Training – Requirements Engineering and Requirements Management for Embedded Systems
Training & Coaching You can find information on other topics in our portfolio here. here.
Expertise You can find information on other topics in our portfolio here. here.
