The Cornell program synthesizer

Teitelbaum, Tim; Reps, Thomas

doi:10.1145/358746.358755

Cited by 590 publications

(93 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…One could imagine heuristic natural language processing methods to rescue some of this material, but GF does not have such methods at present. Finally, an obstacle to the applicability of syntax-directed editors for programming languages, for which special techniques are required [19], is the phenomenon that top-down development as enforced by stepwise refinement is usually incompatible with the direction of the control flow. The latter, however, is more natural from an implementor's point of view.…”

Section: Limitationsmentioning

confidence: 99%

An Authoring Tool for Informal and Formal Requirements Specifications

Hähnle

Johannisson

Ranta

2002

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. We describe foundations and design principles of a tool that supports authoring of informal and formal software requirements specifications simultaneously and from a single source. The tool is an attempt to bridge the gap between completely informal requirements specifications (as found in practice) and formal ones (as needed in formal methods). The user is supported by an interactive syntax-directed editor, parsers and linearizers. As a formal specification language we realize the Object Constraint Language, a substandard of the UML, on the informal side a fragment of English. The implementation is based on the Grammatical Framework, a generic tool that combines linguistic and logical methods.

show abstract

Section: Limitationsmentioning

confidence: 99%

An Authoring Tool for Informal and Formal Requirements Specifications

Hähnle

Johannisson

Ranta

2002

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…This paper describes how three facilities of persistent environments, persistent linkage, strong typing and referential integrity, may be used in the construction of software environments. It is clear that the same activities can be supported by other techniques and indeed other integrated programming environments exist (Teitelbaum and Reps, 1981;Reiss, 1984;Teitelman and Masinter, 1984;Sweet, 1985;Habermann and Notkin, 1986;Dowson, 1987;O'Brien, Halbert et al, 1987;Akima and Ooi, 1989;Bott, 1989;Thomas, 1989) . The stronger hypothesis is that the same activities may be modelled with advantage to both the user and the system constructor in a strongly typed environment with referential integrity.…”

Section: Discussionmentioning

confidence: 99%

“…This paper focuses on the combination of three particular advantages, those of persistent linkage, strong typing and referential integrity. Although other integrated programming environments have been developed (Teitelbaum and Reps, 1981;Reiss, 1984;Teitelman and Masinter, 1984;Sweet, 1985;Habermann and Notkin, 1986;Dowson, 1987;O'Brien, Halbert et al, 1987;Akima and Ooi, 1989;Bott, 1989;Thomas, 1989) , the authors do not know of any that use persistent linkage, strong typing and referential integrity to gain the benefits described here.…”

Section: Introductionmentioning

confidence: 99%

Exploiting Persistent Linkage in Software Engineering Environments

Morrison

Connor

Cutts

et al. 1995

The Computer Journal

View full text Add to dashboard Cite

Abstract. Persistent programming systems are designed to provide technology for the construction and maintenance of large, long-lived object-based application systems. Many successful prototypes have been constructed and a large body of application building experience is emerging. Three common attributes of persistent systems are persistent linkage, strong typing and the referential integrity of data. Persistent linkage allows persistent objects to be included in the binding process. Strong typing guarantees that objects are only manipulated in a manner consistent with their type system descriptions. Referential integrity ensures that once a link (reference) to an object is established, its identity is unique and it persists over time. As a consequence no object can be deleted while another refers to it. Here we examine some of the advantages of providing software engineering environments within a persistent object system with strong typing and referential integrity. It is shown how the integration of system specifications, programs, configuration management tools and documentation all within a single persistent environment leads to powerful new techniques. This new power is achieved by sharing structured persistent data across the hitherto enclosing boundaries of system components.

show abstract

“…Some of the well-cited research on languagedirected editors are Mentor [12], Interlisp [34], Program Synthesizer [33], Rational [6], PECAN [28], and Gandalf [16]. Most of the existing language-based editors such as in Eclipse are based on attribute grammars [15].…”

Section: Related Workmentioning

confidence: 99%

Towards Domain-specific Model Editors with Automatic Model Completion

2009

View full text Add to dashboard Cite

Integrated development environments such as Eclipse allow users to write programs quickly by presenting a set of recommendations for code completion. Similarly, word processing tools such as Microsoft Word present corrections for grammatical errors in sentences. Both of these existing structure editors use a set of constraints expressed in the form of a natural language grammar to restrict/correct the user (syntax-directed editing) or formal grammar (language-directed editing) to aid document completion. Taking this idea further, in this paper we present an integrated software system capable of generating recommendations for model completion of partial models built in editors for domain-specific modelling languages. We present a methodology to synthesize model editors equipped with automatic completion from a modelling language's declarative specification consisting of a metamodel with a visual syntax. This meta-model directed completion feature is powered by a first-order relational logic engine implemented in ALLOY. We incorporate automatic completion in the generative tool AToM 3 . We use the Finite State Machines modelling language as a concise running example. Our approach leverages a correct by construction philosophy that renders subsequent simulation of models considerably less error-prone.

show abstract

The Cornell program synthesizer

Cited by 590 publications

References 9 publications

An Authoring Tool for Informal and Formal Requirements Specifications

An Authoring Tool for Informal and Formal Requirements Specifications

Exploiting Persistent Linkage in Software Engineering Environments

Towards Domain-specific Model Editors with Automatic Model Completion

Contact Info

Product

Resources

About