The Community for Technology Leaders
Green Image
Issue No. 01 - Jan. (1986 vol. 12)
ISSN: 0098-5589
pp: 172-181
Zavdi L. Lichtman , Department of Computer Research and Development, Armament Development Authority, P.O. Box 2250, Haifa, Israel
Program structure is designed, redesigned, and develops and changes during the development phase. This paper describes a mini methodology for generation and representation of design and program structures, and structural consistency checking between two successive designs or between a design and a program. The mini methodology is based on the following. 1) The tool: a special Program Design Language (PDL) which is equipped to extract the actual and complete structure information from design documents and programs, or partial structure information — when required. 2) The representation: two matrices, a Call Relationship Matrix (CRM) and a Global References Matrix (GRM), which completely represent the program structure. 3) The consistency criteria: clear definitions when the structures of two successive designs, or a design and a program, are consistent. The PDL extracts structure information, in a controlled way, from the top level program design, through layers of detailed designs, down to the source code itself. It generates an actual, complete, concise, and easily comparable structure representation. Structural consistency between levels can be checked, both at the development phase and at the operation and maintenance phase, ensuring continued structural consistency between the design(s) and the program. The structure representation can also be used for configuration management of the structure of designs and programs.
Customer relationship management, Computer languages, Aerospace electronics, Nickel, Data mining, Program processors, software tools, Consistency checking, Program Design Language (PDL), program structure, software development, software quality assurance

Z. L. Lichtman, "Generation and consistency checking of design and program structures," in IEEE Transactions on Software Engineering, vol. 12, no. , pp. 172-181, 1986.
92 ms
(Ver 3.3 (11022016))