Glossary

NI Requirements Gateway 2018 Help

Edition Date: March 2018

Part Number: 371714F-01

»View Product Info
Download Help (Windows Only)

A

attribute Describes a requirement. An attribute has a name and a Boolean, numeric, or string value. A requirement can only have one attribute with a specific name. Use attributes and their values when you define filters, which specify the requirements to analyze or display.

C

covering document A document that contains references to requirements defined in another document.
covering link A link between documents on the Project Configuration pane of the Project pane of the Configuration dialog box. A covering link indicates that one linked document covers requirements in another linked document. See also non-covering link and link.

D

derived requirement A requirement that is not defined at the most upstream level, but that is included in a document that covers other upstream requirements. Derived requirements must be covered by another downstream document for the project to cover 100% of all requirements. Requirements Gateway displays an arrow icon to the right of a derived requirement and all parent elements of the requirement.
downstream document A document that contains references that cover the requirements in a document you select in the Coverage Analysis or Impact Analysis view. When you use the Project pane of the Configuration dialog box to specify a covering link in a project, a downstream document points to an upstream document.

E

entity An element that must contain a reference to a requirement. If a defined entity does not contain any reference, Requirements Gateway displays a warning message.

F

feature A set of requirements, macro-requirements, or sub-features in a project.
folder A mechanism for gathering documents related to the same level of a process or organizing a large project.

L

link A non-covering relationship to a requirement or reference to a section or entity. The term link also refers to an arrow between documents on the Project pane of the Configuration dialog box that specifies a covering or non-covering relationship between the documents. See also covering link and non-covering link.

M

macro-requirement A requirement that contains other requirements. The contained requirements inherit any attributes, text, or links the macro-requirement defines. If a downstream element directly references a macro-requirement, the element also references the contained requirements.

N

non-covering link A link between documents on the Project Configuration pane of the Project pane of the Configuration dialog box. A non-covering link indicates a relationship between project documents that is not associated with the coverage of a requirement. See also covering link and link.

P

project document source file The source file you specify for a project document. For example, you specify a LabVIEW VI as the source file for a project document of the LabVIEW type. Some document types specify that you can select more than one source file for a project document.

R

reference A statement in text that indicates the coverage of a macro-requirement, requirement, or derived requirement.
reference attribute Describes the type of coverage for a reference, such as partial coverage or provisional coverage. An attribute has a name and a Boolean, numeric, or string value. A reference can have only one attribute with a specific name.
regular expression A mechanism to select specific text from within a string. An expression contains literal characters, wildcard characters, and operators to locate text patterns in the string. For example, the expression REQ[0–9]+ matches any text that contains the characters REQ followed by one or more digits. Requirements Gateway implements regular expression pattern-matching using the same syntax and semantics as Perl. Refer to Chapter 5, Customizing Types, of the Getting Started with NI Requirements Gateway manual for an example of using regular expressions to match patterns in text.
release A set of features in a project.
requirement Expresses a need or constraint, such as a technical constraint, cost, or deadline.

S

section A hierarchical element that represents structure within a document. Sections represent heading levels in a text or Microsoft Word file, objects within a file or database, or files and directories on disk.

T

text Descriptive wording associated with a section, entity, requirement, or attribute.
type Defines how to select external files that represent a document, read the content of the external files, interpret the content as elements for managing requirements, and display the elements of the document in the main window.

U

upstream document A document that contains requirements that a document you select in the Coverage Analysis or Impact Analysis view covers. When you use the Project pane of the Configuration dialog box to specify a covering link in a project, a downstream document points to an upstream document.

WAS THIS ARTICLE HELPFUL?

Not Helpful