Library

Select one of the listed libraries.

By default, Verifier displays all the available libraries.

Cells and Views

This section provides options to specify

Cell list with:

• Use check box for each cellview in the list
• Cell and View names
• History drop-down list for each cellview in the list

Select the Use check box of the implementation cellviews. Also select the history you want to use with each selected implementation cellview from its The History drop-down list. Verifier will display the tests and outputs of the selected history in the implementations pane of the Setup tab, which you can map to requirements.

You can click Use All to select all the available cellviews as the implementation cellviews. Click Use None to clear all the selections.

You can open a cellview directly from this form. For this, select a cellview entry and click Open.

Create Requirements

Select Create Requirements to create the requirements hierarchy corresponding to the selected implementation cellviews. The auto-created requirements are also mapped to their corresponding implementations.

Library

Select one of the listed libraries.

By default, all the available libraries are displayed.

Cell

Select one of the listed cells.

By default, all the available cells are displayed.

View

Select one of the listed views.

By default, all the available views are displayed.

You specify the library, cell, view of the type maestro, adexl, or adestate,and the cell history, to add that cellview as an implementation. If you select an adexl or adestate cellview, the cellview is first migrated as a verifier cellview and then added as an implementation cellview in Verifier.

History

Select one of the listed histories.

By default, all the available histories are displayed.

Priority

Select the priority for the simulation run.

The default is 0.

Est Run Time

Select the estimated run time for the implementation.

The default is 0.

Run Plan Mode

Select to enable the run plan mode.

By default, Verifier displays the run plan mode check as disabled.

Run

Select to enable the simulation run.

By default, Verifier displays the run check as enabled.

Implementation set name

Lets you specify the name of the new implementation set.

Library

Includes the library containing the Verifier cellview.

Cell

Includes an available cell from the specified library.

View

Includes an available view from the specified library cell.

Source

This section provides options to specify the source settings for the cellview to be opened.

Library

Includes the library containing the Verifier cellview.

Cell

Includes an available cell from the specified library.

View

Includes available view from the specified library cell.

If you specify a Cell or View that does not exist in the specified Library, the following options are enabled:

Create Empty View

Specifies if you want to open an empty Verifier setup.

Import Requirements

Specifies if you want to import only requirements from a CSV file or Excel file.

The Import Form is displayed.

Add Implementations

Specifies if you want to add only implementations from an existing cellview of the type maestro.

The Edit Typical Value Setup Form is displayed.

Corner name

Specifies the enabled corner name that contains the typical related items.

Implementation Typical Setup

This section lists the editable fields that are available in the form.

Name

Specifies the name for the variables, parameters, or model files. The name must be a unique one-line string text without spaces.

CurrentValue

Specifies the value from the global data settings or corner in the implementation cellview.

Typical

By default, the value is taken from the Tools – Setup Typical Value form. You can edit it based on the current value.

Shortcut menu commands

This section lists the shortcut menu commands that are available in the form.

Overwrite Typical

Overwrites the value of Typical with that of the Current Value.

Overwrites only the numeric value for variables and parameters.

Imported Files

This section displays the list of files that have been imported in the current cellview.

File

Displays the relative path to an imported file.

The settings in this form can be saved only if a file has been imported in the cellview.

What to Save

This section lets you specify the properties.

Property

Lets you select the properties to be exported.

The available properties are;Parent, ID, Title, Type, MinSpec, MaxSpec, Unit, Owner, Scope, Domain, Description, Deadline, Overall Status, Mapping, History, Result Data Age, Min Value, Typical Value, Max Value, Passed, Failed, No Results, Unmapped, Verification Space, Coverage, CellviewHolder, Disabled, FailCoverage, Hier, NoneCoverage, PassCoverage, ReadOnly, ReadOnly, Signoff, StatusDescription, Yield, Min, Max, Mean, StandardDeviation, SigmaToTarget, Cpk.

The exported file is saved in the following format;

<name_of_imported_file>_<date as mm_dd_yyyy>_<time as hh:mm:ss>.csv

Summary Information

Adds a summary that includes header row information, author name, the creation date, and a summary of the results above the field information in the exported file.

Export to Setup Library

Saves the exported file in the Setup Library document folder.

CSV file

Exports the mappings to a CSV file.

Excel file

Exports the mappings to a Microsoft Excel file.

Browse

Lets you specify an existing file or a new user-defined filename in CSV or Excel format.

Imported Files

This section displays the list of files that have been imported in the current cellview.

File

Displays the relative path to an imported file.

The settings in this form can be saved only if a file has been imported in the cellview.

What to Save

This section lets you specify the properties.

Property

Lets you select the properties to be exported.

The available properties are: Parent, ID, Title, Type, MinSpec, MaxSpec, Unit, Owner, Scope, Domain, Description, Deadline, Overall Status, Mapping, History, Result Data Age, Min Value, Typical Value, Max Value, Passed, Failed, No Results, Unmapped, Verification Space, Coverage, CellviewHolder, Disabled, FailCoverage, Hier, NoneCoverage, PassCoverage, ReadOnly, ReadOnly, Signoff, StatusDescription, Yield, Min, Max, Mean, StandardDeviation, SigmaToTarget, Cpk.

The exported file is saved in the following format;

<name_of_imported_file>_<date as mm_dd_yyyy>_<time as hh:mm:ss>.csv

Summary Information

Adds a summary that includes header row information, author name, the creation date, and a summary of the results above the field information in the exported file.

Export to Setup Library

Saves the exported file in the Setup Library document folder.

Imported Files

This section displays the list of files that have been imported in the current cellview.

File

Displays the relative path to an imported file.

The settings in this form can be saved only if a file has been imported in the cellview.

What to Save

This section lets you specify the properties.

Property

Lets you select the properties to be exported.

The available properties are;Parent, ID, Title, Type, MinSpec, MaxSpec, Unit, Owner, Scope, Domain, Description, Deadline, Overall Status, Mapping, History, Result Data Age, Min Value, Typical Value, Max Value, Passed, Failed, No Results, Unmapped, Verification Space, Coverage, CellviewHolder, Disabled, FailCoverage, Hier, NoneCoverage, PassCoverage, ReadOnly, ReadOnly, Signoff, StatusDescription, Yield, Min, Max, Mean, StandardDeviation, SigmaToTarget, Cpk.

The exported file is saved in the following format;

<name_of_imported_file>_<date as mm_dd_yyyy>_<time as hh:mm:ss>.csv

Summary Information

Adds a summary that includes header row information, author name, the creation date, and a summary of the results above the field information in the exported file.

Export to Setup Library

Saves the exported file in the Setup Library document folder.

File

This section provides options to specify the source filename that contains the requirements you want to include during the import process.

CSV file

Includes the requirements from a CSV file.

The File, Rows, Header Columns, and Get Contents From File group boxes are displayed.

Excel file

Includes the requirements from a Microsoft Excel file.

The File, Sheet, Rows, Header Columns, and Get Contents From File group boxes are displayed.

Sheet

This section provides options to specify the settings for importing Excel sheets.

Sheet Names

Displays the sheets in the Excel file that will be imported. By default, all sheets are included.

This option is displayed when you click Excel file.

The default is All. The value changes when you deselect one of the sheets from the Sheets in File group box.

Get Sheets

Retrieves all the non-empty sheets that are available in the Excel file specified in the File group box. The included sheets are displayed in the Sheets in File group box.

This option is displayed when you click Excel file.

By default, all sheets are included.

Sheets in File

Lets you select one or more of the listed sheets that are retrieved from the specified Excel file.

This option is displayed when you click Excel file.

By default, all sheets are included.

Select All

Lets you select all the non-empty sheets in the Excel file that contains the requirements you want to include.

This option is displayed when you select Excel file and click Get Sheets and the specified file contains non-empty sheets.

By default, all sheets are included.

Clear All

Lets you deselect all the non-empty sheets in the Excel file.

This option is displayed when you click Excel file.

Rows

This section provides options to specify the valid rows of requirements to be imported.

Header row

Displays when you click CSV or Excel file and then choose Get header definition from row.

Specify the number of row that contains the headers of requirements.

By default, Verifier chooses one top header row to be ignored and none of the bottom most rows to be ignored.

Ignore the rows containing invalid properties

Specifies if any rows that contain invalid properties must be ignored during the import process.

