This schema is specified in IEEE IEEE 1671.1 "Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML: Exchanging Test Descriptions". This schema is a World Wide Web Consortium (W3C) Extensible Markup Language (XML) binding of the ATML component defined in IEEE 1671.1 "Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML: Exchanging Test Descriptions". The purpose of this schema is to allow the creation of IEEE 1671.1 instance documents. This schema uses the W3C XML Schema definition language as the encoding. This allows for interoperability and the exchange of ATML component instances between various systems. This schema shall not be modified but may be included in derivative works. Copyright (c) 20xx Institute of Electrical and Electronics Engineers, Inc. USE AT YOUR OWN RISK Enumeration of types for Electro Optical interfaces. Enumeration of severity levels for faults and failures, as follows: Warning: The fault or failure may impact UUT functionality and has no long term impact on UUT reliability. Error: The fault or failure impacts UUT functionality and impacts UUT reliability (i.e., life is shortened). Fatal: The UUT is unusable. Enumeration of failure types, as follows: Detectable: The failure can be detected by a functional test. NonDetectable: The failure cannot be detected by any functional test. NonFunctional: The failure can be detected by a functional test, but no repair action is required because the failure will not affect any higher assembly in any operating mode under specified service environmental conditions. Enumeration of fault types, with respect to detectability, as follows: DetectableInsertable: The fault can be inserted into the UUT, and detected by functional tests at the channel, division or system level; performance of the functional tests will cause no adverse effect on the life-cycle of the UUT. DetectableDestructive: The fault could be inserted into the UUT, and detected by functional tests; however execution of the functional tests may adversely affect the life expectancy of the UUT or render the UUT unfit for use. NonDetectable: Fault identified by analysis that cannot be detected by functional test or tests. Enumeration of signal types, as follows: Input: The signal is received by the UUT. Output: The signal is generated by the UUT. Bi-Directional: The signal is both received and generated by the UUT. Load: The signal describes a load applied to the UUT. Enumeration of signal roles, as follows: Source: The signal is generated by an ATE resource. Sensor: The signal is measured by an ATE resource. Monitor: The signal is monitored by an ATE resource. Load: An ATE resource applies a load to the UUT. Enumeration of signal characteristic roles, as follows: Control: The characteristic is controlled by an ATE resource. Limit: The characteristic is limited by an ATE resource. Measurement: The characteristic is measured by an ATE resource. Capability: The characteristic is related to the capacity of an ATE resource to satisfy a test requirement, but is not required to be controlled, limited or measured. Enumeration of possible values for outcomes of tests and test groups. Enumeration of possible values for comparison results. Enumeration of test types, as follows: UutIdentification: Verifies that the model of the current UUT is compatible with the testing procedure described in the instance document. PowerStimuliShort: Verifies power or stimulus inputs to be not shorted prior to any stimulus application to the UUT. SafeToTurnOn: Verifies that is it safe to turn on power. Performance: Verifies proper operation of the UUT. Diagnostic: Isolates faults within the UUT. This element shall contain information defining test performance, test conditions, diagnostic requirements, and support equipment to locate, align, and verify the proper operation of a UUT. Shall identify the Test Signal Framework (TSF) Libraries referenced in the current instance document. These TSF Libraries describe the interface and behavior of IEEE Std 1641 signals used in the instance document. Refer to clause 6 of IEEE 1641 for information on describing TSF Libraries. Identifies one TSF Library by referencing the external XML documents that describe the interface and behavior of signals from the TSF Library. References the XML instance document that describes the interface and behavior of signals from the TSF Library. For each TSF Library, the file referenced by this element shall be identical to the file referenced by the ‘xsi:schemaLocation’ attribute of the root element. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. References the XML Schema document that defines the interface of the TSF Library. Descriptive name for the TSF Library. Unique identifier, enables referencing of the TSF Library element. Shall contain descriptive information for the UUT. Shall describe the characteristics of equipment and circuitry required to test the UUT, excluding the test equipment (e.g., UUT connector information). Shall specify all UUT signal requirements for testing the UUT. Shall describe the performance characteristics of the UUT. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall contain all of the sufficient data for each UUT test to completely describe all input conditions and measurements required. Shall contain UUT fault data, including faults and failures. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall identify the Automatic Test Program Generation (ATPG) tools used to generate the test program. Name of the instance document. Version of the instance document. Shall describe all UUT signal requirements for testing the UUT. Note that UUT power requirements can be described using this element, as well as the UUT/TestData/PowerRequirements element. If the instance document contains power requirements specified using both elements, these descriptions shall be consistent. Describes one UUT signal requirement. Identifies the TSF class for the signal. Describes requirements for one attribute of the signal. Specifies the role of the signal characteristic, e.g., control, limit, measurement, capability. Signal role, e.g., source, sensor, monitor, load. Shall describe the characteristics of equipment and circuitry required to test the UUT (excluding the test equipment). The 'ID' attribute of each Connector descendant shall contain the reference designator of the connector, for example "J1". The 'pinID' attribute of each ConnectorPin descendant shall contain the pin number or name, for example: "1", "A2", etc. The type DetailedConnectorLocation shall be assigned to ConnectorPin descendants when it is necessary to provide detailed information for the connector pin. Refer to B.2 for an example on using DetailedConnectorLocation. Shall contain the description of electrical test points. Description of a test point. May reference a test point provided on the circuit board, or a component pin accessible for manual probing. Describes the function of the test point, including signal name, signal definition and signal description. Describes the physical interface of the test point. The attribute 'name' shall contain the reference designator of the test point. Unique identifier, enables referencing the test point. Shall contain the description of Electro-Optical interfaces to the UUT. Describes one Electro-Optical interface. Free-form description. Provided to permit schema extensibility. Unique identifier, enables referencing the interface. Interface type. Shall be one of: Laser, Infrared, Light, Other. Shall contain the description of any fixtures required to verify operation of the UUT. This includes UUT mounting, holding and support fixtures, cooling carts, pneumatic function generators, hydraulic fixtures, etc. Describes one fixture. Child element Definition shall be used to describe the fixture in the current instance document. Child element DescriptionDocumentReference shall be used to reference an external XML document conformant with the schema defined in IEEE Std. 1671.5 Test Adapter. Fixture type (e.g., holding, pneumatic, hydraulic, cooling, etc.). Shall contain a free-form description of signal conditioning requirements. Provided to permit schema extensibility. Shall describe the "performance" envelope of the UUT. The description shall contain sufficient detail that any "black box" with the characteristics described could be inserted in the system without degrading the system performance. Used to assure consistency at all levels of maintenance as well as compatibility between maintenance and Quality Assurance test results. Shall describe all UUT inputs (e.g., electrical, optical, mechanical, etc.), defined along with their range and tolerances. Describes one UUT input. Shall contain nominal, range and tolerance characteristics for the UUT input. Shall specify the nominal value for the UUT input . Shall specify the range of values acceptable for the UUT input. Shall specify the error limit (i.e., tolerance) for the UUT input. Shall describe all UUT outputs, defined in terms of their range, accuracy, and relationship to the input conditions. Describes one UUT output. Shall contain nominal, range and accuracy characteristics for the UUT output. Shall specify the nominal value for the UUT output. Shall specify the range of values expected for the UUT output. Shall specify the error limit (i.e., accuracy) for the UUT output. Shall describe input-output relationships, for the current output. Describes the relationship between one UUT input and the current output. Free-form description of the relationship. ID of the related input. Shall describe control-output relationships, for the current output. Describes the relationship between one UUT control and the current output. Free-form description of the relationship. ID of the related control. Shall describe the controls and ranges of control for the UUT. Describes one UUT control. Shall contain the range characteristics of the UUT control. Shall specify the range of values acceptable for the UUT control. Provided to permit schema extensibility. Shall describe initialization, performance, and diagnostic test information Shall identify the test groups or actions that can be used as entry points for testing the UUT. For each entry point, test conditions are completely stated and are not dependent on previous tests or setups. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall identify the test groups that can be used as entry points for testing the UUT. Shall identify one "test group" entry point. Unique identifier, enables the referencing of the entry point. ID of the test group specified as entry point. Shall identify one of the entry points described through TestGroupEntryPoint child elements as the "primary" entry point of the program. The "primary" entry point is used in the absence of an entry point selection (e.g., by the operator). Shall identify the actions that can be used as entry points for testing the UUT. Shall identify one "action" entry point. This can be a test or a session action. ID of the action specified as entry point. Shall contain the list of actions (tests and session actions) described by the instance document. Shall describe one action (test or session action). Note that ActionType is an abstract type. Consequently, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicates the type of these elements. Shall contain the list of test groups described by the instance document. Shall describe one test group. Note that TestGroupType is an abstract type. Consequently, elements with derived types shall be assigned to this element. The xsi:type' attribute shall be used to indicates the type of these elements. Shall contain the list of state variables. State variables are used to specify conditions for the execution of tests. Refer to B.3 for an example on using state variables to specify conditions. Shall describe one state variable. Free-form description for the state variable. Shall identify the value assumed by the state variable when execution starts. ID of the element containing the initial value specified for the state variable. Shall contain a list of values that can be assumed by the state variable. All the values shall have identical data type, unit and qualifier. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall specify one value that can be assumed by the state variable. Unique identifier, enables referencing the value. Unique identifier, enables referencing the state variable. Name of the state variable. Shall identify global signals, shared by multiple tests. Global signals are referenced from various elements that describe the behavior of actions. Refer to B.4 an example on using global signals. Shall identify one global signal, which can only be a source signal. Shall describes a global source signal. Can be referenced from GlobalSignalOperation child elements of ActionType/Behavior/IeeeStd1641 and from operations with type OperationSetup, OperationChange, OperationReset, OperationConnect, and OperationDisconnect. Unique identifier, enables referencing the global source signal. Name of the global signal. May be used for documentation purposes. Provided to permit schema extensibility. Shall contain descriptive UUT information required to support the test procedure specified in the current instance document. Shall contain UUT Description data, provided inline or in an external XML instance document compliant with the XML schema defined in IEEE Std 1671.3 UUT Description. Shall describe the UUT category, e.g., analog, digital, etc. Shall describe the physical characteristics of the UUT. Shall reference all documents, drawings, diagrams, parts lists associated with the UUT and its sub-assemblies (used to verify UUT operation). The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. UUT Theory of Operation. Engineering data needed to acquire an understanding of the operation of the UUT in its intended environment. Detailed operating instructions for the UUT. Applicable to UUTs whose performance is dependent upon operator interaction. UUT Test Strategy Report. Describes the approach taken to combine factors (constraints, costs, execution times, etc.) that are to be applied to the testing of the UUT. UUT Failure Modes, Effects and Criticality Analysis (FMECA) report. UUT configuration information (outline drawings). UUT installation drawings (main drawings). UUT assembly drawings (detail and subassembly) UUT subassembly schematics, showing the circuitry contained within each module and subassembly. The schematics may include, for example, amplitude and frequency of each input and output, reference designators of each part and test points. UUT specification control drawings for all nonstandard parts. UUT wiring diagrams, showing the actual physical wiring arrangement. Wire Run Lists or tables supplement the diagram. May include Printed Circuit layouts (location of components, junctions, terminals). Detailed UUT logic diagrams. UUT functional block diagrams, identifying parameters and associated signal tolerances at the external and internal interfaces. UUT parts lists, specifying the component parts of each assembly or subassembly. Components will be listed by reference designator and manufacturers part number UUT family tree, identifying each functional module and subassembly. Utilized to enable proper part number and configuration accountability of all UUT subassemblies and modules for which test requirements are defined. Document describing UUT test requirements. Other documentation applicable to the UUT. Provided to permit schema extensibility. Shall contain all of the general UUT data that may be of use in developing test requirements and test programs. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall specify all UUT alternating current (AC) and direct current (DC) power source requirements for testing the UUT. Note that UUT power requirements can be described using this element, as well as the TestDescription/SignalRequirements element. The SignalRequirements element shall be used when signal requirements conformant with IEEE Std 1641 are desired. This element shall be used in all other situations. DC power requirements for testing the UUT. Requirements for one DC power source. Requirement for voltage value, polarity and tolerance. The sign of the floating-point values shall define their polarity. Maximum current requirement. Maximum ripple amplitude, including periodic and random variations. AC power requirements for testing the UUT. Requirements for one AC power source. Requirement for voltage value and tolerance. Requirement for frequency value and tolerance. Maximum current requirement. Requirement for the phase of the AC voltage source. Phase reference. Free-form descriptive information. Provided to permit schema extensibility. Shall specify any precautions or instructions necessary for personnel and equipment protection. Shall include specification of any special handling (e.g., Electrostatic Sensitive Device) required by the UUT and the specification of any general procedures and precautions associated with operating the UUT. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe all conditions required for proper and safe operation, including cooling air, hydraulic pressure, and pneumatic sources. Shall specify adjustment and alignment requirements. Shall describe all special precautions and instructions regarding personnel and equipment protection in the presence of hazards such as high voltage, RF radiation, or lasers. Shall specify special handling and maintenance requirements. Provided to permit schema extensibility. Shall identify all special electrical components required to test the UUT. Identification of one special electrical component required to test the UUT. Shall identify of special tools (e.g., card extenders) required to test the UUT. Identification of one special tool required to test the UUT. Provided to permit schema extensibility. Shall contain UUT fault data, including failures and faults defined for the UUT. Shall contain the list of failures defined for the UUT. A failure is a change in operating characteristics of the UUT resulting in degradation of its performance. The Failures defined for the UUT typically correspond to the prime failure modes of all inputs and outputs to each next lower assembly of the UUT. Shall describe one failure. Type of the failure. Shall be one of: Detectable, Non-Detectable, Non-Functional. Shall describe the faults defined for the UUT. A fault is a condition that causes a component of the UUT to fail to perform in a required manner (e.g., broken wire, short circuit, value out of tolerance, etc.). Refer to B.2 for an example on describing faults. Shall contain the list of UUT components for which faults are defined. Shall describe one UUT component for which faults are defined. The attribute 'designator' of child element Identification shall be used to specify the reference designator of the component (e.g., "R1"). Element Identification/ModelName shall be used to specify the type of the component (e.g., "Resistor"). Shall contain the list of faults defined for the current UUT component. Shall describe one fault defined for the current UUT component. Detectability of the fault. Shall be one of: DetectableInsertable, DetectableDestructive, NonDetectable. Provided to permit schema extensibility. Shall describe one component of the UUT. Shall define the interface of the component. For components that are regular electronic parts, a single "dummy" Connector shall be defined, with minimal information attached. Additional information can be provided and multiple Connector elements can be used when describing "daughter card" components. ID of the pin where the fault occurs. References a connector pin defined under the Component ancestor. Shall define the Automatic Test Program Generator (ATPG) tools that may be used to generate the test program or parts of the test program. Includes UUT simulators, fault simulators, test pattern generators, translators, post-processors, etc. Shall contain the list of ATPG tools. Shall describe one ATPG tool. Shall describe the format of data processed by the ATPG tool (e.g., IEEE Std 1445 DTIF). Free-form description of the format. References a compliance document applicable to the format (for example: IEEE Std 1445 DTIF). Name of the format. Provided to permit schema extensibility. Unique identifier, enables referencing the ATPG tool. Tool type (e.g., pattern generator) Optional tool name. User-defined ATPG data. Abstract base type for test actions. The following derived types are defined in the schema: Test and SessionAction. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements. Free-form description for the action. Shall describe the parameters of the action and shall specify their values. Refer to Annex B for examples on describing parameters. Refer to B.2.15 for usage information regarding parameters. Shall describe one parameter of the action and shall specify its value. Parameters shall be used to represent values that determine the behavior of the action. This includes, for example: the characteristics of stimulus signals, measurement conditions, UUT pins where signals are applied or measured, the limits of parametric sweeps, the indices of UUT channels to be tested, string commands to be sent to the UUT, identification of firmware to be loaded in the UUT, etc. Parameters shall not be used to represent the limits of acceptable UUT operation, as those limits are described using TestResult descendants of complex type Test, which is derived from ActionType. Free-form description of the parameter. Shall specify the value of the parameter. The attributes of this element shall specify the unit (when applicable) and may specify a qualifier. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. The type ConnectionDatum shall be assigned to Datum descendants of this element to specify a connection as the parameter value. The type ValueFromTestGroupParameter shall be assigned to Datum descendants of this element to indicate a parameter value that originates from a Parameter of the containing Test Group. The type ValueFromActionResults shall be assigned to Datum descendants of this element to indicate a parameter value that originates from one or more Test Results of Tests or Session Data of Session Actions from the same Test Group. When present, shall indicate that the value will be retrieved at run-time from an external document, instead of being encoded in the test program. This element shall reference the external document. When present, shall indicate that before action execution the value of the current parameter shall be assigned to a parameter of the called test group. The element can be present only when the current parameter belongs to an action whose behavior is "TestGroupCall". The data type, unit and qualifier of the referenced test group parameter shall be identical to those of the current parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the test group parameter. Provided to permit schema extensibility. Unique identifier, enables referencing the parameter. Name of the parameter. Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific. Shall describe the behavior of the action. The presence of this element shall indicate that behavior is specified using free-form text. The element shall contain the descriptive text. Refer B.2 for an example that contains free-form description of test behavior. The presence of this element indicates that behavior is specified as a sequence of predefined operations. The operation described by the child elements shall be executed sequentially, in the order in which they appear in the instance document. Refer to B.4 for an example where test behavior is described through operations. The presence of this element shall indicate that behavior is specified as a test definition conformant to IEEE Std 1641. Refer to B.3 for an example where test behavior is described through IEEE Std. 1641 signals. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. The presence of this element shall indicate that the action consists in the execution of a test group. The element shall identify the test group. If the test group has multiple entry points, execution shall start at the primary entry point. When the behavior specified for an action is “test group call”, the outcomes defined for that action shall be identical to those of the referenced test group. Note that the previous constraint is not enforced by this XML schema. Consumer applications should verify the constraint programmatically. Refer to B.4 for an example that contains test group calls. ID of the test group that is executed. The presence of this element shall indicate that the part of the test program that corresponds to the current action will be generated automatically by an ATPG tool. The child elements shall identify the tool and the data files used for generation. Shall contain the list of all data files processed or generated by the ATPG tool for the current test. Shall identify one data file. ID of the element describing the ATPG tool that generates the test. Provided to permit schema extensibility. Through this element, test behavior may be specified using XML content that conforms to an external XML schema. Shall identify local signals, shared by multiple operations specified for the current action. Local signals are referenced from operations. Refer to B.4.2 for usage information regarding local signals and to B.4 for an example. Shall describes one local signal, which may be a source signal, a measurement, or a connection. Shall describe a local source signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationChange, OperationDisconnect, and OperationReset located in the current action. Unique identifier, enables referencing the local source signal. Shall describe a local sensor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationRead, OperationDisconnect, and OperationReset located in the current action. Unique identifier, enables referencing the local sensor signal. Shall describe a local monitor signal. Can be referenced from operations with type OperationSetup, OperationChange, OperationConnect, OperationEnable, OperationDisable, OperationDisconnect, and OperationReset located in the current action. Can also be referenced from Synchronization child elements of any Operation element located in the current action. Unique identifier, enables referencing the local monitor signal. Name of the local signal. May be used for documentation purposes. Shall specify the preconditions and postconditions for the action. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describes all preconditions for the action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action. Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action. Provided to permit schema extensibility. Unique identifier, enables referencing the action. Name of the action Indicates if the action is classified. User-defined security classification for the action Custom action type, used to indicate actions that belong to user-defined categories. The semantics attached to categories are user-specific. For example, actions from the same category may be implemented as a single function or procedure. When this attribute is used to provide a guideline for implementation, implementers may choose to follow or ignore the guideline. Cost of action execution, representing the duration of execution, the financial cost associated with execution, or a value calculated by an objective function. May be used to optimize the order of execution. Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not mandated by this standard and can be application-specific. Abstract base type for describing one result of an action (i.e., test or session action). Note that this type is used as base type for other type definitions. Free-form description of the result. Shall describe the data type and the unit of the result. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. When present, this element shall indicate that after action execution the value of the current action result is transferred to a test result of the containing test group. The data type, unit and qualifier of the referenced test result shall be identical to those of the current action result. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the test result the value of the current action result is transferred to. Provided to permit schema extensibility. Unique identifier, enables referencing the result. Name of the action result. Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific. Abstract base type for describing the outcome of an action (test or session action) or test group. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements. Free-form description of the outcome. Shall describe all postconditions for the action or test group, or for an individual outcome of that test or test group. Postconditions defined in a child element of Test/Conditions or SessionAction/Condition shall apply to all outcomes of that test or session action. Postconditions defined in a child element of Outcome shall apply only for that particular outcome, overriding the postconditions defined in a child element of Test/Conditions or SessionAction/Condition. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Note that postconditions can be specified for both actions (i.e., tests or session outcomes) and action outcomes. Postconditions specified for actions become fulfilled after action execution, regardless of the outcome produced by that action. Postconditions specified for action outcomes become fulfilled after action execution only if that specific outcome was produced by the action. If postconditions are specified at both levels, postconditions associated with action outcomes override those associated with the action. Provided to permit schema extensibility. Unique identifier, enables referencing the action outcome. Outcome qualifier (e.g., High, Low). When used, shall contain an adjective providing additional descriptive data for the ‘value’ attribute defined in derived types. When ‘value’ is “Aborted”, ‘qualifier’ shall provide essential descriptive or explanatory information regarding the reason for the action or test group not completing normally. Refer to B.2.12 for an example using qualifiers. Shall describe one test defined in the instance document. See B.2 for examples that contain the description of tests. See B.2.12 for usage information regarding tests. Shall describe the possible outcomes of the current test. The value-qualifier combinations shall be unique for all the outcomes of a test. Note that this constraint is not enforced by the schema. Consumers should verify uniqueness programmatically. Shall describe one outcome of the test. Shall describe the test results of the current test. Shall describe one test result of the current test. Test results serve various purposes, for example: used to determine the test's outcome through comparison with limits, passed to a different test as a parameter, recorded in a test results database for subsequent analysis, etc. Instance documents shall contain one TestResult element for each result produced by the test. For results that are used to determine the test outcome, the TestResult element shall also include the limits or expected value the corresponding result is compared against. When applicable, shall describe through free-form text the transformation used to convert instrument data into the test result. Shall specify the limits the current test result is compared against. The result of the comparison shall determine the outcome of the test, i.e., the test passes if the result of the comparison is “true”, and fails if the result is “false”. If a test has multiple test results that contain test limits, multiple comparisons shall be performed (one for each test result). The results of these comparisons shall be combined through the logical operator “AND”, unless specified otherwise in the descendants of the Behavior child element of Test. Shall specify one limit. The type ValueFromTestGroupParameter shall be assigned to a Datum descendant to indicate an expected value, limit or mask that originates from a parameter of the containing test group. The type ValueFromActionResults shall be assigned to a Datum descendant to indicate an expected value, limit or mask that comes from one or more test results of tests, or session data of session actions from the same test group. Test type. Shall be one of: UutIdentification, PowerStimuliShort, SafeToTurnOn, Performance, Diagnostic. User-defined information regarding the test type. Shall describe one session action defined in the instance document. Session actions describe operations performed on the UUU for purposes other than testing (e.g., loading firmware). to B.2.11 for usage information regarding session actions. Shall describe the possible outcomes of the current session action. The value-qualifier combinations shall be unique for all the outcomes of a session action. Note that this constraint is not enforced by the schema. Consumers should verify uniqueness programmatically. Shall describe one outcome of the session action. Shall describe the data produced by the session action (e.g., measurement results, success or error codes, UUT status information). Shall describe one data item produced by the session action. Shall describe an outcome of a test or test group. Extends base type ActionOutcomeType. Outcome value. Shall be one of: Passed, Failed, Aborted. Shall describe an outcome of a session action. Extends base type ActionOutcomeType. Outcome value. Shall be one of: Done, Aborted. Shall describe a precondition or postcondition. Shall describe the precondition or postcondition in terms of state variable values. ID of the state variable value. Shall describe the precondition or postcondition through free-form text. Name of the precondition or postcondition. Shall describe preconditions and postconditions for an action (test or session action) or a test group. Refer to B.3 for an example where conditions are used. Refer to B.3.2 for usage information regarding conditions. Shall describes all preconditions for the action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Shall describe all preconditions for an action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. Note that this is a recursive definition, allowing the specification of arbitrarily complex composite preconditions. Shall describe one elementary precondition. The presence of this element shall indicate that the logical operator NOT is applied to the elementary precondition. Allows for specification of composite preconditions that consist of elementary preconditions connected through logical operators (e.g., Power is on AND (UUT model is AAA OR UUT model is BBB)). Preconditions to be composed. These can be elementary preconditions or composite preconditions. Logical operator that connects the preconditions specified through child elements of the current element. Shall describe all postconditions for an action or test group, or for a particular outcome of that action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Describes one postcondition. Abstract base type, shall describe a group of actions without specifying an order of execution. Contains information common to all test group types. Derived types define a specific order of execution. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements. Note that the grouping of actions in test groups does not impose a constraint for the modularity and structure of generated test programs. For example, the actions that are part of a test group may be implemented in the same code module or subroutine, or in separate code modules or subroutines. Refer to B.2.22 for usage information regarding test groups. Free-form description of the test group. Shall describe the possible outcomes of the test group. When applicable, shall reference the UUT faults or failures identified by these outcomes. The value-qualifier combinations for the outcomes of a test group shall be unique. Note that this constraint is not enforced by the schema. Consumers should verify uniqueness programmatically. Shall describe one outcome. Shall identify the faults and failures detected or isolated when the parent outcome is obtained through the execution of the test group. Failure and fault data referenced by this element shall be defined under the FailureFaultData child of the root element. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the parameters of the test group, without specifying the actual values of these parameters. Shall describe one parameter. Describes the values supported by the parameter. Typically specifies the data type and the unit. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. The type ConnectionDatumDescription shall be assigned to the DatumDescription child element to indicate that the parameter contains connection data. Provided to permit schema extensibility. Unique identifier, enables referencing the parameter description. Name of the parameter. Shall describe the results produced by the test group. Shall describe one result produced by the test group. The child element ValueToTestResult of type ActionResultType, assigned to descendants of Test or SessionAction elements under the current test group, shall be used to indicate that the value of the test result originates from test results of tests, or from session data of session actions that belong to the current test group. Shall describe the values supported by the test result. Typically specifies the data type and the unit. Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Provided to permit schema extensibility. Unique identifier, enables referencing the test result. Name of the test result. Shall specify the preconditions and postconditions for the action. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describes all preconditions for the action or test group. The specification of preconditions aims to ensure that actions and test groups are executed only if the proper conditions exist. For example: power is applied to the UUT, the appropriate firmware is loaded in the UUT, the UUT temperature is within specified limits, etc. Shall describe all postconditions for the action or test group. Preconditions can be fulfilled by executing actions or test groups with the appropriate postconditions. For example a session action can apply power, download firmware, or change the temperature of a thermal chamber; a test can verify the signature of the UUT, etc. Shall describe the initialization operations for the test group. The implementation of the test program will ensure that these operations are performed before the first test from the test group is executed. Shall describe the termination operations for the test group. The implementation of the test program will ensure that these operations are performed after the last test from the test group is executed. Provided to permit schema extensibility. Unique identifier, enables referencing the test group. Name of the test group. Indicates if the test group is classified. User-defined security classification for the test group. Test group type. Shall be one of: UutIdentification, PowerStimuliShort, SafeToTurnOn, Performance, Diagnostic. User-defined information regarding the test group type. Cost of test group execution, representing the duration of test execution, the financial cost associated with execution, or a value calculated by an objective function. May be used to optimize the order of test execution. Reference to a requirement ID from an external requirements document, which in turn shall be referenced by a Document element under Documentation/Requirements. Note that the format and location of requirement IDs in the external document are not enforced by this standard and can be application-specific. Shall describe a test group where actions are executed sequentially. The order of execution depends on the outcomes returned by the tests. Each step in the sequence represents of the execution of an action (test or session action) or a test group. The next step to be executed is specified in the instance document, for each possible outcome of the executed item, through NextStep elements. This mode of representation for test sequencing is commonly known as a “fault tree”. Refer to Annex B for examples. Refer to B.2.23 for usage information regarding test sequences. Shall describe all the steps of the current sequence. Each step represents the execution of a test or test group. The order of Step elements in the XML instance document is not relevant for the order of execution. The order of execution is determined exclusively by the contents of NextStep descendants. Shall describe one step. Free-form description of the step. The presence of this element shall indicate that the step represents the execution of an action (i.e., test or session action). ID of the action to be executed for the current step. The presence of this element shall indicate that the step represents the execution of a test group. Refer to B.3.1 for additional information regarding this use case for test groups. If the test group has parameters, their nominal values shall be used. To use a different value, use an ActionRef element under Step, referencing an Action of type “Test” whose Behavior references the target TestGroup; assign the desired Parameters to the Action. ID of the test group to be executed for the current step. Shall describe the course of action to be taken when specific results are obtained for the current step (i.e., specific outcomes are returned by the action or test group referenced by the step). This course of action may be: execute another test, adjust components, finish sequence execution and identify components to replace, etc. Shall describe the course of action to be taken for one result of the current step. One Result element shall exist for each action or test group referenced by the current step. Note that this constraint is not enforced by the XML schema. Clients should verify the constraint programmatically. Unique identifier, enables the referencing of the step. Optional step name. Shall identify the entry points of the current sequence. Each entry point references a step that can be executed as the first step in the sequence. Shall describe one entry point. Unique identifier, enables the referencing of the entry point. ID of the step designated as entry point. Shall identify the primary entry point of the sequence. In the absence of an entry point selection (e.g., by the operator), this entry point will be used when the test program is executed. Shall describe a test group where actions can be executed in parallel (i.e., simultaneously), depending on resource availability. The execution of the test group finishes after the all actions finish. The outcome of the test group shall be determined based on the outcomes produced by the individual actions. If at least one action produced an "Aborted" outcome, the outcome of the test group shall be "Aborted"; otherwise, if at least one action produced a "Failed" outcome, the outcome of the test group shall be "Failed"; otherwise, the outcome of the test group shall be "Passed". Shall identify the actions to be executed in parallel. Shall reference one action. ID of the referenced action. Shall describe a test group where actions are executed sequentially. The order of execution is fixed and determine by the order of ActionReference descendants. The outcome of the test group shall be determined based on the outcomes produced by the individual actions. If at least one action produced an "Aborted" outcome, the outcome of the test group shall be "Aborted"; otherwise, if at least one action produced a "Failed" outcome, the outcome of the test group shall be "Failed"; otherwise, the outcome of the test group shall be "Passed". Shall identify the actions to be executed sequentially. Shall reference one action. ID of the referenced action. Shall describe a test group where the order of execution is determined by a diagnostic reasoner in accordance to a diagnostic model (e.g., a diagnostic model conformant with IEEE Std. 1232). Shall reference an external document that contains the diagnostic model. Shall identify the actions to be executed in the order determined by the diagnostic reasoner. Shall reference one action. ID of the referenced action. Shall reference the document that contains the diagnostic model. This may be an XML instance document or another type of document. Shall describe a test group where execution is serial and can be in any order. Shall identify the actions to be executed in any order. Shall reference one action. ID of the referenced action. Shall describe the initialization conditions for a test group. The presence of this element shall indicate that initialization is described through free-form text. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe through free-form text the power sequence required to initialize the UUT. Shall describe through free-form text the warmup required for the UUT. Shall describe through free-form text the conditioning required for the UUT. Shall describe through free-form text the alignment and adjustment operations required to initialize the UUT. Shall describe through free-form text other operations required before the execution of the test group starts. Provided to permit schema extensibility. The presence of this element shall indicate that initialization is performed by executing a single action, which may be a test or a session action. The element shall references that action. An "Aborted" or "Failed" outcome returned by the referenced action shall mean that initialization has failed. When initialization fails, the execution of the current test group shall finish ID of the referenced action. The presence of this element shall indicate that initialization is performed by executing a test group. The element sreferences that test group. A "Failed" or "Aborted" outcome returned by the referenced test group shall mean that initialization has failed. When initialization fails, the execution of the current test group shall finish. ID of the referenced test group. Shall describe the termination conditions for a test group. The presence of this element shall indicate that termination is described through free-form text. The presence of this element indicates that termination is described through free-form text. Shall describe through free-form text the operations required after the execution of the test group is finished. Provided to permit schema extensibility. The presence of this element shall indicate that termination is performed by executing a single action, which may be a test or a session action. The element shall reference that action. An "Aborted" or "Failed" outcome returned by the referenced action shall mean that initialization has failed. When termination of a test group fails, the execution of the test program (e.g., by executing other test groups) shall finish. ID of the referenced action. The presence of this element shall indicate that termination is performed by executing a test group. The element shall reference that test group. A "Failed" or "Aborted" outcome returned by the referenced test group shall mean that termination has failed. When termination of a test group fails, the execution of the test program (e.g., by executing other test groups) shall finish. ID of the referenced test group. Shall describe the course of action to be taken for one result of a step in a test sequence. Shall identify the action outcome the current result corresponds to. This element shall be present if the ancestor Step element represents the execution of an action (test or session action). ID of the referenced action outcome. Shall identify the test group outcome the current result corresponds to. This element shall be present if the ancestor Step element represents the execution of a test group. ID of the referenced test group outcome. The presence of this element shall indicate the that another step will be executed when the current result is obtained. Shall identify the faults and failures detected or isolated when the current Step Result is obtained. Failure and fault data referenced by this element shall be defined in the FailureFaultData child of the root element. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the step to be executed. The presence of this element shall indicate the that the execution of the sequence will finish when the current result is obtained. The element shall specify the sequence outcome to be returned. In turn, this outcome may indicate the failures or faults that were detected or isolated. ID of the sequence outcome to be returned. The presence of this element shall indicate that one or more UUT components will be adjusted when the current result is obtained. The element shall specify the components to be adjusted. Free-form description of the overall adjustment operation. Shall identify all the components to adjust. Shall identify one component to adjust. Free-form description of the adjustment operation for the current component. ID of the component to adjust. Shall describe the course of action to be taken after the adjustment is performed. The presence of this element shall indicate that sequence execution will finish. The element shall specify the sequence outcome to be returned. It is assumed that adjustment solves the problem and re-test is not necessary. ID of the sequence outcome to be returned. The presence of this element shall indicate that the last executed step will be repeated. The presence of this element shall indicate that a different step will be executed. The element shall identify the step to be executed. ID of the step to be executed. Shall describe the operations to be performed if adjustment is impossible (e.g., due to insufficient range). The presence of this element shall indicate that sequence execution will finish if adjustment is impossible. ID of the sequence outcome to be returned when execution is finished. The presence of this element shall indicate that a different step will be executed. The element shall identify the step to be executed. ID of the step to be executed. Shall contain a test definition conformant to IEEE Std. 1641, describing the behavior of a test or session action. Shall specify the relationships between the test definition and other elements of the current instance document such as global signals, parameters and test results. Shall contain a test definition conforming to the STDBSC.xsd schema of IEEE Std. 1641. Note that this test definition can in turn reference TSF signal definitions defined in any TSF Library conformant with IEEE Std. 1641. With one exception described below, IEEE Std 1641 signals defined under this element shall be started (by calling their Run method) when the execution of the current action begins and shall be stopped (by calling the Stop method) when execution of the action finishes. Refer to C.2.2.2 of IEEE Std 1641 for detailed information on the Run and Stop methods. There shall be one exceptions to the above rule: IEEE Std 1641 signals identified as global signals shall not be stopped when execution of the current action finishes; instead, they shall be stopped when execution of the test program finishes, or when executing an action that contains a signal operation of type Stop, whichever comes first. See 4.4.61 for information on identifying global signals. See 4.4.101 for information on the Stop global signal operation. See B.3 for an example on using global signals. Shall describe the mapping of action parameters to IEEE Std. 1641 signal attributes. The signal attributes shall receive at run time, prior to action execution, the values of the mapped parameters. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the mapping of IEEE Std. 1641 measured signal attributes to test results or session data. The test results or session data will receive at run time, after action execution, the values of the mapped signal attributes. Shall describe the mapping of IEEE Std. 1641 signal attributes representing Connection ports to UUT ports (i.e., ports of interface connectors, test points, or component pins). Whenever possible, the mapping of IEEE Std. 1641 ports to ports of UUT connectors should be described through the values of IEEE Std. 1641 signal attributes, using he "pseudo pin name" format connectorID-pinID. For example, the ports of a TwoWire Connection signal to be connected to pins 1 and 2 of connector J1 should be named "J1-1" and "J1-2". When the above solution is used, this element is not needed. In some situations the above solution cannot be applied: when IEEE Std. 1641 ports are mapped to test points or component pins, when preexisting IEEE Std. 1641 contents using a different port name format is integrated into an ATML Test Description instance document, etc. In these cases the mapping of IEEE Std. 1641 ports to UUT ports shall be described using this element. Provided to permit schema extensibility. Describes operations performed on global IEEE Std. 1641 signals. Global signals are identified through GlobalSignal descendants of DetailedTestInformation. Describes one operation performed on a global IEEE Std. 1641 signal. Used to identify a locally defined IEEE 1641 signal as a global signal. Note that, for conformance with IEEE Std 1641, the name of the referenced signal's Connection shall be included in the Out attribute of the std:Signal parent of that signal. See B.3 for an example. Name of the IEEE Std 1641 signal identified as a global signal. This XML attribute shall contain the name of a signal defined under the IeeeStd1641 ancestor of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. This element describes a global signal operation of type Change. The global signal referenced by the parent of this element shall be changed (by calling its Change method) when the action that contains the element is executed. During the Change operation, signal attributes will be assigned the values described through the AttributeChange child elements. See C.2.2.2 of IEEE Std 1641 for detailed information on the Change method. Describes the change of one or more signal attributes during the Change global signal operation. This element specifies a global signal operation of type Stop. The global signal referenced by the parent of this element shall be stopped (by calling its Stop method) when the action that contains the element is executed. See C.2.2.2 of IEEE Std 1641 for detailed information on the Stop method. ID of the global signal on which the operation will be performed. Shall describe the mapping of action parameters and iterators to IEEE Std. 1641 signal attributes. Shall describe the mapping of one action parameter to an IEEE Std. 1641 signal attribute. ID of action parameter. Name of IEEE Std 1641 signal whose attribute is mapped. This XML attribute shall contain the name of an IEEE Std. 1641 signal defined under the IeeeStd1641 ancestor of the current element. Name of mapped IEEE Std 1641 signal attribute. This XML attribute shall contain the name of one of the attributes of the signal referenced by XML attribute 'signalName' of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describes the mapping of one iterator to an IEEE Std. 1641 signal attribute. Shall be used only in conjuction with OperationRepeat operations. ID of the iterator. Name of IEEE Std 1641 signal whose attribute is mapped. This XML attribute shall contain the name of an IEEE Std. 1641 signal defined under the IeeeStd1641 ancestor of the current element. Name of mapped IEEE Std 1641 signal attribute. This XML attribute shall contain the name of one of the attributes of the signal referenced by XML attribute 'signalName' of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the mapping of IEEE Std. 1641 measured signal attributes to test results and session data. Shall dscribe the mapping of one IEEE Std. 1641 measured signal attribute to a test result. Shall be used only in conjunction with actions of type Test. ID of test result. Name of IEEE Std 1641 signal whose attribute is mapped. This XML attribute shall contain the name of an IEEE Std. 1641 signal defined under the IeeeStd1641 ancestor of the current element. Name of mapped IEEE Std 1641 signal attribute. If this XML attribute is absent, the "measurement" signal attribute shall be mapped. When present, this XML attribute shall contain the name of one of the attributes of the signal referenced by XML attribute 'signalName' of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the mapping of one IEEE Std. 1641 measured signal attribute to a session datum. Shall be used only in conjunction with actions of type SessionAction. ID of test result. Name of IEEE Std 1641 signal whose attribute is mapped. This XML attribute shall contain the name of an IEEE Std. 1641 signal defined under the IeeeStd1641 ancestor of the current element. Name of mapped IEEE Std 1641 signal attribute. If this XML attribute is absent, the "measurement" signal attribute shall be mapped. When present, this XML attribute shall contain the name of one of the attributes of the signal referenced by XML attribute 'signalName' of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the mapping of IEEE Std. 1641 signal attributes representing Connection ports to physical UUT ports. Shall describe the mapping of an IEEE Std. 1641 signal attribute representing a Connection port to one or more UUT ports. Identifies the UUT port or ports mapped to the IEEE Std. 1641 signal attribute identified by the XML attributes of the parent element. Each Node children shall reference a Port of an interface connector, a test point, or a component. Name of IEEE Std 1641 signal whose attribute is mapped. This XML attribute shall contain the name of an IEEE Std. 1641 signal defined under the IeeeStd1641 ancestor of the current element. Name of mapped IEEE Std 1641 signal attribute. This XML attribute shall contain the name of one of the attributes of the signal referenced by XML attribute 'signalName' of the current element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the change of one or more IEEE Std 1461 signal attributes Shall describe the change of one signal attribute . Shall specify the value to be assigned to the signal attribute. The presence of this element shall indicate that the value to be assigned to the signal attribute shall be obtained at run time from a parameter of the parent action. The element shall identify the action parameter. ID of the action parameter. The presence of this element shall indicate that the value to be assigned to the signal attribute shall be obtained at run time from the iterator of the OperationRepeat operation that contains the parent operation of the current element. The element shall identify the iterator. ID of the iterator. Name of the IEEE Std 1641 signal attribute to change. This XML attribute shall contain the name of one of the attributes of the signal changed by the current operation. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe a sequence of operations. The operations shall be executed in the order in which they appear in the sequence. Refer to B.4 for an example containing operations. Refer to B.4.2 for usage instruction regarding operations. Shall describe one operation. Abstract base type for all operations. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of these elements. Free-form description of the operation. Unique identifier, enables referencing the operation. Operation name. Shall describe the creation and setup of a signal. The presence of this element shall indicate a source signal. Source signals are used to describe stimulus operations. This element shall contain information specific to the source signal. Shall identify the local source signal to setup. ID of the local source signal. Shall identify the global source signal to setup. ID of the global source signal. Shall contain a Signal definition conforming to the STDBSC.xsd schema of IEEE Std. 1641. Note that this signal definition can in turn reference TSF signal definitions defined in any TSF Library conformant with IEEE Std. 1641. This shall be a valid stimulus definition, including Source, Conditioning, Event and Connection BSCs, as applicable. See B.4 for an example. Describes the mapping of action parameters to IEEE Std. 1641 signal attributes. The signal attributes shall receive at run time, prior to operation execution, the values of the mapped parameters. The presence of this element shall indicate a sensor signal. Sensor signals are used to describe measurement operations. This element shall contain information specific to the sensor signal. Shall identify a local sensor signal to measure. ID of the local sensor signal. Shall contain a signal definition conforming to the STDBSC.xsd schema of IEEE Std. 1641. Note that this signal definition can in turn reference TSF signal definitions defined in any TSF Library conformant with IEEE Std. 1641. This shall be a valid measurement definition (intrinsic or generic), including Connection, Conditioning and Sensor BSCs, as applicable. The measurement definition shall contain exactly one measured signal attribute. See B.4 for an example. Shall describe the mapping of action parameters to IEEE Std. 1641 signal attributes. The signal attributes shall receive at run time, prior to operation execution, the values of the mapped parameters. The presence of this element shall indicate a monitor signal. Monitor signals are used to generate events when a specific condition occurs. Events are typically used to synchronize the operation of other signals. This element shall contain information specific to the monitor signal. Shall identify a local monitor signal. ID of the local monitor signal. The presence of this element shall indicate a signal-based monitor signal. Signal-based monitor signals generate events when a specific change occurs in an attribute of a monitored signal. Shall contain a signal definition conforming to the STDBSC.xsd schema of IEEE Std. 1641. Note that this signal definition can in turn reference TSF signal definitions defined in any TSF Library conformant with IEEE Std. 1641. This shall be a valid signal-based event definition. Shall describes the mapping of action parameters to IEEE Std. 1641 signal attributes. The signal attributes shall receive at run time, prior to operation execution, the values of the mapped parameters. The presence of this element shall indicate a time-based monitor signal. Time-based monitor signals generate events at specific time intervals. Shall specify the period of event repetition. If a DatumType-derived type from Common is assigned to this element, it shall define a scalar numeric value with a unit of time. The type ValueFromActionParameter shall be assigned to this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to indicate that the current value of the iterator is used. Shall specify the time of the initial event, measured from the moment the monitor signal is enabled. If the element is absent, the time of the initial event shall be zero (i.e., the event shall occur when the signal is enabled). If a DatumType-derived type from Common is assigned to this element, it shall define a scalar numeric value with a unit of time. The type ValueFromActionParameter shall be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to indicate that the current value of the iterator is used. Shall specify the duration of the event generation interval, measured from the time of the first event. If a DatumType-derived type from Common is assigned to this element, it shall define a scalar numeric value with a unit of time. The type ValueFromActionParameter shall be assigned to this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to indicate that the current value of the iterator is used. Shall specify the number of events to be generated. If a DatumType-derived type from Common is assigned to this element, it shall define an integer numeric value greater than zero, with no unit. The type ValueFromActionParameter shall be assigned to this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to indicate that the current value of the iterator is used. The presence of this element shall indicate an event-based monitor signal. Event-based monitor signals generate events based on the occurrence of other events. Specifically, the generated event shall be active from the moment a "from" event occurs to the moment a "to" event occurs. Shall identify the "from" event. ID of the "from" event. Shall reference a local monitor signal. The monitor signal shall be set up by an operation of type OperationSetup defined in the current action and enabled by an operation of type OperationEnable defined in the current action. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall identify the "to" event. ID of the "to" event. Shall reference a local monitor signal. The monitor signal shall be set up by an operation of type OperationSetup defined in the current action and enabled by an operation of type OperationEnable defined in the current action. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. The presence of this element shall indicate a monitor signal that generates events based on a user-specified condition. Free-form description of the event condition. Shall specify synchronization conditions for the setup operation. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the changing of an existing signal. Shall identify a local signal to change. ID of the local signal. The local signal shall be set up by an operation of type OperationSetup defined in the current action. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall identify a global signal to change. Shall be used only for source signals. ID of the global signal. The global signal shall be set up by an operation of type OperationSetup defined in a different action. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraint programmatically. Producers can ensure that the constraint is satisfied through proper sequencing of tests (for test groups of type TestGroupSequence), or through conditions (for other types of test groups). Shall describe the change of one or more signal attributes through the OperationChange operation. Shall specify synchronization conditions for the signal operation. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the reset of an existing signal. Shall identify a local signal to reset. ID of the local signal. The local signal shall be set up by an operation of type OperationSetup defined in the current action. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall identify a global signal to reset. Shall be used only for source signals. ID of the global signal. The global signal will be set up by an operation of type OperationSetup defined in a different action. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Producers can ensure that the constraint is satisfied through proper sequencing of tests (for test groups of type TestGroupSequence), or through conditions (for other types of test groups). Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the reset of all active signals. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the measurement of an attribute of an existing sensor signal and the creation of a measurement entity that holds the value read from the measurement. Note that the referenced sensor signal will contain exactly one measured attribute. Shall describe the measurement entity created by the operation. Attributes 'standardUnit' and 'nonStandardUnit' shall be alternative. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Unique identifier, enables referencing the measurement operation. Name of the measurement created by the operation. May be used for documentation purposes. Specifies a unit for the measured value. Shall identify the local sensor signal to measure. ID of the local sensor signal. The local signal shall be set up by an operation of type OperationSetup defined in the current action. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall describe the mapping of IEEE Std. 1641 signal attributes read through this operation to test results or session data. The test results or session data shall receive at run time, after operation execution, the values of the mapped signal attributes. Shall specify the number of samples to be read. The absence of the element shall indicate that one sample will be read. Shall specify synchronization conditions for the signal operation. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the comparison of a measurement result with limits and shall specify the test outcomes to be returned for each comparison result. Operations of this type shall only appear under actions of type test, as their functionality is specific to tests. Note that this constraint is not enforced by the schema. Consumers should verify the constraint programmatically. Shall identify the measurement whose result is compared. ID of the measurement. Shall reference a measurement described in an operation of type OperationRead defined in the current test. The operation of type OperationRead shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall specify the limits the measurement result is compared against. Shall specify a limit, limit pair, or an expected value plus a comparison operator. The type ValueFromActionParameter shall be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to Datum descendants of this element to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to Datum descendants of this element to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to Datum descendants to indicate that the current value of the iterator is used. Shall identify the action outcomes to be returned for specific results of the comparison. Shall identify the action outcome to be returned for one result of the comparison. One element shall be specified for each possible result of the comparison, as described in the following: "Equal" and "NotEqual" elements shall be specified when comparing with an expected value; "FailHigh" and "FailLow" elements shall be used when comparing with a single limit; "InTolerance", "FailHigh" and "FailLow" shall be specified when comparing with a limit pair. Note that the previous constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Describes the comparison result. Identifies action outcome to be returned for the specified comparison result. Shall describe the connection of an existing signal or a set of UUT pins and the creation of a connection entity. The presence of this element shall indicate that the operation connects a signal to UUT pins. Shall identify a local signal to connect. ID of the local signal. The local signal shall be set up by an operation of type OperationSetup defined in the current action. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. The operation that sets up the signal can be executed before or after the current operation. Shall identify a global signal to connect. Applicable to source signals only. ID of the global signal. The global signal shall be set up by an operation of type OperationSetup defined in a different action. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. The operation that sets up the signal can be executed before or after the current operation. Shall contain a signal definition conforming to the STDBSC.xsd schema of IEEE Std. 1641. Note that this signal definition can in turn reference TSF signal definitions defined in any TSF Library conformant with IEEE Std. 1641. This shall be a valid connection definition, including Connection BSCs. See B.4 for an example. Shall describe the mapping of IEEE Std. 1641 signal attributes representing Connection ports to UUT Ports. Whenever possible, the mapping of IEEE Std. 1641 ports to ports of UUT connectors should be described through the values of IEEE Std. 1641 signal attributes, using he "pseudo pin name" format connectorID-pinID. For example, the ports of a TwoWire Connction signal to be connected to pins 1 and 2 of connector J1 should be named "J1-1" and "J1-2". When the above solution is used, this element is not needed. In some situations the above solution cannot be applied: when IEEE Std. 1641 ports are mapped to test points or component pins, when preexisting IEEE Std. 1641 contents using a different port name format is integrated into an ATML Test Description instance document, etc. In these cases the mapping of IEEE Std. 1641 ports to UUT ports shall be described using this element. The presence of this element shall indicate that the operation interconnects pins from the UUT interface. Shall identify the UUT interface pins to be connected by the operation. Shall references two or more ports of the UUT interface. Shall specify synchronization conditions for the signal operation. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the disconnect of an existing connection. The presence of this element shalll indicates that the operation disconnects a signal from the UUT pins where it was previously connected. Shall identify a local signal to disconnect. ID of the local signal. The local signal shall be connected by an operation of type OperationConnect defined in the current action. The operation that connects the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall identify a global signal to disconnect. Shall be used only for source signals. ID of the global signal. The global signal shall be connected by an operation of type OperationConnect defined in a different action. The operation that connects the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Producers can ensure that the constraint is satisfied through proper sequencing of tests (for test groups of type TestGroupSequence), or through conditions (for other types of test groups). The presence of this element shall indicate that the operation disconnects pins from the UUT interface. Shall identify the UUT interface pins to be disconnected by the operation. Shall reference two or more ports of the UUT interface. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe the enabling of event generation for an existing monitor signal. Shall identify the local monitor signal to enable. ID of the local monitor signal. The local signal shall be set up by an operation of type OperationSetup defined in the current test. The operation that sets up the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall specify synchronization conditions for the signal operation. The element shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall specify the connection of the monitored signal to the pins of the UUT. Shall be used only for signal-based event monitors. Note that a connection can also be specified in the OperationSetup operation that creates the monitor signal. The 'name' attribute of each Port descendant shall contain the name of a signal attribute for the signal to connect. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the disabling of event generation for an existing monitor signal. Shall identify the local monitor signal to disable. ID of the local monitor signal. The local signal shall be enabled by an operation of type OperationEnable defined in the current action. The operation that enables the signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. Shall define a timeout for the signal operation. If the operation cannot be completed before the timeout expires then the containing action shall finish and return an "Aborted" outcome. Shall describe a pause in the execution of an action. Shall specify the duration of the wait. The 'standardUnit' attribute shall specify a unit of time (e.g., sec). Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the reading of a state variable's value and the assignment of this value to a test result of the containing test, or to a session datum of the containing session action. The presence of this element shall indicates that the state variable value shall be assigned to a test result of the containing test. This element shall be used only if the containing action is of type "Test". It shall not be used if the containing action is of type "SessionAction". The data type, unit and qualifier of the state variable values shall be identical to the data type, unit and qualifier of the referenced test result. Note that the above constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the test result. The presence of this element shall indicate that the state variable value shall be assigned to a session datum of the containing session action. This element shall be used only if the containing action of this operation is of type "SessionAction". It shall not be used if the containing action is of type "Test". The data type, unit and qualifier of the state variable values shall be identical to the data type, unit and qualifier of the referenced session datum. Note that the above constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the session datum. ID of the state variable. Shall describe the assignment of a value to a state variable. ID of the state variable. ID of the state variable value. The referenced value shall be a child element of the state variable referenced by attribute 'stateVariableID'. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall describe the display of a message to the operator. Shall specify the message to be displayed. This may be a string, a numeric value, boolean value, etc. The type ValueFromActionParameter shall be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to Datum descendants of this element to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to Datum descendants of this element to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to Datum descendants to indicate that the current value of the iterator is used. Shall indicate that the message to be displayed is specified in an external document (e.g., a text document, a bitmap image, a web page, etc.). The element shall contain a reference to that document. Shall describe the retrieval of a value from the operator. Shall describe the input message (i.e., the value provided by the operator). Shall describes the value expected from the operator (e.g., a string, a numeric value, a boolean value, etc.). Types derived from DatumDescriptionType shall be assigned to DatumDescription descendants. Unique identifier, enables referencing the input message. The presence of this element shall indicate that the value provided by the operator is assigned to a test result of the containing test. This element shall be used only if the containing action of this operation is of type "Test". It shall not be used if the containing action is of type "SessionAction". The data type, unit and qualifier of the input message (described through the MessageIn/ValueDescription element) shall be identical to the data type, unit and qualifier of the referenced test result. Note that the above constraint is not enforced by the XML schema. Consumers should verify the constraints programmatically. ID of the test result. The presence of this element shall indicates that the value provided by the operator is assigned to a session datum of the containing session action. This element shall be used only if the containing action of this operation is of type "SessionAction". It shall not be used if the containig action is of type "Test". The data type, unit and qualifier of the input message (described through the MessageIn/ValueDescription element) shall be identical to the data type, unit and qualifier of the referenced session datum. Note that the above constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the session datum. Shall describe repeated execution for a set of operations. Refer to B.6 for an example on using this type. Shall describe the operations used for setup purposes. These operations are executed once, before the other operations. Shall describe the operations to be repeated. Shall describe the decision, i.e., a condition that is evaluated before or after each execution of Body operations, to decide if a new repetition is necessary. The operations shall be repeated if the result of the evaluation is "true". The presence of this element shall indicate that the decision is based on the value of an iterator. Note that the current iterator value may be referenced in the Body operations by using the type IeeeStd1641InValue. The presence of this element shall indicate iteration through a discrete set of values. All the values defined under this element shall have identical data type, unit and qualifier. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall define one of the values assumed by the iterator. The type ValueFromActionParameter shall be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to Datum descendants of this element to describe a series of values obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to Datum descendants of this element to describe a series of values obtained from the operator, through an operation of type OperationMessageIn defined under the same action. The presence of this element shall indicate that iteration is controlled by an iterator whose value is incremented after each execution. Shall define the series of values assumed by the iterator. The DatumType-derived types defined in the Common schema shall not be assigned to this element. The type IncrementedValue shall be assigned to describe a series of values generated through iteration. The type ValueFromOperationMeasurement shall be assigned to describe a series of values obtained from a measurement defined through an operation of type OperationRead defined under the Body ancestor. The type ValueFromOperationMessageIn shall be assigned to describe a series of values obtained from the operator, through an operation of type OperationMessageIn defined under the Body ancestor. Shall define the limits the iterator is compared against. Shall define a limit, limit pair, or an expected value plus a comparison operator. The type ValueFromActionParameter shall be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing action. The type ValueFromOperationMeasurement shall be assigned to Datum descendants of this element to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to Datum descendants of this element to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. Unique identifier, enables referencing of the iterator. Name of the iterator. The presence of this element shall indicate that the decision is described through free-form text. The contents of the element shall describe the decision. Shall describe conditional execution for a set of operations. Shall specify a set of operations to be performed when a condition is satisfied, and a different set of operations to be performed when the condition is not satisfied. Note that descendants OnTrue and OnFalse are both optional. At least one these descendants shall appear in instance documents. This constraint is not enforced by the XML Schema. Consumers should verify this constraint programmatically. Shall describe the decision, i.e., a condition that is evaluated at the beginning of the current operation to decide which set of operations will be executed. The presence of this element shall indicate that the decision is evaluated by comparing a value against a set of limits. The source of the value and the limits shall be described under this element. Shall describe the source of the value to be compared. The DatumType-derived types defined in the Common schema shall not be assigned to this element. The type ValueFromActionParameter shall be assigned to describe a value obtained from a parameter of the containing Action. The type ValueFromOperationMeasurement shall be assigned to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to indicate that the current value of the iterator is used. Shall define the limits the value is compared against. Shall define a limit, limit pair, or an expected value plus a comparison operator. The type ValueFromActionParameter may be assigned to Datum descendants of this element to indicate a value that originates from a parameter of the containing test. The type ValueFromOperationMeasurement shall be assigned to Datum descendants of this element to describe a value obtained from a measurement defined through an operation of type OperationRead defined under the same action. The type ValueFromOperationMessageIn shall be assigned to Datum descendants of this element to describe a value obtained from the operator, through an operation of type OperationMessageIn defined under the same action. If the current operation is located in the Body of an OperationRepeat, the type ValueFromIterator shall be assigned to Datum descendants to indicate that the current value of the iterator is used. The presence of this element shall indicate that the decision is described through free-form text. The contents of the element shall describe the decision. Shall describe the operations to be performed when the result of the evaluation is 'true'. Shall describe the operations to be performed when the result of the evaluation is 'false'. Shall describe an operation with custom behavior. The presence of this element shall indicate that behavior is described through free-form text, embedded in the instance document. The contents of the elelemnt shall describe the behavior. The presence of this element shall indicate that behavior is described in an external document. The element shall reference the external document. Shall describe the synchronization condition for a signal operation defined by an OperationType-derived element. Shall indicate that the signal operation is synchronized to an event (i.e., the operation is performed when the event occurs). Shall identify the monitor signal that generates event. The monitor signal shall be set up by an operation of type OperationSetup defined in the current test and enabled by an operation of type OperationEnable defined in the current test. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. ID of the monitor signal that generates the event. Shall reference a local monitor signal. Shall indicate that the signal operation is gated by events. Shall identify the monitor signal or signals that generate event. The presence of this element shall indicate that the signal operation is gated by one event, i.e., the operation is performed for the duration of the event. Shall identify the monitor signal that generates event. The monitor signal shall be set up by an operation of type OperationSetup defined in the current test and enabled by an operation of type OperationEnable defined in the current test. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. ID of the monitor signal that generates the event. Shall reference a local monitor signal. The presence of this element shall indicate that the signal operation is gated by two events, i.e., the operation is performed from the moment the "from" event occurs until the moment the "to" event occurs. Shall identify the monitor signal that generates the "from" event. The monitor signal shall be set up by an operation of type OperationSetup defined in the current test and enabled by an operation of type OperationEnable defined in the current test. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. ID of the monitor signal that generates the "from" event. Shall reference a local monitor signal. Shall identify the monitor signal that generates the "to" event. The monitor signal shall be set up by an operation of type OperationSetup defined in the current test and enabled by an operation of type OperationEnable defined in the current test. The operations that set up and enable the monitor signal shall be executed before the current operation. Note that the above constraints are not enforced by the XML schema. Consumers should verify the constraints programmatically. ID of the monitor signal that generates the "to" event. Shall reference a local monitor signal. Shall describe UUT power requirements. Shall describe the conditions under which the current specification is defined. Shall describe one condition through free-form text. Shall contain any additional information necessary to clarify the specification. Shall describe a signal present at a UUT pin. Signal name. Signal type. Shall be one of: Input, Output, Bi-Directional, Load. Signal definition, provided as free-form text. Shall describe the function of a UUT pin, including the description of the signal and other descriptive data. Shall contain the description of the signal at the UUT pin. Shall contain other descriptive data relevant for the function of the UUT pin, e.g., wire size, wire length, wire type, grounding, etc. Provided to permit schema extensibility. Abstract base type for describing faults and failures. Shall contain information common to faults and failures. Note that this is an abstract type, used as base type for other type definitions. Note that the 'severity' attribute supports a fixed set of severity levels. The Extension element should be used to specify severity levels that do not belong to that set. Shall specify the failure mode (e.g., Open, Short, Stuck at 0, Stuck at 1, Out of Tolerance). Shall specify the failure rate. Shall indicate the location where the fault or failure occurs. For failures, shall reference one or more UUT interface ports. For faults, shall reference one or more UUT component ports. Shall contain information on repairing the UUT when the fault or failure is detected. The presence of this element shall indicate that the repair actions necessary to remediate the current fault or failure are described in the instance document. The descendants of this element shall describe the repair actions. Shall describes one repair action. Shall contain a free-form description for the repair action. Provided to permit schema extensibility. Name of the repair action. The presence of this element shall indicates that the repair actions necessary to remediate the current fault or failure are described in an external document. Shall reference the external document. Shall reference an external document that contains repair instructions for the UUT. Shall contain user-specific codes allowing the identification in the repair instructions document of the repair actions necessary to remediate the current fault or failure. Shall contain one action code. Provided to permit schema extensibility. Shall contain a free-form comment regarding detection (or non-detection) and isolation of the fault or failure. Provided to permit schema extensibility. Unique identifier, enables referencing the fault or failure. Shall indicate if the fault or failure is insertable. Shall describe the severity of the fault or failure. Shall be one of: Warning, Error, Fatal. Shall describes the source of the fault or failure through free-form text. Shall identify a set of faults and failures detected or isolated. Failure and fault data referenced by this type shall be defined under the FailureFaultData child of the root element. Shall identify the faults detected or isolated. Shall identify one fault. ID of the fault. Shall identify the failures detected or isolated. Shall identify one failure. ID of the failure. Abstract base type for describing the performance characteristics of UUT inputs, outputs and controls. Contains information common to inputs, outputs and controls. Note that this is an abstract type, used as base type for other type definitions. Free-form description. Shall define the ports of the signal associated with the performance characteristic and shall describe their location on the UUT interface. The Network descendants of this element shall only reference ports of UUT interface connectors. Unique identifier, enables referencing the performance characteristic. Functional name for the performance characteristic. Type of the power, input, output or control (e.g., electrical, electro-optical, mechanical, hydraulic, pneumatic). Shall identify a TSF class in a TSF Library. ID of the TSF Library. The TSF Library shall be defined under the TsfLibraries child of the root element. Name identifying the TSF class within the TSF Library. Shall match the name of a TSF class defined in the TSF Library. Note that this constraint is not enforced by the XML schema. Consumers should verify this constraint programmatically. Shall specify a value for an attribute of a TSF class. Name identifying the TSF class attribute. If a TSF class is specified for the signal, this element shall contain the name of an attribute of that TSF class. If a TSF class is not specified, it shall contain one of the attributes defined in H.7.1.3.1 of IEEE Std. 1641. Note that the previous constraints are not enforced by the XML schema. Consumers should verify these constraints programmatically. Shall specify the value of the attribute. For control attributes, this shall be the required value. For measured attributes, it shall be the expected value. Resolution, ErrorLimit, Range and Confidence information can be provided under DatumQuality descendants. Shall describe the name of an attribute of a TSF class. The name provided using this type shall match the name of an attribute of the TSF class specified for the current signal. Note that this constraint is not enforced by the XML schema. Consumers should verify this constraint programmatically. Shall define a signal connection. Shall define the ports that are connected. These are signal / logical ports, e.g., "HI", "LO", "A", "B", "C", "N", "TX", "RX", "GND", etc. Shall define one port. Shall describe the connection of ports defined under the parent element to ports that belong to interface connectors, test points, and components of the UUT. Shall describes one connection. One Node child shall references a Port defined under the Connection ancestor. Other Node children can reference Ports of interface connectors, test points, or components. Shall define a signal connection. Where applicable, can be assigned to elements of type DatumType. The optional attributes and child elements of the base type are not applicable and shall not be used. Shall define the connection. Shall describe a signal connection, without defining the actual ports. Where applicable, can be assigned to elements of type DatumDescriptionType. The optional attributes and elements of the base type are not applicable and shall not be used. Shall indicate the number of ports. This optional element shall appear only if the described connection contains a fixed number of ports. Shall identify the location of a port on a specific connector pin, while providing detailed information for that pin. The type shall be used when it is necessary to provide detailed information for the connector pin. Otherwise, the base type c:ConnectorLocation shall be used instead. An element with this type shall not appear in instance documents unless it has at least one child element. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. See B.2 for an example of using this complex type. Shall describe the function of the pin, including pin designation, signal name, signal definition and signal description. This element shall not appear for pins of type "Not Connected". Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall contain information for the wire that will be connected to the UUT. Shall contain a free-form description of the wire, including wire type (e.g., coaxial), wire size, etc. Shall describe wire dependencies (e.g., twisted with, shielded with). Shall describe one wire dependency. Shall contain a free-form description of the relationship (e.g. twisted with, shielded with). Shall identify the other wire or wires the current wire is in relationship with by referencing one or more ports of the UUT interface. Shall describe "virtual pins", representing firmware variables that may be read during testing (similar to measurements performed on physical pins). Shall specify the command used to retrieve data from the firmware variable. Provided to permit schema extensibility. Indicates that a value originates from a parameter of a test group. Where applicable, can be assigned to elements of type DatumType. If present, the unit and qualifier shall be identical to those of the referenced parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the test group parameter. Indicates that a value originates from one test result of a test, or from one session datum of a session action, or from multiple such child elements of different actions. Where applicable, can be assigned to elements of type DatumType. If the TestResult and SessionDatum child elements reference data items from more than one action, data shall be obtained from the action that is executed last (among the actions executed before the ancestor action of the element this complex type is assigned to). The TestResult and SessionDatum child elements shall not reference more than one data item from the same action. This constraint was introduced because in that situation there would be no way to determine which data item the data will be obtained from. Note that the constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. If present, the unit and qualifier shall be identical to those of the referenced test results and session data. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Note that both child elements TestResult and SessionDatum are optional. Elements with this type shall not appear in instance documents unless at least one of these child elements exists. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Shall identify one session datum the value originates from. ID of the session datum. Shall identify one test result the value originates from. ID of the test result. Indicates that a value originates from a parameter of an action (test or session action) that is an ancestor of the current element. Where applicable, can be assigned to elements of type DatumType. If present, the unit and qualifier shall be identical to those of the referenced parameter. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the action parameter. Indicates that a value originates from a measurement defined through an operation of type OperationRead. Where applicable, can be assigned to elements of type DatumType. If present, the unit and qualifier shall be identical to those of the referenced measurement. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the measurement. Indicates that a value originates from an ATE operator message obtained through an operation of type OperationMessageIn. Where applicable, can be assigned to elements of type DatumType. If present, the unit and qualifier shall be identical to those of the referenced message. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the message. Indicates that a value originates from an iterator defined through an operation of type OperationRepeat. Where applicable, can be assigned to elements of type DatumType. If present, the unit and qualifier shall be identical to those of the referenced iterator. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. ID of the iterator. Shall describe a series of values generated through iteration. Shall define the initial value of the iterator, i.e., the value assumed before executing the OperationRepeat operations. The type ValueFromActionParameter shall be assigned to the Datum child element to indicate an initial value that originates from a Parameter of the containing Test. Shall define the increment for the iterator, i.e., the value to be added to the iterator after each execution of the OperationRepeat operations. The presence of this element shall indicate that a linear increment is used. The element shall define the value of the increment. The data type, unit and qualifier of theincremet shall be identical to those of the initial value. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. The type ValueFromActionParameter shall be assigned to the element to indicate an increment value that originates from a parameter of the containing test. The presence of this element shall indicate that a logarithmic increment is used. The element shall specify the number of steps between the Initial Value and the Limit. An integer data type shall be used to specify the number of steps in the instance document. The type ValueFromActionParameter shall be assigned to the element to indicate an initial value that originates from a parameter of the containing test. The presence of this element shall indicate that another type of increment is used. The element shall describe the increment through free-form text Describes a value, providing an optional nominal value. This type is similar to c:Value, but does not specify the actual value. It is typically used to describe values that will be obtained at run-time through measurement, from the operator, etc. The value consists of one data item. The value consists of a set of heterogeneous data items. Each item may have a different data type and unit. The value consists of an array of homogenous data items. All elements have the same data type and unit. Abstract base type for types that describe a value consisting of a data item (e.g., numeric, boolean, string, date-time), an optional nominal value, optional unit information, and optional quality information (range, resolution and accuracy). Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The 'xsi:type' attribute shall be used to indicate the type of the elements. Attributes 'standardUnit' and 'nonStandardUnit' shall be alternative. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Unit of the data item. Describes a value that consists of a set of heterogeneous data items. Attributes standardUnit and nonStandardUnit shall be alternative. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Describes one data item. Name of the data item. Default unit, applies to data items for which a unit is not explicitly defined. Abstract type, describes a value that consists of an array of homogenous data items. The array shall be zero-based. The elements of the array may be individual data items or collections. All elements of the array shall have the same data type. Note that this constraint is not enforced by the XML schema. Consumers should verify the constraint programmatically. Note that this is an abstract type, used as base type for other type definitions. Where this type is assigned in the schema, elements with derived types shall be provided. The xsi:type attribute shall be used to indicate the type of the elements. Common unit, applies to all array elements. Specifies the array bounds for each dimension. Implicitly specifies the number of dimensions. Describes a binary value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of binary values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a boolean value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of boolean values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a complex numeric value (i.e., a value that has real and imaginary components). Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of complex numeric values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a date-time value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes a date-time value. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a hex-encoded binary value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of hex-encoded binary values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a numeric value that corresponds to the IEEE double precision 64-bit floating point type. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of floating-point numeric values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a 32-bit signed integer value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of 32-bit signed integer values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes an octal-encoded binary value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of octal-encoded binary values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a string value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of string values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element. Describes a 32-bit unsigned integer value. Where applicable, can be assigned to elements of type DatumDescriptionType. Nominal value. Describes an array of 32-bit unsigned integer values. Where applicable, can be assigned to elements of type IndexedArrayDescriptionType. Note that it is possible to have elements with this type that have no elements or attributes. The presence of such an element indicates that the described entity is an array with unknown size and number of dimensions, where elements have no unit, that a default value for elements is not specified, and that a nominal value for the described entity is not specified. Default value, applies to all array elements whose value is not explicitly defined through NominalElementValue child elements. The value of an array element, for the nominal array value. Index of the element.