Software modeling and measurement: the Goal/Question/Metric paradigm
Software modeling and measurement: the Goal/Question/Metric paradigm
Practical software metrics for project management and process improvement
Practical software metrics for project management and process improvement
Orthogonal Defect Classification-A Concept for In-Process Measurements
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
A Practical View of Software Measurement and Implementation Experiences Within Motorola
IEEE Transactions on Software Engineering - Special issue on software measurement principles, techniques, and environments
Integrating a defect typology with containment metrics
ACM SIGSOFT Software Engineering Notes
Using the GQM paradigm to investigate influential factors for software process improvement
Journal of Systems and Software
Applying GQM in an industrial software factory
ACM Transactions on Software Engineering and Methodology (TOSEM)
Software metrics: success, failures and new directions
Journal of Systems and Software - Special issue on invited articles on top systems and software engineering scholars
Validation of an Approach for Improving Existing Measurement Frameworks
IEEE Transactions on Software Engineering
Winning with software: an executive strategy
Winning with software: an executive strategy
Software Engineering Economics
Software Engineering Economics
Software Cost Estimation with Cocomo II with Cdrom
Software Cost Estimation with Cocomo II with Cdrom
Proceedings of the 24th International Conference on Software Engineering
Classification and evaluation of defects in a project retrospective
Journal of Systems and Software
Software-Engineering Research Revisited
IEEE Software
Status Report on Software Measurement
IEEE Software
Can Clean Pipes Produce Dirty Water?
IEEE Software
Learning from Our Mistakes with Defect Causal Analysis
IEEE Software
Software Quality's Eight Greatest Myths
IEEE Software
Measurement Programs in Software Development: Determinants of Success
IEEE Transactions on Software Engineering
What We Have Learned About Fighting Defects
METRICS '02 Proceedings of the 8th International Symposium on Software Metrics
An Industrial Case Study of the Verification and Validation Activities
METRICS '03 Proceedings of the 9th International Symposium on Software Metrics
An empirical evaluation of the G/Q/M method
CASCON '93 Proceedings of the 1993 conference of the Centre for Advanced Studies on Collaborative research: software engineering - Volume 1
Empirical Analysis of Safety-Critical Anomalies During Operations
IEEE Transactions on Software Engineering
The cost behavior of software defects
Decision Support Systems
Towards Reusable Measurement Patterns
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
What Do We Know about Defect Detection Methods?
IEEE Software
Appropriate Agile Measurement: Using Metrics and Diagnostics to Deliver Business Value
AGILE '06 Proceedings of the conference on AGILE 2006
Results from introducing component-level test automation and test-driven development
Journal of Systems and Software - Special issue: Selected papers from the 11th Asia Pacific software engineering conference (APSEC 2004)
Comparing the fault-proneness of new and modified code: an industrial case study
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
From Traditional to Streamline Development — opportunities and challenges
Software Process: Improvement and Practice - Special Issue on Systems Interoperability
Improving software testing via ODC: three case studies
IBM Systems Journal
Hi-index | 0.00 |
Analysis of anomalies reported during testing of a project can tell a lot about how well the processes and products work. Still, organizations rarely use anomaly reports for more than progress tracking although projects commonly spend a significant part of the development time on finding and correcting faults. This paper presents an anomaly metrics model that organizations can use for identifying improvements in the development process, i.e. to reduce the cost and lead-time spent on rework-related activities and to improve the quality of the delivered product. The model is the result of a four year research project performed at Ericsson.