1

I am not really sure how to correctly describe my question, so please forgive me if this is a duplicate. I am creating a flowchart for my program where I implement a method. Let's assume I call this method someMethod.

The C code could look something like this:

bool someMethod(int Foo, int Bar)
{
    foo += 5;
    bar -= 5;
    return (foo == bar);
}

This means that my flowchart will have a subroutine block where I call this function. But how do I correctly show the reader which integers I pass?

And when I create the flowchart of "someMethod", I face a similar problem: how do I correctly show the reader that Foo and Bar are passed parameters?

EDIT:

From what I have found so far, people have solved it by using the Start block as some sort of function declaration block, where they would replace Start with someMethod and place foo and bar on a new line. But from what I understand this isn't good practice since the start and end of every flowchart should be blocks containing respectively Start and Stop.

I also have seen people using an IO-block as the first non-start block where they would "read" the passed parameters but that just seems like a hack.

But unless there are better ideas, I suppose I'll have to go with that.

EDIT 2:

I am starting to wonder if this question is actually valid for this site. Is nobody using flowcharts anymore as a project preparation method?

  • the first thing to address is why are you creating a flow chart for this function? who is the audience? – jk. Jun 26 '13 at 12:29
  • I am hired to create a sort of "webscraper"program that can be used to automize some work in a PDM system. The products are stored in a server that the company can't access directly. They can only access their products through a (very ugly) html-based user interface. It's my job to show a (non-IT) manager how the program would work. And I also have to show it to an IT-manager with little experience in this field how I accomplish tasks such as "Search for PREFERENCE textbar" and stuff like that. So I have to walk a fine line between readable for non-programmers and still technically correct. – Jordy Jun 26 '13 at 12:44
  • It sounds like you are doing this at way to fine detail level for a technical audience let alone a non technical audience – jk. Jun 26 '13 at 13:04
  • Okay, I agree with you that not getting so detailed would save a whole lotta time and perhaps I might just fill in the blanks only when someone directly asks about it. But this probably won't be the last time I have to make a flowchart so the question is still valid I think? – Jordy Jun 26 '13 at 13:13
  • Have a look at this class diagram it might give you something simiar to what you are looking for. – Michael Riley - AKA Gunny Jun 26 '13 at 15:41
4

I've not drawn a flowchart in over 20 years. Thank goodness. By the time the chart is done the code could have been written, debugged, and deployed. Flowcharts were OK at a time when everything was card-punched and batch processed on mainframe computers that were doing priority production runs w/ your development work squeezed in between; computer time was very limited and very in demand. Turn-around time sometimes was days. Anyway, now a days the time and effort is simply a waste of time and effort.

Don't show a flowchart to a manager

It's too much detail and information. All trees, no forest.

Show Management Unified Modeling Language (UML) Diagrams

Here's an overview

There are 14 different diagrams but none are for line by line code detail. That's what the code is for! But you will find diagrams for different aspects and perspectives of your system.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.