Skip Navigation

The Computer Journal 1990 33(2):126-132; doi:10.1093/comjnl/33.2.126
© 1990 by British Computer Society
This Article
Right arrow Full Text (PDF)
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Similar articles in ISI Web of Science
Right arrow Alert me to new issues of the journal
Right arrow Add to My Personal Archive
Right arrow Download to citation manager
Right arrow Search for citing articles in:
ISI Web of Science (1)
Right arrowRequest Permissions
Google Scholar
Right arrow Articles by Dromey, R. G.
Right arrow Articles by Chorvat, T. A.
Right arrow Search for Related Content
Social Bookmarking
 Add to CiteULike   Add to Connotea   Add to Del.icio.us  
What's this?

Structure Clashes – An Alternative to Program Inversion

R. G. Dromey * and T. A. Chorvat

Programming Methodology Research Group, Computing and Information Technology, Griffith University, Nathan, Brisbane, 4111, Australia

A method for handling boundary structure clashes is presented. It provides a simple alternative to Jackson's program inversion technique. It is a constructive approach based on the use of prototypes. Development begins by solving the corresponding simpler problem that has no structure clashes. This solution is then used to guide the solution of the original problem. Programs constructed in this way preserve the correspondence between the program control structure and the data structure. They should therefore be easier to maintain than their counterparts developed using Jackson's program inversion method.


Received May 1988. revised August 1988.

* To whom correspondence should be addressed.

§ Programming Methodology Research Group, Computing and Information Technology, Griffith University, Nathan, Brisbane, 4111, Australia


Add to CiteULike CiteULike   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us    What's this?




Disclaimer:
Please note that abstracts for content published before 1996 were created through digital scanning and may therefore not exactly replicate the text of the original print issues. All efforts have been made to ensure accuracy, but the Publisher will not be held responsible for any remaining inaccuracies. If you require any further clarification, please contact our Customer Services Department.