Starting Improvement of Requirements Engineering Processes: An Experience Report
PROFES '01 Proceedings of the Third International Conference on Product Focused Software Process Improvement
A practitioner's guide to light weight software process assessment and improvement planning
Journal of Systems and Software
A Framework for Predicting Person-Effort on Requirements Changes
Proceedings of the 2006 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the fifth SoMeT_06
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Collaborative resolution of requirements mismatches when adopting open source components
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
| Hi-index | 0.00 |
In this paper a case study on improving requirements engineering is presented. Improving requirements engineering was initiated in a department at Ericsson Eurolab after an analysis had shown that many of the problems in software development had their root cause in insufficient understanding of the customer and in unclear requirements. A method - in respect to Tom Gilb who supported us in this field - called Gilb Style was introduced. This method focuses on quality (or non-functional) requirements quantification strict separation between design and requirements constraints and assumptions After a year of experience and several projects using this method, the findings are presented. The biggest benefit in using this method is a change of culture towards requirements. This change is not limited to requirements specifications for software but includes e.g. requirements on internal service functions. The common understanding of requirements has drastically increased. Several positive side effects include more effective inspections, introduction of weekly reviews, simpler definition of test cases. The biggest problems were communication problems to (internal) customers, who did not participate in the introduction of the method.