ISO IEC 19514-2017 Information technology - Object management group systems modeling language (OMG SysML)《信息技术 对象管理组系统建模语言(OMG SysML)》.pdf

1、Information technology Object management group systems modeling language (OMG SysML) Technologies de linformation Langage de modlisation de sytmes OMG (OMG SysML) INTERNATIONAL STANDARD ISO/IEC 19514 Reference number ISO/IEC 19514:2017(E) First edition 2017-03 ISO/IEC 2017 ii ISO/IEC 2017 All rights

2、 reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet

3、 or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 cop

4、yrightiso.org www.iso.org ISO/IEC 19514:2017(E)ISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved iii Table of Contents FOREWORD .xix INTRODUCTION. xx 1 Scope 1 1.1 General 1 2 Normative References. 1 3 Additional Information 2 3.1 Relationships to Other Standards .2 3.2 How to Read this Inter

5、national Standard.2 3.2.1 Organization 3 3.3 Acknowledgments .4 4 Language Architecture 7 4.1 General 7 4.2 Design Principles.10 4.3 Architecture .10 4.4 Extension Mechanisms .13 4.5 SysML Diagrams .13 5 Conformance. 15 5.1 Overview .15 5.2 Conformance Types 15 6 Language Formalism. 17 6.1 Levels of

6、 Formalism 17 6.2 Clause Structure17 6.2.1 Overview . 17 6.2.2 Diagram Elements 17 6.2.3 UML Extensions 17 6.2.4 Usage Examples. 18 6.3 Conventions and Typography .18 STRUCTURAL CONSTRUCTS 19ISO/IEC 19514:2017(E) iv ISO/IEC 2017 - All rights reserved 7 Model Elements.21 7.1 Overview21 7.1.1 View and

7、 Viewpoint. 21 7.2 Diagram Elements.22 7.3 UML Extensions 25 7.3.1 Diagram Extensions 257.3.1.1 UML Diagram Elements not Included in SysML .25 7.3.2 Stereotypes. 267.3.2.1 Conform 267.3.2.2 ElementGroup 277.3.2.3 Expose .287.3.2.4 Problem 287.3.2.5 Rationale 297.3.2.6 Stakeholder 297.3.2.7 View 297.

8、3.2.8 Viewpoint 30 7.4 Usage Examples .30 8 Blocks 33 8.1 Overview33 8.2 Diagram Elements.34 8.2.1 Block Definition Diagram. 34 8.2.2 Internal Block Diagram 40 8.3 UML Extensions 42 8.3.1 Diagram Extensions 428.3.1.1 Block Definition Diagram 428.3.1.2 Internal Block Diagram .448.3.1.3 UML Diagram El

9、ements not Included in SysML Block Definition Diagrams .468.3.1.4 UML Diagram Elements not Included in SysML Internal Block Diagrams 46 8.3.2 Stereotypes. 478.3.2.1 AdjunctProperty 498.3.2.2 Binding Connector 508.3.2.3 Block .518.3.2.4 Bound Reference .538.3.2.5 ClassifierBehaviorProperty .548.3.2.6

10、 ConnectorProperty .548.3.2.7 DirectedRelationshipPropertyPath .558.3.2.8 DistributedProperty .568.3.2.9 ElementPropertyPath .568.3.2.10 EndPathMultiplicity .568.3.2.11 NestedConnectorEnd .578.3.2.12 ParticipantProperty .578.3.2.13 PropertySpecificType .588.3.2.14 ValueType 58 8.3.3 Model Libraries

11、59ISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved v8.3.3.1 Package PrimitiveValueTypes 598.3.3.2 Package UnitAndQuantityKind .60 8.4 Usage Examples .62 8.4.1 Wheel Hub Assembly 62 8.4.2 Example Value Type Definitions . 64 8.4.3 Design Configuration for SUV EPA Fuel Economy Test. 65 8.4.4 Wa

12、ter Delivery 65 8.4.5 Constraining Decomposition .65 8.4.6 Units and Quantity Kinds 67 9 Ports and Flows. 71 9.1 Overview .71 9.1.1 Ports 71 9.1.2 Flow Properties, Provided and Required Features, and Nested Ports . 71 9.1.3 Proxy Ports and Full Ports 71 9.1.4 Item Flows. 72 9.1.5 Deprecation of Flow

13、 Ports and Flow Specifications 72 9.2 Diagram Elements.73 9.2.1 Block Definition Diagram. 73 9.2.2 Internal Block Diagram 76 9.3 UML Extensions 78 9.3.1 Diagram Extensions 789.3.1.1 DirectedFeature 789.3.1.2 FlowProperty 789.3.1.3 FullPort .789.3.1.4 InvocationOnNestedPortAction 789.3.1.5 ItemFlow .

