IEEE 1641-2007：标准与信号测试定义

需积分: 10 158 浏览量更新于2024-07-22 收藏 2.83MB PDF 举报

"IEEE 1641-2007 是一份重要的标准文档，它定义了信号和测试的规范。这份标准由国际电工委员会（IEC）发布，并且与IEEE 1641-2004版本相关联。该标准的版权受保护，未经许可，任何部分不得复制或以任何形式使用，包括电子和机械方式，如影印和缩微胶片。如果需要获取更多关于IEEE版权的信息或希望获得此出版物的额外使用权，应联系IEC中央办公室或当地的IEC成员国国家委员会。" IEEE 1641标准详细介绍了信号和测试定义的方法，旨在为电子和电气工程领域提供一个统一的框架，以便于在设计、验证和测试过程中进行有效的通信和数据交换。这个标准对于测试设备制造商、系统集成商以及那些需要在不同设备间协调测试程序的工程师来说尤其重要。在 IEEE 1641 中，主要涵盖以下几个关键知识点： 1. **信号定义**：标准定义了如何描述和分类不同的电气信号，包括模拟信号、数字信号和混合信号，确保所有参与者对信号的理解一致。 2. **测试定义**：规定了测试的结构、参数和执行方法，使测试过程可重复且具有可比性，降低了因理解差异导致的错误。 3. **数据模型**：提供了标准化的数据模型，允许不同系统之间共享和交换测试及信号信息，促进了不同工具和平台之间的互操作性。 4. **接口和通信**：定义了接口标准，使得测试设备可以有效地与其他系统通信，包括测试管理软件、自动化系统和测量硬件。 5. **兼容性和升级**：考虑到技术的发展，标准包含了向后兼容性，使得旧系统能够适应新的定义，同时提供了升级路径，鼓励采用最新的技术进步。 6. **知识产权和许可**：明确了知识产权的处理方式，保护了标准制定者的权益，同时也为合法用户提供了使用指南。通过遵循IEEE 1641-2007标准，行业内的工程师能够确保他们的测试流程和结果在全球范围内得到认可，从而提高产品质量，减少测试成本，加速产品上市时间。此外，此标准还有助于推动测试领域的标准化进程，促进技术交流和国际合作。

STANDARD FOR SIGNAL

AND TEST DEFINITION

1. Overview

This standard, also known as the signal and test definition (STD) standard, is the culmination of a radical

review of the Abbreviated Test Language for All Systems (ATLAS) test programming language and the

requirement to create truly portable test requirements. STD will allow test information to pass more freely

between the design, test, and maintenance phases of a project, enabling the same information to be used

directly across project phases. This more efficient use of information will lead to reduced life-cycle costs.

STD provides the capability to describe and control signals, while permitting a choice of operating environ-

ment, including the choice of carrier language. STD permits signal operations to be embedded in any object-

oriented environment and thus to be used by the architecture standards of various automatic test systems

(ATSs).

Portability is extended beyond that of test specifications by virtue of a layered architecture.

STD defines a collection of objects and their interfaces. These objects describe signal components relevant

to test requirements. The STD standard defines how to interconnect these objects using interfaces, through

which the objects exchange information, so that a test model may be defined that describes actual test

requirements.

Finally, the link to published ATLAS standards (such as IEEE Std 716™-1995 [B9]

) is preserved in that

the user can describe signal operations using very similar test-signal-related keywords. These keywords now

have formal definitions. Furthermore, the parameters of the signals themselves also have a rigorous formal

behavioral description.

1.1 Scope

This standard provides the means to define and describe signals used in testing. It also provides a set of com-

mon basic signals, mathematically underpinned so that signals can be combined to form complex signals

usable across all test platforms. The provision of language elements supports test signal descriptions for

interoperability.

The numbers in brackets correspond to the numbers of the bibliography in Annex L.

– 14 – IEC 62529:2007(E)

IEEE 1641-2004(E)

This standard is divided into seven clauses:

— Clause 1 provides an introduction to this standard.

— Clause 2 provides definitions of terms and lists abbreviations.

— Clause 3 describes the structure of the STD standard.

— Clause 4 specifies the signal modeling language (SML).

— Clause 5 specifies the STD basic signal components (BSCs).

— Clause 6 defines the test signal frameworks (TSFs).

— Clause 7 describes the test procedure language (TPL) layer.

This standard also contains the following annexes:

a) Annex A provides the Signals Modeling Language that is used to construct the BSCs and the TSFs.

b) Annex B provides BSC descriptions.

c) Annex C provides dynamic signal model description, states, and state transitions.

d) Annex D provides the interface definition language (IDL) description for the BSCs.

e) Annex E provides a TSF. This framework provides a formal description of signals similar to the

signals defined in IEEE Std 716-1995. It also serves to illustrate how complex test signal models can

be built up from BSCs.

f) Annex F provides the IDL description for the TSF provided in

Annex E.

g) Annex G defines the requirements for a carrier language.

h) Annex H provides the formal TPL description.

i) Annex I provides the extensible markup language (XML) description mapping signal models into

XML descriptions.

j) Annex J provides XML description mapping the TSF provided in Annex E into XML descriptions.

k) Annex K provides a description of how ATLAS nouns and noun modifiers are supported by STD.

l) Annex L provides a bibliography of related documents.

1.2 Purpose

The purpose of this standard is to provide a common signal reference for use throughout the life cycle of a

unit under test (UUT) or test system. Such a reference will in turn facilitate information transfer, test reuse,

and broader application of test information—accessible through commercially available development tools.

2. Definitions, abbreviations, and acronyms

2.1 Definitions

For the purposes of this document, the following terms and definitions apply. The Authoritative Dictionary

