by
Dieter Rombach, Martin Verlage
Abstract:
An experimental framework for assessing process formalisms from project members' points of view is proposed. This framework is based on the goal/question/metric paradigm and uses role definitions to state the assessment goals. The assessment goals are then used to identify the information that must be supplied by a formalism to support a project role. The feasibility of this framework is demonstrated using the ISPW-6 software process example. A number of example roles are identified, and example hypotheses are derived for some of the formalisms used
Reference:
Dieter Rombach, Martin Verlage, "How to assess a software process modeling formalism from a project member's point of view", In 2nd International Conference on the Software Process: Continuous Software Process Improvement, 1993, pp. 147-158, 1993.
Bibtex Entry:
@inproceedings{
author={Rombach, Dieter and Verlage, Martin},
booktitle={2nd International Conference on the Software Process: Continuous Software Process Improvement, 1993},
title={How to assess a software process modeling formalism from a project member's point of view},
year={1993},
pages={147--158},
abstract={An experimental framework for assessing process formalisms from project members' points of view is proposed. This framework is based on the goal/question/metric paradigm and uses role definitions to state the assessment goals. The assessment goals are then used to identify the information that must be supplied by a formalism to support a project role. The feasibility of this framework is demonstrated using the ISPW-6 software process example. A number of example roles are identified, and example hypotheses are derived for some of the formalisms used},
keywords={DP management;project management;software engineering;ISPW-6 software process;assessment goals;goal/question/metric paradigm;role definitions;software process modeling formalism;Automatic programming;Computer aided software engineering;Documentation;Innovation management;Knowledge management;Software maintenance;Software reusability;Software systems;Technological innovation;Technology management},
doi={10.1109/SPCON.1993.236814},
}