Abstract not found

When working on complex software systems, it is often difficult for multiple software developers to coordinate their work, and for developers to coordinate their multiple tool and software process usage. Process-centred Software Engineering Environments attempt to help developers manage the complexities of such coordination by codifying steps in a software process, and codifying the "work context" a developer utilises (i.e. the artefacts, tools and collaborators the developer requires during their work). Unfortunately most process-centred environments do not adequately support work coordination, ease-of-use and improvement of process models. We describe our work utilising histories of past events within a process-centred environment to give developers extra leverage when using process models to guide collaborative software development. We describe techniques for work history determination, improved visualisation support for work coordination, and automatic process enactment and process...

Workflow systems are a common example of end-user programming, in the form of work process modelling, enactment and evolution. Example applications of workflow systems include office automation, software process modelling and business process codification. We describe a workflow system which provides novel end-user programming support for the coordinated use of workflow models, communication and collaboration between multiple people, and the tools being used to perform work. We illustrate the utility of these work coordination mechanisms and outline our future research directions in this area. 1. Introduction Workflow management systems and process modelling environments have become popular for use in various fields, including office automation, business process reengineering and software development [1, 28, 32]. Such systems typically allow users to model work processes using graphical and textual notations, and then run ("enact") these process models to guide (or enforce) work on p...

Software design and development is a collaborative activity, potentially involving many people working on inter-dependent activities. This interdependence has motivated the development of tools that support collaboration in software design. There is a wide range of such tools, and this diversity is representative of the wide range of collaborative activities in which software designers engage. However, as no comprehensive design tool exists, designers must integrate heterogeneous tools to suit their need and accept the limitations of such a toolset. This means frequent migration between tools as the context of their work evolves. The purpose of this document is a survey the body of tools that comprise this toolset. This will serve to illuminate areas where further tool support is needed, and to motivate the design of new tools to address these needs. Acknowledgements I would like to gratefully acknowledge the contribution of my doctoral supervisor, Dr. T.C.N. Graham, without whose guidance and motivation this paper would not exist. I would also like to thank my