This paper categorizes some aspects of software process evolution and customization, and describes how they are handled in the EPOS PM system. Comparisons are made with 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, o ering uniform versioning of all model parts and a context of nested cooperating transactions. Then, there is a re ective object-oriented process speci cation language, on top of the EPOSDB. Policies for model creation, composition, change, instantiation, re nement 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, and a PM Manager to de ne, analyze, customize and evolve the Process Schema.
An early work devoted to software process evolution is REF , which describes the EPOS approach to evolution and customization.
Techniques for Process Model Evolution in EPOS
IEEE Trans. Software Eng.
Computer Science