J. Welsh and J. Han. Software documents: concepts and tools. Software --- Concepts and Tools, 1(1), 1994. To appear.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Keywords: User interface, specification, formal methods, Object Z. 1 Introduction Editors (and their user interfaces) have been a popular choice of case study for formal specification [12, 13, 15, 7] This paper provides an example specification of part of the user interface for the UQ editor [16, 17]. The edit window of the prototype UQ editor user interface is depicted in Figure 1. The UQ editor is an intrinsically interesting case study for specification because it is an example of a ubiquitous genre of systems while providing several unique facilities that editors do not normally ....

J. Welsh and J. Han. Software Documents: Concepts and Tools. Software-Concepts and Tools, 15:12--25, 1994.

....being edited or browsed. During document input, typed text is parsed and formatted. 6 UQ1 is a (text) recognition editor. Figure 4.3 shows a multiple window formatted view of a Pascal program displayed using UQ1. The UQ1 editor is actually a precursor to UQ2 [BWW90] and, more recently, UQ [WH94] new editing environments being developed at the University of Queensland. The physical appearance of UQ1 s user interface was designed intuitively. An heuristic evaluation of this aspect of the interface would identify a number of major deficiencies for professional use, including: ffl user ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software---Concepts and Tools, 15:12--25, 1994.

.... this AST server architecture as the means of introducing persistent document manipulation to our recognition editors, and as a means of supporting constructive semantic tools, i.e. those whose semantic analysis of the document plays a determining role in its further development during input [20]. 10 Conclusions Integration of the tools used to prepare and verify software documents is vital to the effectiveness of the software development process. We have identified the key requirements of such integration from the viewpoints of both the tool users and the tool or environment builders. ....

J. Welsh and J. Han. Software documents: concepts and tools. Software --- Concepts and Tools, 1(1), 1994. To appear.

....to the UQ environment to facilitate interfacing a variety of graph drawing tools. Our preliminary experiments have been performed with GraphEd [8, 9] 2 UQ architecture Work at The University of Queensland has produced an experimental generic languagebased software development environment, UQ [4, 19, 20, 21], which is distinguished by its facilities for capturing and manipulating relational structures within and between software documents, and for displaying these structures in textual or diagrammatic form. By generic language based environment , we mean one which, when provided with appropriate ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software-Concepts and Tools, 15:12--25, 1994.

....by showing their use in call graph visualisation. Sections 6 and 7 then review related work and draw some overall conclusions on the results achieved. 2 UQ architecture Work at The University of Queensland has produced an experimental generic language based software development environment, UQ [4, 22, 23, 24]. By generic language based environment , we mean one which, when provided with appropriate descriptions of the languages and representations involved in a development method, provides its users with language specific support for the method. UQ is distinguished by its facilities for capturing ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software-Concepts and Tools, 15:12--25, 1994.

....It is now widely recognised, however, that manipulation of relational structures or links between (components of) this set of documents is a vital part of effective software engineering. Work at The University of Queensland has produced an experimental software development environment, UQ [WH94] which is distinguished by its facilities for capturing and manipulating relational structures within and between software documents, and for displaying these structures in textual or diagrammatic form. UQ is a generic language based environment in that, when provided with appropriate ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software-Concepts and Tools, 15:12--25, 1994. 14

....or Pascal.proc declaration. This adds nothing to the conceptual complexity involved. 4 Tools and tool views Before considering how the structures defined in the preceding section can be created, presented and manipulated, it is useful to introduce the overall architecture of our UQ environment[14], which is as shown in figure 5. front end graphics front end text tool back end tool back end store document Figure 5: The UQ environment architecture The central document store is responsible for holding the syntactic and relational structures under manipulation, and for ensuring ....

J. Welsh and J. Han. Software documents --- concepts and tools. Software Concepts and Tools, 15:12--25, 1994.

....and an Emacs interface to the Ergo theorem prover addressing these issues was developed jointly with the Ergo developers [NU95] The Emacs Ergo interface uses the active document style of Section 2.5, with navigation via the structure of the proof. An alternative interface using the UQ editor [WH94] is also under development. UQ is a generic syntax directed editor that supports multiple interacting tools. The UQ design is based on the active document model, with a central store that can contain multiple documents and arbitrary relations between documents and parts of documents. In the ....

Jim Welsh and Jun Han. Software documents: Concepts and tools. Software---Concepts and Tools, 15(1):12--25, 1994.

....guidelines for which a logical interpretation was apparent, many simply reinforced the original intuitive design decisions taken for UQ1. Where the guidelines were at odds with design decisions, in many cases they served to confirm subsequent choices made for the interface to UQ1 s successor, UQ [35]. Clearly, if these guidelines had been readily available at the time of UQ1 s design then their use would have been beneficial. Some issues raised by guidelines relate less to physical issues of user interface design and more to higher level issues of concern. Such issues included feedback and ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software---Concepts and Tools, 15:12--25, 1994.

