SOFTWARE PROCESS MODELING AND METRICS - A CASE-STUDY

The paper's specific concern is with software process modelling for the measurement of rework during application development using computer-aided software engineering (CASE) tools. In order to measure aspects of software development, one needs a defined process that models the aspects of interest. The goals of this study are rather different from those of most other software process modelling studies which are typically concerned with process definition and understanding, development standardization, developer guidance, process assessment, evolution and improvement. Most software process models are intrusive, and intentionally so. In contrast, our model is as non-intrusive as is practicable to observe and measure certain aspects of CASE development in order to improve our understanding of software cost and schedule overruns. Model requirements and selection are described. The interlocking mechanisms of software process enaction and measurement are examined and placed within a larger architectural framework including process engineering and management. Some results and experiences with a small case study are presented including the observation that, although quite high-powered tools seem to be necessary for comprehensive software process modelling, much more modest tools may suffice for simpler, more specific, goal-oriented studies.