RE: [AM] Why Traceability?

 I do not think traceability will guarantee that the impact of a change will be gauged sufficiently. I believe it can only be done by looking at the bigger picture - high level use cases.

Sure there are times when traceability has a role to play. These would be enormous projects with very big teams. Most software development does not happen that way.

> -----Original Message-----
> From: McGovern, Patrick J [mailto:[email protected]]
> Sent: 16 March 2004 14:14
> To: [email protected]
> Subject: RE: [AM] Why Traceability?
> 
> 
> IME traceability offers an understanding of impact of change 
> and allows
> you to actually somewhat measure that change.  
> 
> If I change this use case I will also have to review these classes and
> those classes being changed will affect this component and if that
> component changes I have to rerun these tests to ensure that 
> everything
> "still" works correctly...
> 
> Is that too simplistic an answer? That seems to me to be the 
> real value.
> Of course you can go in the other direction too...this 
> machine went down
> so that service is no longer available...blah blah...
> 
> -pjm-
> -----Original Message-----
> From: Tina Erwee [mailto:[email protected]] 
> Sent: Tuesday, March 16, 2004 7:04 AM
> To: [email protected]
> Subject: RE: [AM] Why Traceability?
> 
> Hi
> 
> I think the only real stick traceability ever gave anyone, 
> was the stick
> to hit the client over the head with: "You can't have this, you dirty
> little client. You did not ask for this (2 years ago)!"
> 
> Oh, of course traceability generates work. Keeping your 
> requirements and
> models in sync (explicit traceability) can be so much work 
> that you will
> need an extra resource just to manage the docs, unless you use a tool
> (that cost more than the resource)!
> 
> That's about it!
> Tina
> 
> > -----Original Message-----
> > From: Paul Oldfield [mailto:[email protected]]
> > Sent: 16 March 2004 13:34
> > To: INTERNET:[email protected]
> > Subject: [AM] Why Traceability?
> > 
> > 
> > Hi, all.
> > 
> > There has been a thread over several agile forums in the
> > last 10 days or so about Traceability.
> > 
> > There seemed to be some consensus reached that 
> > traceability is a solution to a problem, one that may no
> > longer hold true (as in no longer the best solution) in an 
> > agile environment.
> > 
> > However, a topic that never seemed to reach consensus,
> > or even be given a satisfactory answer, IMHO, was the
> > question of what problem or problems traceability was
> > trying to solve.
> > 
> > Given the apparent number of greybeards on this forum,
> > (younger folk can also respond, please?) can anyone
> > give an opinion as to why traceability is wanted - what does
> > it give us?
> > 
> > 
> > Paul Oldfield
> > www.aptprocess.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
> 
> 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
--^----------------------------------------------------------------