One of the most challenging aspects of traceability is the management of lifecycle data and linking that data to requirements.
Requirements driven development is a foundational component of any safety critical lifecycle, including ISO 26262, the state-of-the-art standard guiding safety in the development of automotive electronic devices. At face value, requirements seem like a very straight forward concept.
Simple enough, right?
Feedback from industry practitioners paint a much different picture. The ground truth is that there are a whole host of challenges that project teams face and many of those challenges are rooted in inadequate requirements practices.
Challenges
Fortunately, ISO 26262 has provided some guidance in the management of requirements, an example being ISO 26262:2018-8 Clause 6. The guidance covers requirement notation, attributes of a safety requirement, and the management of requirements, but even with this information, project teams still face a host of challenges, including:
Addressing these challenges is further complicated by the rapid growth in complexity for silicon and systems. Project teams must often manage thousands of requirements and the lifecycle data supporting those requirements. Recognizing this, the ISO 26262 standard committee went so far as to recommend the use of requirements management tools.
To read more, click here.
 |
 |
 |
 |
 |
 |
 |
 |
 |
Leave a Reply