Software errors and complexity: an empirical investigation0
Communications of the ACM
Software Engineering Economics
Software Engineering Economics
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Combination of software development effort prediction intervals: why, when and how?
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Measurements for managing software maintenance
ICSM '96 Proceedings of the 1996 International Conference on Software Maintenance
Introducing Measurable Quality Requirements: A Case Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
A Study of the Impact of Requirements Volatility on Software Project Performance
APSEC '02 Proceedings of the Ninth Asia-Pacific Software Engineering Conference
Requirements Evolution in the Midst of Environmental Change: A Managed Approach
CSMR '98 Proceedings of the 2nd Euromicro Conference on Software Maintenance and Reengineering ( CSMR'98)
Evaluation of a software requirements document by analysis of change data
ICSE '81 Proceedings of the 5th international conference on Software engineering
Software requirements: Are they really a problem?
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Types, distribution, and test and correction times for programming errors
Proceedings of the international conference on Reliable software
Requirements Volatility and Defect Density
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
Hi-index | 0.00 |
Requirements changes are normally reviewed by change control committees, who examine costs and consider consequences of additions, deletions and modifications to a piece of software. In order to predict the person effort required for a change, it is important to understand the reasons for the change as the nature of a change is characterized by its attributes which may be inherited and may be internal or external. The activities involved in supplying information for, and approving a requirements change can be time-consuming and complicated. As a result, there is a need to understand the relationships between requirements change characteristics and their attributes, and the level of effort. This paper presents a framework designed to address requirements change relationships. Our approach uses content analysis to study existing change control forms, and a detailed literature review. The contributions of this paper are two fold; firstly, we wish to improve the process of reviewing and approving requirements changes by change management committees. Secondly, we wish to assist project managers in better planning for requirements changes through more accurate prediction of person-effort required for a requirements change.