RE: [AM] Why Traceability? Lean Traceability?

Is it likely, though, that by looking at requirements documentation or at
high-level design models you would be able to spot when a change in one
system could cause errors in other dependant systems? I suspect
comprehensive automated regression tests for all the systems involved would
be of more value.

Jason Gorman
http://www.objectmonkey.com

> -----Original Message-----
> From: Steven Gordon [mailto:[email protected]] 
> Sent: 17 March 2004 13:55
> To: [email protected]
> Subject: RE: [AM] Why Traceability? Lean Traceability?
> 
> The troublesome thing about the ripple effect, of course, is 
> when a change in one system breaks another system, which in 
> turn breaks other systems.  In the worst case for 
> enterprise-wide impact analysis, traceability must be in 
> place for each system at a granularity that allows us to 
> trace through system interfaces.  The prime example was Y2K.
> 
>  
> 
> Steven Gordon
> 
> 
> 
> 	-----Original Message----- 
> 
> 	From: Paul Oldfield [mailto:[email protected]] 
> 
> 	Sent: Wed 3/17/2004 3:25 AM 
> 
> 	To: INTERNET:[email protected] 
> 
> 	Cc: 
> 
> 	Subject: RE: [AM] Why Traceability? Lean Traceability?
> 
> 	
> 
> 	
> 
> 
> 
> 	[CLIP]
> 
> 	One topic that other posters made more of was the need to know
> 
> 	what needed to be re-tested when something changed.  If
> 
> 	we really need to know everything that uses something we
> 
> 	change, then traceability is necessary.  Of course, this need
> 
> 	is an indication that we have failed to control the 
> ripple effect;
> 
> 	also that our testing is still so expensive that we 
> need to cut out
> 
> 	the tests that cannot have changed.
> 
> 	
> 
> 	(This should also address your comments on my "rant mode"
> 
> 	in another posting.  Anyone experiencing 'ripple effect' in the
> 
> 	last 10 years is either developing incompetently, or is
> 
> 	working with legacy code and has failed to install decoupling
> 
> 	mechanisms.  This latter may not be down to incompetence,
> 
> 	but I'd be suspicious...)
> 
> 	
> 
> 	
> 
> 	Paul Oldfield
> 
> 	
> 
> 	++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 	www.aptprocess.com
> 
> 	
> 
> 	any opinions expressed herein are not necessarily those of
> 
> 	Mentors of Cally or the Appropriate Process Movement
> 
> 	++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 	
> 
> 	For more information about AM, visit the Agile Modeling 
> Home Page at www.agilemodeling.com
> 
> 	
> 
> 	
> 
> 
> 
> 
> For more information about AM, visit the Agile Modeling Home 
> Page at www.agilemodeling.com
> 
> 

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
--^----------------------------------------------------------------