Use folded format for composite requirements

Uses the row preceding the header as composite header. The data in folded format is converted into composite requirement structure based on the composite header specified in the file.

This option is displayed only when you select the Excel file format for import. Selecting this option disables the Map source columns to Verifier requirement headers option.

Header Columns

This section provides options to specify settings related to headers from the imported file and the requirements available in the cellview.

Get header definition from row

Select the row in the source file that contains the headers of the requirements. The headers in the source file must map to the Verifier headers in the given sequence:

Parent,ID,Title,Type,MinSpec,MaxSpec,Unit,Owner,Description

Map source columns to Verifier requirement headers

Select to map the source columns to the Verifier requirement columns.

You can choose the number of columns to be included from the Number of Columns to Be Loaded group box. You can then map the column number in the source file to the Verifier requirements headers using the mapping table.

Number of Columns to Be Loaded

This section provides options to specify the valid rows of requirements to be imported. This group box is displayed when you select CSV file or Excel file in the File group box and then click Map source columns to Verifier requirement headers.

Columns

Lets you specify the number of columns that must be loaded into the Verifier session. The headers of these columns are the key fields from the specified file that are used to create requirements.

By default, Verifier is set to import the data from the first nine columns of the source file for the following nine requirement headers.

Parent,ID,Title,Type,MinSpec,MaxSpec,Unit,Owner,Description

You can modify the number of columns as well as the column that must be loaded from the imported file.

Get Columns

Displays all the non-hidden and mapped columns from the first selected or non-empty Excel sheet. The headers of these columns are the key fields from the specified file that are used to create requirements.

This option is displayed when you click Excel file.

Get Contents From File

This section provides options to view and validate the top-most rows of data from the specified file.

Lets you view some rows in the source file to ensure that you have specified the correct file and mapping details. The number of rows that will be shown in this field is Header Row + 1.

This option is displayed when you click CSV file or Excel file.

By default, this option is deselected.

File name

Specifies the name of the SDB file that must be imported in the Setup Library. The field cannot be left empty.

Merge

Merges the new and modified settings from the SDB file into the Setup Library. No visual indicators are displayed.

Compare & Update

Opens the Compare and Update Settings form where a comparison of the Setup Library and the SDB file settings is displayed. All differences are color-coded and appropriate tooltips are displayed.

Done

Closes the Compare and Update Settings form.

Library

Includes the library containing the Verifier cellview.

Cell

Includes an available cell from the specified library.

View

Includes an available view from the specified library cell.

Operation

Lets you select one of the available modes for importing a cellview.

Copy

Specifies that the cellview details must be added in edit mode in the current session.

The available options for the copy operation are:

• Implementations and Mappings
• Requirements

Reference

Specifies that the cellview details must be added in read-only mode in the current session.

The following options for the reference operation are enabled by default and cannot be changed:

• Implementations and Mappings
• Requirements

Data

Lets you import the selected data while importing a cellview.

Implementations and Mappings

Specifies that all implementations and mappings within the cellview must be imported.

Requirements

Specifies that all requirements within the cellview must be imported.

File

Displays the name of the imported file.

Update Action

Specifies the list of actions available for the imported file.

• None: Specifies that no action needs to be taken.
• Merge: Specifies that the variables, parameters, model files, requirements, and implementations from the imported file must be merged into the current cellview.
• Compare: Specifies that the variables, parameters, model files, requirements, and implementations from the imported file must be compared with the current cellview.

Command buttons

This section lists the command buttons that are available in the form.

Add

Lets you add a file by importing it.

Remove

Lets you remove an imported file.

Compare and Merge

Displays the differences in the Show Differences in Requirements for file relative_filename form. All differences are displayed in blue text.

View File

Displays the imported file in a dialog box.

Settings

Lets you modify the import settings in the Import form.

General

This page includes the general options that are applicable globally in a Verifier session, such as specification search order and coverage.

Planning

This page includes the common options related to planning of requirements and implementations, expiration period of implementations, Monte Carlo statistical outputs, and reliability outputs.

Run

This page includes the miscellaneous options, and options related to history management, and environment variables.

Distribution

This page includes the options related to run-related controls and time.

Reporting

