Structure Charts in Function Oriented Design

For a function-oriented design, the design can be represented graphically by structure charts. The structure of a program is made up of the modules of that program together with the modules of that program together with the interconnections between modules. The structure chart of a program is a graphic representation of its structure.

1. In a structure chart a module is represented by a box with the module name written in the box.
2. In general, procedural information is not represented in a structure chart, and the focus is on representing the hierarchy of modules.
3. However, there are situations where the designer may wish to communicate certain procedural information explicitly, like major loop and decisions.
4. Such information can also be represented in a structure chart.
5. Modules in a system can be categorized into few classes as below:
6. Input module: There are some modules that obtain information from their subordinates and then pass it to their superordinate.
7. Output module: Module which take information from their superordinate and pass it on to its subordinates.
8. Transform module: Modules that exist solely for the sake of transforming data into some other form.
9. Coordinate module: Modules whose primary concern is managing the flow of data to and from different subordinates.
10. A structure chart is a nice representation for a design that uses functional abstraction.

The design process for software systems often has two levels. At the first level, the focus is on deciding which modules are needed for the system based on SRS (Software Requirement Specification) and how the modules should be interconnected.

Function Oriented Design is an approach to software design where the design is decomposed into a set of interacting units where each unit has a clearly defined function.