Requirements Management

The requirements are the reason for the project and development work. Requirements set the expectation for the final product. Either these are achieved or there are reasons communicated to the stakeholder to alter or eliminate specific subset of the requirements. Requirements management requires an understanding of the connection between the requirements, the project objective, and ultimately the work of the project. Requirements management includes commitment to meeting the requirements, the bi-directional traceability of the requirements from customer input to instantiation of the product as well as addressing requirements changes systematically.

Requirements Management - Value Transformation

Commit to Requirements

To reach the objective the organization must stand behind the requirements. If the organization is not able to commit to meeting the requirements there is no sense in undertaking the project. To be able to commit to the requirements means understanding the requirements without understanding the commitment is hollow.

Evoke Requirements

There are a number of approaches available to evoke and documenting the requirements. To be able to gather the requirements necessitates knowing who will provide this information. Requirements are written in a very specific way to reduce the possibility of multiple interpretations. There will be metrics by which the requirements will be compared to determine if these are written meeting the objective and where the interpretation is singular.

Work Performed and Requirements Discrepancies

The requirements are documented and the team moves to incarnate the specifics that will constitute the product or system over time. A comparison of the work being performed and the work products are conducted periodically to uncover any deviation from the objective. Once uncovered the project and product development work will be altered to ensure that the work being performed is to deliver the expectations defined in the requirements.

Manage Requirements

Managing the requirements is where inconsistency in the requirements from the project objectives as well as maintaining the interconnectivity and dependencies between requirements are maintained. Any inconsistency in the requirements will require corrective actions. As the projects progresses, changes will likely happen, managing the changes and adaptation to the requirements will also be part of managing requirements.

Requirements Traceability

At any time in the product development lifecycle there is a traceable connection between the requirements and the project objectives and plans. This makes identification of the contents of the product at any given point; that is a connection between an instantiation of the product and the requirements through to the project objectives. This connection ensures the requirements; product development and project effort are aligned to produce the desired project results.

Requirements management – consists of the approaches we use to evoke, prioritize and document the expectations of the product. This includes the quality attributes of the articulation of those requirements along with managing the changes and traceability of the requirements to the customer’s needs or demands.

    1. https://www.ifpug.org/

Project Health Measurement: Beyond Red, Amber, and Green

Project Health Measurement: Beyond Red, Amber, and Green (part 1) This article is by our long-time collaborator and musician. Steve Lauck.  Over the years, I have collaborated with so many…

Design Reviews: Don’t Show Up as the Bait

A design review should be an engineering discussion, not a feeding frenzy. by Jon M. Quigley Effective design reviews start long before the actual review. Throughout my years working in…

Product Aging and Simulation: When Models Fail

The Model Didn’t Age. The Product Did. By Jon M. Quigley This post originates from my time at Automotive Testing Expo in Novi, Michigan.  I want to thank Automotive Testing…

Beyond Pass or Fail: What Testing Changes in a Product

Automotive Testing Expo Well, the Automotive Testing Expo is over.  My notebook is full of notes.  I want to thank all who attended, especially those who spoke during the event.…

Transparency in Embedded Systems Testing | Feynman

Transparency in Embedded-System Development and Testing I was part of a fireside chat at the automotive testing expo on transparency.  The chat was about transparency, and when I think of…

Beyond Pass or Fail: Exploring RF and Environmental Testing at Automotive Testing Expo USA

One of the benefits of attending Automotive Testing Expo USA is the opportunity to meet organizations that approach product testing from different technical perspectives. Two companies that caught my attention…

Rediscovering the Volvo Technology Award: Lessons from the IC05 Project

Volvo Technology Award: Lessons from the IC05 Project   While cleaning out my bookshelf recently, I came across a letter dated April 27, 2006. It was from Torbjörn Holmström, President…

Automotive Testing Expo 2026: Advancing Vehicle Testing and Verification

Automotive Testing Expo North America | October 27–29, 2026 | Novi, Michigan Modern vehicles are becoming increasingly complex. Software-defined vehicles, electrification, connected systems, and distributed electronics introduce new challenges for…

Automotive Project Management: Suppliers, Change & Risk

Automotive Project Management: Suppliers, Change & Risk By Steven G. Lauck Why Automotive Project Management Requires an Integrated Approach Automotive project management is about much more than maintaining a schedule,…

Project Risk Management: Six Steps to Deliver Expected Outcomes

Mitigating Risk No. 1: Deliver the Expected Outcome By Steven G. Lauck  Even a well-planned project can miss its goal. This can waste time and money, damage trust, harm the…

CMMI Tracking

[sdm_download id=”15558″ fancy=”0″]

Pugh Matrix

[sdm_download id=”15560″ fancy=”0″]

Contact Value Transformation about Requirements Management

Error: Contact form not found.

Cart0
Cart0
Cart0