14、789.3.1.6 Port. 789.3.1.7 ProxyPort 799.3.1.8 TriggerOnNestedPort .79 9.3.2 Stereotypes. 799.3.2.1 AcceptChangeStructuralFeatureEventAction .819.3.2.2 Block 829.3.2.3 ChangeStructuralFeatureEvent 829.3.2.4 DirectedFeature 829.3.2.5 FeatureDirection .839.3.2.6 FlowDirection 849.3.2.7 FlowProperty 849

15、3.2.8 FullPort .859.3.2.9 InterfaceBlock .869.3.2.10 InvocationOnNestedPortAction 869.3.2.11 ItemFlow .869.3.2.12 ProxyPort 879.3.2.13 TriggerOnNestedPort .88ISO/IEC 19514:2017(E) vi ISO/IEC 2017 - All rights reserved 9.4 Usage Examples .89 9.4.1 Ports with Required and Provided Features . 89 9.4.2

16、 Flow Ports and Item Flows 89 9.4.3 Ports with Flow Properties 90 9.4.4 Proxy and Full Ports 90 9.4.5 Association and Port Decomposition 91 9.4.6 Item Flow Decomposition 95 10 Constraint Blocks.97 10.1 Overview97 10.2 Diagram Elements.98 10.2.1 Block Definition Diagram. 98 10.2.2 Parametric Diagram

17、98 10.3 UML Extensions 99 10.3.1 Diagram Extensions 9910.3.1.1 Block Definition Diagram .9910.3.1.2 Parametric Diagram 101 10.3.2 Stereotypes. 10010.3.2.1 ConstraintBlock 101 10.4 Usage Examples .101 10.4.1 Definition of Constraint Blocks on a Block Definition Diagram 101 10.4.2 Usage of Constraint

18、Blocks on a Parametric Diagram 101 BEHAVIORAL CONSTRUCTS103 11 Activities 105 11.1 Overview105 11.1.1 Control as Data . 105 11.1.2 Continuous Systems . 105 11.1.3 Probability . 105 11.1.4 Activities as Blocks 106 11.1.5 Timelines. 106 11.2 Diagram Elements.107 11.2.1 Activity Diagram 105 11.3 UML Ex

19、tensions 114 11.3.1 Diagram Extensions 11411.3.1.1 Activity 11411.3.1.2 CallBehaviorAction .11511.3.1.3 ControlFlow 11611.3.1.4 ObjectNode, Variables, and Parameters 116 11.3.2 Stereotypes. 11711.3.2.1 Continuous .118ISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved vii11.3.2.2 ControlOperato

20、r 11911.3.2.3 Discrete 11911.3.2.4 NoBuffer .11911.3.2.5 Overwrite 12011.3.2.6 Optional 12011.3.2.7 Probability .12011.3.2.8 Rate 121 11.3.3 Model Libraries . 12111.3.3.1 Package ControlValues 121 11.4 Usage Examples .122 12 Interactions 127 12.1 Overview .127 12.2 Diagram Elements.128 12.2.1 Sequen

21、ce Diagram . 128 12.3 UML Extensions 133 12.3.1 Diagram Extensions 13312.3.1.1 Exclusion of Communication Diagram, Interaction Overview Diagram, and Timing Diagram .13312.3.1.2 Interactions and Parameters .133 12.4 Usage Examples .134 12.4.1 Sequence Diagrams .134 13 State Machines 135 13.1 Overview

22、 .135 13.2 Diagram Elements.135 13.2.1 State Machine Diagram 135 13.3 UML Extensions 140 13.3.1 Diagram Extensions 14013.3.1.1 State Machines and Parameters .140 13.4 Usage Examples .140 13.4.1 State Machine Diagram 140 14 Use Cases. 141 14.1 Overview .141 14.2 Diagram Elements.142 14.2.1 Use Case D

23、iagram 142 14.3 UML Extensions 143 14.4 Usage Examples .143 CROSSCUTTING CONSTRUCTS 145ISO/IEC 19514:2017(E) viii ISO/IEC 2017 - All rights reserved 15 Allocations .147 15.1 Overview147 15.2 Diagram Elements.147 15.2.1 Representing Allocation on Diagrams. 148 15.3 UML Extensions .149 15.3.1 Diagram