of IEEE Standards Terms [B8] should be referenced for terms not defined in this clause.

2.1.1 Abbreviated Test Language for All Systems (ATLAS): A stylized, abbreviated English language

used in the preparation and documentation of test requirements and test programs, which can be imple-

mented either manually or with automatic or semi-automatic test equipment.

2.1.2 argument: Input values that can be passed to a function.

2.1.3 attribute: A property value that is used to define signal characteristics or behaviour.

– 15 –IEC 62529:2007(E)

IEEE 1641-2004(E)

2.1.4 automatic test system (ATS): A system that includes the automatic test equipment (ATE) and all sup-

port equipment, support software, test programs, and interface adapters.

2.1.5 base class: A class from which another class inherits attributes or properties.

2.1.6 basic signal component (BSC): The lowest level of building block used to define signals.

2.1.7 class: A generic set of predefined abstract test objects.

2.1.8 component: A part of a system, which may be hardware or software and which may be subdivided

into other components. Components communicate their functionality through their interface definitions.

2.1.9 connection: The application of a signal to a unit under test (UUT).

2.1.10 data bus: A signal line or set of signal lines used by a data communication system to interconnect a

number of devices and to communicate information.

2.1.11 dynamic signal: A signal whose definition changes over time, by use of the control interface. These

changes must be initiated with one of the signal method calls or by changing the interconnections of a signal

model.

2.1.12 function: A construct that is a logically separated block of code that operates upon test values (i.e.,

arguments). Another name for a function is method. Syn: method.

2.1.13 interface definition language (IDL): A machine-compilable language that is used to describe the

interfaces that software objects call and object implementations provide. The language provides a neutral

way to define software interfaces.

2.1.14 method: Syn: function.

2.1.15 model: A mathematical or physical representation (i.e., simulation) of system relationships for a

process, device, or concept.

2.1.16 physical: Pertaining to the natural characteristics of the universe according to the natural laws of

science.

2.1.17 procedural: The part of an signal and test definition (STD) test requirement that defines the tests in

the manner and order required for testing.

2.1.18 property: The special form of method (or function) that supports the semantics of assignment

(l-value) and reading (r-value).

2.1.19 reserved word: A keyword whose meaning and use are fixed by the semantics of a language. In cer-

tain or all contexts, a reserved word cannot be used for any other purpose than as defined for that language.

2.1.20 semantics: A branch of linguistics concerned with meaning. For the test procedure language (TPL),

semantics is the connotative meaning of words in an TPL statement. For software, semantics is the

relationships of symbols and their meaning, independent of the manner of their interpretation and use. For

meta-languages, semantics is the discipline for expressing the meanings of computer-language constructs in

a meta-language.

2.1.21 sensor: A transducer that converts a test parameter to a form suitable for measurement.

2.1.22 SignalFunction: The name of the base class, for all classes that provide signals.

– 16 – IEC 62529:2007(E)

IEEE 1641-2004(E)

2.1.23 SubClass: A class that inherits attributes or properties from a base class.

2.1.24 static signal: A signal whose definition does not change over time. All basic signal components

(BSCs) and test signal frameworks (TSFs) are static signals.

2.1.25 syntax: The grammatical arrangement of words in a language statement.

2.1.26 system: A set of interconnected hardware and/or software entities that achieves a defined objective

by performing specified functions.

2.1.27 system architecture: The structure of and relationship between the entities of a system. A system

architecture may include the system interface with its operational environment.

2.1.28 template: A pattern or design that establishes the outline, dimensions, or process for subsequent

users or implementers.

2.1.29 test: An action or group of actions that are performed on a unit under test (UUT) to evaluate its

parameter(s) or characteristic(s).

2.1.30 test requirement: A definition of the tests and test conditions required to be performed on a unit

under test (UUT) to verify conformance with its performance specification.

2.1.31 test specification: A definition of the tests to be performed on a unit under test (UUT) to verify con-

formance with its performance specification, with or without fault diagnostics, and without reference to any

specific test equipment.

2.1.32 test procedure: A description of the tests, test methods, and test sequences to be performed on a unit

under test (UUT) to verify conformance with its test specification, with or without fault diagnostics, and

without reference to specific test equipment.

2.1.33 test program: An implementation of the tests, test methods, and test sequences to be performed on a

unit under test (UUT) to verify conformance with its test specification, with or without fault diagnosis. A

test program is configured for execution on a specific test system.

2.1.34 transducer: A device that converts a physical magnitude of one form of energy into another form,

generally on a one-to-one correspondence or according to a specified mathematical formula.

2.1.35 unit under test (UUT): An entity that can be tested and that may range from a single component to a

complete system.

2.1.36 value: The quantitative size of a signal attribute.

2.2 Abbreviations and acronyms

ARB auxiliary reference burst

ARINC Aeronautical Radio, Inc.

ASCII American Standard Code for Information Interchange

ARINC provides engineering specifications and services to airlines, airframe constructors, and avionics

suppliers.

– 17 –IEC 62529:2007(E)

IEEE 1641-2004(E)

剩余417页未读，继续阅读

ryoichi

粉丝: 0
资源: 1

IEEE 1641-2007：标准与信号测试定义

IEEE1641-2010

IEEE 1641标准

IEEE 1686-2007

IEEE 1615-2007

IEEE 1459-2000:IEEE 1459-2000 功率定义-matlab开发

IEEE-39-bus-power-system-master_ieee39-bus_ieee39

IEEE 1057-2007标准：数字化波形记录器

IEEE-39-bus-power-system-master_ieee39-bus_ieee39.zip

eetop.cn_SystemVerilog IEEE 1800-2017.pdf.zip_IEEE 1800-2017_IEE

IEEE 1394 -----------------------笔记本通用版

最新资源