Mastering the requirements process
Mastering the requirements process
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Principles of Corporate Finance with Cdrom
Principles of Corporate Finance with Cdrom
Communications of the ACM - Spam and the ongoing battle for the inbox
TOWARDS A SERVICE-ORIENTED DEVELOPMENT METHODOLOGY
Journal of Integrated Design & Process Science
Extending FeatuRSEB with Concepts from Systems Engineering
ICSR '09 Proceedings of the 11th International Conference on Software Reuse: Formal Foundations of Reuse and Domain Engineering
Value based management and agile methods
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
A value-based approach in requirements engineering: explaining some of the fundamental concepts
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
| Hi-index | 0.00 |
Managing requirements for business value? What's there to manage? Aren't they just...there?" Such perplexity was perfectly understandable in the good old days, when all you had to do was get the requirements from your customer, design your system, and produce one of those awful conformance matrices that demonstrated that you had implemented each and every one of the requirements in your system. Against this dreary backdrop of conformance matrices and the like, it is indeed hard to imagine a role for requirements in the development and execution of business strategy. But, as the song says, the times, they are a changin'. We are now looking outside the traditional boundaries and developing ways of getting maximum business value from our investment in requirements. This paper discusses three ways of realizing this value: managed requirements process, requirements agility, and contractual innovation