Generation and consistency checking of design and program structures

The author describes a mini methodology for generation and representation of design and program structures and for structural consistency checking between two successive designs or between a design and a program. This methodology comprises a tool (Program Design Language), a representation, and cons...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering Vol. SE-12; no. 1; pp. 172 - 181
Main Author: Lichtman, Z. L.
Format: Journal Article
Language:English
Published: New York, NY IEEE 01.01.1986
Institute of Electrical and Electronics Engineers
IEEE Computer Society
Subjects:
Aerospace electronics
Algorithms
Applied sciences
Computer languages
Computer science; control theory; systems
Consistency checking
Customer relationship management
Data mining
Design
Development
Exact sciences and technology
Nickel
Program Design Language (PDL)
Program processors
program structure
Quality control
Reliability
Software
software development
Software engineering
software quality assurance
software tools
Structure
Software tool
Software development
Module
Large scale system
ISSN:0098-5589, 1939-3520
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The author describes a mini methodology for generation and representation of design and program structures and for structural consistency checking between two successive designs or between a design and a program. This methodology comprises a tool (Program Design Language), a representation, and consistency criteria. The Program Design Language (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.
Bibliography:ObjectType-Article-1
SourceType-Scholarly Journals-1
content type line 14
ObjectType-Article-2
ObjectType-Feature-1
content type line 23
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.1986.6312930