Issue No. 12 - December (1993 vol. 19)
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/32.249660
<p>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.</p>
process model evolution; schema; software process evolution; EPOS PM system; meta-classes; model entities; underlying software engineering database; EPOSDB; uniform versioning; nested cooperating transactions; reflective object-oriented process specification language; model creation; PM automatic tools; planner; execution manager; PM manager; process schema; process support environment; SPELL; configuration management; object-oriented databases; object-oriented languages; object-oriented programming; programming environments; specification languages
M. Jaccheri and R. Conradi, "Techniques for Process Model Evolution in EPOS," in IEEE Transactions on Software Engineering, vol. 19, no. , pp. 1145-1156, 1993.