24、Extensions 14915.3.1.1 Tables .14915.3.1.2 Allocate Relationship Rendering 14915.3.1.3 Allocation Compartment Format .14915.3.1.4 Allocation Callout Format .14915.3.1.5 AllocatedActivityPartition Label 149 15.3.2 Stereotypes. 15015.3.2.1 Allocate(from Allocations) .15015.3.2.2 AllocateActivityPartit

25、ion(from Allocations) 151 15.4 Usage Examples .152 15.4.1 Behavior Allocation of Actions to Parts and Activities to Blocks . 152 15.4.2 Allocate Flow. 15315.4.2.1 Allocating Structure .15415.4.2.2 Automotive Example 154 15.4.3 Tabular Representation. 155 16 Requirements 157 16.1 Overview157 16.2 Dia

26、gram Elements.159 16.2.1 Requirement Diagram. 159 16.3 UML Extensions 162 16.3.1 Diagram Extensions 16216.3.1.1 Requirement Diagram 16216.3.1.2 Requirement Notation 16216.3.1.3 Requirement Property Callout Format 16216.3.1.4 Requirements on Other Diagrams 16216.3.1.5 Requirements Table .163 16.3.2 S

27、tereotypes. 16416.3.2.1 Copy .16416.3.2.2 DeriveReqt .16516.3.2.3 Refine .16516.3.2.4 Requirement .16516.3.2.5 TestCase 16716.3.2.6 Satisfy .16716.3.2.7 Trace 16716.3.2.8 Verify 168 16.4 Usage Examples .168 16.4.1 Requirement Decomposition and Traceability 168 16.4.2 Requirements and Design Elements

28、 169ISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved ix 16.4.3 Requirements Reuse 171 16.4.4 Verification Procedure (Test Case). 172 17 Profiles & Model Libraries 175 17.1 Overview .175 17.2 Diagram Elements.176 17.2.1 Profile Definition in Package Diagram 17617.2.1.1 Extension .178 17.2.2

29、Stereotypes Used On Diagrams . 17817.2.2.1 StereotypeInNode 17917.2.2.2 StereotypeInComment .18017.2.2.3 StereotypeInCompartment .180 17.3 UML Extensions 180 17.4 Usage Examples .180 17.4.1 Defining a Profile. 180 17.4.2 Adding Stereotypes to a Profile 181 17.4.3 Defining a Model Library that Uses a

30、 Profile. 182 17.4.4 Guidance on Whether to Use a Stereotype or Class 183 17.4.5 Using a Profile. 183 17.4.6 Using a Stereotype . 184 17.4.7 Using a Model Library Element. 184 ANNEXES . 187 Annex A: Diagrams. 189 Annex B: SysML Diagram Interchange 195 Annex C: Deprecated Elements . 205 Annex D: Samp

31、le Problem . 213 Annex E: Non-normative Extensions 251 Annex F: Requirements Traceability 319 Annex G: Model Interchange 321 Annex H: Legal Information 325ISO/IEC 19514:2017(E) x ISO/IEC 2017 - All rights reservedISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved xi List of Figures Figure 4.1

32、 Overview of SysML/UML Interrelationship.7 Figure 4.2 - SysML Extension of UML11 Figure 4.3 - SysML Package Structure .12 Figure 4.4 - Non-normative Package Structure.13 Figure 7.1 - Stereotypes defined in package ModelElements.26 Figure 7.2 - Rationale and Problem examples 31 Figure 8.1 - Nested p

33、roperty reference .45 Figure 8.2 - Abstract syntax extensions for SysML blocks 47 Figure 8.3 - Abstract syntax extensions for SysML properties.47 Figure 8.4 - Abstract syntax extensions for SysML value types.47 Figure 8.5 - Abstract syntax extensions for SysML property paths48 Figure 8.6 - Abstract

34、syntax extensions for SysML connector ends.48 Figure 8.7 - Abstract syntax extensions for SysML property-specific types48 Figure 8.8 - Abstract syntax extensions for SysML bound references .49 Figure 8.9 - Abstract syntax extensions for SysML adjunct properties and classifier behavior properties49 F

35、igure 8.10 - Model library for primitive value types 59 Figure 8.11 - Model library for Unit and QuantityKind .60 Figure 8.12 - Block diagram for the Wheel Package63 Figure 8.13 - Internal Block Diagram for WheelHubAssembly.64 Figure 8.14 - Defining Value Types with units of measure from the Interna

36、tional System of Units (SI) 64 Figure 8.15 - Vehicle decomposition 65 Figure 8.16 - Vehicle internal structure.66 Figure 8.17 - Vehicle specialization66 Figure 8.18 - Example of Unit, QuantityKind and ValueType definitions .67 Figure 8.19 - Instance-level view of the Unit, QuantityKind and ValueType

