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? I have been evaluating Adalon
as a tool to introduce into our development process for the purpose of
linking requirements to processes and screens but I assume other tools
and methods exist. In addition, how do you handle new requirements,
updating your models, etc? We currently have an ad-hoc approach and I am
looking into formalizing the process as this is an area where we waste a
lot of time... well not waste, but sure as hell are not as efficient as
we could be. For instance, we have many documents floating in numerous
folders that outline original requirements, new requirements, bugs,
processes, data dictionary, etc etc.... but to me, all these documents
floating around with next to no naming conventions is a waste. What
tools would you recommend looking into to help organize all the aspects
of the development process from requirements gathering and analysis to
ongoing maintenance and future development.
Thanks!
Mike
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
