Re: Documenting my project
Mohitz wrote:
[..] Ya, may be i am following the wrong approach. It
should have
been documented first. But i didnt really have much time. I had to
complete a huge project
in 2 months time.
"Huge"? In 2 montsh time? How "huge" is it, really? According to
[now somewhat obsolete] IBM's research, a programmer can produce about
10 lines of debugged code a day, on average, if you take the project
as a whole, from the inception to the release. That makes your "huge"
project about 400 lines of code. OK, even if we bump the programmer
productivity 10 times, you still only have about 4000 lines of code in
the project you can do in two months. "Huge"? I doubt it.
So, i couldn't think much about the architecture and
documentation. I just
did it the way it occured to me.
Programming "as it occurs" is a VERY BAD IDEA(tm). Once you learn
that (and learn the ways to avoid doing that), you'll progress from
a mere coder to a software engineer and beyond.
Is there a software development standard approach that most people
follow?
Ask in 'comp.software-eng'.
If yes, where can i find more information?
In good books. See "Code Complete", "Mythical Man-month", and so on.
V
--
Please remove capital 'A's when replying by e-mail
I do not respond to top-posted replies, please don't ask