1、 International Telecommunication Union ITU-T Z.109TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (10/2013) SERIES Z: LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS Formal description techniques (FDT) Specification and Description Language (SDL) Specification and Description La
2、nguage Unified modeling language profile for SDL-2010 Recommendation ITU-T Z.109 ITU-T Z-SERIES RECOMMENDATIONS LANGUAGES AND GENERAL SOFTWARE ASPECTS FOR TELECOMMUNICATION SYSTEMS FORMAL DESCRIPTION TECHNIQUES (FDT) Specification and Description Language (SDL) Z.100Z.109Application of formal descri
3、ption techniques Z.110Z.119 Message Sequence Chart (MSC) Z.120Z.129 User Requirements Notation (URN) Z.150Z.159 Testing and Test Control Notation (TTCN) Z.160Z.179 PROGRAMMING LANGUAGES CHILL: The ITU-T high level language Z.200Z.209 MAN-MACHINE LANGUAGE General principles Z.300Z.309 Basic syntax an
4、d 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 telecommunications networks Z.360Z.379 QUALITY Quality of telec
5、ommunication 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 the list of ITU-T Recommendations. Rec. ITU-T Z.109 (1
6、0/2013) i Recommendation ITU-T Z.109 Specification and Description Language Unified modeling language profile for SDL-2010 Summary Objective: Recommendation ITU-T Z.109 defines a unified modeling language (UML) profile that maps to SDL-2010 semantics so that UML is able to be used in combination wit
7、h the ITU-T Specification and Description Language. Appendix I includes an (informative) Example language specification for a concrete grammar and its mapping to the UML profile. Coverage: This Recommendation presents a definition of the UML-to-SDL-2010 mapping for use in the combination of SDL-2010
8、 and UML. Application: The main area of application of this Recommendation is the specification of telecommunication systems. The combined use of SDL-2010 and UML permits a coherent way to specify the structure and behaviour of telecommunication systems, together with data. Status/Stability: This Re
9、commendation is the complete reference manual describing the UML to SDL-2010 mapping for use in the combination of SDL-2010 and UML. It replaces the previous Recommendation ITU-T Z.109 that concerned earlier versions of UML and Specification and Description Language. Associated work: Recommendations
10、 ITU-T Z.100, ITU-T Z.101, ITU-T Z.102, ITU-T Z.103, ITU-T Z.104 and ITU-T Z.107 concerning the ITU-T Specification and Description Language 2010 (SDL-2010). History Edition Recommendation Approval Study Group Unique ID*1.0 ITU-T Z.109 1999-11-19 10 11.1002/1000/4767-en 2.0 ITU-T Z.109 2007-06-13 17
11、 11.1002/1000/9117-en 3.0 ITU-T Z.109 2012-04-29 17 11.1002/1000/11583-en3.1 ITU-T Z.109 (2012) Amd. 1 2012-11-29 17 11.1002/1000/11759-en4.0 ITU-T Z.109 2013-10-14 17 11.1002/1000/12035-en_ *To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, f
12、ollowed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T Z.109 (10/2013) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technol
13、ogies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of 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 Telecomm
14、unication Standardization Assembly (WTSA), which meets every four years, establishes the topics 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
15、 of information technology which fall within ITU-Ts purview, the necessary standards are prepared 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 opera
16、ting agency. Compliance with this Recommendation is voluntary. However, the Recommendation may 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
17、“ or some other obligatory language such as “must“ and the negative equivalents are used to express 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 prac
18、tice or implementation of this Recommendation may involve the use of a claimed Intellectual Property 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 develo
19、pment process. As of the date of approval of this Recommendation, ITU had not received notice of 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 therefo
20、re strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Z.109 (10/2013) iii Table of Contents Page 1 Scope and o
21、bjectives 1 1.1 Conformance 1 1.2 Restrictions on SDL-2010 and UML . 2 1.3 Mapping 2 2 References. 3 3 Definitions 3 3.1 Terms defined elsewhere 3 3.2 Terms defined in this Recommendation . 3 4 Abbreviations and acronyms 4 5 Conventions 4 5.1 Conventions 4 5.2 Names and name resolution: NamedElement
22、 . 5 5.3 Transformation . 8 6 Summary of stereotypes and metaclasses . 8 6.1 Stereotype summary . 8 6.2 Metaclass summary 9 7 Structure 11 7.1 Structure metamodel diagrams . 12 7.2 ActiveClass . 13 7.3 ChoiceType . 16 7.4 Classifier . 17 7.5 Connector . 19 7.6 DataTypeDefinition 21 7.7 Interface 23
23、7.8 LiteralType . 24 7.9 Operation 25 7.10 Package . 28 7.11 Parameter 28 7.12 Port . 30 7.13 Property 31 7.14 Signal 34 7.15 Specification . 35 7.16 StructureType . 35 7.17 Syntype . 36 7.18 Timer 37 8 State machines 37 8.1 State machine metamodel diagrams . 38 iv Rec. ITU-T Z.109 (10/2013) Page 8.
24、2 FinalState 38 8.3 Pseudostate . 39 8.4 Region . 42 8.5 State 43 8.6 StateMachine 45 8.7 Transition 48 9 Actions and activities 51 9.1 Action and activity metamodel diagrams . 52 9.2 Activity . 53 9.3 AssignValueAction . 55 9.4 Break . 55 9.5 CallOperationAction . 56 9.6 ConditionalNode . 57 9.7 Co
25、ntinue . 58 9.8 CreateObjectAction 59 9.9 ExpressionAction . 60 9.10 LoopNode . 60 9.11 ResetAction 61 9.12 Return . 62 9.13 SequenceNode 63 9.14 SendSignalAction . 63 9.15 SetAction 64 9.16 Stop . 65 9.17 Variable 65 10 ValueSpecification 67 10.1 ValueSpecification metamodel diagrams . 67 10.2 Acti
26、veAgentsExpression 70 10.3 AnyExpression . 71 10.4 ClosedRange . 71 10.5 ConditionalExpression . 72 10.6 ConditionItem . 72 10.7 EqualityExpression . 73 10.8 ImperativeExpression . 74 10.9 LiteralValue 74 10.10 NowExpression . 75 10.11 OpenRange . 75 10.12 OperationApplication . 76 10.13 PidExpressi
27、on . 77 10.14 PidExpressionKind . 77 Rec. ITU-T Z.109 (10/2013) v Page 10.15 RangeCheckExpression 78 10.16 RangeCondition 78 10.17 SdlExpression . 79 10.18 SizeConstraint . 79 10.19 StateExpression 80 10.20 TimerActiveExpression 80 10.21 TimerRemainingDuration . 81 10.22 TypeCheckExpression 82 10.23
28、 TypeCoercion . 82 10.24 Undefined . 83 10.25 ValueReturningCallNode . 83 10.26 VariableAccess . 84 11 Context parameters . 85 11.1 Context parameter metamodel diagrams 85 11.2 ActualContextParameter . 88 11.3 AgentContextParameter . 89 11.4 AgentTypeContextParameter . 89 11.5 CompositeStateTypeCont
29、extParameter 90 11.6 FormalContextParameter 91 11.7 GateContextParameter 92 11.8 GateConstraint 92 11.9 InterfaceContextParameter . 93 11.10 ProcedureContextParameter . 94 11.11 SignalContextParameter . 94 11.12 SortContextParameter . 95 11.13 SynonymContextParameter 96 11.14 TimerContextParameter .
30、 96 11.15 VariableContextParameter . 97 12 Predefined data . 97 12.1 Non-parameterized data types 97 12.2 Parameterized data types 99 12.3 Pid . 101 12.4 UndefinedVariable . 101 Appendix I Example language specification 102 I.1 Conventions 102 I.2 Lexical rules and names . 105 I.3 Organization . 114
31、 I.4 Basic concepts 120 I.5 Structure . 132 vi Rec. ITU-T Z.109 (10/2013) Page I.6 Communication 136 I.7 State machine 141 I.8 Sequential behaviour 153 I.9 Data . 164 I.10 Exceptions 191 I.11 Generic system definition . 191 Bibliography. 194 Rec. ITU-T Z.109 (10/2013) vii Introduction The UML profil
32、e presented in Recommendation ITU-T Z.109 is intended to support the usage of UML (version 2 or later) as a front-end for tools supporting specification and implementation of reactive systems, in particular for telecommunication applications. The intention is to enable tool vendors to create tools t
33、hat benefit from the closure of semantic variations in UML with SDL-2010 semantics and benefit from the Specification and Description Language tool technology that supports this particular application area. The intention is that when the profile is applied to a model, the set of stereotypes and meta
34、classes defined in this Recommendation extends the elements in the model and has several consequences: additional properties are available as specified by the stereotype attributes; constraints defined for the stereotypes apply to the model elements introducing more semantic checks that need to be f
35、ulfilled for the model; semantics, in particular dynamic semantics, are defined for the model elements as specified by the mapping of the stereotyped UML concepts to the SDL-2010 abstract grammar. The details of the profile mechanism in this Recommendation follow: The Recommendation is structured in
36、to a number of clauses. Each clause defines one stereotype or metaclass. Each stereotype usually captures the semantics of one SDL-2010 concept based on a UML concept. A stereotype in most cases constrains a UML element with a multiplicity of 11 (that is, the stereotype is required), but in some cas
37、es extends rather than constrains the basic UML language. The UML user never manually has to apply the stereotype to a UML element: instead stereotypes are applied automatically when applying the profile to the model itself, or if the user has not kept within the language defined by this profile a s
38、uitable message is displayed to the user. As a consequence, applying this profile results in extra properties, extra semantic checks, and a clearly comprehensible semantics that can be used in tools to provide features such as static model analysis, simulation and application generation as the model
39、 is sufficiently well defined to be executable. Apart from the set of stereotypes, the Recommendation defines a set of metaclasses as extensions to the UML metamodel in order to represent SDL-2010 expressions and value specifications. This is because the UML concepts for value specification are not
40、appropriate for this purpose. This Recommendation introduces no particular textual notation for stereotypes defined by this UML profile. Instead, a textual notation and its mapping to corresponding model elements has to be defined by an additional description (possibly an ITU-T Recommendation or inf
41、ormation provided by a tool supplier). So that the application of transformation models of SDL-2010 referenced in this profile are understandable, the syntax for an appropriate textual notation should be a subset of the concrete syntax of SDL-2010 or an SDL-like syntax, which is modified to the part
42、icular requirements of a UML-based domain specific language. The idea is that when a user enters the described syntax, a tool should automatically create the corresponding model element with the correct stereotype applied. Rec. ITU-T Z.109 (10/2013) 1 Recommendation ITU-T Z.109 Specification and Des
43、cription Language Unified modeling language profile for SDL-2010 1 Scope and objectives This Recommendation defines a unified modeling language (UML) profile for SDL-2010. It ensures a well-defined mapping between parts of a UML model and the SDL-2010 semantics. The profile is based upon the UML met
44、amodel and upon the abstract grammar of SDL-2010, and in the following text is referred to as SDL-UML. The specializations and restrictions are defined in terms of stereotypes for metaclasses of the UML metamodel and the abstract grammar of SDL-2010 and are in principle independent of any notation.
45、However, to generate particular model elements, especially those that are instances of UML actions or activities, it is assumed that an appropriate notation is specified (see an Example language specification in Appendix I). A software tool that claims to support this Recommendation (hereafter refer
46、red to as a tool) should be capable of creating, editing, presenting and analysing descriptions compliant with this Recommendation. 1.1 Conformance A model that claims to be compliant to this Recommendation shall meet the metamodel constraints of UML and this Recommendation and, when mapped to the a
47、bstract grammar of SDL-2010, shall conform to the abstract grammar of the ITU-T Z.100 series of Recommendations included by reference. A model is non-compliant if it does not meet the constraints of the ITU-T Z.100 series of Recommendations, or if it includes an abstract grammar that is not allowed
48、by the ITU-T Z.100 series of Recommendations, or if it has analysable semantics that can be seen to differ from said series of Recommendations. The abstract grammar of this Recommendation is a profile of UML and a set of additional metaclasses, which are specializations of the UML ValueSpecification
49、 metaclass. Therefore, any model that conforms to this Recommendation also conforms to the requirements of UML. A tool that supports the profile shall support the specializations and restrictions of UML defined in the profile to conform to the Recommendation and should be capable of exporting such models to other tools and of importing such models from other tools. A conformance statement clearly identifying the profile features and requirements not supported should accompany any tool
