Tag: traceabilty

Leveling Requirements

Leveling Requirements ArgonDigital - enterprise automation experts

I was recently asked the question. “Suboptimal leveling of requirements seems to be a recurring issue for the projects in my business group (we’ve even seen low-level mechanical dimensions specified in the system requirements). We’ve been reading through the INCOSE Guide for Writing Requirements characteristic “C2 – appropriate” and it briefly mentions “leveling exercises.” Could […]

Requirements – What’s the Big Deal????

Requirements – What’s the Big Deal???? ArgonDigital - enterprise automation experts

Note: this is an update to this blog originally published in 2012. Preparing for the future A constant throughout the evolution of systems engineering is an ever-increasing complexity of systems which can be observed in terms of the number of system functions, components, and interfaces and their non-linear interactions and emergent properties. Each of these […]

How to Handle Implementation in Customer Requirements

How to Handle Implementation in Customer Requirements ArgonDigital - enterprise automation experts

I was asked the following question from a friend of mine: “I see a propensity to copy requirements from the Customer Specification to various levels of the requirement hierarchy in order to link between a Customer requirement written as implementation in their specification to where it is allocated to in HW/SW.  Is there any guidance […]

How Well Are Your Requirements Connected?

How Well Are Your Requirements Connected? ArgonDigital - enterprise automation experts

On our Ask the Experts page , the following question was asked: “I am a systems engineer currently involved in a complex aerospace system development.  While I was searching for some related topics on requirements management, your interesting website was pointed out. I am curious to know if you have a way of finding how […]

Controlling and Managing Change

Controlling and Managing Change ArgonDigital - enterprise automation experts

Controlling and managing change is one of the most important tasks for both the Project Manager and Systems Engineer.  Failing to do so often results in massive cost overruns, schedule slips, and failed projects. In the previous blog “Why do my requirements keep changing?”, we talked about why requirements change.  In this blog we discuss […]

Is the Requirement Verifiable?

Is the Requirement Verifiable? ArgonDigital - enterprise automation experts

This is another common question.  It is also a major complaint of both developers and testers.  Developers often receive requirements from their customers that are not verifiable.  How many times do we see requirements like the following: “The system shall be user friendly.”  “The system shall be robust.”  “The system shall perform better than the […]

Do we really need all these requirements?

Do we really need all these requirements? ArgonDigital - enterprise automation experts

We are often asked this question.  It is common to see cases where projects over specify their requirements for a product.  In one of our classes, we were told that one government organization had defined over 4,000 requirements for a single instrument!! Mandatory characteristics for any requirement is that it is Needed, Verifiable, and Attainable.  […]

Traceability – Multiple Parent Requirements – Update

Traceability – Multiple Parent Requirements – Update ArgonDigital - enterprise automation experts

We were asked by one of our clients the following question via our Ask the Experts page:  “Can a child requirement have more than one parent requirement?” More recently we received a similar question: “At our company, we take stakeholder “voices” and decompose them into one or many “translations”.  Can a “child” translation ever trace […]

Managing Traceability Links When Requirements are Deleted

Managing Traceability Links When Requirements are Deleted ArgonDigital - enterprise automation experts

We were recently asked the following question from one of our clients concerning managing traceability and allocation links: “When you delete a requirement should you break the link so that it doesn’t continue to show up in Traceability Reports?” I am very happy to hear from organizations that maintain traceability links for their  requirements and […]

Allocation and Traceability

Allocation and Traceability ArgonDigital - enterprise automation experts

We were recently asked the following question from one of our clients concerning the decomposition of requirements: “Do Requirements Traceability Matrices always trace down? One of the concepts we try to ensure is parent requirements at lower levels of design. So there we would be more interested in showing traceability up. But examples in textbooks […]

Requirements Decomposition

Requirements Decomposition ArgonDigital - enterprise automation experts

We were recently asked the following question from one of our clients concerning the decomposition of requirements: “I have used your company’s materials as reference for many years and recently had the pleasure of meeting Ivy Hooks in person at the recent INCOSE International Symposium. My question is this: Does your company have any numbers […]

How to Prioritize Requirements

How to Prioritize Requirements ArgonDigital - enterprise automation experts

This is a continuation of the previous blog:  Why You Should Prioritize Requirements 1. Assign priorities once you have a set of requirements for your system of interest. 2. Assign a relative importance to requirements. Keep it simple, like 1, 2, & 3 – Have rules for each category or “bucket” The rules must be […]