Breaking News
Design How-To

Requirements Traceability design how-to

8/6/2012 03:01 PM EDT
9 comments
NO RATINGS
More Related Links
View Comments: Newest First | Oldest First | Threaded View
ShanBhattacharya
User Rank
Rookie
re: Requirements Traceability design how-to
ShanBhattacharya   9/13/2012 1:48:03 PM
NO RATINGS
Good point Prabhakar. Requirments illicitation, authoring, and validation can't be automated in the classic sense and neither can traceability. Tools don't know anything about the context of the product so how can it make any decisions. They can have visually compelling decomposition and linking layouts that make understanding and enforcing spec tree disciple much easier. The can generate impact analysis and traceability reports. They can import/export in/out content from different sources (design, test, modeling tools, etc)to unify the RTM, and they can automatically highlight suspect links for easier "cleanup". Along with managing baselines, versioning, report generation etc. I find all these benefits make searching for your favorite tools and learning it worthwhile.

ShanBhattacharya
User Rank
Rookie
re: Requirements Traceability design how-to
ShanBhattacharya   9/13/2012 1:40:32 PM
NO RATINGS
Lots of good points here. As EREBUS mentioned there is no replacement for diligent and knowledgeable requirements engineers but good traceability tools can made issues much easier to spot. Also the excel based approach that antedeluvian mentioned is also very pragmatic but when you scale in number of requirements documents, number of users, need verfication history etc it can fall apart. Usually Excel based team will have VB gurus who can stretch excel to its limits BUT when they leave .... that's often when we get a phone call.

I_B_GREEN
User Rank
Rookie
re: Requirements Traceability design how-to
I_B_GREEN   8/21/2012 5:55:51 PM
NO RATINGS
I think it depends on the size and skill and depth of the team of engineers. If it is a small well oiled machine then a excell based approuch is ok. or do the software team sit in another area firewalled from hardware team and the team is two digits or bigger then more formal requirements tracking has value.

StephanWeber
User Rank
Rookie
re: Requirements Traceability design how-to
StephanWeber   8/8/2012 7:59:57 AM
NO RATINGS
Hi, I wonder if there are also public, free RTM/bug-tracker/project-planing tools? As calendar I use Google and can share it with everybody if I like. Is there something similar for these slightly advanced things?

StephanWeber
User Rank
Rookie
re: Requirements Traceability design how-to
StephanWeber   8/8/2012 7:56:58 AM
NO RATINGS
Diligence is the 1st step, but at some point it can happen also due to bad software, that diligence drops in a team more and more. I think if the tools are fine this will not happen. At Cadence our issue tracking systems works since many many years and people like it (in opposite to some other in-house software of course).

StephanWeber
User Rank
Rookie
re: Requirements Traceability design how-to
StephanWeber   8/8/2012 7:51:45 AM
NO RATINGS
This is what I have often observed: At some point engineers re-invent such tracking software with Excel, but this is often a bad workaround. You should have web-support, history tracking, permissions, etc.

prabhakar_deosthali
User Rank
CEO
re: Requirements Traceability design how-to
prabhakar_deosthali   8/8/2012 4:32:00 AM
NO RATINGS
I am doubtful whether the tools exist to automatically break up the high level requirement specs ( approved by the client) into module level requirements for software coding. Thgis process is obviously manual and its verification hence will also be manual. What a tool can do is only flag any modifications later on to any of the specs at any level. Based upon the dependencies defined manually again,one can have trace ability of the changes happening .

antedeluvian
User Rank
Blogger
re: Requirements Traceability design how-to
antedeluvian   8/7/2012 4:10:29 PM
NO RATINGS
I realise that this article refers to some sophisticated tools for a traceabilty matrix. However, for what it is worth, I developed a simple method in Excel- http://electronicdesign.com/article/embedded/use-excel-to-develop-a-traceability-matrix9584

EREBUS0
User Rank
Rookie
re: Requirements Traceability design how-to
EREBUS0   8/6/2012 8:20:58 PM
NO RATINGS
Requirements traceability is a matter of diligence, not tools. Tools can make it easier, though I have seen some that make it impossible. First you need to define the requirement so that it can be tested. Otherwise it is just a goal. Second you need to make sure that your understanding of the requirement is the same as the customer. Validate before you trace. Third, you need to continually assess the relationships between the requirements. A change elsewhere could impact different components. You need to include dependencies with your traceability. Art requires inspiration. Science relies on good process implemented by diligent people. Just a thought.

Flash Poll
Radio
LATEST ARCHIVED BROADCAST
EE Times editor Junko Yoshida grills two executives --Rick Walker, senior product marketing manager for IoT and home automation for CSR, and Jim Reich, CTO and co-founder at Palatehome.
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed