{"id":346923,"date":"2024-10-20T00:23:32","date_gmt":"2024-10-20T00:23:32","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-14-30288700-dc\/"},"modified":"2024-10-25T23:51:57","modified_gmt":"2024-10-25T23:51:57","slug":"bsi-14-30288700-dc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-14-30288700-dc\/","title":{"rendered":"BSI 14\/30288700 DC"},"content":{"rendered":"

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
5<\/td>\nCONTENTS <\/td>\n<\/tr>\n
6<\/td>\nForeword <\/td>\n<\/tr>\n
7<\/td>\nIntroduction
0.1 RM-ODP
0.2 UML <\/td>\n<\/tr>\n
8<\/td>\n0.3 Overview and motivation <\/td>\n<\/tr>\n
9<\/td>\n1 Scope
2 Normative references
2.1 Identical Recommendations | International Standards
2.2 Additional References <\/td>\n<\/tr>\n
10<\/td>\n3 Definitions
3.1 Definitions from ODP standards
3.1.1 Modelling concept definitions
3.1.2 Viewpoint language definitions
3.2 Definitions from the Enterprise Language
3.3 Definitions from the Unified Modeling Language <\/td>\n<\/tr>\n
11<\/td>\n4 Abbreviations
5 Conventions <\/td>\n<\/tr>\n
12<\/td>\n6 Overview of modelling and system specification approach
6.1 Introduction
6.2 Overview of ODP concepts (extracted from RM-ODP Part 1)
6.2.1 Object Modelling <\/td>\n<\/tr>\n
13<\/td>\n6.2.2 Viewpoint specifications
Figure 1 \u2013 RM-ODP viewpoints <\/td>\n<\/tr>\n
14<\/td>\n6.2.3 Distribution transparency
6.2.4 Conformance
6.2.5 Enterprise language <\/td>\n<\/tr>\n
15<\/td>\n6.2.6 Information language
6.2.7 Computational language
6.2.8 Engineering language <\/td>\n<\/tr>\n
16<\/td>\n6.2.9 Technology language
6.3 Overview of UML concepts
6.3.1 Structural models <\/td>\n<\/tr>\n
17<\/td>\n6.3.2 Behavioural models
6.3.3 Model management
6.3.4 Extension mechanisms <\/td>\n<\/tr>\n
18<\/td>\n6.4 Universes of discourse, ODP specifications and UML models
Figure 2 \u2013 Relationships between UOD, ODP specifications, and UML models <\/td>\n<\/tr>\n
19<\/td>\n6.5 Modelling concepts and UML profiles for ODP viewpoint languages and correspondences
6.6 General principles for expressing and structuring ODP system specifications using UML
6.7 Correspondences between viewpoint specifications
6.7.1 ODP Correspondences <\/td>\n<\/tr>\n
20<\/td>\n6.7.2 Expressing ODP correspondences in UML
7 Enterprise specification
7.1 Modelling concepts <\/td>\n<\/tr>\n
21<\/td>\n7.1.1 System concepts
7.1.2 Community concepts
7.1.3 Behaviour concepts
7.1.4 Deontic concepts <\/td>\n<\/tr>\n
22<\/td>\n7.1.5 Policy concepts
7.1.6 Accountability concepts <\/td>\n<\/tr>\n
23<\/td>\n7.1.7 Structure of an enterprise specification
7.1.8 Summary of the enterprise language metamodel
Figure 3 \u2013 System concepts. <\/td>\n<\/tr>\n
24<\/td>\nFigure 4 \u2013 Community concepts. <\/td>\n<\/tr>\n
25<\/td>\nFigure 5 \u2013 Behaviour concepts.
Figure 6 \u2013 Policy concepts. <\/td>\n<\/tr>\n
26<\/td>\nFigure 7 \u2013 Deontic and accountability concepts.
Figure 8 \u2013 Deontic token lifecycle.
7.2 UML profile <\/td>\n<\/tr>\n
27<\/td>\n7.2.1 ODP system
7.2.2 Scope
7.2.3 Field of application
7.2.4 Community
7.2.5 Enterprise object
7.2.6 Object types and templates as enterprise objects <\/td>\n<\/tr>\n
28<\/td>\nFigure 9 \u2013 An explicit representation of the type of an enterprise object so that the object can access its type.
7.2.7 Community object
7.2.8 Objective
7.2.9 Contract
7.2.10 Behaviour
7.2.10.1 General
7.2.10.2 Behaviour as processes and steps <\/td>\n<\/tr>\n
29<\/td>\n7.2.10.3 Behaviour as interactions between roles
7.2.10.4 Interface role
7.2.10.5 Violation <\/td>\n<\/tr>\n
30<\/td>\n7.2.11 Action Roles
7.2.11.1 Actor (with respect to an action)
7.2.11.2 Artefact (with respect to an action)
7.2.11.3 Resource (with respect to an action)
7.2.12 Deontic concepts
7.2.12.1 Burden
7.2.12.2 Permit
7.2.12.3 Embargo <\/td>\n<\/tr>\n
31<\/td>\n7.2.13 Policy
Figure 10 \u2013 Pattern for UML expression of a policy. <\/td>\n<\/tr>\n
32<\/td>\n7.2.14 Accountability concepts
7.2.14.1 Party
7.2.14.2 Accountable action
7.2.14.3 Authorization
7.2.14.4 Delegation
7.2.14.5 Principal
7.2.14.6 Agent
7.2.14.7 Prescription
7.2.14.8 Commitment
7.2.14.9 Declaration
7.2.14.10 Evaluation
7.2.15 Summary of UML extensions for the enterprise language <\/td>\n<\/tr>\n
33<\/td>\nFigure 11 \u2013 Model management.
Figure 12 \u2013 Classifiers. <\/td>\n<\/tr>\n
34<\/td>\nFigure 13 \u2013 Activities.
Figure 14 \u2013 Constraints. <\/td>\n<\/tr>\n
35<\/td>\nFigure 15 \u2013 Relationships. <\/td>\n<\/tr>\n
36<\/td>\n7.3 Enterprise specification structure (in UML terms)
7.4 Viewpoint correspondences for the enterprise language
7.4.1 Contents of this clause
7.4.2 Enterprise and information viewpoint specification correspondences
7.4.3 Enterprise and computational viewpoint specification correspondences <\/td>\n<\/tr>\n
37<\/td>\n7.4.4 Enterprise and engineering viewpoint specification correspondences
7.4.5 Enterprise and technology viewpoint specification correspondences
8 Information specification
8.1 Modelling concepts
8.1.1 Information object <\/td>\n<\/tr>\n
38<\/td>\n8.1.2 Information object type
8.1.3 Information object class
8.1.4 Information object template
8.1.5 Information action and action types
8.1.6 Invariant schema
8.1.7 Static schema
8.1.8 Dynamic schema
8.1.9 Structure of an information specification <\/td>\n<\/tr>\n
39<\/td>\n8.1.10 Summary of the information language metamodel
Figure 16 \u2013 Information language concepts.
8.2 UML profile
8.2.1 Information object
8.2.2 Object types and templates as information objects <\/td>\n<\/tr>\n
40<\/td>\nFigure 17 \u2013 An explicit representation of the type of an information object so that the object can access its type.
8.2.3 Information action and action types
8.2.4 Relationships between information objects and between information object types
8.2.5 Invariant schema <\/td>\n<\/tr>\n
41<\/td>\n8.2.6 Static schema
8.2.7 Dynamic schema
8.2.8 Summary of the UML extensions for the information language
Figure 18 \u2013 Graphical representation of the information language profile.
8.3 Information specification structure (in UML terms) <\/td>\n<\/tr>\n
42<\/td>\n8.4 Viewpoint correspondences for the information language
8.4.1 Contents of this clause
8.4.2 Enterprise and information viewpoint specification correspondences
8.4.3 Information and computational viewpoint specification correspondences <\/td>\n<\/tr>\n
43<\/td>\n8.4.4 Information and technology viewpoint specification correspondences
9 Computational specification
9.1 Modelling concepts
9.1.1 Computational object
9.1.2 Interface [Part 2 \u2013 8.4]
9.1.3 Interaction [Part 2 \u2013 8.3]
9.1.4 Environment contract [Part 2 \u2013 11.2.3] <\/td>\n<\/tr>\n
44<\/td>\n9.1.5 Behaviour (of an object) [Part 2 \u2013 8.6]
9.1.6 Signal [Part 3 \u2013 7.1.1]
9.1.7 Operation [Part 3 \u2013 7.1.3]
9.1.8 Announcement [Part 3 \u2013 7.1.3]
9.1.9 Interrogation [Part 3 \u2013 7.1.4]
9.1.10 Flow [Part 3 \u2013 7.1.5]
9.1.11 Signal interface [Part 3 \u2013 7.1.6]
9.1.12 Operation interface [Part 3 \u2013 7.1.7]
9.1.13 Stream interface [Part 3 \u2013 7.1.4] <\/td>\n<\/tr>\n
45<\/td>\n9.1.14 Computational object template [Part 3 \u2013 7.1.9]
9.1.15 Computational interface template [Part 3 \u2013 7.1.9]
9.1.16 Signal interface signature [Part 3 \u2013 7.1.11]
9.1.17 Operation interface signature [Part 3 \u2013 7.1.12]
9.1.18 Stream interface signature [Part 3 \u2013 7.1.13]
9.1.19 Binding object [Part 3 \u2013 7.1.14]
9.1.20 Binding [Part 2 \u2013 13.4, Part 3 \u2013 7. 2.3]
9.1.21 Transparency schema [Part 3 \u2013 16] <\/td>\n<\/tr>\n
46<\/td>\n9.1.22 Structure of a computational specification
9.1.23 Summary of the concepts of the computational metamodel <\/td>\n<\/tr>\n
47<\/td>\nFigure 19 \u2013 Computational language concepts. <\/td>\n<\/tr>\n
48<\/td>\n9.2 UML profile
9.2.1 Computational object <\/td>\n<\/tr>\n
49<\/td>\n9.2.2 Object types and templates as computational objects
Figure 20 \u2013 An explicit representation of the type of a computational object so that the object can access its type.
9.2.3 Binding object
9.2.4 Environment contract
9.2.5 Signal
9.2.6 Announcement
9.2.7 Invocation
9.2.8 Termination <\/td>\n<\/tr>\n
50<\/td>\n9.2.9 Computational interface
9.2.10 Computational interface signature
9.2.11 Computational signature
9.2.12 Signal signature
9.2.13 Announcement signature
9.2.14 Invocation signature
9.2.15 Termination signature
9.2.16 Interrogation signature <\/td>\n<\/tr>\n
51<\/td>\n9.2.17 Bindings
Figure 21 \u2013 Two operation interface signatures.
Figure 22 \u2013 An explicit primitive binding between two interfaces.
Figure 23 \u2013 An explicit primitive binding between two interfaces showing their interface signatures. <\/td>\n<\/tr>\n
52<\/td>\nFigure 24 \u2013 An implicit primitive binding between two interfaces.
9.2.18 Flow
Figure 25 \u2013 An example of the specification of flows.
9.2.19 Transparency schema <\/td>\n<\/tr>\n
53<\/td>\n9.2.20 Summary of the UML extensions for the computational language
Figure 26 \u2013 Graphical representation of the computational language profile (using the UML notation).
9.3 Computational specification structure (in UML terms) <\/td>\n<\/tr>\n
54<\/td>\n9.4 Viewpoint correspondences for the computational language
9.4.1 Contents of this clause
9.4.2 Enterprise and computational viewpoint specification correspondences
9.4.3 Information and computational viewpoint specification correspondences
9.4.4 Computational and engineering viewpoint specification correspondences <\/td>\n<\/tr>\n
55<\/td>\n10 Engineering specification
10.1 Modelling concepts
10.1.1 Basic concepts
10.1.1.1 Basic engineering object <\/td>\n<\/tr>\n
56<\/td>\n10.1.1.2 Cluster
10.1.1.3 Cluster manager
10.1.1.4 Capsule
10.1.1.5 Capsule manager
10.1.1.6 Nucleus
10.1.1.7 Node
10.1.1.8 Engineering interfaces and signatures
10.1.2 Channel concepts
10.1.2.1 Channel
10.1.2.2 Stub
10.1.2.3 Binder
10.1.2.4 Interceptor
10.1.2.5 Protocol object
10.1.2.6 Communication domain <\/td>\n<\/tr>\n
57<\/td>\n10.1.2.7 Communication interface
10.1.3 Identifier concepts
10.1.3.1 Binding endpoint identifier
10.1.3.2 Engineering interface reference
10.1.3.3 Engineering interface reference management domain
10.1.3.4 Engineering interface reference management policy
10.1.3.5 Cluster template
10.1.4 Checkpointing concepts
10.1.4.1 Checkpoint
10.1.4.2 Checkpointing
10.1.4.3 Cluster checkpoint
10.1.4.4 Deactivation
10.1.4.5 Cloning
10.1.4.6 Recovery
10.1.4.7 Reactivation
10.1.4.8 Migration
10.1.5 ODP functions in the context of the engineering viewpoint specifications <\/td>\n<\/tr>\n
58<\/td>\n10.1.6 Summary of the engineering language metamodel
10.1.6.1 Engineering Objects
Figure 27 \u2013 Engineering objects. <\/td>\n<\/tr>\n
59<\/td>\nFigure 28 \u2013 Engineering interfaces.
10.1.6.2 Node structure
Figure 29 \u2013 Engineering language \u2013 basic concepts. <\/td>\n<\/tr>\n
60<\/td>\n10.1.6.3 Channels
Figure 30 \u2013 Engineering language model \u2013 channels. <\/td>\n<\/tr>\n
61<\/td>\n10.1.6.4 Domains
Figure 31 \u2013 Domains. <\/td>\n<\/tr>\n
62<\/td>\n10.1.6.5 Identifiers
Figure 32 \u2013 Engineering language model \u2013 identifiers.
10.1.6.6 Checkpoints
Figure 33 \u2013 Engineering language model \u2013 checkpoints.
10.1.6.7 ODP functions <\/td>\n<\/tr>\n
63<\/td>\nFigure 34 \u2013 Engineering language model \u2013 ODP functions.
10.2 UML profile
10.2.1 Engineering object templates and types <\/td>\n<\/tr>\n
64<\/td>\n10.2.2 Object types and templates as engineering objects
Figure 35 \u2013 An explicit representation of the type of an engineering object so that the object can access its type.
10.2.3 Cluster
10.2.4 Cluster manager
10.2.5 Capsule <\/td>\n<\/tr>\n
65<\/td>\n10.2.6 Capsule manager
10.2.7 Nucleus
10.2.8 Node
10.2.9 Channel
10.2.10 Stub
10.2.11 Binder
10.2.12 Interceptor
10.2.13 Protocol object
10.2.14 Communication domain
10.2.15 Engineering Interfaces
10.2.15.1 Communication interface
10.2.15.2 Operation interface
10.2.15.3 Stream interface
10.2.15.4 Signal interface
10.2.15.5 Engineering interface signature <\/td>\n<\/tr>\n
66<\/td>\n10.2.16 Binding endpoint identifier
10.2.17 Engineering interface reference
10.2.18 Engineering interface reference management domain
10.2.19 Engineering interface reference management policy
10.2.20 Checkpoint
10.2.21 Checkpointing
10.2.22 Cluster checkpoint
10.2.23 Deactivation
10.2.24 Cloning
10.2.25 Recovery
10.2.26 Reactivation
10.2.27 Migration
10.2.28 ODP functions
10.2.29 Summary of the UML extensions for the engineering language <\/td>\n<\/tr>\n
67<\/td>\nFigure 36 \u2013 Graphical representation of the engineering language profile (using the UML notation). <\/td>\n<\/tr>\n
68<\/td>\n10.3 Engineering specification structure (in UML terms)
10.4 Viewpoint correspondences for the engineering language
10.4.1 Contents of this clause
10.4.2 Engineering and computational viewpoint specification correspondences
10.4.3 Engineering and technology viewpoint specification correspondences <\/td>\n<\/tr>\n
69<\/td>\n11 Technology specification
11.1 Modelling concepts
11.1.1 Implementable standard
11.1.2 Implementation
11.1.3 IXIT
11.1.4 Summary of the technology language metamodel
Figure 37 \u2013 Model of the technology language.
11.2 UML profile
11.2.1 Technology object
11.2.2 Object types and templates as technology objects <\/td>\n<\/tr>\n
70<\/td>\n11.2.3 Implementable standard
11.2.4 Implementation
11.2.5 IXIT
11.2.6 Summary of the UML extensions for the technology language
Figure 38 \u2013 Graphical representation of the technology language profile (using the UML notation).
11.3 Technology specification structure (in UML terms) <\/td>\n<\/tr>\n
71<\/td>\n11.4 Viewpoint correspondences for the technology language
12 Correspondences specification
12.1 Modelling concepts
12.1.1 Correspondence specification
12.1.2 Correspondence rule <\/td>\n<\/tr>\n
72<\/td>\n12.1.3 Correspondence link
12.1.4 Correspondence endpoint
12.1.5 Term
12.1.6 Summary of the Correspondences metamodel
Figure 39 \u2013 Correspondences specification concepts.
12.2 UML profile
12.2.1 Correspondence specification
12.2.2 Correspondence rule
12.2.3 Correspondence link <\/td>\n<\/tr>\n
73<\/td>\n12.2.4 Correspondence endpoint
12.2.5 Summary of the UML extensions for correspondences specification
Figure 40 \u2013 Graphical representation of the UML profile for correspondences specifications.
13 Modelling conformance in ODP system specifications
13.1 Modelling conformance concepts
13.2 UML profile <\/td>\n<\/tr>\n
74<\/td>\nFigure 41 \u2013 UML profile for conformance.
14 Conformance and compliance to this document
14.1 Conformance
14.2 Compliance <\/td>\n<\/tr>\n
75<\/td>\nAnnex A An example of ODP specifications using UML
A.1 The Templeman Library System
A.1.1 Introduction
A.1.2 Rules of operation of the Library <\/td>\n<\/tr>\n
76<\/td>\nA.1.3 Expressing the Library System Specification in UML
Figure A.1 \u2013 UML specification of the ODP system.
A.2 Enterprise specification in UML
A.2.1 Basic enterprise concepts
Table A.1 \u2013 Enterprise language icons. <\/td>\n<\/tr>\n
78<\/td>\nA.2.2 Communities
Figure A.2 \u2013 UML Enterprise specification of the Library system. <\/td>\n<\/tr>\n
79<\/td>\nFigure A.3 \u2013 UML specification of the Library community.
A.2.3 Processes
Figure A.4 \u2013 Processes.
A.2.3.1 Borrow item process <\/td>\n<\/tr>\n
80<\/td>\nFigure A.5 \u2013 Borrow item process.
A.2.3.2 Add member process <\/td>\n<\/tr>\n
81<\/td>\nFigure A.6 \u2013 Add member process. <\/td>\n<\/tr>\n
82<\/td>\nFigure A.7 \u2013 Validate member subprocess.
A.2.4 Roles
Figure A.8 \u2013 Library community roles. <\/td>\n<\/tr>\n
83<\/td>\nFigure A.9 \u2013 Behaviour of the Library system role.
A.2.5 Interactions
Figure A.10 \u2013 Process loan interaction. <\/td>\n<\/tr>\n
84<\/td>\nFigure A.11 \u2013 State diagram for Library system role in the interaction Process loan.
A.2.6 Enterprise Objects
A.2.6.1 Actors
Figure A.12 \u2013 Actor role fulfilment and assignment rules. <\/td>\n<\/tr>\n
85<\/td>\nA.2.6.2 Artefacts
Figure A.13 \u2013 Loan as an artefact.
A.2.6.3 Summary of enterprise objects
Figure A.14 \u2013 Enterprise objects.
A.2.6.4 Enterprise object states <\/td>\n<\/tr>\n
86<\/td>\nFigure A.15 \u2013 States of the loan enterprise object.
Figure A.16 \u2013 States of the Library member enterprise object.
A.2.7 Policies
A.2.7.1 General <\/td>\n<\/tr>\n
87<\/td>\nA.2.7.2 Expressing ODP policies in UML
A.2.7.3 Expressing Loan policies in the Templeman Library
Figure A.17 \u2013 Structure of the Policies package. <\/td>\n<\/tr>\n
88<\/td>\nFigure A.18 \u2013 Examples of policy expressions: Lending limit policy.
Figure A.19 \u2013 Examples of policy expressions: Loan duration policy. <\/td>\n<\/tr>\n
89<\/td>\nA.2.8 Accountability
Figure A.20 \u2013 Example of delegation.
A.3 Information specification in UML
A.3.1 Overview
Table A.2 \u2013 Information language icons. <\/td>\n<\/tr>\n
90<\/td>\nFigure A.21 \u2013 Structure of the information viewpoint specification of the Library system (excerpt).
A.3.2 Basic elements
Figure A.22 \u2013 Object types of the information viewpoint specification of the Library system. <\/td>\n<\/tr>\n
91<\/td>\nFigure A.23 \u2013 Action types of the information viewpoint specification of the Library system. <\/td>\n<\/tr>\n
92<\/td>\nA.3.3 Invariant Schemata <\/td>\n<\/tr>\n
93<\/td>\nA.3.4 Static Schemata
Figure A.24 \u2013 Static schema with the initial state of the Library system. <\/td>\n<\/tr>\n
94<\/td>\nFigure A.25 \u2013 Static schema with the configuration of the Library system at day 95.
A.3.5 Dynamic Schemata: Description of the system behaviour <\/td>\n<\/tr>\n
95<\/td>\nFigure A.26 \u2013 StateMachine of the Loan information object.
Figure A.27 \u2013 StateMachine of a Borrower information object. <\/td>\n<\/tr>\n
96<\/td>\nFigure A.28 \u2013 StateMachine of an Item information object.
A.3.6 Correspondences between the Enterprise and the Information specifications
Figure A.29 \u2013 Example of correspondence between the enterprise and information specifications. <\/td>\n<\/tr>\n
97<\/td>\nA.4 Computational specification in UML
A.4.1 Overview
A.4.2 Computational objects and interfaces
Figure A.30 \u2013 Basic structure of the computational viewpoint specification of the Library system.
Table A.3 \u2013 Computational language icons. <\/td>\n<\/tr>\n
98<\/td>\nFigure A.31 \u2013 Component diagram with computational object templates and interface signatures of the system. <\/td>\n<\/tr>\n
99<\/td>\nFigure A.32 \u2013 Interaction signatures.
Figure A.33 \u2013 Internal structure of the LibrarySystemMainFunctionality computational object. <\/td>\n<\/tr>\n
100<\/td>\nFigure A.34 \u2013 Data types handled by the computational objects.
A.4.3 Behaviour <\/td>\n<\/tr>\n
101<\/td>\nFigure A.35 \u2013 Interaction diagram for the borrowing process.
A.4.4 Correspondences between the Enterprise and Computational specifications
Figure A.36 \u2013 Example of correspondence between the enterprise and computational specifications.
A.4.5 Correspondences between the Information and Computational specifications <\/td>\n<\/tr>\n
102<\/td>\nFigure A.37 \u2013 Example of correspondence between the information and computational specifications.
A.5 Engineering specification in UML
A.5.1 Overview
Table A.4 \u2013 Engineering language icons. <\/td>\n<\/tr>\n
103<\/td>\nA.5.2 Computational Objects
A.5.3 Node configuration
Figure A.38 \u2013 Node configuration overview. <\/td>\n<\/tr>\n
104<\/td>\nA.5.4 Node structures
Figure A.39 \u2013 Example of BEO configuration. <\/td>\n<\/tr>\n
105<\/td>\nFigure A.40 \u2013 Example EnterpriseServer internals.
A.5.5 Channels <\/td>\n<\/tr>\n
106<\/td>\nFigure A.41 \u2013 Internals of a channel.
A.5.6 Communication Domain
Figure A.42 \u2013 Example of a communication domain.
A.5.7 Representing Functions
Figure A.43 \u2013 Checkpointing process. <\/td>\n<\/tr>\n
107<\/td>\nFigure A.44 \u2013 Deactivation process.
Figure A.45 \u2013 Cloning process.
Figure A.46 \u2013 Reactivation process.
Figure A.47 \u2013 Recovery process. <\/td>\n<\/tr>\n
108<\/td>\nFigure A.48 \u2013 Migration process.
Figure A.49 \u2013 Use of functions.
A.5.8 Channel creation and interface location
Figure A.50 \u2013 Channel creation interface. <\/td>\n<\/tr>\n
109<\/td>\nA.5.9 Interface reference management domain
Figure A.51 \u2013 Interface reference management domain.
A.5.10 Management functions <\/td>\n<\/tr>\n
110<\/td>\nFigure A.52 \u2013 Management functions.
A.5.11 Correspondences between Enterprise and Engineering specifications <\/td>\n<\/tr>\n
111<\/td>\nFigure A.53 \u2013 Example of correspondences between enterprise and engineering specifications.
A.5.12 Correspondences between Computational and Engineering specifications
Figure A.54 \u2013 Example of correspondences between computational and engineering specifications. <\/td>\n<\/tr>\n
112<\/td>\nA.6 Technology specification in UML
A.6.1 Overview
Table A.5 \u2013 Technology language icons.
A.6.2 Node configuration
Figure A.55 \u2013 Node configuration overview. <\/td>\n<\/tr>\n
113<\/td>\nA.6.3 Node structure
Figure A.56 \u2013 Node structure.
A.6.4 IXIT <\/td>\n<\/tr>\n
114<\/td>\nFigure A.57 \u2013 IXIT.
A.6.5 Implementation
Figure A.58 \u2013 Example of implementation process.
A.6.6 Correspondences between engineering and technology specifications <\/td>\n<\/tr>\n
115<\/td>\nFigure A.59 \u2013 Example of correspondences between engineering and technology specifications. <\/td>\n<\/tr>\n
116<\/td>\nAnnex B An example of the representation of deontic concepts
B.1 The scenario
Figure B.1 \u2013 The community. <\/td>\n<\/tr>\n
117<\/td>\nFigure B.2 \u2013 Basic behaviour.
B.2 Expressing the deontic constraints
Figure B.3 \u2013 Refined basic behaviour. <\/td>\n<\/tr>\n
118<\/td>\nFigure B.4 \u2013 The Place Order interaction. <\/td>\n<\/tr>\n
119<\/td>\nFigure B.5 \u2013 The Delegation interaction.
Figure B.6 \u2013 The DeliverGoods interaction. <\/td>\n<\/tr>\n
120<\/td>\nFigure B.7 \u2013 The Confirmation interaction.
Figure B.8 \u2013 The Payment interaction. <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

BS ISO\/IEC 19793 AMD1. Information technology. Open Distributed Processing. Use of UML for ODP system specifications<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2014<\/td>\n122<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":346931,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-346923","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/346923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/346931"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=346923"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=346923"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=346923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}