Just my two cents, I would start with UML models to document the functioning application and work backwards from there. Are you on hourly or flat bid? Doing the modelling correctly could take some time, and not everyone wants to pay for that level of documentation.
On 5/31/06, John Galt <[EMAIL PROTECTED]> wrote: > > Ok, > > So my initial task at the new job is to do a thorough analysis of an > existing application, and make suggestion for changes and improvements > both > small and large. > > Right now we need to establish some sort of documented baseline, so we > know > where we came from (Gov't work). Essentially a requirements document, > with > all the bad stuff added. > > Is this clear? > > Does anyone have a template like this?? > > I'm not sure how I on one hand make sure a requirement is mentioned, and > if > it has errors or needs optimization or whatever, it all gets recorded in > an > easy to read format. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:5:207858 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
