Action Diagram



Take F on Create Object in row 2. Below is the action diagram of create object.

Action diagram user exit points                  
- Processing before DBF write                    
    - USER: Processing before DBF update         
    - USER: Processing if DBF already exists     
- Processing after DBF write                     
    - USER: Processing if DBF update error       
    - USER: Processing after DBF update          

An action diagram contains the processing steps that make up a function. Each action diagram consists of a list of actions, where each action may be either a call to another function or one of a number of low level built-in functions; for example, *ADD.

Following are brief descriptions of each of the three constructs and the way in which each is shown on the action diagram. Refer to the diagram following these descriptions as you read.

■ Sequential construct—A sequential construct is the simplest construct. It is a list of actions or other constructs to be executed in the order in which they appear in the action diagram. It is shown on the action diagram enclosed by a bracket of dots (:).

■ Conditional construct—A conditional construct specifies a condition and a series of actions to be taken if the condition is true. It is equivalent to an IF THEN ELSE logic statement or a SELECT set. This construct appears on the action diagram between CASE and ENDCASE statements and is enclosed by a bracket of broken vertical bars (|). You can specify several mutually exclusive conditions in a single conditional construct.

■ Iterative construct—An iterative construct includes a list of actions that are to be executed while an initial condition is true. It is equivalent to a DO WHILE logic statement. An iterative construct appears on the action diagram between REPEAT WHILE and ENDWHILE statements. It is indented and enclosed by a bracket of solid vertical bars (|). The controlling condition is specified at the beginning of the bracket.


Top-Down Application Building

If you are developing a new application, a top-down approach is a good way to design the functions for your application. This approach, which assumes that your data model and access paths are defined, includes

· identifying the functions to be called from points in processing

· working top-down to define functions and function parameters as needed

· specifying top level constructs and the logic flow of user points

· filling in user point detail                             

Post Comments