Tag Archives: systems engineering

Simplicity

Three events this week have me focused on the theme of simplicity. On Tuesday, I participated in a panel discussion hosted by the INCOSE Crossroads of America chapter in Indianapolis. We fielded multiple questions about the practice of Systems Engineering, … Continue reading

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

Creating Value through Interaction Management

The ability to define, visualize and manage the interactions associated with any product or systems is growing in importance.  Mastering Interaction Management tools such as the N-Squared Diagram can create new value for your organization.  But where should you apply … Continue reading

Posted in Decision Concepts, Decision Driven Architecture, Decision Driven Product Development, Use Cases or Applications | Tagged , , , , , , , , , , , , | Leave a comment

The Interaction Management Challenge

There is the potential for interaction(s) between every pair of components that comprise a product or system. These interactions are governed by the scientific principles/laws of our universe, i.e. any two components can and will interact in every way made … Continue reading

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

Let’s Manage Interactions

We are putting the finishing touches on a N-Squared Interaction Manager for our U.S. Government customer; it won’t be long until this new tool is blended into our Decision Driven® Solutions Framework.  I can write a lot about WHAT interactions … Continue reading

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

Functional decomposition is a decision

Systems engineers do a task that is commonly known as functional decomposition.  This task starts at the very top of the definition of a system and breaks down all the functions required to support the product’s mission (use cases) into … Continue reading

Posted in Decision Concepts, Decision Driven Architecture, Decision Driven Product Development | Tagged , , , , , , , , , , , | 2 Comments

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