Techniques for process model evolution in EPOS
Letizia Jaccheri, Reidar Conradi · IEEE Transactions on Software Engineering · 1993
The authors categorize some aspects of software process evolution and customization, and describe how they are handled in the EPOS PM system. Comparisons are made to other PM systems. A process model in EPOS consists of a schema of classes and meta-classes, and its model entities and relationships. There is an underlying software engineering database, EPOSDB, offering uniform versioning of all model parts and a context of nested cooperating transactions. Then, there is a reflective object-oriented process specification language, on top of the EPOSDB. Policies for model creation, composition, change, instantiation, refinement, and enaction are explicitly represented and are used by a set of PM automatic tools. The main tools are a planner to instantiate tasks, an execution manager to enact such tasks, and a PM manager to define, analyze, customize, and evolve the process schema.>
Cited by 117 works. doi:10.1109/32.249660
Authors
References
- Smalltalk-80: The Language and its Implementation
- Planning for conjunctive goals
- Self: The power of simplicity
- Program Evolution: Processes of Software Change
- Integrating planning, execution and monitoring
- Language constructs for managing change in process-centered environments
- A programmer's guide to object-oriented programming in Common LISP
- Delegation is inheritance
- Relations as semantic constructs in an object-oriented language
- Software process development and enactment: concepts and definitions