RE: [AM] Why Traceability?

> > How do people satisfy CMM's need for Bidirectional 
> > Traceability without being crushed by documents or
> > distracted by tools?

> By reducing the number and depth of formal software artifacts 
> that are not code, to 0 if at all possible.  
>  
> For example, if all our requirements were formalized as 
> executable acceptance tests and our formal design was the 
> code itself, then bidirectional traceability could be 
> provided by just running code analysis tools.

I'd have a difficult time translating all of the requirements I receive into
executable tests. I find that probably 80-90% could be pretty easily
expressed as tests but the rest would take quite an effort to map over. Do
you also have this problem? How do you handle it?

For more information about AM, visit the Agile Modeling Home Page at www.agilemodeling.com
--^----------------------------------------------------------------
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrKDA.bWnbtk.Z2NtYS1h
Or send an email to: [email protected]

For Topica's complete suite of email marketing solutions visit:
http://www.topica.com/?p=TEXFOOTER
--^----------------------------------------------------------------