Do you sit around, draw something on a table napkin, and then off you
go (a little silly, but could be true)? I would think some of it would
have to do with how large the project is, how many developers are
involved, and so on. I also guess that while the application overview
may be planned, the actually programming may be organic. By that last
one I simply mean that a developer may not really know how to design
functionality x, so they develop something and then use trial and
error.
I would be interested in any links someone may have that shows what a
real lifetime development cycle entails, if anyone has any
recommendations.
Thank you.
In reality most people do at least some "prototype coding" before fully
defining the requirements - in many cases this is basically writing the
code first then writing the requirements to fit. This at least makes
it look like you defined some requirements.
Of course, some people just write the code and go with it without ever
doing anything formal like a requirement document. This is alot faster
but is likely to result in sloppy code full of bugs. You may spend
more time overall because you will go through more debugging and
re-releasing of the code.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=-88043838&z=17&l=0&m=h
"jm" <needin...@gmail.com> wrote in message
news:1163436769.1...@b28g2000cwb.googlegroups.com...
--
HTH,
Kevin Spencer
Microsoft MVP
Ministry of Software Development
http://unclechutney.blogspot.com
Any experience you can walk away from
is a good one.
"clintonG" <csgal...@REMOVETHISTEXTmetromilwaukee.com> wrote in message
news:%23fdM6O1...@TK2MSFTNGP02.phx.gbl...
There was a period in architectural history where the expression of needless
ornamentation on a building became questionable. Persons such as the Nazi
architect Mies Van der Rohe and the era of modernism brought this about.
Comparitively speaking, Agility foregoes the needless ornamentation of the
software development process. Again, comparitively speaking, software
development is undergoing its own period of modernism but be advised, it is
post-modernism that comes next!
Clear as mud? :-) Read, Read, Read...
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=-88043838&z=17&l=0&m=h
"Kevin Spencer" <sp...@uce.gov> wrote in message
news:eDfSqn%23BHH...@TK2MSFTNGP02.phx.gbl...