Representation formalisms for software process modelling
ISPW '88 Proceedings of the 4th international software process workshop on Representing and enacting the software process
Software modeling and measurement: the Goal/Question/Metric paradigm
Software modeling and measurement: the Goal/Question/Metric paradigm
Discovering models of software processes from event-based data
ACM Transactions on Software Engineering and Methodology (TOSEM)
Refactoring: improving the design of existing code
Refactoring: improving the design of existing code
Software Process Modelling and Technology
Software Process Modelling and Technology
Tool-Supported Unobtrusive Evaluation of Software Engineering Process Conformance
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
Use of relative code churn measures to predict system defect density
Proceedings of the 27th international conference on Software engineering
Are developers complying with the process: an XP study
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
CodeVizard: a tool to aid the analysis of software evolution
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Hi-index | 0.00 |
In the past decades the Software Engineering community has proposed a large collection of software development life cycles, models, and processes. The goal of a major set of these processes is to assure that the product is finished within time and budget, and that a predefined set of functional and non functional requirements (e.g. quality goals) are satisfied at delivery time. Based upon the assumption that there is a real relationship between the process applied and the characteristics of the product developed from that process, we developed a tool-supported approach that uses process nonconformance detection to identify potential risks in achieving the required process characteristics. In this paper we present the approach and a feasibility study that demonstrates its use on a large-scale software development project in the aerospace domain. We demonstrate that our approach, in addition to meeting the criteria above, can be applied to a real system of reasonable size; can represent a useful and adequate set of rules of relevance in such an environment; and can detect relevant examples of process nonconformance that provide useful insight to the project manager.