Despite many attempts in both research and industry to develop successful language-based software engineering tools, the resulting systems consistently fail to become adopted by working programmers. One of the main reasons for this failure is the closed-world view adopted by these systems: it is virtually impossible to integrate them with any outside technology. To address this problem, and to create a research infrastructure, we created HARMONIA, an open framework for constructing interactive language-based programming tools. This report presents the architecture of the HARMONIA framework. We brie review the design of the two earlier Berkeley projects, the PAN and ENSEMBLE systems, discuss their in on the design of HARMONIA, and present the organization and interactions of the major components in the HARMONIA framework. This work was supported in part by NSF grant CCR-9988531, by NSF Graduate Research Fellowship, and by Sun Microsystems Fellowship to Marat Boshernitsan. Contents 1

This paper describes the syntax and semantics of PSL using a simple text document as a running example and compares PSL to a number of other presentation specification languages. 1 Introduction

The software development process generates a wide variety of artifacts. Supporting the management and editing of these artifacts in a single, tightly-integrated development environment is a widely shared goal. To support a software object means not only managing its evolution, representation and storage, but also its display and user interaction. To integrate support for the representation, display, and editing of all the objects in the development process, we regard objects as documents - structured compositions of primitive types. We present a document model for software development that accommodates textual documents in natural and formal languages, multimedia documents, and the results of programmatic analysis. We also present an architecture that supports presentation and editing of these documents, in such a way that the services for each primitive type are reusable in all classes of documents. This document architecture is implemented in a working prototype system, Ensemble. Our experiences with Ensemble provide solutions to some of the key architectural problems in integrated environments.

The Software Concordance project is examining how hypermedia technology can provide improved tools for managing the full range of documents produced by the software life cycle. The project's aim is to help software developers better maintain conformance between these many documents as they and the software that they describe change over time. This research requires solutions to open problems in a number of areas including document representation and formatting (especially for program source code), fine-grained version control for tree-structured documents, the categorization of relationships among software documents, and the analysis and visualization of document relationships. The Software Concordance prototype will support Java programs and XML documents and will provide tools for defining, maintaining, and analyzing document relationships. 1 Introduction Much of the advance of the human condition is based on our ability, through word-of-mouth, written documents, and other...

We present a novel approach to incremental recovery from lexical and syntactic errors in an interactive software development environment. Unlike existing techniques, we utilize the history of changes to the program to discover the natural correlation between user modifications and errors detected during incremental lexical and syntactic analysis. Our technique is non-correcting---the analysis refuses to incorporate invalid modifications, while still permitting correct changes to be applied. Errors are presented to the user simply by highlighting the invalid changes. The approach is automated---no user action is required to detect or recover from errors. Multiple textual and structural edits, arbitrary timing of incremental analysis, multiple errors per analysis, and nested errors are supported. Historybased error recovery is language independent and is compatible with the best known methods for incremental lexing and parsing, adding neither time nor space overhead to those algorithms. Effective integration with the environment's history services ensures that other tools can efficiently discover regions of the program (un)affected by errors, and that any transformations of the program required to isolate or present errors are themselves efficiently reversible operations. Keywords--- Error recovery, software development environments, incremental parsing, incremental lexing, development log, program presentation I.

, Paper Using Static Single Assignment Form to Improve Flow-Insensitive Pointer Analysis Rebecca Hasti and Susan Horwitz (Computer Sciences Dept., University of Wisconsin - Madison) Abstract, Paper Edge Profiling vs. Path Profiling: The Showdown Thomas Ball, Peter Mataga (Bell Laboratories, Lucent Technologies), and Mooly Sagiv (TelAviv University) Abstract, Paper 3:30-4:00 Break 4:00-5:30 Technical Session II Action Transformation: An Application of Sort Inference Kent Lee (Dept. of Computer Science, Luther College) Abstract, Slides, Slide supplement: test0.action, Slide supplement: test0.sorts, Paper Integration of Software Development Documents with the Software Concordance Ethan Munson (Dept. of Electrical Engineering and Computer Science, University of Wisconsin - Milwaukee) Abstract, Paper Issues in the Design of SWAR Programming Models Randall J. Fisher and Hank Dietz (Dept. of Electrical and Computer Engineering, Purdue University) Abstract 5:30-6:00 MSPLS Spring '9...

This paper describes the syntax and semantics of PSL using a simple text document as a running example and comparesPSL to a number of other presentation specification languages. 1