Useful References

  1. Ambler, Scott. 1995. "Reduce Development Costs with Use-Case Scenario Testing." Software Development 3(7):53–61.

  2. Collard, Ross. 1999. "Test Design." Software Testing and Quality Engineering 1(4):30–37.

  3. Gottesdiener, Ellen. 2002. Requirements by Collaboration: Workshops for Defining Needs. Boston: Addison-Wesley.

  4. Kulak, Daryl, and Eamonn Guiney. 2004. Use Cases: Requirements in Context, Second Edition. Boston: Addison-Wesley.

  5. Wiegers, Karl E. 1996. Creating a Software Engineering Culture. New York: Dorset House Publishing.

  6. Wiegers, Karl E. 2002. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley.

  7. Wiegers, Karl E. 2003. Software Requirements, Second Edition. Redmond, WA: Microsoft Press.

  8. Wiegers, Karl E. 2006. More About Software Requirements: Thorny Issues and Practical Advice. Redmond, WA: Microsoft Press.

Get Beautiful Teams now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial