Hi,
If your working by yourself I'd be looking at a quicker development methodology such as the Agile Methodology. It allows for quicker releases with adequate documentation.
RUP is excellent but it is very verbose and you can get lost in the amount of documentation, design and models it produces. I would suggest that if you are creating large scale systems on an organisation wide scale then RUP is definitely a good way to go.
However, if you are a lone developer, developing smaller scale applications then I'd be using a cut down version of RUP (sort of a what you decide to put in yourself) or the Agile Methodology is a very good alternative. Both are iterative methodologies.
http://agilemethodology.or
http://en.wikipedia.org/wi
Agile Documentation
http://www.agilemodeling.c
http://www.pragmaticsw.com
http://www.agilemodeling.c
Agile and UML
http://www.hostfrontier.co
UML is an important tool in the development process but I would not get to cought up in it unless you have time to learn it properly. Just a few of the key models would surfice, such as Use Case diagrams, Class diagrams and (maybe Sequence but not essential). Lots of people seem to think it's easy to create a set of models but in reality there is a bit of a learning curve to UML if you have not used it before. I use UML but I found it hard to get used to until I got a good book and had the time to discover it properly. Even then I would only use it for certain projects where I thought it was required.
No matter which methodology you choose you will need time to learn and understand it first!
Hope this helps,
Darren
Main Topics
Browse All Topics
by: marklorenzPosted on 2009-09-16 at 09:36:33ID: 25347478
There are a number of choices. An all-inclusive methodology is RUP (http://en.wikipedia.org/w
Certainly, you need to use UML (http://en.wikipedia.org/w
There are some time-proven design patterns to follow (http://www.dofactory.com/
HTH, Mark