<[EMAIL PROTECTED]> wrote:
> Once you have gotten your requirements for a new application and the
> modeling/architecture process ensues, what tools do you use to link
> requirements to screens, processes, etc?
We don't keep a formal one-to-one record of requirements to fragments
of code but we use Borland's Together Control Center for much of our
application modeling. That lets us create Use Case diagrams and
Collaboration diagrams that have placeholders for requirement IDs. We
refine those into logical and physical Class diagrams and carry over
the requirement IDs. In the past, I've built some extensions to
Together that support Jim Conallen's Web Extensions for UML so that we
can model web pages and forms and links, again with requirement IDs
attached.
Like I say, we *can* do all of that. But we typically don't. We do try
to version control our specs tho', either manually using in-document
annotations or explicitly using CVS.
It's very, very hard to formalize the requirements / analysis / design
process but I will say that it's definitely very worthwhile. The more
you can front-load your process, the easier the rest of the process
becomes. Whilst I am not exactly a FLiP convert, I will say that it's
emphasis on the front-end of the lifecycle (wireframing, prototyping,
architecture and Fusedocs) means that the tail-end (coding, testing)
should go much more smoothly.
--
Sean A Corfield -- http://www.corfield.org/
Team Fusebox -- http://www.fusebox.org/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
