A single computational rule

A sequence of interactions between a system and an external actor

A description of the entire organization

A list of the software's internal components

To describe only the technical architecture

To record only defects found after release

To replace all software requirements specifications

To bring together the business requirements and set the stage for subsequent development work

Starting with a final list of no more than two classes

Eliminating classes that were not proposed by the sponsor

Initially generating a broad list of possible classes, then combining or grouping classes with similar needs

Identifying one class and then dividing it into every possible role

It consists of occasional users

Its members should not use the product for legal, security, or safety reasons

It has no interaction with the system

Its users need additional training

Use consistent wording for obligations and state priority separately

Mix them freely for stylistic variety

Avoid all modal verbs entirely

Use “should” for every mandatory behavior