(or: Requirements Analysis Document)

• Name of the project/product
• Date
• Version number
• Author(s)
• Responsibilities of every author
• Key changes since last version

Specification of Functional requirements.

Specification of Non-functional requirements (e.g. standards to be met, platform, memory requirements)

• Scenarios (optional)
• Use Case Model: It is important to define who the actors are, and to have a use case diagram summarizing all of the actors and use cases.
• Object Model, with class diagrams
• Dynamic Models: illustrate use cases with statechart and sequence diagrams.

navigational paths and screen mock-ups

A short definition of each concept (classes) used in the models.