Smalltalk-80: the language and its implementation
Smalltalk-80: the language and its implementation
Abstraction and specification in program development
Abstraction and specification in program development
A Remote Procedure Call Facility for Interconnecting Heterogeneous Computer Systems
IEEE Transactions on Software Engineering
Software processes are software too
ICSE '87 Proceedings of the 9th international conference on Software Engineering
Guided tours and tabletops: tools for communicating in a hypertext environment
ACM Transactions on Information Systems (TOIS)
Rationale for the design of the Ada programming language
Rationale for the design of the Ada programming language
APPL/A: a prototype language for software-process programming
APPL/A: a prototype language for software-process programming
The design and implementation of hierarchical software systems with reusable components
ACM Transactions on Software Engineering and Methodology (TOSEM)
Flexible, active support for collaborative work with ConversationBuilder
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
An architecture for multi-user software development environments
SDE 5 Proceedings of the fifth ACM SIGSOFT symposium on Software development environments
The ProcessWall: a process state server approach to process programming
SDE 5 Proceedings of the fifth ACM SIGSOFT symposium on Software development environments
Supporting dynamic interdependencies among collaborative activities
COCS '93 Proceedings of the conference on Organizational computing systems
A case study in process definition
TRI-Ada '93 Proceedings of the conference on TRI-Ada '93
A Framework for Integrated CASE
IEEE Software
Commonsense Approach to Process Modeling
IEEE Software
Proceedings of the conference on TRI-Ada '96: disciplined software development with Ada
Hi-index | 0.00 |
Process-centered computing environments are currently in their infancy, with notable exceptions [1][19][21][22]. Two important components of envisioned environments are the language used to describe the processes, and the architecture for the language implementation and execution. These must support the multi-user emphasis of team work, process monitoring, process improvement, and automated execution.This paper reports on the STARS Process Engine, Boeing's language and architectural approach to specification and automatic execution of processes. A language concept called AAA (Agents, Artifacts and Activities) is implemented using an internally developed persistent programming language, called Denali. The architecture of the Process Engine is composed of the Denali Runtime System tailored to the process aspects of AAA, integrated with an Object-Oriented Repository and supporting unobtrusive metrics collection.Activity programs are the computational unit used by the Denali Language to encapsulate tools, parameters, and readable descriptions. Activities are managed by the Process Engine which provides a User Interface supporting context sensitive, hyper-text access to the necessary tools and information defined by the activity. Aspects of the Denali language are described showing how the syntax of the language is relatively implementation neutral when accessing the synchronization and relationship properties provided by the repository.