This page includes the options related to creating, opening, and managing reports.

Specification Search Order

This section provides options to let you specify the search order to be used for specifications.

Requirement specifications and check to implementation

Check if the specification values set in the requirements match the specification values set in the corresponding implementations. If the values match, Verifier uses those values to determine the verification status of the requirement. Otherwise, the specification check for that requirement fails.

• The implementation specification is always used when the requirement specification is an expression or a string because Verifier cannot interpret the expressions. For example, if the requirement specification is a valid expression >(0.5*VAR("vdd")) and the implementation specification is >(0.51*VAR("vdd")). This is a typical case of Spec Check Fail and the implementation specification is used even if the requirement specification is valid expression.
• Verifier does not check the syntax of expression. You can overwrite the implementation specification with a requirement expression or string specification that has invalid syntax, but the status of that output will be 'Fail' after run.

Environment Variable: reqspecscheckunits

Requirement specifications

Use the specification values set in the requirements to determine their verification status. If a requirement does not have any specification values, use the values set in the mapped implementations.

Environment Variable: reqspecs

Implementation specifications

Use the specification values set in the implementations to determine the verification status of the mapped requirements. If an implementation does not have any specification values, use the values set in the requirement mapped to that implementation.

Environment Variable: reqspecs

Check unit

Select this option to check if the specification units set in the requirements and their corresponding implementations match.

• All the implementations mapped to a requirement of the type Spec Pass must have the same specification values.
• A check for specification units is only done when both the requirement and the implementation contain a unit value.

Environment Variable: reqspecscheckunits

Evaluate Metric Prefix

Specifies settings of the metric prefix for specification comparison and evaluation. If enabled, the metric prefix from the specification unit is used for specification comparison and evaluation.

• All the implementations mapped to a requirement of the type Spec Pass must have the same specification values.
• By default, the specification units are not used in the specification comparison. They are used for documentation purposes and when the requirement and implementation specifications are compared.

For more information, see Evaluation of Metric Prefix.

Environment Variable: evaluateMetricPrefix

Coverage

The following options let you specify the coverage settings.

Weighted average for hierarchical coverage

Ensures that weighted average is used to calculate coverage hierarchically.

Environment Variable: weightedAverageForCoverage

Show results for Verification Space parameter conditions

Enables result reporting for verification space parameter conditions.

Environment Variable: resultForSpaceCoverage

Current User Name

The following option lets you specify the user-specific settings.

Specifies the current user name that Verifier should consider when processing requirements with owners.

The current user name is also the default owner of new requirements.

By default, Verifier displays the login identity of the current user in this field. If required, you can change the user name.

Common Options

This section provides options to specify commonly used planning settings.

Show cross mapping at cursor

Indicates the record mapped with the record currently highlighted by the mouse cursor.

When this option is enabled, you can view the implementation mapped with a requirement by placing the pointer over the requirement. That requirement and the mapped implementation are highlighted in light gray. Similarly, you can place the pointer over the implementation to highlight the mapped requirement.

Environment Variable: enablecrossselection

Map only one requirement to one implementation

Ensures that a requirement can be mapped to only one implementation.

Environment Variable: mappingonetoone

Create requirements for outputs with no specification values

Ensures that a requirement is created for outputs for which you have not specified any specification values.

Environment Variable: createRequirementsWithNoSpec

Include disabled run, reliability, test, or output for implementation

Includes disabled tests when you import implementations. If you select this check box and choose Show – Disabled in the Requirements pane, it loads all enabled and disabled runs, reliability analyses, tests, or outputs. If this check box is not selected, it loads only enabled runs, reliability analyses, tests, or outputs.

Environment Variable: importDisabledTests

Allow editing the enabled or disabled state for implementation run or test

Enables editing of the enabled or disabled state for implementation runs or tests.

Expiration Period of Implementation Results (in days)

This section provides options to specify the expiration limit for implementation results.

Specifies the implementation as outdated when the results are older than the specified expiration period.

You can specify the value as 0 to disable the expiration check. The upper limit for this field is 365. Therefore, it always shows the implementation as outdated when the loaded results are older than 365 days.

By default, Verifier displays No expiration period in this field. If required, you can change the value.

Environment Variable: impresexpperiod

