ANSI INCITS 423.3-2009 Information Technology C Conformance Testing Methodology C Part 3 Conformance Testing Methodology for ANSI INCITS 377-2004 Finger Pattern Data Interchange Fo.pdf

《ANSI INCITS 423.3-2009 Information Technology C Conformance Testing Methodology C Part 3 Conformance Testing Methodology for ANSI INCITS 377-2004 Finger Pattern Data Interchange Fo.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 423.3-2009 Information Technology C Conformance Testing Methodology C Part 3 Conformance Testing Methodology for ANSI INCITS 377-2004 Finger Pattern Data Interchange Fo.pdf（32页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Conformance Testing Methodology Part 3: Conformance Testing Methodologyfor ANSI INCITS 377-2004,Finger Pattern Data Interchange FormatINCITS 423.3-2009INCITS 423.3-2009INCITS 423.3-2009American National Standardfor Information Technolo

2、gy Conformance Testing Methodology Part 3: Conformance Testing Methodologyfor ANSI INCITS 377-2004,Finger Pattern Data Interchange FormatSecretariatInformation Technology Industry CouncilApproved June 16, 2009 American National Standards Institute, Inc.Approval of an American National Standard requi

3、res review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected

4、interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexist

5、ence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumst

6、ances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat

7、or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard.

8、Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2009 by Informati

9、on Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION:

10、 The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may a

11、pply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any

12、 standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.Contents Forewordii 1 Scope 1 2 Conformance . 1 3 Normative References 1 4 Terms and Definitions 2 5 Symbols (and Abbreviated Terms) 3 6 Conformance Testing Me

13、thodology 4 6.1 General. 4 6.2 Level I and Level II Assertions. 4 Note 1: (Test #3.2) Total Bytes Expected. 6 Note 2: (Test #9) Range of X Number of Cells. 6 Note 3: (Test #10) Range of Y Number of Cells. 6 Note 4: (Test #25.1) Length of Data Block Bytes Expected . 6 6.3 Test Method . 7 6.4 Test Pro

14、cedures 9 6.5 Test Report 10 7 Test Assertions for Type A Conformance Testing 12 7.1 General Consideration 12 7.2 Level 1 and Level 2 Testing of the Record Header 12 7.3 Level 1 and Level 2 Testing of the Finger Pattern Record Header 20Table 1 Assertions for ANSI INCITS 377-2004 Data Records Field w

15、ith Conformance Level Contraints and Operators 5 Figures 1 ANSI INCITS 377-2004 BDR File Format Level 1 and Level 2 Conformance Test Flow 8 2 INCITS 377 BDIR Data File Level 1 and 2 Conformance Testing Implementation Procedure 11 i iiForeword (This foreword is not part of American National Standard

16、INCITS 423.3-2009.)The Finger Pattern Data Interchange Format, ANSI INCITS 377-2004, provides anindustry standard to allow for fingerprint pattern data extracted with one vendors al-gorithm to be useful to another vendors matching algorithm. Currently, there are no standardized methods for conductin

17、g conformance tests ofcommercial products that claim to support the Finger Pattern Data Interchange For-mat, ANSI INCITS 377-2004. Application and Biometric Service Provider (BSP) de-velopers may interpret ANSI INCITS 377-2004 differently from one another;therefore, their implementations of ANSI INC

18、ITS 377-2004 may differ and not inter-operate. There is a need for a standardized, generally accepted, Finger Pattern DataInterchange Format conformance testing methodology that would allow implementa-tion of a set of test tools realizing this methodology. A particular fingerprint pattern template c

19、an be considered to be in conformance withANSI INCITS 377-2004. In this case, a template can be parsed and examined to as-sure that the data layout is consistent with ANSI INCITS 377-2004. A process thattransforms fingerprint images into fingerprint pattern templates can conform to ANSIINCITS 377-20

20、04 by producing conformant templates. A process that assesses thesimilarity of fingerprints can conform to ANSI INCITS 377-2004 by accepting a con-formant pattern template as input.ANSI INCITS 423.3 defines a testing methodology to assure conformance of a ven-dors application or service to the Finge

21、r Pattern Data Record requirements as setforth in ANSI INCITS 377-2004. It intends to:a) Establish elements of the Conformance Testing Methodology framework that arespecific to the Finger Pattern Data Record requirements of ANSI INCITS 377-2004.b) Define requirements and guidelines for specifying co

22、nformance test suites and re-lated test methods for measuring conformity of products and services to the Fin-ger Pattern Data Record requirements of ANSI INCITS 377-2004, andc) Define test procedures to be followed before, during, and after conformancetesting.This part of the ANSI INCITS 423 series

23、of standards is applicable to the develop-ment and use of conformity test method specifications, conformity test suites for Fin-ger Pattern Data Record requirements as specified in ANSI INCITS 377-2004, andconformance testing programs for ANSI INCITS 377-2004-conformant products. It isintended prima

24、rily for use by testing organizations, but may be applied by developersand users of test method specifications and test method implementations.Requests for interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to InterNational Committee for Infor

25、mationTechnology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC20005.This standard was processed and approved for submittal to ANSI by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted for its approval. At the time it app

26、roved this standard, INCITS had thefollowing members:iiiDon Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe Systems, Inc. .Scott FosheeSteve Zilles (Alt.)AIM Global, Inc. Dan MullenCharles Biss (Alt.)Apple Computer, Inc. Kwok LauHelene Workman (Alt.)David

