šŸ”„šŸ”„ Donā€™t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

šŸ”
BSI 14/30288700 DC:2014 Edition

BSI 14/30288700 DC:2014 Edition

$24.66

BS ISO/IEC 19793 AMD1. Information technology. Open Distributed Processing. Use of UML for ODP system specifications

Published By Publication Date Number of Pages
BSI 2014 122
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. Weā€™re here to assist you 24/7.
Email:[email protected]

PDF Catalog

PDF Pages PDF Title
5 CONTENTS
6 Foreword
7 Introduction
0.1 RM-ODP
0.2 UML
8 0.3 Overview and motivation
9 1 Scope
2 Normative references
2.1 Identical Recommendations | International Standards
2.2 Additional References
10 3 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
11 4 Abbreviations
5 Conventions
12 6 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
13 6.2.2 Viewpoint specifications
Figure 1 ā€“ RM-ODP viewpoints
14 6.2.3 Distribution transparency
6.2.4 Conformance
6.2.5 Enterprise language
15 6.2.6 Information language
6.2.7 Computational language
6.2.8 Engineering language
16 6.2.9 Technology language
6.3 Overview of UML concepts
6.3.1 Structural models
17 6.3.2 Behavioural models
6.3.3 Model management
6.3.4 Extension mechanisms
18 6.4 Universes of discourse, ODP specifications and UML models
Figure 2 ā€“ Relationships between UOD, ODP specifications, and UML models
19 6.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
20 6.7.2 Expressing ODP correspondences in UML
7 Enterprise specification
7.1 Modelling concepts
21 7.1.1 System concepts
7.1.2 Community concepts
7.1.3 Behaviour concepts
7.1.4 Deontic concepts
22 7.1.5 Policy concepts
7.1.6 Accountability concepts
23 7.1.7 Structure of an enterprise specification
7.1.8 Summary of the enterprise language metamodel
Figure 3 ā€“ System concepts.
24 Figure 4 ā€“ Community concepts.
25 Figure 5 ā€“ Behaviour concepts.
Figure 6 ā€“ Policy concepts.
26 Figure 7 ā€“ Deontic and accountability concepts.
Figure 8 ā€“ Deontic token lifecycle.
7.2 UML profile
27 7.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
28 Figure 9 ā€“ 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
29 7.2.10.3 Behaviour as interactions between roles
7.2.10.4 Interface role
7.2.10.5 Violation
30 7.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
31 7.2.13 Policy
Figure 10 ā€“ Pattern for UML expression of a policy.
32 7.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
33 Figure 11 ā€“ Model management.
Figure 12 ā€“ Classifiers.
34 Figure 13 ā€“ Activities.
Figure 14 ā€“ Constraints.
35 Figure 15 ā€“ Relationships.
36 7.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
37 7.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
38 8.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
39 8.1.10 Summary of the information language metamodel
Figure 16 ā€“ Information language concepts.
8.2 UML profile
8.2.1 Information object
8.2.2 Object types and templates as information objects
40 Figure 17 ā€“ 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
41 8.2.6 Static schema
8.2.7 Dynamic schema
8.2.8 Summary of the UML extensions for the information language
Figure 18 ā€“ Graphical representation of the information language profile.
8.3 Information specification structure (in UML terms)
42 8.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
43 8.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 ā€“ 8.4]
9.1.3 Interaction [Part 2 ā€“ 8.3]
9.1.4 Environment contract [Part 2 ā€“ 11.2.3]
44 9.1.5 Behaviour (of an object) [Part 2 ā€“ 8.6]
9.1.6 Signal [Part 3 ā€“ 7.1.1]
9.1.7 Operation [Part 3 ā€“ 7.1.3]
9.1.8 Announcement [Part 3 ā€“ 7.1.3]
9.1.9 Interrogation [Part 3 ā€“ 7.1.4]
9.1.10 Flow [Part 3 ā€“ 7.1.5]
9.1.11 Signal interface [Part 3 ā€“ 7.1.6]
9.1.12 Operation interface [Part 3 ā€“ 7.1.7]
9.1.13 Stream interface [Part 3 ā€“ 7.1.4]
45 9.1.14 Computational object template [Part 3 ā€“ 7.1.9]
9.1.15 Computational interface template [Part 3 ā€“ 7.1.9]
9.1.16 Signal interface signature [Part 3 ā€“ 7.1.11]
9.1.17 Operation interface signature [Part 3 ā€“ 7.1.12]
9.1.18 Stream interface signature [Part 3 ā€“ 7.1.13]
9.1.19 Binding object [Part 3 ā€“ 7.1.14]
9.1.20 Binding [Part 2 ā€“ 13.4, Part 3 ā€“ 7. 2.3]
9.1.21 Transparency schema [Part 3 ā€“ 16]
46 9.1.22 Structure of a computational specification
9.1.23 Summary of the concepts of the computational metamodel
47 Figure 19 ā€“ Computational language concepts.
48 9.2 UML profile
9.2.1 Computational object
49 9.2.2 Object types and templates as computational objects
Figure 20 ā€“ 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
50 9.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
51 9.2.17 Bindings
Figure 21 ā€“ Two operation interface signatures.
Figure 22 ā€“ An explicit primitive binding between two interfaces.
Figure 23 ā€“ An explicit primitive binding between two interfaces showing their interface signatures.
52 Figure 24 ā€“ An implicit primitive binding between two interfaces.
9.2.18 Flow
Figure 25 ā€“ An example of the specification of flows.
9.2.19 Transparency schema
53 9.2.20 Summary of the UML extensions for the computational language
Figure 26 ā€“ Graphical representation of the computational language profile (using the UML notation).
9.3 Computational specification structure (in UML terms)
54 9.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
55 10 Engineering specification
10.1 Modelling concepts
10.1.1 Basic concepts
10.1.1.1 Basic engineering object
56 10.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
57 10.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
58 10.1.6 Summary of the engineering language metamodel
10.1.6.1 Engineering Objects
Figure 27 ā€“ Engineering objects.
59 Figure 28 ā€“ Engineering interfaces.
10.1.6.2 Node structure
Figure 29 ā€“ Engineering language ā€“ basic concepts.
60 10.1.6.3 Channels
Figure 30 ā€“ Engineering language model ā€“ channels.
61 10.1.6.4 Domains
Figure 31 ā€“ Domains.
62 10.1.6.5 Identifiers
Figure 32 ā€“ Engineering language model ā€“ identifiers.
10.1.6.6 Checkpoints
Figure 33 ā€“ Engineering language model ā€“ checkpoints.
10.1.6.7 ODP functions
63 Figure 34 ā€“ Engineering language model ā€“ ODP functions.
10.2 UML profile
10.2.1 Engineering object templates and types
64 10.2.2 Object types and templates as engineering objects
Figure 35 ā€“ 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
65 10.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
66 10.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
67 Figure 36 ā€“ Graphical representation of the engineering language profile (using the UML notation).
68 10.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
69 11 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 ā€“ Model of the technology language.
11.2 UML profile
11.2.1 Technology object
11.2.2 Object types and templates as technology objects
70 11.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 ā€“ Graphical representation of the technology language profile (using the UML notation).
11.3 Technology specification structure (in UML terms)
71 11.4 Viewpoint correspondences for the technology language
12 Correspondences specification
12.1 Modelling concepts
12.1.1 Correspondence specification
12.1.2 Correspondence rule
72 12.1.3 Correspondence link
12.1.4 Correspondence endpoint
12.1.5 Term
12.1.6 Summary of the Correspondences metamodel
Figure 39 ā€“ Correspondences specification concepts.
12.2 UML profile
12.2.1 Correspondence specification
12.2.2 Correspondence rule
12.2.3 Correspondence link
73 12.2.4 Correspondence endpoint
12.2.5 Summary of the UML extensions for correspondences specification
Figure 40 ā€“ 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
74 Figure 41 ā€“ UML profile for conformance.
14 Conformance and compliance to this document
14.1 Conformance
14.2 Compliance
75 Annex 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
76 A.1.3 Expressing the Library System Specification in UML
Figure A.1 ā€“ UML specification of the ODP system.
A.2 Enterprise specification in UML
A.2.1 Basic enterprise concepts
Table A.1 ā€“ Enterprise language icons.
78 A.2.2 Communities
Figure A.2 ā€“ UML Enterprise specification of the Library system.
79 Figure A.3 ā€“ UML specification of the Library community.
A.2.3 Processes
Figure A.4 ā€“ Processes.
A.2.3.1 Borrow item process
80 Figure A.5 ā€“ Borrow item process.
A.2.3.2 Add member process
81 Figure A.6 ā€“ Add member process.
82 Figure A.7 ā€“ Validate member subprocess.
A.2.4 Roles
Figure A.8 ā€“ Library community roles.
83 Figure A.9 ā€“ Behaviour of the Library system role.
A.2.5 Interactions
Figure A.10 ā€“ Process loan interaction.
84 Figure A.11 ā€“ State diagram for Library system role in the interaction Process loan.
A.2.6 Enterprise Objects
A.2.6.1 Actors
Figure A.12 ā€“ Actor role fulfilment and assignment rules.
85 A.2.6.2 Artefacts
Figure A.13 ā€“ Loan as an artefact.
A.2.6.3 Summary of enterprise objects
Figure A.14 ā€“ Enterprise objects.
A.2.6.4 Enterprise object states
86 Figure A.15 ā€“ States of the loan enterprise object.
Figure A.16 ā€“ States of the Library member enterprise object.
A.2.7 Policies
A.2.7.1 General
87 A.2.7.2 Expressing ODP policies in UML
A.2.7.3 Expressing Loan policies in the Templeman Library
Figure A.17 ā€“ Structure of the Policies package.
88 Figure A.18 ā€“ Examples of policy expressions: Lending limit policy.
Figure A.19 ā€“ Examples of policy expressions: Loan duration policy.
89 A.2.8 Accountability
Figure A.20 ā€“ Example of delegation.
A.3 Information specification in UML
A.3.1 Overview
Table A.2 ā€“ Information language icons.
90 Figure A.21 ā€“ Structure of the information viewpoint specification of the Library system (excerpt).
A.3.2 Basic elements
Figure A.22 ā€“ Object types of the information viewpoint specification of the Library system.
91 Figure A.23 ā€“ Action types of the information viewpoint specification of the Library system.
92 A.3.3 Invariant Schemata
93 A.3.4 Static Schemata
Figure A.24 ā€“ Static schema with the initial state of the Library system.
94 Figure A.25 ā€“ Static schema with the configuration of the Library system at day 95.
A.3.5 Dynamic Schemata: Description of the system behaviour
95 Figure A.26 ā€“ StateMachine of the Loan information object.
Figure A.27 ā€“ StateMachine of a Borrower information object.
96 Figure A.28 ā€“ StateMachine of an Item information object.
A.3.6 Correspondences between the Enterprise and the Information specifications
Figure A.29 ā€“ Example of correspondence between the enterprise and information specifications.
97 A.4 Computational specification in UML
A.4.1 Overview
A.4.2 Computational objects and interfaces
Figure A.30 ā€“ Basic structure of the computational viewpoint specification of the Library system.
Table A.3 ā€“ Computational language icons.
98 Figure A.31 ā€“ Component diagram with computational object templates and interface signatures of the system.
99 Figure A.32 ā€“ Interaction signatures.
Figure A.33 ā€“ Internal structure of the LibrarySystemMainFunctionality computational object.
100 Figure A.34 ā€“ Data types handled by the computational objects.
A.4.3 Behaviour
101 Figure A.35 ā€“ Interaction diagram for the borrowing process.
A.4.4 Correspondences between the Enterprise and Computational specifications
Figure A.36 ā€“ Example of correspondence between the enterprise and computational specifications.
A.4.5 Correspondences between the Information and Computational specifications
102 Figure A.37 ā€“ Example of correspondence between the information and computational specifications.
A.5 Engineering specification in UML
A.5.1 Overview
Table A.4 ā€“ Engineering language icons.
103 A.5.2 Computational Objects
A.5.3 Node configuration
Figure A.38 ā€“ Node configuration overview.
104 A.5.4 Node structures
Figure A.39 ā€“ Example of BEO configuration.
105 Figure A.40 ā€“ Example EnterpriseServer internals.
A.5.5 Channels
106 Figure A.41 ā€“ Internals of a channel.
A.5.6 Communication Domain
Figure A.42 ā€“ Example of a communication domain.
A.5.7 Representing Functions
Figure A.43 ā€“ Checkpointing process.
107 Figure A.44 ā€“ Deactivation process.
Figure A.45 ā€“ Cloning process.
Figure A.46 ā€“ Reactivation process.
Figure A.47 ā€“ Recovery process.
108 Figure A.48 ā€“ Migration process.
Figure A.49 ā€“ Use of functions.
A.5.8 Channel creation and interface location
Figure A.50 ā€“ Channel creation interface.
109 A.5.9 Interface reference management domain
Figure A.51 ā€“ Interface reference management domain.
A.5.10 Management functions
110 Figure A.52 ā€“ Management functions.
A.5.11 Correspondences between Enterprise and Engineering specifications
111 Figure A.53 ā€“ Example of correspondences between enterprise and engineering specifications.
A.5.12 Correspondences between Computational and Engineering specifications
Figure A.54 ā€“ Example of correspondences between computational and engineering specifications.
112 A.6 Technology specification in UML
A.6.1 Overview
Table A.5 ā€“ Technology language icons.
A.6.2 Node configuration
Figure A.55 ā€“ Node configuration overview.
113 A.6.3 Node structure
Figure A.56 ā€“ Node structure.
A.6.4 IXIT
114 Figure A.57 ā€“ IXIT.
A.6.5 Implementation
Figure A.58 ā€“ Example of implementation process.
A.6.6 Correspondences between engineering and technology specifications
115 Figure A.59 ā€“ Example of correspondences between engineering and technology specifications.
116 Annex B An example of the representation of deontic concepts
B.1 The scenario
Figure B.1 ā€“ The community.
117 Figure B.2 ā€“ Basic behaviour.
B.2 Expressing the deontic constraints
Figure B.3 ā€“ Refined basic behaviour.
118 Figure B.4 ā€“ The Place Order interaction.
119 Figure B.5 ā€“ The Delegation interaction.
Figure B.6 ā€“ The DeliverGoods interaction.
120 Figure B.7 ā€“ The Confirmation interaction.
Figure B.8 ā€“ The Payment interaction.

Related products

BSI 14/30288700 DC
$24.66