{"id":346808,"date":"2024-10-20T00:22:57","date_gmt":"2024-10-20T00:22:57","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-13-30264404-dc\/"},"modified":"2024-10-25T23:50:49","modified_gmt":"2024-10-25T23:50:49","slug":"bsi-13-30264404-dc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-13-30264404-dc\/","title":{"rendered":"BSI 13\/30264404 DC"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
3<\/td>\n | S060768e <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Introduction 0.1 RM-ODP 0.2 Overview and motivation <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1 Scope 2 Normative references 2.1 Identical ITU-T Recommendations | International Standards 2.2 Additional References <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 3 Terms and definitions 3.1 Definitions from ODP standards 3.1.1 Modelling concept definitions <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 3.1.2 Viewpoint language definitions 4 Abbreviations <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 5 Conventions 6 Concepts 6.1 System concepts 6.2 Community concepts 6.3 Behaviour concepts <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 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. <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 6.5 Policy concepts 6.6 Accountability concepts <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 7 Structuring rules 7.1 Overall structure of an enterprise specification 7.2 Contents of an enterprise specification <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 7.3 Community rules 7.3.1 Community <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 7.3.2 Relationships between communities <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 7.6.2 Assignment policy 7.6.3 Changes in a community 7.6.4 Terminating a community 7.7 Objective rules <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 7.8 Behaviour rules 7.8.1 Roles and processes 7.8.2 Role rules <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 7.8.3 Interface roles and interactions between communities 7.8.4 Enterprise objects and actions 7.8.5 Process rules <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 7.8.6 Behaviour violations 7.8.7 Deontic token rules <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 7.8.8.4 Authorization 7.9 Policy rules 7.9.1 The specification of a policy <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 7.9.2 Policies for federation 7.9.3 Policy setting behaviour 7.9.4 Policy enforcement <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 7.10 Accountability rules 7.10.1 Delegation rules 7.10.2 Authorization rules 7.10.3 Commitment rules 7.10.4 Declaration rules <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 7.10.5 Prescription rules 8 Compliance, completeness and field of application 8.1 Compliance 8.2 Completeness 8.3 Field of application <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 9 Enterprise language compliance 10 Conformance and reference points 11 Consistency rules 11.1 Viewpoint correspondences <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 11.4.2 Required correspondences 11.4.3 Required correspondence statements 11.5 Enterprise and technology specification correspondence <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | Annex A Model of the enterprise language concepts <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Annex B Explanations and examples B.1 First example \u2013 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] <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 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 \u2013 Specification of a library <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | B.2.3 Behaviour B.2.3.1 Action B.2.3.2 Process and step [6.3.6 and 6.3.7] <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 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] <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | B.2.6.6 Prescription [6.6.3 and 7.10.5] <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | C.4 Use of utility to prioritize possible behaviours <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | INDEX <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" BS ISO\/IEC 15414 AMD1. Information technology. Open distributed processing. Reference model. Enterprise language<\/b><\/p>\n |