BSI 13/30264404 DC:2013 Edition
$13.70
BS ISO/IEC 15414 AMD1. Information technology. Open distributed processing. Reference model. Enterprise language
Published By | Publication Date | Number of Pages |
BSI | 2013 | 51 |
PDF Catalog
PDF Pages | PDF Title |
---|---|
3 | S060768e |
7 | Introduction 0.1 RM-ODP 0.2 Overview and motivation |
9 | 1 Scope 2 Normative references 2.1 Identical ITU-T Recommendations | International Standards 2.2 Additional References |
10 | 3 Terms and definitions 3.1 Definitions from ODP standards 3.1.1 Modelling concept definitions |
11 | 3.1.2 Viewpoint language definitions 4 Abbreviations |
12 | 5 Conventions 6 Concepts 6.1 System concepts 6.2 Community concepts 6.3 Behaviour concepts |
13 | 6.4 Deontic Concepts 6.4.1 deontic token: an enterprise object which expresses a constraint on the ability of an active enterprise object holding it to perform certain actions. An active enterprise object carries a set of deontic tokens, which control the occurrence of co… 6.4.2 token group: a group of tokens named so that it can be referred to as a whole. |
14 | 6.5 Policy concepts 6.6 Accountability concepts |
15 | 7 Structuring rules 7.1 Overall structure of an enterprise specification 7.2 Contents of an enterprise specification |
16 | 7.3 Community rules 7.3.1 Community |
17 | 7.3.2 Relationships between communities |
18 | 7.4 Enterprise object rules 7.5 Common community types 7.5.1 -domain community type 7.5.2 -federation community type 7.6 Lifecycle of a community 7.6.1 Establishing a community |
19 | 7.6.2 Assignment policy 7.6.3 Changes in a community 7.6.4 Terminating a community 7.7 Objective rules |
20 | 7.8 Behaviour rules 7.8.1 Roles and processes 7.8.2 Role rules |
21 | 7.8.3 Interface roles and interactions between communities 7.8.4 Enterprise objects and actions 7.8.5 Process rules |
22 | 7.8.6 Behaviour violations 7.8.7 Deontic token rules |
23 | 7.8.8 The specification of obligations, permissions, prohibitions and authorizations 7.8.8.1 Obligation 7.8.8.2 Permission 7.8.8.3 Prohibition |
24 | 7.8.8.4 Authorization 7.9 Policy rules 7.9.1 The specification of a policy |
25 | 7.9.2 Policies for federation 7.9.3 Policy setting behaviour 7.9.4 Policy enforcement |
26 | 7.10 Accountability rules 7.10.1 Delegation rules 7.10.2 Authorization rules 7.10.3 Commitment rules 7.10.4 Declaration rules |
27 | 7.10.5 Prescription rules 8 Compliance, completeness and field of application 8.1 Compliance 8.2 Completeness 8.3 Field of application |
28 | 9 Enterprise language compliance 10 Conformance and reference points 11 Consistency rules 11.1 Viewpoint correspondences |
29 | 11.2 Enterprise and information specification correspondences 11.2.1 Concepts related by correspondences 11.2.2 Required correspondences 11.2.3 Required correspondence statements |
30 | 11.3 Enterprise and computational specification correspondences 11.3.1 Concepts related by correspondences 11.3.2 Required correspondences 11.3.3 Required correspondence statements 11.4 Enterprise and engineering specification correspondences 11.4.1 Concepts related by correspondences |
31 | 11.4.2 Required correspondences 11.4.3 Required correspondence statements 11.5 Enterprise and technology specification correspondence |
32 | Annex A Model of the enterprise language concepts |
36 | Annex B Explanations and examples B.1 First example – Enterprise specification of an e-commerce system B.1.1 Specification [Part 3-4.2.2] B.1.2 Field of application (of a specification) [6.1.2] B.1.3 System [Part 2-6.5] |
37 | B.1.4 Scope [6.1.1] B.1.5 Community [Part 3-5.1.1] B.1.5.1 Enterprise object [Part 3-4.2.2] B.1.5.2 Objective [6.2.1] B.1.5.3 Contract [Part 2-11.2.1] B.1.5.4 Role [Part 2-9.17] B.1.5.5 Interface Role [6.3.4 and 7.8.3] |
38 | B.1.5.6 Establishing a community [7.6.1] B.1.5.7 Assignment policy [7.6.2] B.1.5.8 Relationship between communities [7.3.2, 7.8.3] B.1.5.9 Domain [Part 2-10.3] |
39 | B.1.5.10 Federation [Part 3-5.1.2] B.1.6 Behaviour [Part 2-8.7] B.1.6.1 Action [Part 2-8.3] B.1.6.2 Process [6.3.6] B.1.6.3 Violation [6.3.8 and 7.8.6] B.1.7.1 Deontic tokens B.1.7.2 Authorization [6.6., 7.8.8.4] |
40 | B.1.7.3 Obligation [Part 2-11.2.4] B.1.7.4 Permission [Part 2-11.2.5] B.1.7.5 Prohibition [Part 2-11.2.6] B.1.8 Policy [Part 2-11.2.8, 6.5] B.1.9 Accountability [6.6 and 7.10] B.1.9.1 Party [6.6.1 and 7.10.1] B.1.9.2 Commitment [6.6.2 and 7.10.3] B.1.9.3 Declaration [6.6.5 and 7.10.4] B.1.9.4 Delegation and authorization [6.6.4 and 7.10.1, 7.10.2] |
41 | B.1.9.5 Agent and principal [6.6.8, 6.6.9, and 7.10] B.1.9.6 Evaluation [6.6.7 and 7.10] B.1.9.7 Prescription [6.6.3 and 7.10.5] B.2 Second example – Specification of a library |
42 | B.2.1 Enterprise specification B.2.1.1 System B.2.1.2 Scope [6.1.1] B.2.1.3 Enterprise specification [Part 3-4.2.2] B.2.1.4 Field of application B.2.2 Community B.2.2.1 Community [Part 3-5.1.1] |
43 | B.2.2.2 Objective [6.2.1] B.2.2.3 Contract [Part 2-11.2.1] B.2.2.4 Role [Part 2-9.17] B.2.2.5 Enterprise object B.2.2.6 Lifecycle of a community [7.6] B.2.2.7 Assignment rules [7.6.2] B.2.2.8 Relationship between communities |
44 | B.2.3 Behaviour B.2.3.1 Action B.2.3.2 Process and step [6.3.6 and 6.3.7] |
45 | B.2.3.3 Enterprise object and action B.2.3.4 Interface role B.2.4 Deontic concepts B.2.5 Policy [Part 2-11.2.8 and 6.5] |
46 | B.2.6 Accountability [6.6 and 7.10] B.2.6.1 Party [6.6.1 and 7.10] B.2.6.2 Commitment [6.6.2 and 7.10.3] B.2.6.3 Declaration [6.6.5 and 7.10.4] B.2.6.4 Delegation and authorization [6.6.4, 6.6.6 and 7.10.1] B.2.6.5 Agent and principal [6.6.8 and 6.6.9] |
47 | B.2.6.6 Prescription [6.6.3 and 7.10.5] |
48 | Annex C An Operational Semantics for Enterprise Behaviour C.1 A Semantics for basic behaviour C.2 Frames and markings C.3 Calculating the utility of possible courses of action |
49 | C.4 Use of utility to prioritize possible behaviours |
50 | INDEX |