27、Singer (Alt.)Distributed Managment Task ForceTony DiCenzoJeff Hilland (Alt.)Winston Bumpus (Alt.)Electronic Industries Alliance Edward Mikoski, Jr.EMC Corporation Gary RobinsonFarance, Inc. .Frank FaranceTimothy Schoechle (Alt.)Google Zaheda BhoratRobert Tai (Alt.)GS1 US.Ray DelnickiFrank Sharkey (A

28、lt.)James Chronowski (Alt.)Mary Wilson (Alt.)Hewlett-Packard Company .Paul JeranKaren Higginbottom (Alt.)Scott Jameson (Alt.)IBM CorporationRonald F. SillettiRobert Weir (Alt.)IEEEJudith GormanTerry DeCourcelle (Alt.)Bill Ash (Alt.)Jodie Haasz (Alt.)Bob Labelle (Alt.)Susan Tatiner (Alt.)Intel .Phili

29、p WennblomDave Thewlis (Alt.)Grace Wei (Alt.)Lexmark International .Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Microsoft CorporationJim HughesDave Welsh (Alt.)Mark Ryland (Alt.)National Institute of Standards this flow shall be repeated for every finger pattern record in the data file. Start Ope

30、n/parse the data file containing fingerprint pattern in accordance with ANSI INCITS 377-2004 Level 1 testing: Verify value of each field and the ranges of the values in those fields Level 2 testing: Verify values of those specified fields are internally consistent. Output test report Figure 1 ANSI I

31、NCITS 377-2004 BDR File Format Level 1 and Level 2 Conformance Test Flow This testing methodology can only demonstrate nonconformity (i.e., if errors are found, nonconformance of the IUT shall be proven), but the absence of errors does not necessarily imply the converse. This test method is intended

32、 to provide a reasonable level of confidence and practical assurance that the IUT conforms to the base standard. To guarantee such conformity, a very exhaustive testing would be required, which is impractical for both technical and economic reasons. 6.3.2 Test Method Implementation Requirements A te

33、st method implementation shall document that it conforms to this standard by including the following: a) A CTS conformant to ANSI INCITS 377-2004 that includes documentation of the test suite, describing test categories, test objectives for each individual test, instructions on how to execute the te

34、st suite, and the expected results of executing the individual tests. The CTS shall be capable of executing the test script sets, capturing the returned results, evaluating the results, and reporting them in a human-readable form. b) Documented test cases that shall sufficiently assure conformity to

35、 the requirements as specified in the base standard. The test cases shall be formally represented in the form of test assertions, preferably using a test assertion language, which can be submitted to the CTS for subsequent execution. c) A Conformance Testing Procedure, which shall identify and defin

36、e all the activities necessary to prepare for conformance testing, perform the conformance testing and report the test results. The procedure shall be detailed enough so that testing of a given IUT can be repeated with no significant changes in test results. The procedure shall also identify necessa

37、ry administrative processes that may include record keeping, personnel, security, and other requirements. A test method implementation shall use the required assertion definitions, types, syntax, and constructs specified in this standard as applicable. Also, it shall use test result codes specified

38、in this standard. INCITS 423.3-2009 9 6.3.3 Conformance Testing Process The conformance testing process is the complete process of accomplishing of all conformance testing activities necessary to assess the conformity of an IUT to the requirements as specified in ANSI INCITS 377-2004. The conformanc

39、e testing process involves three phases: 1) Preparation for testing, which includes the collection of the necessary information that is related to the submitted finger pattern records that needs to be included in the test report. 2) Test execution, which includes execution of the CTS and recording t

40、he observed test results in conformity test log(s). The results of conformance testing shall apply only to the IUT and the test environment for which the tests are run. 3) Test report production, which includes the recording of all events that occur during the execution of each test case, including

41、all test outcomes and test verdicts. To achieve the objective of credible conformance testing, the result of executing a test case on an IUT should be the same whenever it is performed. It may be necessary to review the observed test outcomes in order to make sure that all procedures have been corre

42、ctly followed. It is essential that all inputs, outputs, and other test events be logged for each test case being executed with sufficient information to produce a conformity log for each test execution for future reference. 6.4 Test Procedures 6.4.1 General A software product can claim conformance

43、to requirements as specified in ANSI INCITS 377-2004 and document this claim in the FCS as described in 6.1.3. Conformance of a software product with respect to the ability to produce finger pattern data records shall be verified by testing the conformance of a reasonable number of data records crea

44、ted by the product. Please refer to 6.1 of ANSI INCITS 423.1-2008. The product shall be determined to be conformant to the requirements as specified in ANSI INCITS 377-2004 if and only if all those data records (tested using the test assertions specified in Clause 7) have passed the tests. Most soft

45、ware products that process finger pattern data records will emit some form of error message when they detect an invalid input (for example, an error message may be directed to a user through the user interface or may be written to a log file). Conformance testing of software products that process da

46、ta records can only be performed if the product emits error messages that are observable by a testing operator. Every file that conforms to ANSI INCITS 377-2004 must be able to be fully parsed or partially parsed by the CTS. Failure to meet ANSI INCITS 377-2004 for a single test input file results i

47、n the test case failing to be conformant for the test. The test procedures are based on the three-levels testing specification described in ANSI INCITS 423.1-2008. 6.4.2 ANSI INCITS 377-2004 Level 1 and 2 Conformant Testing Procedure Flow Chart Figure 2 shows the detailed flow of the BDIR data file

48、conformance testing implementation procedure. The flow chart in figure 2 starts with parsing of the finger image-based BDIRs and then proceeds to evaluate the values in each data field. In this figure, finger image-based BDIR indicates the dataset file containing data records under test. 6.4.3 Test

49、Execution The execution of the conformance test shall include execution of a Conformance Test Suite (CTS) capable of processing the test cases (test assertions) specified in clause 7. The test execution shall include automated and/or manual testing INCITS 423.3-2009 10 procedures implementing individual test cases, and recording the observed test results in conformity test log(s). The results of conformance testing shall apply only to IUT and the test environment for which the tests a