S. P. Reiss. Simplifying data integration: The design of the desert software development environment. In Proceedings of the 18th International Conference on Software Engineering, pages 398--407, 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....analyses to provide novel and informative views that help developers understand their systems. These systems provide interactive browsing but do not support interactive editing and their analyses are performed in a batch manner. Perhaps the system most similar to the Software Concordance is Desert[29], a software development environment that integrates a variety of tools through broadcast messages. It includes a common editor based on FrameMaker [1] that integrates program editing with editing tools for design diagrams and user interfaces. Desert views all of its artifacts as documents and ....

Steven P. Reiss. Simplifying data integration: The design of the desert software development environment. In Proceedings of the 18th International Conference on Software Engineering, pages 398--407, 1996.

....in a relational database management system (RDBMS) The Documents Integration Facility (DIF) 6] used hypertext services to integrate and manage the documents. The HyperPro [16] system extended hypertext model to be as a common internal representation. No program analysis was provided. Desert[18] is an IDE that integrates a set of tools through broadcast messages. It includes an editor based on Frame Maker that supplements program editing with additional editing tools for design diagrams and user interfaces. However, Desert s design deliberately avoids a uniform document model and thus ....

S. P. Reiss. Simplifying data integration: The design of the desert software development environment. In Proceedings of the 18th International Conference on Software Engineering, pages 398--407, 1996.

....task. At the same time, it is also one of the few systems that can handle visualization of large software systems. 1.2 Overview of our Approach To create a practical approach to software visualization we need to deal with the three problems cited above. Our system and the Desert environment [22] it is a part of, attempt to accomplish this by 1) providing a range of automatic and inexpensive data collection techniques, 2) offering a range of back end visualization methods, 3) providing a facility to let the user define high quality visualizations quickly and easily, and 4) allowing the ....

Steven P. Reiss, "Simplifying data integration: the design of the Desert software development environment," Proc. 18th Intl Conf on Software Engineering, pp. 398-407 (March, 1996).

....concepts from multi user dialogue systems (MUDs) which represent a new kind of hypertext functionality that can support project communication, information sharing, and a place to find and use tools. Endeavors, HyperDisco, Desert and DHT provide alternative approaches to tool integration. Desert [R96] was not designed around the use of software hypertext, as were the others. HyperDisco [WIL95] provides an objectoriented scheme for tool integration, but an object oriented scheme that inherits objects across a network can violate the conditions for autonomy that DHT seeks to maintain. Endeavors ....

Reiss, S. (1996) "Simplifying Data Integration: The Design of the Desert Software Development Environment". Proceedings of the 18th IEEE International Conference on Software Engineering, Berlin, March, pp. 398-407

....problem has been addressed by the programming language and software engineering communities through the continual evolution of programming languages and supporting tools. However, the limitations of source file based organization have not been addressed, or in fact even recognized until recently[2, 6, 5] By extending the notion of source files with a layer of indirection and abstraction, we can defeat the tyranny of source files, and provide a useful tool for addressing the separation of concerns. I ll illustrate this using the classic example of a compiler for a simple programming language. ....

....The CMU system, however, did not provide any integration with an SCM system. The integration with SCM is crucial, because without it, storing, versioning, and managing multiple users becomes extremely difficult. More recently, Lin and Reiss built a programming environment called Desert[6, 5], which has capabilities similar to those of Coven. 4 Conclusions In this paper, I have proposed an alternative mechanism for allowing advanced, multidimensional separation of concerns. Instead of using a tool that performs source code transformation or composition, I have proposed using a ....

S. REISS. Simplifying data integration: the design of the Desert software development environment. In Proceedings of ICSE 18 (1996), pp. 398--407.

....presented by Tufte [Tuf90] Within the eld of software engineering, visualisation systems have also received attention. One of the most basic types of visualisation is pretty printing code where font faces and colour highlight keywords and syntactical constructs (e.g. in Emacs [Sta84] Desert [Rei96] and commercial environments from Borland and Microsoft) Dynamic behaviour can be visualised through animation of data structures to illustrate algorithm executions. Another type of dynamics is shown by tools that visualise e.g. call graphs for particular executions. Finally software structure ....

Steve Reiss. Simplifying Data Integration: The Design of the Desert Software Development Environment. In 18th International Conference on Software Engineering, Berlin, 1996. IEEE, ACM SIGSOFT, IEEE Computer Society Press.

....a variety of collaborative applications. While Notes might be used to provide a substrate on which an approach to agenda management may be based, no guidance to this end is provided: the concepts of agenda and agenda item are absent. Similarly, while approaches to tool integration such as Desert [18] and distributed object computing standards such as CORBA address several of the requirements of agenda management provided by the AMS substrate, these systems provide little guidance for implementing an agenda management system and are not explicitly designed to be used by humans. The Workflow ....

Steven P. Reiss. Simplifying Data Integration: The Design of the Desert Software Development Environment. In Proceedings of ICSE-18, 1996.

.... Endeavors and HOSS are addressing issues of versioning, but based on the available reports, have not yet addressed the range of standard CM services [8] and CM update policy models [10] that have been addressed by DHT and NUCM [19] nor the multi tactic tool integration schemes of DHT or DESERT [41]. Finally, recent surveys of conventional and process centered software engineering environments [21, 12] underscore the growing trend toward the support of process life cycle activities, such as modeling, enactment, and repository management [25] Many such environments rely upon the use of a ....

S. Reiss. Simplifying Data Integration: The Design of the Desert Software Development Environment. In Proc. 18th. Intern. Conf. Software Engineering, IEEE Computer Society, Berlin, 398--407, March 1996.

....amount of information that is inherently needed; and they are too difficult to set up and use. 2.0 Overview of our Approach To create a practical approach to program visualization we need to deal with the three problems cited above. The Cacti system we are developing, and the Desert environment [17] it is a part of, attempt to accomplish this by 1) providing a range of automatic and inexpensive data collection techniques, 2) offering a range of back end visualization methods, and 3) providing the facilities to allow the user to define high quality visualizations quickly and easily. The first ....

Steven P. Reiss, "Simplifying data integration: the design of the Desert software development environment," Proc. 18th Intl Conf on Software Engineering, pp. 398-407 (March, 1996).

No context found.

S. P. Reiss. Simplifying data integration: The design of the desert software development environment. In Proceedings of the 18th International Conference on Software Engineering, pages 398--407, 1996.

No context found.

S. Reiss. Simplifying data integration: the design of the Desert software development environment. In Proceedings of ICSE 18, pages 398--407, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC