RE: [AM] Why Traceability?

> First, let me correct a possible misconception.  Agile 
> approaches are not absolutely anti-tool.  The agilists are 
> most enthusiastic about use of appropriate tools, and are 
> pretty prolific at the creation of appropriate tools (as all 
> Unix programmers used to be, way back... but don't let me get 
> distracted!).  Agilists don't like big, unwieldy, expensive 
> tools that require big, unwieldy, expensive process to go along with.

Oops, I should have been clearer on that. I'm currently consulting to a
company that is working towards CMM level 2 using a process loosely based on
RUP. They want to be able to trace their requirements from request to
running software and gradually add traceability to their old requirement
documents. They've already got a lot of documents but no traceability so I'm
writing a tool (an appropriate tool!) to extract traceability information
and generate a traceability matrix.

They are awfully attached to their documentation but perhaps I can squeeze
in a little agility by using unobtrusive tools to help them manage their
requirements. My attempts to get them interested in automated unit testing
have so far failed...

> Other tools can be used for testing the user interface - 
> there's a yahoo forum specifically on the topic of doing 
> test-first development for user interfaces, if you need help...
> http://groups.yahoo.com/group/TestFirstUserInterfaces

Thanks for this pointer, I've been looking for something like this for quite
a while.

John Manuel

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