Software engineering concepts
Software Quality: Analysis and Guidelines for Success
Software Quality: Analysis and Guidelines for Success
A Study of the Impact of Requirements Volatility on Software Project Performance
APSEC '02 Proceedings of the Ninth Asia-Pacific Software Engineering Conference
Statistics and data mining: intersecting disciplines
ACM SIGKDD Explorations Newsletter
Code Churn: A Measure for Estimating the Impact of Code Change
ICSM '98 Proceedings of the International Conference on Software Maintenance
Detection of software modules with high debug code churn in a very large legacy system
ISSRE '96 Proceedings of the The Seventh International Symposium on Software Reliability Engineering
Jazzing up Eclipse with collaborative tools
eclipse '03 Proceedings of the 2003 OOPSLA workshop on eclipse technology eXchange
Building Collaboration into IDEs
Queue - Distributed Development
A study to investigate the impact of requirements instability on software defects
ACM SIGSOFT Software Engineering Notes
ISSTA '04 Proceedings of the 2004 ACM SIGSOFT international symposium on Software testing and analysis
Use of relative code churn measures to predict system defect density
Proceedings of the 27th international conference on Software engineering
Linked: How Everything Is Connected to Everything Else and What It Means
Linked: How Everything Is Connected to Everything Else and What It Means
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Jazz and the Eclipse Way of Collaboration
IEEE Software
Proceedings of the 30th international conference on Software engineering
Predicting defects using network analysis on dependency graphs
Proceedings of the 30th international conference on Software engineering
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Foundations of Software Testing
Foundations of Software Testing
Hi-index | 0.00 |
Literature suggests that requirements defects are a very costly problem to fix. Understanding how requirements changes influence the overall quality of software is important. Having some defect predictors at the requirements stage may help the stakeholders avoid making choices that could bring about catastrophic defect numbers at the end or at least be prepared for it. In this paper, six requirements-related attributes are analyzed to discover if they can be used for determining the occurrences of requirements-related defects. We measured two types of attributes: point and aggregate. The point attributes include time estimates, priority and ownership. The aggregate attributes include the number of indirect stakeholders, the number of related stories and the story creation time. Our analysis is based on data from the development of the IBM Jazz system. Our result shows that the number of indirect stakeholders and the number of related stories are good predictors for the number of defects, but other attributes show no or little correlation with the defects.