You're definitely right about fusedocs helping a larger team and larger projects. I've found them worthwhile in both large and small projects.
The great thing about fusedocs is the system they create for development. Once you're done with a prototype: 1) take each page in the prototype and fusedoc 2) test the fusedocs, compare in/out variables 3) define the database from the fusedocs. 3a) redefine any fusedocs that are impossible because of db constraints 4) write the code for each fusedoc 5) test each fuse This seems like a lot of steps, but they go REALLY quick. 1) takes 10-20 minutes for each fuse, depending on your experience with fusedocs 2) takes a couple hours, if you've got a good testing tool 3) This goes MUCH faster when you know exactly what fields you need. You simply need to normalize the data 3a) This sometimes opens up BIG holes in your design, big holes often mean lots of time 4) 15-30 minutes for each fuse, some take MUCH longer, others take no time at all 5) This will go quick with Jeff's new Fusedoc harness tool (which isn't out) Look at the huge amount of testing that goes on in this process. It's so systematic and elegant. I just wish Windows was written this way so I'd stop seeing so many damn blue screens. While Fusedocs help with big teams and big projects. The size of the team and the size of the project doesn't matter. The size of the team and project simply change how long the application will take to build. Fusedocs offer a good process to work around. Steve Nelson ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
