ISO 19440-2020 pdf free download.Enterprise modelling and architecture – Constructs for enterprise modelling.
5 Representations, relationships, roles and common concepts
5.1 Modelling language constructs, purpose and applicability
Clauses 7 and fi define, describe and provide templates for generic modelling constructs. As a set, these constructs contribute to a modelling language for creating a wide range of Business Process-based enterprise models. When utilized, each construct shall include the attributes that are pre-defined in this document. Other attributes may be added to meet distinct user needs by a suitable extension of the template (see .3. Clause B.4 and Clause B.5).
Constructs are often applicable to several model views and are elaborated to different extents at each of the modelling phases. Where the applicability of a construct, as defined in this document, is limited to a certain model view or enterprise model phase, that limitation is noted in remarks.
NOTE Because of the interrelationships and dependencies between constructs, they cannot be described in this document in strict linear sequence (i.e. with no forward reference to not-yet-described constructs). The sequence of text used herein for core constructs (and not intended as a modelling methodology) has been chosen to minimize this forward reference problem and is as follows:
— start with Domain (the scope and boundary of the model);
— add functionality in terms of Business Processes, Services, Enterprise Activities and Events;
— add information representation in terms of Enterprise Object and Object View, and the specializations Product and Order;
— provide for resourcing with Resource and Capability;
— lastly, address organizational and role issues as subclasses of Role, with Organizational Unit, Decision Centre, Organizational Role, Operational Role and Person Profile.
5.2 Dimensions of enterprise models
5.2.1 Dimension of genericity
Relative to the dimension of genericity defined in ISO 19439, constructs are generic elements for use in constructing partial and particular models. For partial models (e.g. industry or trade specific models), some attribute values may remain undefined for partial model instances (e.g. inputs/outputs for Events for Domains and inputs/outputs for Business Processes), with value definition occurring for the particular model instance. Such missing entries need to be completed for the particular model.
5.2.2 Dimension of enterprise model phase
The dimension of enterprise model phase in ISO 19439 addresses the life cycle of models and model components. The concern of this dimension is the development and evolution of the model of the domain, starting from the identification of the enterprise domain and progressing to a processable model and the decommissioning thereof. Therefore, the specifications of modelling language constructs need to accommodate their intended usage and representation in a distinct model phase. At each phase, all constructs specified at that phase shall be specified to a comparable level of detail. Attributes of modelling language constructs shall be adaptable and selectable for the different model phases according to the envisioned needs.
5.2.3 Dimension of enterprise model views
ISO 19439 and ISO 15704 use enterprise model views (often shortened to ‘model views’) to provide a selective perception of an enterprise that emphasizes some distinct aspect of the matter under consideration and disregards others, thereby reducing complexity of representation. Model views need to be understood as selective views on an integrated enterprise model. This document identifies four mandatory enterprise model views (Function, Information, Resource, Organization) that allow the modelling of the major aspects of an enterprise. Additionally, other views may be defined as needed and supported by the modelling methodology, e.g. economic view, decision view, purpose view and implementation view. In this case, additional attributes may augment the constructs defined in this document or relevant new constructs may be defined. Therefore, the specifications of modelling language constructs should accommodate their intended usage and representation in one or several model views. To assure consistency of constructs that can appear in more than one view, automated tools are usually necessary.
5.3 Construct representation
Modelling language constructs shall be represented in a form that is both understandable by humans and interpretable by digital technology. This means there is the need for
— a visual (graphical, iconic) representation of construct structures for use by model builders and business users,
— a structured information-capturing representation (for which this document uses templates) for use by model builders and business users, and
— a machine-interpretable representation for computer-based model simulation and model-based enterprise operation control and monitoring.ISO 19440 pdf download.