Traditional requirements management shortfalls
Traditional waterfall methodologies produced a requirements document
by selecting a set of business analysts and subject matter experts who
would spend some number of months creating a (theoretically) complete
requirements statement.
In most projects today, a lapse of several months would either invalidate
these requirements or miss the market window altogether.
Internet speed and agility mean that projects must be quick to market and
must evolve continuously to meet the changing needs and demands of their
users.
Can Requirements be Agile?
In a word, yes, but requirements must also be effective, consistent,
and must be traceably adaptable to changing conditions.
Top level functional
requirements must be associated with a top-level use case.
As each use case decomposes into detailed use cases, these should
associate with sub-level requirements. Each requirement must be
associated with at least one test, and each test must map to a requirement.
Requirements may have parents, children, and dependencies. These
relationships are illustrated below.
