Software Documents: Concepts and Tools

In this paper, we review software development as a document-based process, with the capture of a full but ideal development history as the assumed purpose of the documents concerned. We identify generic requirements for perusal, editing and veriication of such documents, and illustrate how these requirements could be met in a software development environment based on current interaction technology. Finally, we propose a generic environment architecture for implementation of the facilities concerned, and outline how our own research work has addressed some of the requirements of this architecture.

[1]  G. Tamkovich.  The Program. , 1909, California state journal of medicine.

[2]  J Welsh,et al.  User Interface Requirements for Interactive Verification Systems , 1990 .

[3]  David Lorge Parnas,et al.  A Rational Design Process: How and Why to Fake It , 1985, TAPSOFT, Vol.2.

[4]  Yun Yang,et al.  Tool Integration Techniques , 1991 .

[5]  Jim Welsh,et al.  A case study in user interface design , 1989 .

[6]  N. Falconer.  Structured Programming , 1973, Nature.

[7]  Jim Welsh,et al.  Providing user-oriented support for software development by formal methods , 1993, Proceedings of 6th International Workshop on Computer-Aided Software Engineering.

[8]  Jim Welsh,et al.  Incremental semantic evaluation in language‐based editors , 1992, Softw. Pract. Exp..

[9]  Luke Wildman,et al.  UQ2: A Multilingual Document Editor , 1990 .

[10]  J. Welsh,et al.  ANOTHER APPROACH TO LITERATE PROGRAMMING. , 1988 .

[11]  Donald E. Knuth,et al.  TeX: The Program , 1986 .

[12]  Jim Welsh,et al.  Supporting multiple tool integration paradigms within a single environment , 1993, Proceedings of 6th International Workshop on Computer-Aided Software Engineering.

[13]  Jim Welsh,et al.  An Adaptive Program Editor , 1986, Aust. Comput. J..

[14]  Jim Welsh,et al.  Retrospective application of user interface guidelines: a case study of a language-based editor , 1991 .

[15]  Jim Welsh,et al.  Structural Representation of Proofs , 1991 .

[16]  John Gatewood Ham.  A syntax-directed editor for Borland's Turbo Pascal , 1993 .

[17]  Jim Welsh.  Software is history , 1994 .

[18]  Jim Welsh,et al.  Object Organisation in Software Environments for Formal Methods , 1993, TAPSOFT.

[19]  J. Welsh,et al.  Formatted programming languages , 1981, Softw. Pract. Exp..

[20]  Donald E. Knuth,et al.  Literate Programming , 1984, Comput. J..

[21]  Chris D. Marlin,et al.  An Integrated Programming Environment Based on Multiple Concurrent Views , 1988, Aust. Comput. J..

[22]  Luke Wildman,et al.  A Literate Rigorous Program Case Study , 1990 .

[23]  Donald E. Knuth,et al.  Metafont: The Program , 1986 .

[24]  Wolfgang Emmerich,et al.  Databases for Software Engineering Environments - The Goal has not yet been attained , 1993, ESEC.

[25]  Görel Hedin,et al.  Incremental Semantic Analysis , 1992 .

[26]  Niklaus Wirth,et al.  Program development by step-wise refinement , 1971 .

[27]  Jim Welsh,et al.  Conceptual Issues in Language-Based Editor Design , 1992, Int. J. Man Mach. Stud..

[28]  A. Wood,et al.  Incorporating Constructive Tools into a Generic Language-Based , 1993 .

[29]  Jim Welsh,et al.  An empirical investigation of menu design in language-based editors , 1992, SDE 5.

[30]  Jim Welsh,et al.  A design rationale for a language‐based editor , 1991, Softw. Pract. Exp..