how to make a plan of how you implement a program?

[takashi]

Hi, I have a question. I am learning about how to use c++ language. I
have attempted to make my own programs, using the knowledge that I have,
but sometimes when I get stuck on writing a code, it took me a long time
to figure out what I should do. For instance, I was writing a program
which tells you all the prime numbers that are less than the number you
input on the console. It was a very short program, but it took me a
while to write the code successfully. Then I thought that the reason why
I got stuck was that I started writing the code without having any plan.
I just sat down in front of the computer, and started writing the code.
I heard that some people knows how to make a over-all plan of how he
wants to implement his code before he actually starts writing. I heard
about drawing a flowchart, then somebody said that a flowchart is not an
effective way for a large program.
Could anybody tell me how more experienced programer makes his plan
for writing his code, so that there is less chance that he gets stuck
while he's writing his code?
Thank you very much, and have a good day.

[Tom Mullan]

In article <INY5b.8876$kW. 2449@edtnps84>, takashi <tw******@telus .net>
writes

Hi, I have a question. I am learning about how to use c++ language. I
have attempted to make my own programs, using the knowledge that I
have, but sometimes when I get stuck on writing a code, it took me a
long time to figure out what I should do. For instance, I was writing a
program which tells you all the prime numbers that are less than the
number you input on the console. It was a very short program, but it
took me a while to write the code successfully. Then I thought that the
reason why I got stuck was that I started writing the code without
having any plan. I just sat down in front of the computer, and started
writing the code. I heard that some people knows how to make a over-all
plan of how he wants to implement his code before he actually starts
writing. I heard about drawing a flowchart, then somebody said that a
flowchart is not an effective way for a large program.
Could anybody tell me how more experienced programer makes his plan
for writing his code, so that there is less chance that he gets stuck
while he's writing his code?
Thank you very much, and have a good day.

You will need to learn UML which in turn will teach you object oriented
software development principles. There are loads of books on the subject
or you could take a course.

good luck
Tom
--
http://www.shacc.demon.co.uk

[Bob Jacobs]

"Tom Mullan" <to*@shacc.demo n.co.uk> wrote in message
news:cH******** ******@shacc.de mon.co.uk...

In article <INY5b.8876$kW. 2449@edtnps84>, takashi <tw******@telus .net>
writes

Hi, I have a question. I am learning about how to use c++ language. I
have attempted to make my own programs, using the knowledge that I
have, but sometimes when I get stuck on writing a code, it took me a
long time to figure out what I should do. For instance, I was writing a
program which tells you all the prime numbers that are less than the
number you input on the console. It was a very short program, but it
took me a while to write the code successfully. Then I thought that the
reason why I got stuck was that I started writing the code without
having any plan. I just sat down in front of the computer, and started
writing the code. I heard that some people knows how to make a over-all
plan of how he wants to implement his code before he actually starts
writing. I heard about drawing a flowchart, then somebody said that a
flowchart is not an effective way for a large program.
Could anybody tell me how more experienced programer makes his plan
for writing his code, so that there is less chance that he gets stuck
while he's writing his code?
Thank you very much, and have a good day.

You will need to learn UML

Gosh, how did we manage all these years, without UML? ;-)

[Chris Newton]

Bob Jacobs wrote...

"Tom Mullan" <to*@shacc.demo n.co.uk> wrote...

You will need to learn UML

Gosh, how did we manage all these years, without UML? ;-)

We drew class diagrams, sequence diagrams et al. using other notation
instead, and got on with it without invoking the Elder God Hype.

:o)

Chris

[Govindan]

"E. Robert Tisdale" <E.************ **@jpl.nasa.gov > wrote in message
news:3F******** ******@jpl.nasa .gov...

takashi wrote:

Could anybody tell me how more experienced programmer makes his plan for writing his code, so that there is less chance that he gets stuck while
he's writing his code?

1. Identify all of data objects in your problem.
2. Group the data objects of the same type together.
3. Implement the Abstract Data Type (ADT) for each group as a class.
An ADT specifies
a. all of the values that an object of a particular type can have and
b. all of the methods which can be applied to an object of that type.
4. Solve the problem by instantiating the objects and applying
the appropriate methods for objects of each type.

Some programmers start typing their code into the PC,
they first write some comments and then fill in the code thereafter.
They may refer to their previous working code or somebody's else's code
for useable design patterns or idioms to use in their solution.
They may even refer to some Algorithms text to get some helpful
datastructures and pseudocode
if the programming problem is a particularly hard one.

Using pencil and paper to draw some classes and attributes and jotting down
some tricky algorithms in short pseudocode
may help in school projects or assignments where the solutions may not be
readily available in any textbooks or journal articles