Baseline Requirements

Version control is an important part of document management. Companies may use their own notation for version such as x.y or x.y.z or so. Version management will help to see how a group of requirements are changed together on the entire set of requirements. History of a requirement helps to know how that particular requirement changed over a period of time.

Current Draft Version means that the version code will be used for any new requirements or newly edited requirements.

Baselined Version means, that the version can no more be used to add requirements or editing requirements.

Navigate to Settings -- Lookup codes -- Baseline Requirement Version.

• You need to have one curent draft version to add or edit requirements.
• Select Project from the Project list box.
• Set the radio button ON "Set a new "Current Draft Version"
• When this is done, the list of versions that are added in lookup codes, will appear in the Version list box.
• Select the appropriate version to be made Current from the list box.
• Enter baseline notes.
• Click on Save Changes.
• The details will appear on the right hand side grid of the screen.

At any given point of time, only one version can be made current.

When users add a new requirement, only the current draft version will appear in the version list box. When a user edits an existing requirement with older version, the latest current draft version will appear in the version list box.

When you want to freeze a particular draft version, you need to baseline the same.

• Select Project from the Project list box.
• Set the radio button ON "Mark "Current Draft Version" as "Base lined Version"
• When this is done, the current draft version, will appear in the Version list box.
• Select the appropriate version to be made Baseline from the list box.
• Enter baseline notes.
• Click on Save Changes.
• The details will appear on the right hand side grid of the screen.