Critical to this module is the review of several Connexions modules:
- m_18861 – Titled: Modularization and C++ Program Layout
- m_19136 – Titled: Pseudocode Examples for Functions
- m_18682 – Titled: Hierarchy or Structure Chart
You should review these materials before proceeding. If you are viewing this module on-line, links to these items are in the "Links" box to your right.
Concept of Modularization
The concept is everywhere present in the real world about us. Simply put it is to take a large complicated problem and to divide it into smaller manageable pieces. The hierarchy chart of any large organization (government unit, company, university, hospital, etc.) will show levels of people with job titles that indicate a different area of responsibility. Each person is a small piece of the overall workings of the organization. Each person can concentrate on their unique talent or task to make sure it works properly. Collectively they accomplish the goals of the organization.
Additionally, the concept has been around for a long time. A village of 300 years ago had farmers, tailors, butchers, blacksmiths, etc. Manufacturing is a prime example of not just work being modularized but the product itself is viewed in terms of modules or systems (Example of a automobile: engine, steering, brakes, etc.).
The world of computers, both hardware (equipment) and software (computer programs), also uses this modular concept. Thus, the concept migrates to a single computer program; allowing us to modularize the program into manageable tasks called functions.
Program Control Functions
Program Control functions normally do not communicate information to each other but use a common areafor variable storage. The rules for how data is communicated in and out of a function vary greatly by programming language, but the concept is the same. The data items passed (or communicated) are called parameters. Thus the wording: parameter passing. However, with program control functions we use the data communication option of no communication in – with no communication out. Our data variables and constants are placed in a common area available to all functions (called global scope).
The identifier names for program control functions usually imply a task to be accomplished, such as get-data, process-data or show-results. As you learn to write more complicated programs the number of lines of code will increase. Prudence dictates that it would be beneficial to divide the program into functions that perform unique tasks. The larger the program the more need for modularization or creating of program control functions.
Depending on the programming language, there is a formal way to:
define a function (it’s definition or the code it will execute))
call a function
declare a function (a prototype is a declaration to a complier)
One of the easier ways to understand program control function is to view an example. Even if you don’t know the C++ programming language, you can study the materials to help understand the modularization process.
Demonstration Program in C++
Creating a Folder or Sub-Folder for Source Code Files
Depending on your compiler/IDE, you should decide where to download and store source code files for processing. Prudence dictates that you create these folders as needed prior to downloading source code files. A suggested sub-folder for the Bloodshed Dev-C++ 5 compiler/IDE might be named:
If you have not done so, please create the folder(s) and/or sub-folder(s) as appropriate.
Download the Demo Program
Download and store the following file(s) to your storage device in the appropriate folder(s). You may need to right click on some of the links and select "Save Target As" in order to download some of the files. Following the methods of your compiler/IDE, compile and run the program(s). Study the source code file(s) in conjunction with other learning materials.
Download from Connexions: Demo_Program_Control_Functions_before_Compiler_Test.cpp
Download from Connexions: Demo_Program_Control_Functions_Pseudocode.txt
Download from Connexions: Demo_Program_Control_Functions_Hierarchy_Chart.jpg
Download from Connexions: Demo_Program_Control_Functions.cpp
Study the Materials Collectively to Understand Modularization
The four items represent a progression from no modularization to modularization:
- Program code before it is modularized
- Modularized pseudocode and a hierarchy chart for the program
- Program code that has been modularized
The simplicity of the program should not be considered during this review. It is obvious that the program does not need modularization. The example is to show or demonstrate how to modularize a program for program control.
- Common Area
- An area of the program where variables and constants are defined so that they are available to all functions.