5.7. Recommended Resources
References related to requirements with use cases are covered in a subsequent chapter. Use-case-oriented requirements texts, such as Writing Effective Use Cases [Cockburn01] are the recommended starting point in requirements study, rather than more general (and usually, traditional) requirements texts.There is a broad effort to discuss requirementsand a wide variety of software engineering topicsunder the umbrella of the Software Engineering Body of Knowledge (SWEBOK ), available at www.swebok.org.The SEI (www.sei.cmu.edu) has several proposals related to quality requirements. The ISO 9126, IEEE Std 830, and IEEE Std 1061 are standards related to requirements and quality attributes, and available on the Web at various sites.A caution regarding general requirements books, even those that claim to cover use cases, iterative development, or indeed even requirements in the UP:
Most are written with a waterfall bias of significant or "thorough" up-front requirements definition before moving on to design and implementation. Those books that also mention iterative development may do so superficially, perhaps with "iterative" material recently added to appeal to modern trends. They may have good requirements elicitation and organization tips, but don''t represent an accurate view of iterative and evolutionary analysis.
Any variant of advice that suggests "try to define most of the requirements, and then move forward to design and implementation" is inconsistent with iterative evolutionary development and the UP.