1、 International Telecommunication Union ITU-T Z.163TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2007) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Testing and Test Control Notation (TTCN) Testing and Test Control Notation ve
2、rsion 3: TTCN-3 graphical presentation format (GFT) ITU-T Recommendation Z.163 ITU-T Z-SERIES RECOMMENDATIONS LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS FORMAL DESCRIPTION TECHNIQUES (FDT) Specification and Description Language (SDL) Z.100Z.109 Application of formal descrip
3、tion techniques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 Extended Object Definition Language (eODL) Z.130Z.139 User Requirements Notation (URN) Z.150Z.159 Testing and Test Control Notation (TTCN) Z.160Z.199 PROGRAMMING LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE L
4、ANGUAGE General principles Z.300Z.309 Basic syntax and dialogue procedures Z.310Z.319 Extended MML for visual display terminals Z.320Z.329 Specification of the man-machine interface Z.330Z.349 Data-oriented human-machine interfaces Z.350Z.359 Human-machine interfaces for the management of telecommun
5、ications networks Z.360Z.379 QUALITY Quality of telecommunication software Z.400Z.409 Quality aspects of protocol-related Recommendations Z.450Z.459 METHODS Methods for validation and testing Z.500Z.519 MIDDLEWARE Processing environment architectures Z.600Z.609 For further details, please refer to t
6、he list of ITU-T Recommendations. ITU-T Rec. Z.163 (11/2007) i ITU-T Recommendation Z.163 Testing and Test Control Notation version 3: TTCN-3 graphical presentation format (GFT) Summary ITU-T Recommendation Z.163 defines the graphical presentation format for the TTCN-3 core language as defined in IT
7、U-T Recommendation Z.161. This presentation format uses a subset of Message Sequence Charts as defined in ITU-T Recommendation Z.120 with test specific extensions. This Recommendation is based on the core TTCN-3 language defined in ITU-T Recommendation Z.161. It is particularly suited to display tes
8、ts as GFTs. It is not limited to any particular kind of test specification. The specification of other formats is outside the scope of this Recommendation. Source ITU-T Recommendation Z.163 was approved on 13 November 2007 by ITU-T Study Group 17 (2005-2008) under the ITU-T Recommendation A.8 proced
9、ure. ii ITU-T Rec. Z.163 (11/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of
10、 ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topic
11、s for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepa
12、red on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may
13、 contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to expr
14、ess requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Prop
15、erty Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of
16、 intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008 A
17、ll rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Z.163 (11/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Abbreviations 1 4 Overview 2 5 GFT language concepts 3 6 Mapping between GFT and TTCN-3 Co
18、re language . 5 7 Module structure. 5 8 GFT symbols 7 9 GFT diagrams . 9 9.1 Common properties 9 9.2 Control diagram 10 9.3 Test case diagram . 11 9.4 Function diagram 12 9.5 Altstep diagram 13 10 Instances in GFT diagrams . 14 10.1 Control instance 14 10.2 Test component instances. 14 10.3 Port ins
19、tances 15 11 Elements of GFT diagrams. 15 11.1 General drawing rules. 15 11.2 Invoking GFT diagrams . 17 11.3 Declarations 19 11.4 Basic program statements. 21 11.5 Behavioural program statements 24 11.6 Default handling . 29 11.7 Configuration operations 30 11.8 Communication operations. 33 11.9 Ti
20、mer operations. 52 11.10 Test verdict operations . 55 11.11 External actions 56 11.12 Specifying attributes. 56 Annex A GFT BNF. 57 A.1 Meta-language for GFT 57 A.2 Conventions for the syntax description 57 A.3 The GFT grammar 58 Annex B Reference guide for GFT. 81 iv ITU-T Rec. Z.163 (11/2007) Page
21、 Annex C Examples . 110 C.1 The Restaurant example . 110 C.2 The INRES example. 119 ITU-T Rec. Z.163 (11/2007) v Introduction The graphical presentation format of TTCN-3 (GFT) is based on ITU-T Z.120 defining Message Sequence Charts (MSC). GFT uses a subset of MSC with test specific extensions. The
22、majority of extensions are textual extensions only. Graphical extensions are defined to ease the readability of GFT diagrams. Where possible, GFT is defined like MSC, so that established MSC tools with slight modifications can be used for the graphical definition of TTCN-3 test cases in terms of GFT
23、. The core language of TTCN-3 is defined in ITU-T Z.161 and provides a full text-based syntax, static semantics and operational semantics as well as a definition for the use of the language with ASN.1. The GFT presentation format provides an alternative way of displaying the core language (see Figur
24、e 1). TTCN-3 Core Language Presentation formatnTTCN-3 User ASN.1 Types the guidelines for the use of GFT; the grammar of GFT; the mapping from and to the TTCN-3 core language. Together, these characteristics form the graphical presentation format of TTCN-3. ITU-T Rec. Z.163 (11/2007) 1 ITU-T Recomme
25、ndation Z.163 Testing and Test Control Notation version 3: TTCN-3 graphical presentation format (GFT) 1 Scope This Recommendation defines the graphical presentation format for the TTCN-3 core language as defined in ITU-T Z.161. This presentation format uses a subset of Message Sequence Charts as def
26、ined in ITU-T Z.120 with test specific extensions. This Recommendation is based on the core TTCN-3 language defined in ITU-T Z.161. It is particularly suited to display tests as GFTs. It is not limited to any particular kind of test specification. The specification of other formats is outside the sc
27、ope of this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other refer
28、ences are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference
29、to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T X.292 ITU-T Recommendation X.292 (2002), OSI conformance testing methodology and framework for protocol Recommendations for ITU-T applications The Tree and Tabular Combined Not
30、ation (TTCN). ISO/IEC 9646-3:1998, Information technology Open Systems Interconnection Conformance testing methodology and framework Part 3: The Tree and Tabular Combined Notation (TTCN). ITU-T Z.120 ITU-T Recommendation Z.120 (2004), Message sequence chart (MSC). ITU-T Z.161 ITU-T Recommendation Z.
31、161 (2007), Testing and Test Control Notation version 3: TTCN-3 core language. ITU-T Z.162 ITU-T Recommendation Z.162 (2007), Testing and Test Control Notation version 3: TTCN-3 tabular presentation format (TFT). 3 Abbreviations This Recommendation uses the following abbreviations and acronyms: BNF
32、Backus-Naur Form CATG Computer Aided Test Generation GFT Graphical presentation Format of TTCN-3 MSC Message Sequence Chart MTC Main Test Component PTC Parallel Test Component SUT System Under Test 2 ITU-T Rec. Z.163 (11/2007) TFT Tabular presentation Format of TTCN-3 TTCN Testing and Test Control N
33、otation 4 Overview According to the OSI conformance testing methodology defined in ITU-T X.292, testing normally starts with the identification of test purposes. A test purpose is defined as: “A prose description of a well-defined objective of testing, focusing on a single conformance requirement or
34、 a set of related conformance requirements as specified in the appropriate OSI specification“. Having identified all test purposes an abstract test suite is developed that consists of one or more abstract test cases. An abstract test case defines the actions of the tester processes necessary to vali
35、date part (or all) of a test purpose. Applying these terms to Message Sequence Charts (MSCs) we can define two categories for their usage: 1) Using MSCs for the definition of test purposes Typically, an MSC specification that is developed as a use-case or as part of a system specification can be vie
36、wed as test purpose, i.e., it describes a requirement for the SUT in the form of a behaviour description that can be tested. For example, Figure 2 presents a simple MSC describing the interaction between instances representing the SUT and its interfaces A, B and C. In a real implementation of such a
37、 system the interfaces A, B and C may map onto service access points or ports. The MSC in Figure 2 only describes the interaction with the SUT and does not describe the actions of the test components necessary to validate the SUT behaviour, i.e., it is a test purpose description. BSUT CA a b c msc T
38、estPurposeExample Figure 2 MSC describing the interaction of an SUT with its interfaces 2) Using MSCs for the definition of abstract test cases An MSC specification describing an abstract test case specifies the behaviour of the test components necessary to validate a corresponding test purpose. Fig
39、ure 3 presents a simple MSC abstract test case description. It shows one Main Test Component (MTC) that exchanges the messages a, b and c with the SUT via the ports PortA, PortB and PortC in order to reach the test purpose shown in Figure 2. The messages a and c are sent by the SUT via the ports A a
40、nd B (Figure 2) and received by the MTC (Figure 3) via the same ports. The message b is sent by the MTC and received by the SUT. NOTE The examples in Figures 2 and 3 are only simple examples to illustrate the different usages of MSC for testing. The diagrams will be more complicated in case of a dis
41、tributed SUT that consists of several processes or a distributed test configuration with several test components. ITU-T Rec. Z.163 (11/2007) 3 PortBMTC PortCPortA a b c msc AbstractTestCaseExample Figure 3 MSC describing the interaction of an MTC with SUT interfaces In identifying these two categori
42、es of MSC usage two distinct areas of work can be identified (see Figure 4): a) Generation of abstract test cases from MSC test purpose descriptions TTCN-3 core language or GFT may be used to represent the abstract test cases. However, it is perceived that test case generation from test purposes is
43、non-trivial and involves the usage and development of Computer Aided Test Generation (CATG) techniques. b) Development of a Graphical presentation format for TTCN-3 (GFT) and definition of the mapping between GFT and TTCN-3. generategeneratemappingMSC test purpose MSC test case (GFT diagram) TTCN-3
44、test case Figure 4 Relations between MSC test purpose description, MSC test case descriptions and TTCN-3 This Recommendation focuses on item b), i.e., it defines GFT and the mapping between GFT and the TTCN-3 core language. 5 GFT language concepts GFT represents graphically the behavioural aspects o
45、f TTCN-3 like the behaviour of a test case or a function. It does not provide graphics for data aspects like declaration of types and templates. GFT defines no graphical representation for the structure of a TTCN-3 module, but specifies the requirements for such a graphical representation (see also
46、clause 7). NOTE The order and the grouping of definitions and declarations in the module definitions part define the structure of a TTCN-3 module. 4 ITU-T Rec. Z.163 (11/2007) GFT defines no graphical representation for: module parameter definitions; import definitions; type definitions; signature d
47、eclarations; template declarations; constant declarations; external constant declarations; and external function declarations. TTCN-3 definitions and declarations without a corresponding GFT presentation may be presented in the TTCN-3 core language or in the tabular presentation format for TTCN-3 (T
48、FT) (ITU-T Z.162). GFT provides graphics for TTCN-3 behaviour descriptions. This means a GFT diagram provides a graphical presentation of either: the control part of a TTCN-3 module; a TTCN-3 test case; a TTCN-3 function; or a TTCN-3 altstep. The relation between a TTCN-3 module and a corresponding
49、GFT presentation is shown in Figure 5. TTCN-3 module in core language GFT presentation module structure Requirements for the graphical presentation of the module structuremodule parameter definitions, import definitions, type definitions, signature declarations, template declarations, constant declarations, external constant declarations, tlftidltiNo graphical representation module control Graphical representation (Control diagram) testcase function altstep Graphical representation (Test ca
copyright@ 2008-2019 麦多课文库（www.mydoc123.com）网站版权所有
备案/许可证编号：苏ICP备17064731号-1