A system for multiparadigm development of software systems

Meyers, Scott; Reiss, Steven P.

doi:10.1109/iwssd.1991.213060

Cited by 12 publications

(6 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Robinson [49] proposes a multiple perspectives integration architecture as part of a model of specification design. Meyers and Reiss [40] study interperspective (cf. inter-Viewpoint) communication, and propose the development of a single canonical representation for software specification.…”

Section: Related Workmentioning

confidence: 99%

A framework for expressing the relationships between multiple views in requirements specification

Nuseibeh

Kramer

Finkelstein

1994

IIEEE Trans. Software Eng.

374

187

View full text Add to dashboard Cite

Composite systems are generally comprised of heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives that overlap, complement, and contradict each other. Furthermore, these requirements are generally developed and specified using multiple methods and notations, respectively. It is therefore necessary to express and check the relationships between the resultant specification fragments. In this paper, we deploy multiple ViewPoints that hold partial requirements specifications, described and developed using different representation schemes and development strategies. We discuss the notion of inter-Viewpoint communication in the context of this Viewpoints framework, and propose a general model for Viewpoint interaction and integration. We elaborate on some of the requirements for expressing and enacting inter-Viewpoint relationships-the vehicles for consistency checking and inconsistency management. Finally, though we use simple fragments of the requirements specification method CORE to illustrate various components of our work, we also outline a number of larger case studies that we have used to validate our framework. Our computer-based Viewpoints support environment, The Viewer, is also briefly described.

show abstract

Section: Related Workmentioning

confidence: 99%

A framework for expressing the relationships between multiple views in requirements specification

Nuseibeh

Kramer

Finkelstein

1994

IIEEE Trans. Software Eng.

374

187

View full text Add to dashboard Cite

show abstract

“…Meyers and Reiss [30] describe another problem with ASTs: they do a poor job of supporting views that are unrelated to the program's syntax. In their search for a "single canonical representation for software systems", they present their own Semantic Program Graphs (SPGs), which support a range of views directly.…”

Section: Historical Contextmentioning

confidence: 99%

A pattern language for extensible program representation

Vainsencher

Black

2006

Proceedings of the 2006 Conference on Pattern Languages of Programs

View full text Add to dashboard Cite

Abstract. For the last 15 years, implementors of multiple view programming environments have sought a single code model that would form a suitable basis for all of the program analyses and tools that might be applied to the code. They have been unsuccessful. The consequences are a tendency to build monolithic, single-purpose tools, each of which implements its own specialized analyses and optimized representation. This restricts the availability of the analyses, and also limits the reusability of the representation by other tools. Unintegrated tools also produce inconsistent views, which reduce the value of multiple views. This article describes a set of architectural patterns that allow a single, minimal representation of program code to be extended as required to support new tools and program analyses, while still maintaining a simple and uniform interface to program properties. The patterns address efficiency, correctness and the integration of multiple analyses and tools in a modular fashion.

show abstract

“…Although we examine the application of ViewPoints for requirements specification, we further argue that requirements engineering from multiple perspectives, multiparadigm specification [46] and multiparadigm programming [29], are all facets of the same generic (multiple perspectives) problem.…”

Section: Scope Of Papermentioning

confidence: 98%

“…Robinson [37] proposes an multiple perspectives integration architecture as part of a model of specification design. Meyers and Reiss [29] study inter-perspective (cf. inter-ViewPoint) communication, and propose the development of a single canonical representation for software specification.…”

Section: Related Workmentioning

confidence: 99%

Expressing the relationships between multiple views in requirements specification

Nuseibeh¹,

Kramer²,

Finkelstein³

Proceedings of 1993 15th International Conference on Software Engineering

View full text Add to dashboard Cite

Composite systems generally comprise heterogeneous components whose specifications are developed by many development participants. The requirements of such systems are invariably elicited from multiple perspectives which will overlap, complement and contradict each other. If these requirements are developed and specified using multiple methods and notations respectively, then it is necessary to express and check the relationships between the resultant specification fragments.In this paper we deploy multiple "ViewPoints" that hold partial requirements specifications, described and developed using different representation schemes and development strategies. We discuss the notion of inter -ViewPoint communication in the context of this ViewPoints framework, and propose a general model for such communication. We elaborate on some of the requirements for expressing and enacting inter-ViewPoint relationships, and use fragments of the requirements specification method CORE to illustrate our model. * Since CORE uses the term "viewpoint" as part of its terminology, we substitute the term "agent" in its place to avoid the clash in nomenclature.

show abstract

A system for multiparadigm development of software systems

Cited by 12 publications

References 15 publications

A framework for expressing the relationships between multiple views in requirements specification

A framework for expressing the relationships between multiple views in requirements specification

A pattern language for extensible program representation

Expressing the relationships between multiple views in requirements specification

Contact Info

Product

Resources

About