37、 definitions 68 Figure 8.20 - Example of equivalent Unit representations .68 Figure 8.21 - Instance-level representation of equivalent Unit definitions.69 Figure 9.1 - Port Stereotypes79 Figure 9.2 - Stereotypes for Actions on Nested Ports.80 Figure 9.3 - Stereotypes for Property Value Change Events

38、80 Figure 9.4 - Provided and Required Features80 Figure 9.5 - ItemFlow Stereotype .81 Figure 9.6 - Usage example of ports with provided and required features.89 Figure 9.7 Usage example of proxy and full ports.91 Figure 9.8 - Water Delivery association block92 Figure 9.9 - Internal structure of Wat

39、er Delivery association block .92 Figure 9.10 - Two views of Water Delivery connector within House block.93 Figure 9.11 - Specializations of Water Client in house example 93 Figure 9.12 - Plumbing association block.94 Figure 9.13 - Internal structure of Plumbing association block94 Figure 9.14 - Wat

40、er Delivery association block with internal Plumbing connector .94ISO/IEC 19514:2017(E) xii ISO/IEC 2017 - All rights reserved Figure 9.15 - Usage example of item flows in internal block diagrams .95 Figure 9.16 - Usage example of item flow decomposition .96 Figure 9.17 - Usage example of item flow

41、decomposition .96 Figure 10.1 - Stereotypes defined in SysML ConstraintBlocks package100 Figure 11.1 - Block definition diagram with activities as blocks115 Figure 11.2 - CallBehaviorAction notation.with behavior stereotype 115 Figure 11.3 - CallBehaviorAction notation.with action name 115 Figure 11

42、4 - Control flow notation.116 Figure 11.5 - Block definition diagram with activities as blocks associated with types of object nodes, variables, and parameters116 Figure 11.6 - ObjectNode notation in activity diagrams.117 Figure 11.7 - ObjectNode notation in activity diagrams.117 Figure 11.8 - Abst

43、ract Syntax for SysML Activity Extensions 118 Figure 11.9 - Control values121 Figure 11.10 - Continuous system example 1 .123 Figure 11.11 - Continuous system example 2 .124 Figure 11.12 - Continuous system example 3 .124 Figure 11.13 - Example block definition diagram for activity decomposition .12

44、5 Figure 11.14 - Example block definition diagram for object node types125 Figure 12.1 - Block definition diagram with interactions as blocks associated with used interactions and types of parameters.133 Figure 13.1 - Block definition diagram with state machines as blocks associated with submachines

45、 and types of parameters.140 Figure 15.1 - Abstract syntax extensions for SysML Allocation150 Figure 15.2 - Abstract syntax expression for AllocatedActivityPartition.150 Figure 15.3 - Generic Allocation, including /from and /to association ends 152 Figure 15.4 - Behavior allocation152 Figure 15.5 -

46、Example of flow allocation from ObjectFlow to Connector.153 Figure 15.6 - Example of flow allocation from ObjectFlow to ItemFlow 153 Figure 15.7 - Example of flow allocation from ObjectNode to FlowProperty .154 Figure 15.8 - Example of Structural Allocation154 Figure 15.9 - Allocation Matrix showing

47、 Allocation for Hybrid SUV Accelerate Example155 Figure 16.1 - Non-normative Examples of Tabular Representations of Requirements 163 Figure 16.2 - Abstract Syntax for Requirements Stereotypes.164 Figure 16.3 - Requirements Derivation.169 Figure 16.4 - Links between requirements and design170 Figure

48、16.5 - Requirement satisfaction in an internal block diagram .171 Figure 16.6 - Use of the copy dependency to facilitate reuse .171 Figure 16.7 - Linkage of a Test Case to a requirement: This figure shows the Requirement Diagram 172 Figure 16.8 - Linkage of a Test Case to a requirement: This figure

49、shows the Test Case as a State Diagram.173 Figure 17.1 - Defining a stereotype.178 Figure 17.2 - Using a stereotype .179ISO/IEC 19514:2017(E) ISO/IEC 2017 - All rights reserved xiii Figure 17.3 - Using stereotypes and showing values180 Figure 17.4 - Other notational forms for showing values .180 Figure 17.5 - Definition of a profile181 Figure 17.6 - Profile Contents.181 Figure 17.7 - Two model libraries.182 Figure 17.8 - A model with applied profile and imported model library183 Figure 17.9 - Using two