Re:Is there a software-engineering methodology for functiona...
by flatline on Sunday February 06, 2011 @12:23PM
(#2185981)
While I love doing bottom-up programming for my own projects or with a small team, I think there is something to be said for many elements of the top-down approach. It is often wasteful and overbearing in its process, but when engineering large systems, having a general consensus on modelling (UML being the most common form) and code structure does have its payoffs. Not all team members are equals in their passion for writing code, their interest in the current project, or their general competency. If you have to write code for the lowest common denominator - and I don't mean this in any deprecatory sense - clarity and consistency are tangible benefits.
A clear methodology also provides both a shield to the developers and a benefit for those involved in the project but not directly working on the code.
Instead of looking for "proven" programming methodologies, one should develop an aptitude and taste for how to write good programs. This can only come from "doing" it and seeing how other people do it.
"Bottom up programming" is not a methodology. It's not a step-by-step process, nor is it a set of strict rules and guidelines. It's just a general idea; and it's not something you implement, it's a mindset you absorb and imitate.
By the way, UML & co. are horrible abominations and you should steer away from them. If you want to sketch something out on a piece of paper, just use your common sense: draw boxes, circles, arrows, trees, or whatever you like.