Notes

As a requirements specifier I want to create a requirement so that I can specify a feature that we want the system under development to have. This will allow us to create correct marketing materials and also ensure that the detailed requirements and tasks support the planned features.

Scenario: Create requirement

Given that I have permission to create a requirement,

And am working in a current project,

When I choose “new requirement,”

And enter a name, description, and optional fields (release number, requirement type),

And choose “save,”

Then the system assigns a unique number to the requirement,

And the requirement's status is “new,”

And the requirement is stored in the current project,

And a transaction is entered into the requirement's history indicating that it was created, when, and by whom,

And the requirement is available for retrieval and updating.

Details:

The name can be up to 100 characters and must be non-blank.
The description size is virtually unlimited and must be non-blank.
There is an optional release number. The release numbers are defined in the current project. The release number, if entered must be one of the release numbers in the current project. If the current project has a current release, then this release is the default value for the release number, however this may be overridden, including not to have a release number.
A requirement has an optional Requirement Type field that identifies the type of requirement, if it is relevant to the project. This is completely up to the user. By default, this field is blank. Possible choices for this are: Epic, Theme, User Story, Non-Functional, and Scenario.
Requirements have a priority associated with them. The priority is either blank (empty), High, Medium, or Low.
Requirements may contain other requirements. These are sub-requirements that must be satisfied (completed) in order for the containing requirement to be considered satisfied. Initially, this is an empty set.
Requirements may also contain notes. How these are use is up to the end user. Initially, a requirement has an empty set of notes.
Requirements may be scheduled for an iteration. By default, the iteration is empty.
Requirements have an actual effort value associated with them. This value is initially zero.
Requirements may be assigned to zero or more team members. Initially, this is an empty set.
Requirements have a estimate associated with it. This is a non-negative integer value. Initially, the value is zero.
Requirements have development tasks associated with them. Initially, this is an empty set.
Requirements have acceptance tests associated with them. Initially this is an empty set.
Requirements have attachements associated with them. An attachment can be any file such as an image, archive, and so on.
Requirements have a history (log) associated with them. Each history / log record indicates a change to the requirement. All log records have a timestamp, user who performed the action, and text indication the action.