MODEL(ID:4112/mod009)


for Module Description Language

Noah S. Prywes, Moore School Univ. of Pennsylvania 1976



Related languages
MODEL => MODEL II   Evolution of

References:
  • Prywes, N. S., "Automatic Generation of Computer Programs", University of Pennsylvania Moore School Report 76-02, 1976 view details
  • Prywes, Noah S. "Automatic generation of computer programs" pp679-690 view details Abstract: This is an introduction and summary of research on Automatic Program Generation conducted at the Moore School, University of Pennsylvania. This research culminated in development of a Module Description Language (MODEL) designed for use by management, business, or accounting specialists who are not required to have computer training. MODEL statements describe input, output, and various formulas associated with system specification. No processing or sequencing information is required from the user. A MODEL Processor analyzes the specifications and interacts with the user in resolving inconsistencies, ambiguities, and incompleteness. A program for performing the required functions is then generated based on the "complete" specification.
          in [AFIPS] Proceedings of the 1977 AFIPS National Computer Conference Dallas, Texas, June 13-16, 1977 view details
  • Ruth, Gregory R. "Automatic programming: Automating the software system development process", Proceedings of the 1977 annual conference, p.174-180, January 1977 view details Extract: Application Specification Media and Aids
    Application Specification Media and Aids
    The direction that work in the DPS-type based approach has taken is toward making it easy for the user to describe his application. Simple and concise descriptive media for describing the user's processing requirements and the data his application uses and generates have been developed. The ISDOS APS uses the ADS, SSL and PSL languages, all of which involve RPGlike forms to be filled out by the user. Protosystem I makes use of HIBOL, an English-like statement language (like COBOL, but at a higher level of abstraction).
    The power and simplicity of these languages is most easily Illustrated by a short HIBOL fragment. If PAY, HOURS_WORIPAY IS HOURS_WORKED * RATE
    indicates that for each employee for which there is a record in the HOURS_WORKED file, the PAY file will have a corresponding record with an associated value obtained by multiplying the number of hours the employee worked by his hourly rate. The iteration through the files involved, the file i/O, record generation, EOF checking, and so forth, which would have to be explicit in a PL/I program equivalent to this statement, are all implicit here.
    The development of simple descriptional facilities for the full range of more complicated common data processing activities such as summation and the maintenance of running totals is the subject of continuing research.
    At USC/ISI a research effort is currently underway that is aimed at allowing the user to express his application specification in English. This promises the ultimate in user convenience, but natural language comprehension by machines is difficult. It is conjectured, however, that the usually formidable problems of ambiguity and detail suppression (e.g. anaphoric reference) will be mitigated to, some degree by the highly constrained nature of the processing described. That is, it is felt that tentative program attempts will act as effective filters of possible alternative interpretations of the English specifications.
    Another way in which the developers of APS's are seeking to make the description process easy for the user involves the use of consistency and completeness checks. Whenever parts of a user's description are inconsistent (e.g. he associates different keys with the same file in different places) the clever system will point this out and demand resolution. Completeness checking (e.g. is the source and destination of all data specified?) can be used to guide the user in his specification effort, too. The ISDOS and MODEL systems provide such aids to the user. Abstract: To meet the burgeoning software demands of the future the computer will have to take a more active role in the writing of its own software. Many computer tools have been developed that enable the machine to help human software developers. It would be preferable, and in the not too distant future it will be necessary, for the machine to actually take over a substantial part of software development. Automatic programming seeks to do this by moving the human developer up from the implementation level of programming (e.g. COBOL, where the human has to include such details as data and control structures), to a level of programming that is less specific, where it is left to the computer decide the best way to fill in implementation. This article provides a survey of current research and development in automatic programming and a dlscussion of future directions in this field.
          in [AFIPS] Proceedings of the 1977 AFIPS National Computer Conference Dallas, Texas, June 13-16, 1977 view details
  • Kurzban, S. A. Review of Prywes view details Extract: Review
    The paper describes the MODEL II system well and in some detail. The description and examples lead this reviewer to conclude that it is well designed to meet its very ambitious objectives.

    While the abstract accurately describes Professor Prywes' work, the reviewer must observe that the author's claim that "people [with no] computer training [will] be able to obtain programs" is hardly substantiated by the paper. Either descriptions of actual achievements or examples of statements in outputs of MODEL should have been included. A note is in order on proceedings reproduced directly from typed masters. Being up to date is certainly desirable, but some of us doubt that a few months' advantage justifies subjecting the careful reader to the insult (and the carelessly imitative one to the insidious paradigms) of poor spelling (e.g., "formulea," "similarily," and "it's" for the possessive pronoun), grammar (e.g., dangling modifiers and unhyphenated compound adjectives), and typography (e.g.,"occurrs" and "questionning"). Does the publisher owe less to linguistics than to computer science?

    S. A. Kurzban, Poughkeepsie, N.Y.
          in ACM Computing Reviews 20(10) October 1979 view details
  • Cheng, T. T.; Lock, E. D. and Prywes, N. S.; "Use of very high level languages and program generation by management professionals," IEEE Trans. Software Eng., vol. SE-IO, Sept. 1984. view details
          in ACM Computing Reviews 20(10) October 1979 view details