The maturity of any discipline is reflected in the amount of experience that is captured explicitly and can be reused effectively. In software engineering, we have just begun to develop languages for capturing ” process models” explicitly (e.g., APPL,/A, GRAPPLE, HFSP, i W V E L , h/Np-L 141). Initial applications of these languages have taught us two important lessons: (i) ’Real’ software processes are very complex, and (ii) they cannot be appiied across projects without prior customization to the specific needs and characteristics of each project. As a result we need to support (i) reuse of existing process models t o avoid re-creating complex models for each project from scratch, and (ii) customizacion before reuse to acknowledge each project’s specific goals and characteristics. In this position paper, we list a number of requirements for representing and organizing process models so they can be reused effectively. The process representation language MVP-L is designed to satisfy these requirements. Some of the reuse related language features are pointed out.
[1]
H. D. Rombach,et al.
Establishing a measurement-based maintenance improvement program: lessons learned in the SEL
,
1989,
Proceedings. Conference on Software Maintenance - 1989.
[2]
Christopher M. Lott,et al.
A MVP-L1 Solution for the Software-Process Modeling Problem
,
1990
.
[3]
H. Dieter Rombach.
MVP-L: a language for process modeling in-the-large
,
1991
.
[4]
Victor R. Basili,et al.
The TAME Project: Towards Improvement-Oriented Software Environments
,
1988,
IEEE Trans. Software Eng..
[5]
Victor R. Basili,et al.
Support for comprehensive reuse
,
1991,
Softw. Eng. J..