The object management system of PCTE as a software engineering database management system
SDE 2 Proceedings of the second ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
The Turing programming language
Communications of the ACM
Expressing structural hypertext queries in graphlog
HYPERTEXT '89 Proceedings of the second annual ACM conference on Hypertext
Building IPSE's by combing heterogeneous CASA tools
Proceedings of the European symposium on Software development environments and CASE technology
A “curriculum-cycle” environment for teaching programming
SIGCSE '93 Proceedings of the twenty-fourth SIGCSE technical symposium on Computer science education
A conceptual framework for software development
CSC '93 Proceedings of the 1993 ACM conference on Computer science
Hy+: a Hygraph-based query and visualization system
SIGMOD '93 Proceedings of the 1993 ACM SIGMOD international conference on Management of data
Software engineering environments: automated support for software engineering
Software engineering environments: automated support for software engineering
The software landscape: a visual formalism for programming-in-the-large
The software landscape: a visual formalism for programming-in-the-large
Algorithms for Drawing Graphs: An Annotated Bibliography
Algorithms for Drawing Graphs: An Annotated Bibliography
Multicolour programming and metamorphic programming: object oriented programming-in-the-large
CASCON '92 Proceedings of the 1992 conference of the Centre for Advanced Studies on Collaborative research - Volume 1
| Hi-index | 0.00 |
A developer must often be able to understand a software system at several levels of detail -- from abstract system architecture down to source code -- before being able to change system functionality or fix bugs. Each of these levels might require its own notation and tools. For example, source code, written in a programming language, is viewed and manipulated using browsers and editors, whereas architectural designs, expressed as diagrams, are viewed and manipulated using visual editors.In this paper we show how a multi-view perspective of a software system can be realized, simply and economically, by loosely integrating a set of existing independent tools. Ideally, all environments would be designed a priori to allow their combination into tightly integrated systems. In actual fact, it is common that developers of individual tools cannot foresee the ways in which their tools will be used. People who integrate such tools must exploit what is available to them. The Star system demonstrates how loose integration among existing tools can rapidly and simply result in useful environments for software development.