Proceedings of Australian Software Engineering Conference ASWEC 97
DOI: 10.1109/aswec.1997.623764
|View full text |Cite
|
Sign up to set email alerts
|

Utilising past event histories in a process-centred software engineering environment

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Publication Types

Select...
3

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 25 publications
0
4
0
Order By: Relevance
“…The work coordination examples in Figures 1 and 5 are simple enough for novices to both understand and to build for themselves for use in similar situations. Our filter/action language has also proved to be powerful enough for experienced users to build reusable, complex event handling models to implement a range of diverse work coordination facilities (Grundy et al, 1997b;Grundy and Hosking, 1998). Figure 6 shows an example of a filter/action model, built by an expert end user, being used to highlight icons in Serendipity views, to indicate access/update of artefacts and use of tools.…”
Section: Work Coordinationmentioning
confidence: 99%
See 2 more Smart Citations
“…The work coordination examples in Figures 1 and 5 are simple enough for novices to both understand and to build for themselves for use in similar situations. Our filter/action language has also proved to be powerful enough for experienced users to build reusable, complex event handling models to implement a range of diverse work coordination facilities (Grundy et al, 1997b;Grundy and Hosking, 1998). Figure 6 shows an example of a filter/action model, built by an expert end user, being used to highlight icons in Serendipity views, to indicate access/update of artefacts and use of tools.…”
Section: Work Coordinationmentioning
confidence: 99%
“…Artefacts and tools in use by judy and her collaborators are highlighted. This was achieved by storing recent artefact modification and tool events, and filter/actions use this history to highlight appropriate icons to support group awareness (Grundy et al, 1997b).…”
Section: Work Coordinationmentioning
confidence: 99%
See 1 more Smart Citation
“…When executing, the state of these agents can be examined by users, and their configurations modified as required. In our previous work we have built mainly local machine agents, with some centralized, shared agents [3,5,6]. These agents suffered from difficulties in specifying and controlling agents used by multiple people, difficulties in coordinating agent activities, and the inability to produce robust agents that don't require a centralized, single server architecture.…”
Section: Introductionmentioning
confidence: 99%