I would like to make the case for separate Requirements/Use Cases
documents. For 2 reasons:
- a MUST in the requirements section doesn't mean the same thing as a
MUST in the main specification. The former applies to the specification
itself while the latter applies to a user agent. That could be confusing.
- Splitting makes the specification shorter. Use cases may still make
sense in the specification to help users, but they should be very simple
and just shown as examples.
feedback?
Max.