....a case study which explores those requirements. 2 Requirements for a Generic, Language based Diagram Editor 2 The UQM Software Development Environment UQM is an integrated software development environment, based on a loosely coupled tool integration paradigm [14] and a structured document model [12]. It allows for the representation of the syntactic and semantic structure of documents. At present it provides document construction facilities via textual views of document structures. Documents may also be constructed by integrated software analytic tools and by importing text files. Relational ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software--Concepts and Tools, 15(1):12--25, January 1994.

....interpreted in terms of the underlying documents themselves. In these cases such direct manipulation is a natural extension of the integrated manipulation and visualisation facilities involved and should be supported. Work on UQM, a generic language based software development environment [1, 2, 20, 21, 37], has shown that software development environments can provide syntactic views, relational views and a hybrid of both, and that such views can be smoothly integrated into the activities of presentation and interaction. In this paper we describe how the UQM editor is able to provide a wide variety ....

....presentation and interaction, which in turn provides the basis for software visualisation in the editor. 4. 1 UQM Software Development Environment UQM is an integrated software development environment, based on a loosely coupled tool integration paradigm [38] and a structured document model [37]. It allows for representation of the syntactic and semantic structure of documents. The architecture providing this support is a persistent store of documents manipulated by front end and backend tools. Front end tools are those that interact with users to present and perhaps modify the ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software--Concepts and Tools, 15(1):12--25, January 1994.

....products and software processes, and only limited attention has been given to configuration management support in such environments. In developing software engineering environments, we have taken a document based approach to providing integrated support for software products and software processes [3, 4, 5]. In particular, our approach is generic in the sense that a generic environment is developed to address the general requirements for support and it can be augmented by a specification of the requirements specific to a particular methodology or project and by some modules realising specific ....

....relationships. In providing such support, we have taken requirements specific generic specific modules specific environment environment Figure 1. Generation of methodology or project specific environments. a document based approach and regard software development as a document based process [3]. In contrast to process centred and product centered approaches, our approach aims to provide integrated support for software products and software processes. In this section, we present a brief overview of the major features of our approach. Concrete examples of these features can be found in ....

[Article contains additional citation context not shown here]

J. Welsh and J. Han. Software documents: Concepts and tools. Software --- Concepts and Tools, 15(1):12--25, 1994.

....they have led to the development of process centred and product centred software engineering environments. To provide integrated support for the software process and the software documents, we have taken a documentbased approach and regard software development as a document based process [12]. We assume that the end product of a software development process is a necessary history of the development, rather than just the compilable or executable programs that result. This history includes not only the software documents involved in the software process, but also the relationships ....

....every document segment has a unique identification. External tool functions. The back end tools which are integrated into the environment may provide a wide range of functionalities. These tools may provide a mere analysis of the documents, or make contributions or changes to the document content [12]. To handle the invocation of the tool functionalities, we model them as tool functions which may take document constructs as parameters and return analysis results or new document constructs. Composite operations. The primitive operations are independent of any software development methodologies ....

[Article contains additional citation context not shown here]

J. Welsh and J. Han. Software documents: Concepts and tools. Software --- Concepts and Tools, 15(1):12-- 25, 1994.

.... such as program slicing [18, 12] and program dependence graphs [17, 14, 1] and approaches to tool support for change management [13, 4, 7, 5] In this paper, we address the tool support issues for software change management in the context of a (generic) software engineering environment [19, 8, 9], in particular impact analysis and change propagation. In our approach, the kernel of the software engineering environment, augmented with specific features for change management, can be seen as a generic tool for change management. The policies, models and methods for change management in a ....

....in the context of C programs. This raises the need for a general approach that allows the codification of context specific change management policies and methods. In our approach to software change management, the generic tool is served by the kernel of a (generic) software engineering environment [19, 8, 9, 10] augmented with additional change management capabilities. The policies, models and methods for change management in a particular application context can be codified to specialise the environment kernel, so that the resulting environment provides the specific change management support required. ....

[Article contains additional citation context not shown here]

J. Welsh and J. Han. Software documents: Concepts and tools. Software --- Concepts and Tools, 15(1):12--25, 1994.

....In particular, they have led to the development of process centred and product centred software development environments. To provide unified support for the software process and the software products, we follow a document based approach and regard software development as a document based process [11]. We assume that the end product of a software development process is a necessary history of the development, rather than just the compilable or executable programs that result. This history includes not only the software documents involved in the software process, but also the relationships ....

....for document representation and description. Case studies of larger scale are planned. The representation issues reported in this paper are only part of a document model for software development environments that we have been developing. Other aspects of the model include document presentation [11] and document manipulation (to be reported elsewhere) Based on this model and a corresponding document description language, a generic environment kernel supporting software development is to be developed. Acknowledgements Much of the work reported in this paper was carried out when the author ....

J. Welsh and J. Han. Software documents: Concepts and tools. Software --- Concepts and Tools, 15(1):12-- 25, 1994.

No context found.

J. Welsh and J. Han, 'Software Documents: Concepts and Tools', Software--Concepts and Tools, 15, 12-25 (1994).

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