I'm not sure this is the proper forum for this question, so my apologies in advance if it indeed is not...
When constructing software in an object-oriented (or really any) fashion, one must implicitly or explicitly use a design process to structure their tasks; ie, vision, requirements gathering, use-case modeling etc...
I have been exposed to a number of design processes: the (Rational) Unified Process, Xtreme Programming, generic iterative development, the 'Waterfall' process, etc. While these methods may be tried and true, nearly all of the modern, recommended approaches require a team of programmers to feasibly use them.
I am looking for a proven software design process that can accommodate the programmer who is working alone day after day. It should be compatible with good OOA/D. Can anyone reccomend anything?
jared@eae.net -
When constructing software in an object-oriented (or really any) fashion, one must implicitly or explicitly use a design process to structure their tasks; ie, vision, requirements gathering, use-case modeling etc...
I have been exposed to a number of design processes: the (Rational) Unified Process, Xtreme Programming, generic iterative development, the 'Waterfall' process, etc. While these methods may be tried and true, nearly all of the modern, recommended approaches require a team of programmers to feasibly use them.
I am looking for a proven software design process that can accommodate the programmer who is working alone day after day. It should be compatible with good OOA/D. Can anyone reccomend anything?
jared@eae.net -