Creating Specifications
Under each requirements project, you can add functional specifications that define the project, its purpose, and its goals. A project can contain multiple specifications. To create specifications, you can use existing templates or create a new one. For example, prerequisites and functional specifications.
You can create specifications using existing templates or create a new one. For more information on specification templates, refer to the Creating Templates topic.
To create specifications, follow these steps:
- Go to Application Menu > Data Catalog > Requirements Manager.
- In the Requirements Workspace pane, right-click a project.
- Click Create Specification.
- Enter appropriate values to the fields. Fields marked with a red asterisk are mandatory. Refer to the following table for field descriptions.
- Click
.
The Create Specification page appears.
|
Field Name |
Description |
|---|---|
|
Specification Template Type |
Displays a list of available specification templates. Select an appropriate template. You can create templates and add artifacts to templates under Requirements Manager Settings. For example, Health Migration Template. |
|
Specification Template Description |
Displays the selected specification template type’s description. For example: The Health Migration Template is to capture functional and business requirements of the data migration project. |
|
Specification Name |
Specifies the name of the specification. For example, OrganMatch. |
|
Specification Version |
Specifies the version of the specification. For example, 1.01. Specification version is autopopulated. For more information on specification version, refer to the Configuring Version Display topic. |
|
Version Label |
Specifies the version label of the specification. For example, Beta. For more information on specification version label, refer to the Configuring Version Display topic. |
|
Specification Description |
Specifies the description of the specification. For example: The specification uses the Health Migration Template to capture functional and business requirements of the data migration project. |
|
Specification Owner |
Specifies the specification owner's name. For example, Jane Doe. |
|
Status |
Specifies the status of the specification. For example, Pending Review. |
|
Mail Comments |
Specifies mail comments that are sent to project users. For example: The specification uses the Health Migration Template. For more information on configuring email notifications, refer to the Configuring Email Settings topic. |
A new specification is created and added to the Specifications tree.
A tree of artifacts appears under the specification node. These are the artifacts that were added to the selected specification template.
Once a specification is added to a project, you can enrich it further by:
Right-click a specification in the Requirements Workspace pane to manage it. Managing specifications involves:
- Editing specifications
- Creating specification version
- Sharing specification link
- Exporting and importing specifications
- Copying specifications
- Deleting specifications
|
Copyright © 2024 Quest Software Inc. |