Tag Archives: requirements traceability

Manage knowledge, not documents

I stopped thinking much about documents 20+ years ago.  I know that most business processes still demand them (stage-gate, systems engineering, new product development, government contracting, proposals, etc.).  I know that lots of effort is expended in maintaining document templates, … Continue reading

Posted in Decision Concepts | Tagged , , , , , , , , , , , | Leave a comment

A 3V Traceability Model

I’ve written numerous posts on decision-to-requirements traceability based on the fact that decisions are the creators and consumers of requirements.  Consistent with this, I use a 3V (or 3-Vee) model of traceability that is best represented by a 3-D model … Continue reading

Posted in Decision Concepts, Decision Driven Product Development | Tagged , , , , , , , , , , , , , , , , , | Leave a comment

Derived requirements – continued

If decisions create requirements (as explained in my previous post), then decisions also create ALL the interactions between requirements.  This implies that there is never a constant, always-present, solution-independent relationship between any 2 requirements. Perhaps you’ve been involved in populating or … Continue reading

Posted in Decision Concepts, Decision Driven Innovation, Decision Driven Product Development, Decision Driven Strategy | Tagged , , , , , , , , , , , , , , | Leave a comment