Capturing requirements - SRS Vs Use cases

An SRS provides a consistent structured format consisting of a number of separate sections for capturing a wide range of information about your requirements. The strength of an SRS is that the extensively-identified set of topics makes sure important areas are addressed.


Use cases describe step-by-step how an actor interacts with the system, where an actor is usually the user, but could be another system or a piece of hardware. Use cases are a widely used and highly regarded format for capturing requirements. Because of their concrete step-by-step format, they are easy for a variety of stakeholders to understand in essentially the same way.


Use cases vs. SRS for requirements gathering.

Attitude towards quality

"With software increasingly underpinning business-critical applications, sloppy attitudes toward quality from the people who make it is no longer acceptable."

A software quality crisis is brewing

Actually Doing It - An Extreme Programming practice

"It is entirely do-able without a huge amount of extra effort to unit test 95%+ of your code. And it's almost as do-able to write all those tests first."

New XP Practice: "Actually Doing It"