1 / 47

Introduction

svetlana-velika
Download Presentation

Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Code Visual to Flowchart is a code maintain and understand software that is capable to rapidly analyze source code and to display in the flowchart window the graphical presentation of currently edited code. Code Visual to Flowchart is composed of a code editor and a flowchart Window .The flowchart engine is so fast that the flowchart can be constantly displayed as the alternative view of the currently edited source code. You can export flowchart of current edited code as Bitmap on any flowchart expand level you like ,Help you to create code flowchart document easily. Introduction

  2. Code Visual to Flowchart supports all primary program languages,such as VC ,C ,C++ ,Java ,JavaScript ,VB ,BASIC ,Qbasic ,ASP ,Vbscript ,Delphi ,Pascal ,PHP ,C#,VB.NET ,Perl... Code Visual to Flowchart is composed of a code editor and a flowChart window . • In the various implementations of flow charts, they are usually displayed in a way that all the source code is partitioned in fragments and displayed inside the drawn blocks. • Code Visual to Flowchart is based on different philosophy . The Flow Chart engine is so fast that the Flow Chart can be constantly displayed as the alternative view of the currently edited source code. • Code Visual to Flowchart does not display code in flow charts. Since flow charts can always be synchronized with Editor, it is enough to display the code structure from the source inside of the flow chart. The real code can always be edited in its natural way - inside of the Editor window.

  3. Another strategy with which Code Visual to Flowchart fights against enormously large flow charts is the concept of expand levels. The maximum depth of displaying the enclosed blocks can always be specified and easily changed.Code Visual to Flowchart features the quickest navigation of source code and it is also a good assistant when you are working on a program IDE .

  4. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Multiply Hours by Pay Rate. Store result in Gross Pay. Display Gross Pay What is a Flowchart? • A flowchart is a diagram that depicts(“yosor”) the “flow” of a program. • The figure shown here is a flowchart for the pay-calculating program in Chapter 1.

  5. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Rounded Rectangle Basic Flowchart Symbols • Notice there are three types of symbols in this flowchart: • rounded rectangles • parallelograms • a rectangle • Each symbol represents a different type of operation. Parallelogram Multiply Hours by Pay Rate. Store result in Gross Pay. Rectangle Rounded Rectangle

  6. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate START END Display Gross Pay Terminal Basic Flowchart Symbols • Terminals • represented by rounded rectangles • indicate a starting or ending point Multiply Hours by Pay Rate. Store result in Gross Pay. Terminal

  7. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display message “How many hours did you work?” Read Hours Display Gross Pay Basic Flowchart Symbols • Input/Output Operations • represented by parallelograms • indicate an input or output operation Input/Output Operation Multiply Hours by Pay Rate. Store result in Gross Pay.

  8. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Basic Flowchart Symbols • Processes • represented by rectangles • indicates a process such as a mathematical computation or variable assignment Multiply Hours by Pay Rate. Store result in Gross Pay. Process Multiply Hours by Pay Rate. Store result in Gross Pay.

  9. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart Stepping Through the Flowchart Output Operation How many hours did you work? Multiply Hours by Pay Rate. Store result in Gross Pay. Variable Contents: Hours: ? Pay Rate: ? Gross Pay: ?

  10. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart Stepping Through the Flowchart Input Operation (User types 40) How many hours did you work? 40 Multiply Hours by Pay Rate. Store result in Gross Pay. Variable Contents: Hours: 40 Pay Rate: ? Gross Pay: ?

  11. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart Stepping Through the Flowchart How much do you get paid per hour? Output Operation Multiply Hours by Pay Rate. Store result in Gross Pay. Variable Contents: Hours: 40 Pay Rate: ? Gross Pay: ?

  12. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart Stepping Through the Flowchart How much do you get paid per hour? 20 Input Operation (User types 20) Multiply Hours by Pay Rate. Store result in Gross Pay. Variable Contents: Hours: 40 Pay Rate: 20 Gross Pay: ?

  13. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart How much do you get paid per hour? Multiply Hours by Pay Rate. Store result in Gross Pay. Process: The product of 40 times 20 is stored in Gross Pay Variable Contents: Hours: 40 Pay Rate: 20 Gross Pay: 800

  14. START END Display message “How many hours did you work?” Display message “How much do you get paid per hour?” Read Hours Read Pay Rate Display Gross Pay Stepping Through the Flowchart Your gross pay is 800 Multiply Hours by Pay Rate. Store result in Gross Pay. Variable Contents: Hours: 40 Pay Rate: 20 Gross Pay: 800 Output Operation

  15. Four Flowchart Structures • Sequence • Decision • Repetition • Case

  16. Sequence Structure • a series of actions are performed in sequence • The pay-calculating example was a sequence flowchart.

  17. Decision Structure • One of two possible actions is taken, depending on a condition.

  18. NO YES Decision Structure • A new symbol, the diamond, indicates a yes/no question. If the answer to the question is yes, the flow follows one path. If the answer is no, the flow follows another path

  19. NO YES x < y? Process B Process A Decision Structure • In the flowchart segment below, the question “is x < y?” is asked. If the answer is no, then process A is performed. If the answer is yes, then process B is performed.

  20. NO YES x < y? Calculate a as x times 2. Calculate a as x plus y. Decision Structure • The flowchart segment below shows how a decision structure is expressed in C++ as an if/else statement. Flowchart C++ Code if (x < y) a = x * 2; else a = x + y;

  21. NO YES x < y? Calculate a as x times 2. Decision Structure • The flowchart segment below shows a decision structure with only one action to perform. It is expressed as an if statement in C++ code. Flowchart C++ Code if (x < y) a = x * 2;

  22. Repetition Structure • A repetition structure represents part of the program that repeats. This type of structure is commonly known as a loop.

  23. Repetition Structure • Notice the use of the diamond symbol. A loop tests a condition, and if the condition exists, it performs an action. Then it tests the condition again. If the condition still exists, the action is repeated. This continues until the condition no longer exists.

  24. YES x < y? Process A Repetition Structure • In the flowchart segment, the question “is x < y?” is asked. If the answer is yes, then Process A is performed. The question “is x < y?” is asked again. Process A is repeated as long as x is less than y. When x is no longer less than y, the repetition stops and the structure is exited.

  25. YES x < y? Add 1 to x Repetition Structure • The flowchart segment below shows a repetition structure expressed in C++ as a while loop. Flowchart C++ Code while (x < y) x++;

  26. YES x < y? Display x Controlling a Repetition Structure • The action performed by a repetition structure must eventually cause the loop to terminate. Otherwise, an infinite loop is created. • In this flowchart segment, x is never changed. Once the loop starts, it will never end. • QUESTION: How can thisflowchart be modified soit is no longer an infiniteloop?

  27. YES x < y? Display x Add 1 to x Controlling a Repetition Structure • ANSWER: By adding an action within the repetition that changes the value of x.

  28. YES x < y? Display x Add 1 to x A Pre-Test Repetition Structure • This type of structure is known as a pre-test repetition structure. The condition is tested BEFORE any actions are performed.

  29. YES x < y? Display x Add 1 to x A Pre-Test Repetition Structure • In a pre-test repetition structure, if the condition does not exist, the loop will never begin.

  30. x < y? Display x Add 1 to x YES A Post-Test Repetition Structure • This flowchart segment shows a post-testrepetition structure. • The condition is tested AFTER the actionsare performed. • A post-test repetition structure alwaysperforms its actions at least once.

  31. x < y? Display x Add 1 to x YES A Post-Test Repetition Structure • The flowchart segment below shows a post-test repetition structure expressed in C++ as a do-while loop. C++ Code do{ cout << x << endl; x++;} while (x < y); Flowchart

  32. Case Structure • One of several possible actions is taken, depending on the contents of a variable.

  33. CASEyears_employed 1 3 Other 2 bonus = 100 bonus = 400 bonus = 800 bonus = 200 Case Structure • The structure below indicates actions to perform depending on the value in years_employed.

  34. CASEyears_employed 1 3 Other 2 bonus = 100 bonus = 400 bonus = 800 bonus = 200 Case Structure If years_employed = 2, bonus is set to 200 If years_employed = 3, bonus is set to 400 If years_employed is any other value, bonus is set to 800 If years_employed = 1, bonus is set to 100

  35. YES x < y? Display x Add 1 to x Combining Structures • Structures are commonly combined to create more complex algorithms. • The flowchart segment below combines a decision structure with a sequence structure.

  36. NO YES x > min? NO YES Display “x is outside the limits.” x < max? Display “x is outside the limits.” Display “x is within limits.” Combining Structures • This flowchart segment shows two decision structures combined.

  37. features and benefits of this full-featured visual code editor • 1. Code Visual to Flowchart is a widely used automatic flow chart generator software that can reverse engineering a program, create programming flowchart from code, mostly used on flowcharting a progress • 2. Code Visual to Flowchart can generate Bmp, PNG, Visio, Word, Excel and PowerPoint flowcharts document, help programmers to document, visualize and understand source code. • 3. Code Visual to Flowchart works with the following programming languages: C, C++, VC++ (Visual C++ .NET), VB (Visual Basic), VBA, Qbasic (quickbasic), VBScript (VBS), ASP, Visual C# (C sharp), Visual Basic .NET (VB.NET), Visual J# .NET, VC++.NET, ASP.NET, Java, JSP, JavaScript (JScript), Delphi (Object Pascal), PowerBuilder (PowerScript), Peoplesoft SQR, PHP, Visual FoxPro, PL/SQL, T-SQL (Transact-sql) and Perl.and documenting source code.

  38. 4. Code Visual to Flowchart works with flowchart window to help programmers to edit complex source code easily. We can click on any part of the edited code ,and then the related part of flowchart will be highlighted. Flowcharts can be exported in MS Visio or BMP formats on any flowchart expand level. So developers can create code flowchart documents easily. • 5. Current edited code can directly be printed or be exported as RTF or HTML with colors and the format is just the same as its appearance in editor. That is real what you see is what you get. • 6. Code Visual to Flowchart has 2 kinds of flowcharts: The first one is displayed in a way that all the source code is partitioned in fragments and displayed inside the drawn blocks. The other one does not display code in flow chart. Since flow chart can always be synchronized with Editor, it is enough to display the code structure from the source inside of the flow chart. The real code can always be edited in its natural way - inside of the Editor window.

  39. Another strategy with which Code Visual to Flowchart fights against enormously large flow chart is the concept of expands levels. The maximum depth of displaying the enclosed blocks can always be specified and easily changed. Code Visual to Flowcharts features the quickest navigation of source code and it is also a good assistant when we are working on a programming IDE. • 7. Additional features of Code Visual to Flowchart include: Synchronization between flowchart and source code in editor; unlimited programming flow chart expand levels; Syntax highlighting for Source code; Support all Windows system, include Vista and so on.

  40. The Top 5 Reasons To Use Flowcharts(why we use flow chart ) Sometimes it's more effective to visualize something graphically that it is to describe it with words. That is the essence of what flowcharts do for you. Flowcharts explain a process clearly through symbols and text. Moreover, flowcharts give you the gist of the process flow in a single glance. The following are some of the more salient reasons to use flowcharts.

  41. Process Documentation / Training Materials • Another common use for flowcharts is to create process documentation. Although this reason overlaps with regulatory and quality management requirements (below), many non-regulated businesses use flowcharts for their documentation as well. These can range in form from high-level procedures to low-level, detailed work instructions. • You may think that this applies mainly to large organizations, but small companies can greatly benefit from flowcharting their processes as well. Small enterprises need to be nimble and organized. Standardizing their processes is a great way to achieve this.

  42. Workflow Management and Continuous Improvement • Workflows don't manage themselves. To ensure that you are meeting your customers' needs, you need to take control of your business processes. The first step to workflow management is to define the current state of your processes by creating an "As-Is Flowchart". That allows you to analyze your processes for waste and inefficiency. After you have identified areas for process improvement, you can then craft new flowcharts to document the leaner processes.

  43. Programming • Information technology played a big influence on the use and spread of flowcharts in the 20th century. While Dr. W. Edwards Deming was advocating their use in quality management, professionals in the data processing world were using them to flesh out their programming logic. Flowcharts were a mainstay of procedural programming, however, and with the advent of object oriented programming and various modeling tools, the use of flowcharts for programming is no longer as commonplace as it once was.

  44. Troubleshooting ” problem solve” Guides • Most of us have come across a troubleshooting flowchart at one time or another. These are usually in the form of Decision Trees that progressively narrow the range of possible solutions based on a series of criteria. The effectiveness of these types of flowcharts depends on how neatly(care) the range of problems and solutions can fit into a simple True/False diagnosis model. A well done troubleshooting flowcharts can cut the problem solving time greatly

  45. Regulatory and Quality Management Requirements • Your business processes may be subject to regulatory requirements such as Sarbanes-Oxley (SOX), which requires that your accounting procedures be clearly defined and documented. An easy way to do this is to create accounting flowcharts for all your accounting processes.

  46. Notation :- The “Code Visual to Flowchart” is Upper case tools (support analysis and design phases) So its process analysis tools

  47. End

More Related