Creating products customers demand
Communications of the ACM
Improvement of software process by process description and benefit estimation
Proceedings of the 17th international conference on Software engineering
Software process improvement: methods and lessons learned (tutorial)
ICSE '97 Proceedings of the 19th international conference on Software engineering
Software process improvement experience in the DP/MIS function: experience report
ICSE '94 Proceedings of the 16th international conference on Software engineering
Software process improvement: practical guidelines for business susccess
Software process improvement: practical guidelines for business susccess
Toward computational support for software process improvement activities
Proceedings of the 20th international conference on Software engineering
Proceedings of the 22nd international conference on Software engineering
European experiences with software process improvement
Proceedings of the 22nd international conference on Software engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Software Process Improvement at Hughes Aircraft
IEEE Software
SEL's Software Process Improvement Program
IEEE Software
Software Process Improvement At Raytheon
IEEE Software
How Software Process Improvement Helped Motorola
IEEE Software
Introducing Measurable Quality Requirements: A Case Study
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Hi-index | 0.00 |
Defining and managing customer requirements is becoming increasingly important in product development. Many software organizations are interested in improving their requirements engineering processes, but they do not know how and where to begin. This report describes the experiences of two Finnish organizations that have started to develop their requirements practices systematically. To guide these development activities, software process improvement procedures and guidelines published in the literature were adjusted and applied. The most important lesson learned was that introducing requirements engineering can require a change of culture and not merely a change of process and technology. The change of culture firstly requires that product development personnel fully understand the reasons for documenting requirements from a customer's point of view. Secondly, they must commit to defining and managing customer requirements systematically.