{"id":347057,"date":"2024-10-20T00:24:16","date_gmt":"2024-10-20T00:24:16","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-154142015\/"},"modified":"2024-10-25T23:53:18","modified_gmt":"2024-10-25T23:53:18","slug":"bs-iso-iec-154142015","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-154142015\/","title":{"rendered":"BS ISO\/IEC 15414:2015"},"content":{"rendered":"

This Recommendation | International Standard provides:<\/p>\n

    \n
  1. \n

    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 defined in Rec. ITU-T X.903 | ISO\/IEC 10746-3);<\/p>\n<\/li>\n

  2. \n

    rules which establish correspondences between the enterprise language and the other viewpoint languages (defined in Rec. ITU-T X.903 | ISO\/IEC 10746-3) to ensure the overall consistency of a specification.<\/p>\n<\/li>\n<\/ol>\n

    The language is specified to a level of detail sufficient to enable the determination of the compliance of any modelling language to this Recommendation | International Standard and to establish requirements for new specification techniques.<\/p>\n

    This Recommendation | International Standard is intended for use in preparing enterprise viewpoint specifications of ODP systems, and in developing notations and tools to support such specifications.<\/p>\n

    As specified in clause 5 of Rec. ITU-T X.903 | ISO\/IEC 10746-3, an enterprise viewpoint specification defines the purpose, scope and policies of an ODP system.<\/p>\n

    This Recommendation | International Standard is a refinement and extension of Rec. ITU-T X.903 | ISO\/IEC 10746-3, clauses 5 and 10, but does not replace them.<\/p>\n

    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
    PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
    6<\/td>\nBlank Page <\/td>\n<\/tr>\n
    7<\/td>\n0.1 RM-ODP
    0.2 Overview and motivation <\/td>\n<\/tr>\n
    9<\/td>\n1 Scope
    2 Normative references
    2.1 Identical ITU-T Recommendations | International Standards
    2.2 Additional References <\/td>\n<\/tr>\n
    10<\/td>\n3 Terms and definitions
    3.1 Definitions from ODP standards
    3.1.1 Modelling concept definitions <\/td>\n<\/tr>\n
    11<\/td>\n3.1.2 Viewpoint language definitions
    4 Abbreviations <\/td>\n<\/tr>\n
    12<\/td>\n5 Conventions
    6 Concepts
    6.1 System concepts
    6.2 Community concepts
    6.3 Behaviour concepts <\/td>\n<\/tr>\n
    13<\/td>\n6.4 Deontic concepts <\/td>\n<\/tr>\n
    14<\/td>\n6.5 Policy concepts
    6.6 Accountability concepts <\/td>\n<\/tr>\n
    15<\/td>\n7 Structuring rules
    7.1 Overall structure of an enterprise specification
    7.2 Contents of an enterprise specification <\/td>\n<\/tr>\n
    16<\/td>\n7.3 Community rules
    7.3.1 Community <\/td>\n<\/tr>\n
    17<\/td>\n7.3.2 Relationships between communities <\/td>\n<\/tr>\n
    18<\/td>\n7.4 Enterprise object rules
    7.5 Common community types
    7.5.1 -domain community type
    7.5.2 -federation community type <\/td>\n<\/tr>\n
    19<\/td>\n7.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 <\/td>\n<\/tr>\n
    20<\/td>\n7.8 Behaviour rules
    7.8.1 Roles and processes
    7.8.2 Role rules <\/td>\n<\/tr>\n
    21<\/td>\n7.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>\n7.8.6 Behaviour violations
    7.8.7 Deontic token rules <\/td>\n<\/tr>\n
    23<\/td>\n7.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>\n7.8.8.4 Authorization
    7.9 Policy rules
    7.9.1 The specification of a policy <\/td>\n<\/tr>\n
    25<\/td>\n7.9.2 Policies for federation
    7.9.3 Policy setting behaviour
    7.9.4 Policy enforcement <\/td>\n<\/tr>\n
    26<\/td>\n7.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>\n7.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>\n9 Enterprise language compliance
    10 Conformance and reference points
    11 Consistency rules
    11.1 Viewpoint correspondences <\/td>\n<\/tr>\n
    29<\/td>\n11.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>\n11.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>\n11.4.2 Required correspondences
    11.4.3 Required correspondence statements
    11.5 Enterprise and technology specification correspondence <\/td>\n<\/tr>\n
    36<\/td>\nB.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>\nB.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] <\/td>\n<\/tr>\n
    38<\/td>\nB.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] <\/td>\n<\/tr>\n
    39<\/td>\nB.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] <\/td>\n<\/tr>\n
    40<\/td>\nB.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] <\/td>\n<\/tr>\n
    41<\/td>\nB.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] <\/td>\n<\/tr>\n
    42<\/td>\nB.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
    43<\/td>\nB.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] <\/td>\n<\/tr>\n
    44<\/td>\nB.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 <\/td>\n<\/tr>\n
    45<\/td>\nB.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 <\/td>\n<\/tr>\n
    46<\/td>\nB.2.5 Policy [Part 2-11.2.8 and 6.5]
    B.2.6 Accountability [6.6 and 7.10] <\/td>\n<\/tr>\n
    47<\/td>\nB.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] <\/td>\n<\/tr>\n
    49<\/td>\nC.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 <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

    Information technology. Open distributed processing. Reference model. Enterprise language<\/b><\/p>\n\n\n\n\n
    Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
    BSI<\/b><\/a><\/td>\n2015<\/td>\n56<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":347066,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-347057","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\/347057","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\/347066"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=347057"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=347057"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=347057"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}