Doug, we are using the traditional meaning of the waterfall model, which implies that when a project employs the waterfall approach it is difficult, or impossible, to backtrack or make corrections to the existing system. Hydro4GE resources assist in system evolution. We assume a system is never complete, never perfect and Hydro4GE assists the developer in refining the system to meet the needs of the firm. Hydro4GE is being developed in an Agile environment by software engineers who strongly believe in the Agile Manifesto, see http://www.agilemanifesto.org/.
If you’re going to ‘do’ spiral, you might as well mention Agile – and at least hook that group. I’ve skimmed the material on the website, and can’t quite figure out why/how Hydro4age is any more ’spiral’ than ‘waterfall’. It looks like you may compress the development cycle, but if you ‘hydro4ge’ the whole application in one step, I’d argue you’ve got a waterfall.
Doug, we are using the traditional meaning of the waterfall model, which implies that when a project employs the waterfall approach it is difficult, or impossible, to backtrack or make corrections to the existing system. Hydro4GE resources assist in system evolution. We assume a system is never complete, never perfect and Hydro4GE assists the developer in refining the system to meet the needs of the firm. Hydro4GE is being developed in an Agile environment by software engineers who strongly believe in the Agile Manifesto, see http://www.agilemanifesto.org/.
Comment by Jack B — September 4, 2008 @ 3:12 pm
If you’re going to ‘do’ spiral, you might as well mention Agile – and at least hook that group. I’ve skimmed the material on the website, and can’t quite figure out why/how Hydro4age is any more ’spiral’ than ‘waterfall’. It looks like you may compress the development cycle, but if you ‘hydro4ge’ the whole application in one step, I’d argue you’ve got a waterfall.
Comment by doug makofka — April 4, 2008 @ 9:12 am