Monte Carlo Statistical Outputs

This section provides options to select Monte Carlo statistical outputs during simulation runs.

Yield

Environment Variable: displayStress

Mean

Environment Variable: displaymean

StandardDeviation

Environment Variable: displaystandarddeviation

Cpk

Environment Variable: displaycpk

Min

Environment Variable: displaymin

Max

Environment Variable: displaymax

SigmaToTarget

Environment Variable: displaysigmatotarget

Reliability Outputs

This section provides options to specify settings for reliability outputs.

Show reliability outputs

Fresh

Displays the reliability outputs for fresh tests.

Environment Variable: displayFresh

Stress

Displays the reliability outputs for stress tests.

Environment Variable: displayStress

Aged

Displays the reliability outputs for age tests.

Environment Variable: displayAge

Show outputs for ages

All

Displays the reliability outputs for all ages.

Environment Variable: displayRelOutputAges

Last

Displays the reliability outputs for the last age.

Environment Variable: displayRelOutputAges

Miscellaneous

This section provides options to specify miscellaneous settings for simulation runs.

Debug mode, open implementation interface

Runs implementations in debug mode, where the implementation interface, such as ADE Assembler, is displayed to help monitor the runs. When you select this option and run simulations, the ADE Assembler interface stays open.

Environment Variable: impuimode

Create ADE Assembler datasheet at run or reload time

Creates a datasheet at run time or reload time. This datasheet is saved and referenced only when you create the HTML report in Verifier.

Environment Variable: autoCreateDataSheet

History Name

This section provides options to specify custom history names.

Prefix

Adds a prefix to the ADE Assembler history name.

The available run modes in ADE Assembler are:

• Single Run, Sweeps and Corners => srsc
• Run Plan => runplan
• Monte Carlo Sampling => mc

Append date

Adds the current date as a suffix to the history name.

If enabled, the history name is saved in the format historyNamePrefix_srsc_date.0.RO.

Example: verifier_srsc_20190812.0.RO.

Append time

Adds the current time as a suffix to the history name.

If enabled, the history name is saved in the format historyNamePrefix_srsc_time.0.RO. Selecting both Append date and Append time displays the history name in the format historyNamePrefix_srsc_date_time.0.RO.

Example: verifier_srsc_20190812_140245.0.RO.

Report Identical History

This section provides options to check histories in ADE Verifier and ADE Assembler.

Report identical histories before run

Performs implementation runs and loads external results only if there are changes since the last run.

Environment Variable: usereportidenticalhistory

Check the following:

Assembler setup

Performs checks on the Assembler setup and test states. This option is enabled by default.

Design (schematic/configurations)

Performs checks on schematic and configuration views for each test.

Simulation files (model/definition files)

Performs checks for model and definition files.

Verifier runs implementations based on the settings in the Check the following items group box.

Environment Variables

This section provides options to specify settings for defining environment variables.

Enabled

Lets Verifier use the OverrideValue for running simulations.

Tool.[Partition]

Specifies the name of the tool and its optional partition.

Name

Specifies the name of the environment variable.

Type

Specifies the type of the environment variable. Possible values: string, int, boolean, cyclic, float, toggle.

CurrentValue

Specifies the currently used value of the environment variable set through the .cdsenv or .cdsinit file, or through the envSetVal SKILL function ().

OverrideValue

Specifies the value of the environment variable used for the simulation in ADE Verifier.

This value overwrites the current value before running a simulation and restores the current value after the simulation is complete.

Run Controls

This section provides options to specify global settings for managing simulation runs using run setups.

Run Setup

Specifies the name of the run setup that controls the rest of the fields in the Run Controls group box. It loads existing run setups from the .cadence directories found using the Cadence Setup Search File (CSF) mechanism. If a run setup does not exist, you can specify a name in this field and save it as a new run setup.

Save

Saves the specified settings in the Run Controls group box as a run setup to the .cadence directories found using the Cadence Setup Search File (CSF) mechanism.

Delete

Deletes the selected run setup.

Maximum implementations to run in parallel

Specifies the maximum number of implementations that can run in parallel per Verifier session.

Running multiple implementations in parallel might require more resources. Therefore, consider your system capabilities when increasing the maximum number.

