Software Development Methodologies

[TheCPUWizard]

I am curious if there is any interest in developing a serious thread regarding the various software development methodologies.

Hopefully this would discuss the pros/cons of each approach to software development (Extreme Programming, etc.).

The discussions would be largely in a language/platform independant fashion, although features of a given environment that help/hurt a given methodology would be appropriate.

[kasracer]

Sounds kind of dumb to me..... but whatever floats your boat

[TheCPUWizard]

Most professionals agree that coding per se takes only 20%-30% of time and money necessary to successfully design, develop and deploy an application, the remainder of the time is spend on other activities.

As more and more projects are being done by groups of people working independantly (think out-sourcing or even open-source) the "process" really does become more important than the line of code themselves.

My quess is that prople here on CodeGuru who make their living writing code would be interested, but those who just "play" probably would not think it applies to them.

But even if you are just part of a group of guys/girls writing a game together, these practices can make difference.

Dumb...NO!

Interesting to this audience....That is what I am trying to find out

[Andy Tacker]

well, that's pretty nice an idea. but as you already pointed out, there are people who just code, and there are people who design. for latter audience, this is quite an interesting issue.

but what's the point?

discuss it. dont poll it

[TheCPUWizard]

I specifically put this up as a poll. If the repsonse had been of a significant size (and postive) I would then begin to request the moderators to create a distinct forum.

There are a number of other boards that I use for design issues already [In fact I ask most of my questions there and provide most of my assistance here ].

Looks like one stop shopping is not in the future.

ps: Those who code without design are those who are doomed to fail.

[Deniz]

I agree with coding only taking %20-%30 of your time. The rest of my time is spent either outside having a smoke, or on one of my extended lunch breaks, or in the mens room, or having junk food, or just plain surfing the web.


jk


I think design is very important without it what would you know what do do?

I spend a lot of time in my head thinking up ways to improve, how to go about doing the new stuff, how to bring it all together, what else can we do etc ect... Mostly at odd times, when watching tv, while driving, when spending quality time with my fiance listening to her opinions. But thats all I do, I dont draw up diagrams, I dont create ERD's, flowcharts or any other of those wacky things you youngsters do.

But its for a reason, my app isnt required to move/manipulate data. If it did, then I wouldnt move a finger till the design was complete.

You asked for opinions, that was mine.

[Kheun]

Well... probably most of you have already known, I have been participating into some discussions related to software processes. I agree with TheCPUWizard that mostly we spent 20% - 30% coding. It may be a bit atonishing, but in an article I have read (can't remember where is it), it mentioned that effectively, programmer writes a line of good code everyday. This is because lot of time is needed on designing and evolving a good framework as well as debugging it.

Please bear with me for thinking out loud. IMHO, I don't think we should see ourselves as being only a passive coder. Ultimately, by some time in the future if nothing goes wrong, we will advanced and need to start thinking about design. This is because with a large project that uses a lousy framework is not likely to survive long due rapid requirement changes. Due to the restrictive limitation of the framework, how can we be competitive in todays aggressive market.

Beside design, we also need to be aware of the process of how we deliver our product. It is something that we practise so that successes are repeatable and at the same time, gives us an edge over our competitors. Without a clear understanding of the current process, how can we be able to do our work effciently? Also, it is very crucial that we need to spot and amend the process if there is something amiss. Even if we are very familiar with the process, we shouldn't be content at where we are, repeating the same process over and over again. This is because there is no way we can obtain different result by repeatly doing the same thing. This only means that we only staying at where we currently are while our competitors are always moving. In other words, we need to improve on our current process so that we can move together with our competitors, if not ahead.

BTW, if galathea is around, I am sure that she will be very interested in such topic. If I remember correctly, she has been trying to apply XP at work. It will be enlighteing if she can shared some of her insight.


My 0.2 cents.

[Joseph_R_Thomas]

i would love to learn from that thread... count me in..as audience

[hspc]

in fact i'm the only one who voted Somewhat Interested till now.
but if you're going to make the new forum for software development methodologies it can also handle topics like SW companies organization and solution architecture and frameworks like MSF (Microsoft Solution Framework).

[TheCPUWizard]

Deniz,

...or any other of those wacky things you youngsters do.

Oh wishing I qualified for that statement

[Been programming professionally since the mid-70's]

-------

HSPC,

I agree that those topics should be included.

[Kheun]

Originally posted by hspc
in fact i'm the only one who voted Somewhat Interested till now.
but if you're going to make the new forum for software development methodologies it can also handle topics like SW companies organization and solution architecture and frameworks like MSF (Microsoft Solution Framework).

Hmm... I think this forum is well suited such discussion.

Since the discussion is very wide, we probably like to create a list of topics so that we can start somewhere. Anyway, here comes my list... :P
1. Requirement capturing
2. XP
3. RUP
4. other Agile process
5. Metrices used.
6. Design stage
7. code review
8. team dynamics

[hspc]

Originally posted by Kheun
Hmm... I think this forum is well suited such discussion.

so let's invert the idea !!
why creating a new forum ? we can discuss design methodologies in the same forum

[TheCPUWizard]

I will start some sample threadt in that forum to get the ball rolling in the next few days....

[Kheun]

Great!

[Andy Tacker]

Originally posted by TheCPUWizard
I will start some sample threadt in that forum to get the ball rolling in the next few days....

Good idea. i will join in.