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 - http://webfx.eae.net

No - I only can recommend searching for helpers, perhaps a friend - and discipline.

It's really difficult to change the perspective, and to try aggressively to find an error, if it's your own code.

And to plan and balance ideas, without talking to someone, is a very hard thing too - it's so much easier, if you can talk to somebody about your ideas - even if this person gives no hints, it's easier to find out which idea is poor, if you explain it to a real person.

One of the better posts I've never read, stefanwagner.

You conveyed in three perfectly exact lines 15 years of my thoughts.

buho (A)stonished.

Thank you for the advice; it certainly does make sense. I do, however, still look forward to finding a proven design method that a standalone programmer can use...

Thanks again,
Jared N

jared@eae.net - http://webfx.eae.net

From a former singleton development staff: you just have to pick a strategy and play all the parts yourself.  I echo the sentiment that it certainly isn't easy, but it is sometimes necessary.

You may want to check into the Iconix methodology.

Its a very simplified UML based meth that only utilizes a handful of diagrams: use cases, sequence/colalboration, robustness, and class/static.

I've used it before in situations where it was pretty much just myself, and found that it was very helpful. Its a very basic meth, but one that works.

D'Arcy

jfrost10 - iconix sounds pretty interesting.  Do you have any more links or anything?  All I could find was where they want to sell you something.

Cheers
-d

I was introduced to Iconix from a book by Doug Rosenberg called Use Case Driven Object Modelling with UML.

Here's the link for it at Amazon:
http://www.amazon.com/exec/obidos/tg/detail/-/0201432897/qid=1079485045/sr=1-2/ref=sr_1_2/102-4722049-9364967?v=glance&s=books

The entire book uses the ICONIX methodology, and is what I used to base my single-developer meth off of.

Sorry, I know its not a free site or anything, but at least you can browse it at the bookstore first and see if its of interest.
:)

D'Arcy

I found that sticking to the last methodoloy used is best.ie it is still fresh and saves the angst of researching an other method. The trick with documentation is to stop once ones thoughts have reached a conclussion, then start implementing.

Thanks again guys. I will certainly be looking further into this 'Iconix' solution.

jared@eae.net - http://webfx.eae.net

To jfrost10 (Programmer)

I want to use the Iconix methodology, but I don't have the book, do you know what kind of life cycle use. Because my proyect use waterfall and I need to use a methodology that acept this life cycle.

Lucila

You can go to the iconix website and see a diagram showing the overview of the process at this link:

http://www.iconixsw.com/UMLBook.html

The process as its taught starts with GUI prototypes, which generate use cases. These use cases go through a refining phase using robustness diagrams. Once refined, sequence diagrams can be completed, as well as updating static diagrams (class/domain).

Check out the site, and let me know if you have any other questions about it.

D