Abstract
Software processes are long-lived entities. Careful design and thorough validation of software process models are necessary to ensure the quality of the process. They do not prevent, however, process models from undergoing change. Change requests may occur in the context of reuse, i.e., statically, in order to support software process model customization. They can also occur dynamically, while software process models are being executed, in order to support timely reaction as data are gathered from the field during process enactment. In this paper, we discuss the mechanisms a process language should possess in order to support changes. We illustrate the solution adopted in the context of the SPADE environment and discuss how the proposed mechanisms can be used to model different policies for chanmnp a software nrncess model.
| Original language | English |
|---|---|
| Pages (from-to) | 1128-1144 |
| Number of pages | 17 |
| Journal | IEEE Transactions on Software Engineering |
| Volume | 19 |
| Issue number | 12 |
| DOIs | |
| Publication status | Published - Dec 1993 |
| Externally published | Yes |
Keywords
- Object-oriented databases
- object-oriented languages
- Petrinets process-centered software engineering environments (PSEE’s)
- process enactment
- process evolution process modeling reflective languages
- software process