The default value of this field is 1 because, by default, Verifier is not set to run multiple implementations in parallel.

Environment Variable: simparallelcount

Maximum batch runs to start in parallel

Specifies the maximum number of external virtuoso processes to launch, where each virtuoso process runs Verifier simulations.

The default value of this field is 1 because, by default, Verifier is not set to run multiple implementations in parallel.

Executable or script for batch runs

Specifies the external program to use when running Virtuoso with Batch Run. For new cellviews, this field is populated from the environment variable settings. Existing cellviews use the setting in the preferences.

Example:

bsub -K -P "IC:6.1.8:RD:test" -R "select[OSREL==EE60]" -R "rusage[mem=3000]" -W 200:0 -sp 50 -o /tmp/bsub_job_$$ virtuoso

To know more, see Distributing Batch Simulation Runs.

The value of this field is also used for other Virtuoso processes started by Verifier, such as child processes started in the project directory setup.

To know more, see Histories from the Project Directory Setup.

Environment Variable: binaryName

Number of retries

Specifies the number of times Verifier retries running a failed simulation. Clicking the Stop button cancels the specified retries.

Environment Variable: numberOfRetries

Retry time threshold

Specifies the retry time threshold for a failed simulation run in the <d><hour>:<minute>:<second> format.

The simulation is retried only if the time taken by the previous simulation is less than the specified value. The default is 00:00:00.

A few examples of the time format are as follows:

• 1d (1 day)
• 42 (42 seconds)
• 2:15:10 (2 hours, 5 minutes and 10 seconds)
• 4h (4 hours)
• 1d 2:15:10 (1 day, 2 hours, 15 minutes and 10 seconds)

Environment Variable: retryTimeThreshold

Override job control mode

Overrides the job control mode of all the implementations with the mode selected from the drop-down list.

Environment Variable: impJobControlMode

Override simulation job policy

Overrides the simulation job policy for all the implementations that use the ICRP and LSCS modes.

Environment Variable: impjobpolicy

Override netlisting job policy

Overrides the netlisting job policy for all the implementations that use LSCS mode.

Environment Variable: impNetlistingJobPolicy

Estimated Run Time

This section provides options to specify settings related to estimated run time of simulations.

Display estimated run time as:

Seconds

Displays the estimated run time in seconds.

Environment Variable: estRunTimeDisplayFormat

Formatted Time

Displays the estimated run time as formatted time.

Environment Variable: estRunTimeDisplayFormat

Automatically update estimated run time

Enables the automatic updating of the EstRunTime values after simulation runs are triggered from Verifier.

Create and Open Options

This section provides options to specify settings for creating and opening verification reports.

Auto-create all enabled reports

Creates all the enabled reports automatically after each interactive run is completed, or when a data update process is completed after external changes are found.

Environment Variable: autocreatereports

Overwrite reports

Overwrites HTML reports without any prompts for confirmation.

Environment Variable: overwritereports

Link implementation datasheets to the created HTML report

Creates the ADE Assembler or ADE Explorer datasheets of the implementation cellviews from their history and link the datasheets to the HTML report generated by Verifier. You can click the links in the HTML report to access the datasheets.

Environment Variable: linkdatasheets

Append implementation information to the created HTML report

Displays mapping information for the implementations in the HTML report.

Create HTML Report File

This section provides options to specify report generation settings.

Generates the HTML report.

You can specify the report filename and location in the associated field. If you do not specify this information, Verifier uses the default filename, VerifierCellviewName.html in the current directory.

Environment Variable: createbatchhtmlreport, batchhtmlreport

HTML Report

This section provides options to specify the settings for saving HTML reports.

Directory

Path to the directory where the HTML report is saved.

You can specify the report directory in the associated field. If this information is not specified, the default directory path is set to  ./lib_cell_view.

Environment Variable: useTemplate, htmlReportDirectory

Datetime suffix format

Customizable suffix format appended to the report directory name to indicate date and time.

This field can contain only alphanumeric characters, '.', ':', '-', or '_'.

The default format yyyyMMdd_HHmmss appends currentDate_currentTime to the directory name.

Environment Variable: useTemplate, dateTimeSuffixFormat

Library

