Documente Academic
Documente Profesional
Documente Cultură
The For Import tab contains columns for various Requirements Fields that can be imported using ALM's Excel Add-In tool. Some fields in this tab use Data Validation a
Conditional Formatting to assure successful import into ALM.
The Excel vs. ALM Fields tab compares those Requirements fields recommended by standard Requirements Engineering documents, and the associated ALM Fields.
Standard fields are highlighted in blue, ALM fields in red. ALM fields highlighted in yellow require special consideration, as they are either generated by ALM, are unne
in a database environment, or have a different usage than the Standard field.
The Excel vs. ALM Fields tab also lists special characteristics of both the ALM fields and the associated fields in the spreadsheet. For example, since the ALM "Name" fi
limited to 255 characters, the Excel field is formatted to turn the text in this cell red when the content exceeds 255 characters. This is accomplished using conditional
formatting.
In addition, some ALM fields, such as "Requirement Type" are validated against look-up lists in the ALM tool. These look-up lists have been recreated in the Template
Controls tab of this spreadsheet, and are used as part of Excel's Data Validation process for fields on the For Import tab. The lists on the Template Controls tab shoul
modified to include any customizations made to the original lists in ALM. This allows Requirements Analysts to assure that data entered in the spreadsheet will match
allowed values in ALM.
In ALM, requirements are presented in a directory tree. This highest level folder is named "Requirements". If no path is specified during the import pro ce
imported requirements will be placed in the Requirement folder.
To specify the location of requirements, use the path cell in the Excel spreadsheet. First, list the first folder directly under the Requirement parent folder,
list all subsequent folders or requirements, separated by a forward slash.
For example, to import "Requirement A1.1" in the sample below, the path would be as follows:
OASSIS\TEST CONVERSION TO TESTS\Requirement A\Requirement A1
Requirement Type Requirement Name
Requirement Description
Comments Requirement Priority
Author Review Status
Path
Standard Field Names Requirement Type
Complex DB Configuration
ALM Field Database Name
RQ_TYPE_ID is a 10 character
number, generated based on
field entries.
RQ_REQ_PRIORITY
70 char
Lookup List: Priority
Requirement History
Author
(Managed in ALM)
RQ_REQ_AUTHOR
70 char
Lookup List: User List
RQ_DEV_COMMENTS RQ_REQ_REVIEWED