AS/NZS ISO/IEC 15414:2024 identically adopts ISO/IEC 15414:2015, which specifies a language (the enterprise language) comprising concepts, structures, and rules for developing, representing and reasoning about a specification of an ODP system from the enterprise viewpoint, as well as rules which establish correspondences between the enterprise language and the other viewpoint languages
Table of contents
Header
About this publication
Preface
Foreword
Introduction
1 Scope
2 Normative references
2.1 Identical ITU-T Recommendations | International Standards
2.2 Additional References
3 Terms and definitions
3.1 Definitions from ODP standards
3.1.1 Modelling concept definitions
3.1.2 Viewpoint language definitions
4 Abbreviations
5 Conventions
6 Concepts
6.1 System concepts
6.2 Community concepts
6.3 Behaviour concepts
6.4 Deontic concepts
6.5 Policy concepts
6.6 Accountability concepts
7 Structuring rules
7.1 Overall structure of an enterprise specification
7.2 Contents of an enterprise specification
7.3 Community rules
7.3.1 Community
7.3.2 Relationships between communities
7.4 Enterprise object rules
7.5 Common community types
7.5.1 <X>-domain community type
7.5.2 <X>-federation community type
7.6 Life cycle of a community
7.6.1 Establishing a community
7.6.2 Assignment policy
7.6.3 Changes in a community
7.6.4 Terminating a community
7.7 Objective rules
7.8 Behaviour rules
7.8.1 Roles and processes
7.8.2 Role rules
7.8.3 Interface roles and interactions between communities
7.8.4 Enterprise objects and actions
7.8.5 Process rules
7.8.6 Behaviour violations
7.8.7 Deontic token rules
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
7.8.8.4 Authorization
7.9 Policy rules
7.9.1 The specification of a policy
7.9.2 Policies for federation
7.9.3 Policy setting behaviour
7.9.4 Policy enforcement
7.10 Accountability rules
7.10.1 Delegation rules
7.10.2 Authorization rules
7.10.3 Commitment rules
7.10.4 Declaration rules
7.10.5 Prescription rules
8 Compliance, completeness and field of application
8.1 Compliance
8.2 Completeness
8.3 Field of application
9 Enterprise language compliance
10 Conformance and reference points
11 Consistency rules
11.1 Viewpoint correspondences
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
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
11.4.2 Required correspondences
11.4.3 Required correspondence statements
11.5 Enterprise and technology specification correspondence
Annex A
Annex B
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]
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.5 and 7.8.3]
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]
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 Deontic concepts
B.1.7.1 Deontic tokens
B.1.7.2 Authorization [6.6, 7.8.8.4]
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, 6.6.6, 7.10.1 and 7.10.2]
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
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]
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 Life cycle of a community [7.6]
B.2.2.7 Assignment rules [7.6.2]
B.2.2.8 Relationship between communities
B.2.3 Behaviour
B.2.3.1 Action
B.2.3.2 Process and step [6.3.6 and 6.3.7]
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]
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, 7.10.1 and 7.10.2]
B.2.6.5 Agent and principal [6.6.8, 6.6.9 and 7.10]
B.2.6.6 Prescription [6.6.3 and 7.10.5]
Annex C
C.1 A semantics for basic behaviour
C.2 Frames and markings
C.3 Calculating the utility of possible courses of action
C.4 Use of utility to prioritize possible behaviours
