Qu'est-ce que la gestion des exigences ?

La gestion des exigences est un ensemble itératif d'activités qui permet de livrer une description complète du produit qui répond aux besoins et aux attentes des clients et des parties prenantes internes ou externes, regarding every step which needs to be performed during the requirements development process like elicitation, evaluation, documentation, or refinement. Therefore, requirements management is an especially important topic in the automotive industry. The reason behind this is very simple – automotive requirements management process has its own list of very strict requirements.

Proper management of requirements gives more benefits the greater the complexity of the project is. In any case, please don’t miss the point: proper requirements management process is always a legitimate approach, especially if you consider how often a real complexity is underestimated or it is just impossible to estimate it correctly.

Pourquoi gérer les exigences ?

The answer to that question seems obvious and, in my opinion, it is – requirements management simply pays off. Besides a long list of advantages like improvement of quality, decreasing risks, or enabling effective scope management, it is also necessary to take into consideration the disadvantages.

Cependant, ce qui peut sembler à première vue être les plus grandes faiblesses, par exemple unnecessary additional effort or increase of costs, turn out to be advantages because at the end of day requirements management brings cost and time reduction, especially in the automotive word. The crucial thing is to adjust the requirements management plan to project needs and limitations.

Que signifie la gestion des exigences pour l'industrie automobile ?

A significant part of the automotive products has combined various types of features that could be related to safety. From the requirements perspective, it means an increase of complexity level, additional processes that need to be achieved and of course a new branch of the requirements to create – safety requirements.

The safety requirements are defined for risk reduction. It is associated with additional required activities like additional traceability structure, safety attributes management. Furthermore, the automotive quality process requires a number of artifacts that need to be created and maintained in terms of requirements engineering as well.

When developing an automotive product, it is emphasized that the vehicle meets the safety requirements, but it is just the thin end of the wedge. The creation of a proper tailored requirements management process can help during the whole product lifecycle development process.

L'une des premières étapes à franchir consiste à déterminer le type d'exigence. Il s'agit d'une technique qui permet de créer une hiérarchie d'exigences avec une relation en cascade entre les différents niveaux d'abstraction. La variété des types d'exigences doit être adaptée aux besoins du projet ; toutefois, on peut supposer avec un certain degré de certitude que la distinction suivante conviendra à la plupart des applications liées à la sécurité :

  • Fonctionnel,
  • Non fonctionnel,
  • Partie prenante,
  • Sécurité fonctionnelle,
  • Sécurité technique,
  • Activité,
  • Interface,
  • Composant.

Chaque type d'exigence décrit son propre périmètre. Sur cette base, la définition d'un produit est réalisée selon une perspective différente. Cependant, les exigences peuvent être distinguées et structurées non seulement par « type ».

An integral part of the requirements are attributes, which are used to precisely define characteristics of a particular requirement. The total number of used attributes depends on project scope, level of complexity and specialisation diversity involved in a project. Les attributs exemplaires qui pourraient être mis en avant sont :

  • JLR
  • Catégorie,
  • Discipline,
  • Faisabilité,
  • Sécurité,
  • Version,
  • Version planifiée.

A proper attributes definition constitutes a strong basis for a traceability chain. In relation to the standards as well as Automotive SPICE and Automotive Functional Safety standard – ISO 26262, required traceability and suitable artifacts are determined, but neither of those standards provides information on how to plan and implement traceability in practice. Thereupon, adjusted requirements management plan gives a space to tailor it to owns needs.

En savoir plus sur l'ISO 26262 !

Consultez notre guide

Quels sont les meilleurs outils de gestion des exigences dans l'Automobile ?

Undoubtedly during the development of a serious project, it is crucial to maintain requirements with respect to traceability and change version in a structured way. Manual coordination of the living complex structure sounds impossible even for one person, not to mention the whole team. That’s why these market gaps have been quickly filled with dozen of various tools which can support and maintain a significant part of the requirements dependencies.

Comme toujours, le meilleur outil dépend de l'objectif d'utilisation particulier, il n'existe donc certainement pas une seule bonne réponse. Au final, au-delà des arguments concrets, le choix final dépend également des habitudes et des préférences personnelles.

Planification de la gestion des exigences : bonnes pratiques pour garantir le succès du plan d'exigences

The key is to avoid surprises. Ensure to implement requirements management as early as possible for example in your strategy planning and make sure that every dependent competence is aware of the importance of requirements management. For obvious reasons, there is no possibility to anticipate every possible dependency which can happen in a project, so it is a very wise approach to prepare a requirements management plan ready for iterative evolution during a product lifecycle.

Certainly, there is a number of benefits, which requirements management brings to both project and organisation, but the most crucial is to remember that requirements management is for help and support. An unsuitable approach could bring overwhelming bureaucratic limitations, which can be counterproductive.

Requirements management is an iterative process that ensures the product description is complete and accurate, and aligned with the expectations of customers and stakeholders. It involves activities such as eliciting, evaluating, documenting and refining requirements. Effective requirements management improves quality, reduces risks and supports effective scope management. Although it may initially appear to incur additional effort or cost, it ultimately saves time and resources, particularly in complex industries such as automotive, by preventing rework, misunderstandings, and overlooked dependencies.

Automotive products include many safety-related features, which increase complexity. This requires additional processes such as defining safety requirements, creating safety artifacts, ensuring traceability, and managing safety attributes. Proper requirements management helps navigate these complexities and maintain compliance with industry standards like Automotive SPICE and ISO 26262.

Automotive projects use multiple requirement types, functional, nonfunctional, stakeholder, functional safety, technical safety, business, interface, and component, each offering a different product perspective. Requirements also include attributes such as ID, feasibility, safety level, category, and planned release. These attributes support traceability across all development stages.

The right choice depends on project goals and user preferences. However, tools are essential due to the complexity and traceability needs in automotive projects. Best practices include implementing requirements management early, ensuring all teams understand its importance, and keeping the requirements plan flexible to evolve throughout the product lifecycle while avoiding unnecessary bureaucracy.