1、IEEE Std 771-1998(R2009)IEEEGuide to the USE of the ATLASSpecificationSponsorATLAS 771 Sub Committeeof theIEEE Standards Coordinating Committee 20Reaffirmed 9 December 2009Approved 19 March 1998IEEE-SA Standards BoardAbstract: Guidance in the use of ATLAS test languages is provided. ATLAS may be use
2、dto describe test requirements independent of any specific test equipment, and examplesof best practice in the use of ATLAS are given.Keywords: ATE, ATLAS, automatic test equipment, C/ATLAS, guide, test language, testrequirement unit under test, UUTThe Institute of Electrical and Electronics Enginee
3、rs, Inc.345 Park Avenue, New York, NY 10017-2394, USACopyright 1998 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 30 November 1998. Printed in the United States of America.Print: ISBN 0-7381-0195-8 STD94524PDF: ISBN 973-07381-5860-0 STDPD94624No part of
4、 this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the priorwritten permission of the publisher.Authorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IEEE Xplore. Restrictions apply. IEEE Stand
5、ards documents are developed within the IEEE Societies and the Standards Coordinating Committees of theIEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards through a consensus develop-ment process, approved by the American National Standards Institute, which brings t
6、ogether volunteers representing variedviewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve with-out compensation. While the IEEE administers the process and establishes rules to promote fairness in the consensus devel-opment process
7、, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information containedin its standards.Use of an IEEE Standard is wholly voluntary. The IEEE disclaims liability for any personal injury, property or other dam-age, of any nature whatsoever, whether special, indire
8、ct, consequential, or compensatory, directly or indirectly resultingfrom the publication, use of, or reliance upon this, or any other IEEE Standard document.The IEEE does not warrant or represent the accuracy or content of the material contained herein, and expressly disclaimsany express or implied
9、warranty, including any implied warranty of merchantability or fitness for a specific purpose, or thatthe use of the material contained herein is free from patent infringement. IEEE Standards documents are supplied “AS IS.”The existence of an IEEE Standard does not imply that there are no other ways
10、 to produce, test, measure, purchase, market,or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved and issued is subject to change brought about through developments in the state of the art andcomments re
11、ceived from users of the standard. Every IEEE Standard is subjected to review at least every five years for revi-sion or reaffirmation. When a document is more than five years old and has not been reaffirmed, it is reasonable to concludethat its contents, although still of some value, do not wholly
12、reflect the present state of the art. Users are cautioned to checkto determine that they have the latest edition of any IEEE Standard.In publishing and making this document available, the IEEE is not suggesting or rendering professional or other servicesfor, or on behalf of, any person or entity. No
13、r is the IEEE undertaking to perform any duty owed by any other person orentity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a com-petent professional in determining the exercise of reasonable care in any given circumstances.Interpretat
14、ions: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specificapplications. When the need for interpretations is brought to the attention of IEEE, the Institute will initiate action to prepareappropriate responses. Since IEEE Standards represent a co
15、nsensus of concerned interests, it is important to ensure that anyinterpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of itssocieties and Standards Coordinating Committees are not able to provide an instant response to interpretation requ
16、estsexcept in those cases where the matter has previously received formal consideration. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership affiliation withIEEE. Suggestions for changes in documents should be in the form of a proposed change of te
17、xt, together with appropriatesupporting comments. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LanePiscataway, NJ 08854USAAuthorization to photocopy portions of any individual standard for internal or personal use is granted
18、 by the Institute ofElectrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. Toarrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,Danvers, MA 01923 USA; (978) 750-8400. Perm
19、ission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this standard may require use of subject mat-ter covered by patent rights. By publicati
20、on of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patentsfor which a license may be required by an IEEE standard or for conducting inquiries into the legal validity orscop
21、e of those patents that are brought to its attention.Authorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IEEE Xplore. Restrictions apply. Copyright 1998 IEEE. All rights reserved.iiiIntroduction(This introduction is not part of IEEE Std 771-1998
22、, IEEE Guide to the Use of the ATLAS Specication.)IEEE Std 716-1995, IEEE Standard Test Language for All SystemsCommon Abbreviated Test Languagefor All Systems (C/ATLAS), and ARINC Specication 626-3, Standard ATLAS Language for Modular Test,dene ATLAS, a standardized test language for expressing tes
23、t specications and procedures. This guidesupplements IEEE Std 716-1995 and ARINC Specication 626-3 and is part of the documentation set for thelanguage.The need for a guide to the use of ATLAS arose from the experience of users in the preparation of test proce-dures in the language. This experience
24、showed that differences of interpretation existed for technique andmethod, if not denition. The purpose of this guide is to provide guidance in the matter of technique andusage; it is seen as particularly important in promoting the use of the language envisaged by its originators.This document is no
25、t intended as an instruction manual for ATLAS nor as a substitute for some formal train-ing, but by its nature it should nd some applicability in the training environment.IEEE Std 771-1998 corresponds with IEEE Std 716-1995 and ARINC Specication 626-3. It is the intentionof the IEEE ATLAS Committee
26、that there shall be a continued correspondence between these standards andIEEE Std 771.The members of the ATLAS 771 Subcommittee during the preparation of this guide were as follows:Ashley M. B. Hulme,ChairIn addition, acknowledgment is made of the valuable individual contributions made by the follo
27、wing:The following members of the balloting committee voted on this standard:Jean-Yves BarbierAntonius BunsenBarry BurnageAnthony FitzpatrickArthur HannBill HeatherLinda O. LundNeil A. McKinnonGoran NordstromMichael SeaveyJoseph StancoAnthony A. F. VogelpoelMichael BlairWilliam BorahPatrice BrardGeo
28、rge J. DiabHans HopfHans LecluyseLarry LuszWilliam E. ReevesHelmut ScheibenzuberGuy AdamJean-Yves BarbierChristos BezirtzoglouMichael BlairAntonius BunsenLarry D. CarpenterRichard D. ChurcherJames E. CottrellMichael T. EllisAnthony FitzpatrickArnold M. GreenspanArthur HannMichael G. HarrisonJohn E.
29、HeiserAshley M. B. HulmeFrank KearnsJean PouillyWilliam E. ReevesMichael L. SeaveyJohn W. SheppardWilliam R. SimpsonJoseph J. StancoKirk D. ThompsonLouis Y. UngarRichard J. WegerWill W. YoungAuthorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IE
30、EE Xplore. Restrictions apply. ivCopyright 1998 IEEE. All rights reserved.When the IEEE-SA Standards Board approved this standard on 19 March 1998, it had the followingmembership:Richard J. Holleman,ChairDonald N. Heirman,Vice ChairJudith Gorman,Secretary*Member EmeritusKim BreitfelderIEEE Standards
31、 Project EditorSatish K. AggarwalClyde R. CampJames T. CarloGary R. EngmannHarold E. EpsteinJay Forster*Thomas F. GarrityRuben D. GarzonJames H. GurneyJim D. IsaakLowell G. JohnsonRobert KennellyE. G. Al KienerJoseph L. Koepnger*Stephen R. LambertJim LogothetisDonald C. LoughryL. Bruce McClungLouis-
32、Franois PauRonald C. PetersenGerald H. PetersonJohn B. PoseyGary S. RobinsonHans E. WeinrichDonald W. ZipseAuthorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IEEE Xplore. Restrictions apply. Copyright 1998 IEEE. All rights reserved.vContents1.
33、Overview 11.1 Scope 11.2 Purpose. 11.3 Related documents. 12. References 23. Definitions 24. The need for a test language standard 44.1 The importance of unambiguous communication 44.2 Types of languages 44.3 Need for unambiguous language . 64.4 The portability of ATLAS . 64.5 ATLAS development. 74.
34、6 Continued regulated growth of ATLAS 114.7 ATLAS as an aid to the management of testing 124.8 Benefits of a standard. 125. The current ATLAS standards. 125.1 Definition of ATLAS. 125.2 IEEE Std 716-1995 125.3 ARINC Specification 626-3. 135.4 IEEE Std 771-1998 136. Structure and characteristics of A
35、TLAS 136.1 General definition 136.2 General characteristics of ATLAS.136.3 Levels of ATLAS. 136.4 ATLAS test requirement structures . 146.5 FSD 196.6 Non-ATLAS usage 207. The elements of ATLAS 207.1 The ATLAS character set 207.2 ATLAS keywords 237.3 ATLAS number conventions .237.4 User-defined label
36、s 267.5 Types of ATLAS data 277.6 Constants 297.7 Variables 297.8 Initializing variables. 307.9 Connections 317.10 Classification of the language elements.317.11 Verbs 317.12 Nouns and modifiers 37Authorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC f
37、rom IEEE Xplore. Restrictions apply. viCopyright 1998 IEEE. All rights reserved.8. Writing a test requirement in ATLAS . 378.1 Introduction 378.2 Analysis of the test problem 378.3 Segmenting the test requirement 388.4 Flowcharting 388.5 Logical branching 408.6 Test resources. 428.7 Arrangement of t
38、est requirement . 428.8 Using procedures . 448.9 Instructions to and from the operator. 458.10 Applying power to the UUT 488.11 Resource allocation 498.12 Identifying signals with resources . 508.13 Applying analog test signals 508.14 Applying digital signals . 528.15 Sensing UUT responses . 528.16
39、Statement execution rate 548.17 Postponing statement execution. 548.18 Branching. 588.19 Entry points 588.20 Iteration in testing 598.21 Multiple-action verbs. 658.22 Time-out fields. 658.23 Test problems not explicitly covered by ATLAS vocabulary . 668.24 Use of comments 678.25 Shutting down a UUT
40、688.26 Recommended practices for good ATLAS 699. Documentation and structuring of test requirements 729.1 Documentation of test requirements 729.2 UUT . 729.3 Design requirement 739.4 Production test procedure 749.5 ATLAS test specification. 7710. ATLAS elements . 10210.1 Introduction 10210.2 ATLAS
41、verbs. 10210.3 ATLAS nouns 10310.4 ATLAS noun modifiers . 10510.5 ATLAS units 11211. Glossary of ATLAS keywords. 11912. ATLAS problems and proposals 16412.1 Submitting an ATLAS problem. 16412.2 Submitting an ATLAS proposal 16512.3 Submitting an ATLAS extension. 16612.4 Involvement with ATLAS standar
42、ds activities 167Authorized licensed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IEEE Xplore. Restrictions apply. Copyright 1998 IEEE. All rights reserved.viiAnnex A (informative) ATLAS in analog testing . 168Annex B (informative) ATLAS in digital testing 1
43、80Annex C (informative) ATLAS in air navigation system testing 196Annex D (informative) Timing and synchronization in ATLAS 223Annex E (informative) ATLAS in data-bus testing. 242Annex F (informative) The ATLAS escape mechanism . 254Annex G (informative) Complex signals in ATLAS . 260Authorized lice
44、nsed use limited to: IHS Stephanie Dejesus. Downloaded on June 16,2010 at 16:31:31 UTC from IEEE Xplore. Restrictions apply. Copyright 1998 IEEE. All rights reserved.1IEEE Guide to the Use of the ATLAS Specication1. OverviewThis guide is divided into clauses that introduce the history, use, and stru
45、cture of the Abbreviated Test Lan-guage for All Systems (ATLAS) language followed by general guidance on good usage practice. The mainclauses also contain information and language elements that apply to all test disciplines. The guide also contains annexes that provide more specic examples of ATLAS
46、usage as applied to particu-lar test disciplines. The information in each annex includes language elements and structures used in a par-ticular test discipline with some examples and descriptions of usage.1.1 ScopeThis guide has been written as an applications manual for engineers and others who wri
47、te test requirementsin ATLAS. The initial clauses are intended to provide managers with a brief introduction to the applicationof ATLAS. This guide is in no way intended to be a substitute for an instruction manual in the ATLAS lan-guage; rather it is intended to provide practical support to such a
48、manual.1.2 PurposeThe purpose of this guide is to provide principles of good practice in the use of ATLAS for writing testrequirements. This advice has been drawn from practical applications in many organizations and a numberof companies that generate test requirements in ATLAS. Since ATLAS must be
49、capable of communicating complex test requirements, the language has a largevocabulary and appropriate syntax. The guide concentrates on the proper use of the ATLAS syntax andsemantics for the generation of unambiguous test requirements. The guide assists in preparing test require-ments as well as in writing computer software that will efciently process ATLAS test requirements forautomatic implementation.1.3 Related documentsThe material in this guide is applicable to IEEE Std 716-1995 and ARINC Specication 626-3. Supplementsto these standards will be issued per