Select one of the listed libraries.

By default, all the available libraries are displayed.

Cell

Select one of the listed cells.

By default, all the available cells are displayed.

View

Select one of the listed views.

By default, only verifier views are available.

Requirement owner names

Lets you specify the name of the owner of the selected requirements. You can specify a comma-separated list of owners. However, Verifier considers only the first name in the list as the owner.

Signoff Data

This section provides options to specify all details related to a requirement signoff.

User name

Displays the user name of the signoff.

Lifetime

This section provides options to specify lifetime-related settings for a requirement that needs signoff.

Select the appropriate option to specify the validity time frame of the signoff:

• Once: The signoff is valid only for a specific set of simulation results and becomes disabled when newer simulation results become available.
• Indefinitely: The signoff is valid for an infinite time.
• Until Date: The signoff is valid up to the date specified in the corresponding field.

Apply Signoff?

Select the appropriate option to save signoff data:

• Yes: Select to store the signoff information after applying the signoff to the requirement.
• No: Select to store the signoff information without applying the signoff to the requirement.

Percentage Complete

This section provides options to specify the percentage of completion for a requirement that needs signoff.

Enables the percentage list box for specifying the completion percentage of the selected requirement. The specified percentage value is also used to calculate the OverallStatus of requirements with type Note.

Comments

This section lets you specify comments related to a requirement signoff.

Lets you specify useful information about the signoff.

Basic Information (Read Only)

This section lets you view the basic information related to a requirement signoff in read-only format.

Owner name

Displays the owner name of the requirement being signed off.

Location

Displays the location of the requirement being signed off.

Date time

Displays the signoff date and time of the requirement being signed off.

Requirement Information (Read Only)

This section lets you view the requirement information related to a requirement signoff in read-only format.

ID

Displays the ID of the requirement being signed off.

Title

Displays the title of the requirement being signed off.

Description

This section lets you view the description of the requirement signoff.

Displays the description of the requirement being signed off.

Name

Specify a name for the variable, parameter, or model file. The name must be a unique one-line string text without spaces.

Value

Specify a numeric value for the variable or parameter; unique section value for a model file.

Shortcut menu commands

This section lists the shortcut menu commands that are available in the form.

Add

Add the item with a unique name.

Remove

Remove the selected items.

Import from CSV

Import the variables or parameters from a CSV file. The columns headers must define the ‘Name,Value’ column. The value could be blank or a number.

Export to CSV

Export the typical setup to a CSV file.

Enabled

Enables or disables the vManager connection. When this check box is checked, all fields on the form are editable, and let you perform the various tasks, such as upload and download of data. Deselecting this check box disconnects the connection with vManager and disables all fields on the form.

Connection

This section lets you specify the connection settings.

Hostname

Specify the hostname of vManager server.

Port

Specify the port of vManager server.

Timeout

Specify the duration in seconds after which the connection terminates when the vManager server does not answer.

Security

This section lets you specify the security settings.

User

Specify the user name of the vManager server.

Password/Token

Specify the password or the token for the user name.

Show Password
/Show Token

Select if you want to display the password or the token text instead of the '*' characters.

Setup

This section lets you specify the settings related to the vManager setup.

Project

Specify a project. Project data is populated automatically when a connection to the vManager server is established.

vPlan

Location

Displays the selected state of the vPlan in database option from the vManager server.

Possible values: On disk (default), In database.

File

Specifies the path to an existing vplan file. You can specify a new *.vplanx filename to create a new vPlan using Verifier.

You can use UNIX shell variables and relative paths to specify the vPlan file name such as:

$HOME/abc.vplanx

This field is displayed when Location is set to On disk.

Path

Specifies the path to a vPlan in the vManager database. Selecting an existing vPlan path from the list updates the Name list with the corresponding vPlan names. By default, the Path value is empty and the Name list contains names of all the vPlans in the vManager database.

This field is displayed when Location is set to In database.

Name

Specifies the name of a vPlan in the vManager database. You can specify a unique name to create a new vPlan in the vManager database with the specified path. Selecting an existing vPlan name in the Name list updates the Path field with the corresponding path.

This field is displayed when Location is set to In database.

vManager version

Displays the version number of the vManager server. This is a read-only value.