Information technology Metamodel framework for interoperability (MFI) Part 1: Framework

ISO/IEC JTC 1/SC 32 Date: 2014-06-19 ISO/IEC DIS 19763-1 ISO/IEC JTC 1/SC 32/WG 2 Secretariat: ANSI Information technology Metamodel framework for interoperability (MFI) Part 1: Framework Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: International Standard Document subtype: Document stage: (40) Enquiry Document language: E

ISO/IEC DIS 19763-1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Copyright notice This ISO document is a working draft or committee draft and is copyright-protected by ISO. While the reproduction of working drafts or committee drafts in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO's member body in the country of the requester: ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyright@iso.ch Web www.iso.ch Reproduction for sales purposes may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii ISO/IEC 2014 All rights reserved

ISO/IEC DIS 19763-1 16 Contents Page 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 Foreword... v Introduction... vi 1 Scope... 1 1.1 Inclusions... 1 1.2 Exclusions... 1 2 Conformance... 2 3 Normative references... 2 4 Terms, definitions and abbreviated terms... 2 4.1 Terms and definitions... 2 4.2 Abbreviated terms... 5 5 Purpose and objectives of MFI... 7 5.1 Purpose of MFI... 7 5.2 Strengthening interoperability and integration capability... 7 5.2.1 Introduction... 7 5.2.2 System interoperability... 8 5.2.3 Semantic interoperability... 10 5.3 interoperability... 10 5.4 Model discovery... 11 6 Model registration... 11 6.1 Basic idea of the MFI metamodels... 11 6.2 Basic concept of model registration... 12 7 MFI Architecture... 14 7.1 The overall structure of MFI... 14 7.2 A common modelling facility for MFI... 14 Annex A (informative) Internal structure of MFI... 16 Annex B (informative) Future harmonised structure for MFI and MDR... 18 Bibliography... 19 ISO/IEC 2014 All rights reserved iii

ISO/IEC DIS 19763-1 45 46 47 48 49 50 51 52 53 54 55 56 57 58 Figures Figure 1 Two types of interoperability... 8 Figure 2 Current problems with cross-industries interoperation... 9 Figure 3 Basic concept of model sharing through a Model... 9 Figure 4 interoperability using RS and ROR... 10 Figure 5 Discovering services and processes based on RGPS... 11 Figure 6 MFI metamodels and the UML metamodel... 12 Figure 7 Basic concept of MFI registration... 12 Figure 8 Relationship between model and the associated model information... 13 Figure 9 Overall structure of MFI and its relationships to MDR and UML... 14 Figure 10 Basic concept of the core model... 15 Figure 11 Common base for MFI subparts... 15 Figure A.1 Relationship between parts within the MFI family of standards... 16 Figure B.1 The future harmonisation target... 18 59 60 61 Tables No table of figures entries found. iv ISO/IEC 2014 All rights reserved

ISO/IEC DIS 19763-1 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 19763-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information Technology, Subcommittee SC 32, Data management and Interchange. ISO/IEC 19763 consists of the following parts, under the general title Information technology Metamodel framework for interoperability (MFI): Part 1: Framework Part 3: Metamodel for ontology registration Part 5: Metamodel for process model registration Part 6: summary Part 7: Metamodel for service model registration Part 8: Metamodel for role and goal model registration Part 9: On demand model selection based on RGPS [Technical Report] Part 10: Core model and basic mapping Part 12: Metamodel for information model registration Part 13: Metamodel for form design registration ISO/IEC 2014 All rights reserved v

ISO/IEC DIS 19763-1 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 Introduction Due to the proliferation of internet-enabled communication aided by mobile devices, social network systems and cloud computing, both the efficient and effective sharing of information and the handling of business transactions across countries and cultures has become easier. In the private sector the handling of these business transactions using Electronic Data Interchange (EDI) has been common for a long time. Companies hold large quantities of structured, semi-structured and unstructured data the Big Data explosion. It is in their interest to make effective use of this data to extract business intelligence and knowledge. In the public sector, governments in many countries and territories are working on the establishment of new schemes that enable interoperation and collaboration among different departments or agencies, materialising the semantic interoperability of data and surmounting border and/or language differences. At the same time, many governments and agencies are attempting to make their data available to their citizens over the internet, the Open Data initiatives. These Open Data initiatives could be the driver for similar innovations in the private sector. One of the issues for users is to access the various sets of open data easily and integrate them for analysis so as to create new value through added information or knowledge. These trends have produced new needs for standards that enable effective information sharing in both private and public sectors. One of the key enablers of this sharing of the information that is used by different communities through the interoperability of systems is a registry, or a network of inter-connected registries, that provides for the discovery and sharing of meta-information, such as metadata or models. The Metamodel Framework for Interoperability (MFI) provides the specifications for such registries. The MFI specifications can be considered as an extension of those for a Metadata (MDR) as defined in ISO/IEC 11179-3 because MFI and MDR share the same registration mechanism and procedures. In 2010 a special study project was initiated to consider the harmonisation of MDR and MFI and a key recommendation of that study project was that the common facilities should be identified and used for both MDR and MFI. It is anticipated that MDR and MFI could be more closely related and integrated, leading to benefits for the users who need more effective sharing of information and models, or more sophisticated interoperation of systems. This new edition of Part 1 has been developed to provide a clear overview of MFI and to illustrate the overall architecture of the MFI family of standards to reflect the major changes described above. vi ISO/IEC 2014 All rights reserved

DRAFT INTERNATIONAL STANDARD ISO/IEC DIS 19763-1 121 122 Information technology Metamodel framework for interoperability (MFI) Part 1: Framework 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 1 Scope 1.1 Inclusions This standard is a part of the ISO/IEC19763 (Metamodel framework for interoperability) (MFI) family of standards. As the first part of MFI, this standard provides an overview of the whole of MFI. In particular, the purpose, the underlying concepts, the overall architecture and the requirements for the development of other standards within the MFI family are described. MFI provides a set of normative metamodels to enable the registration of many different types of model. Each of these metamodels is expressed as a UML Class Diagram. MFI is evolving. Currently, in addition to this part, the MFI family comprises: A core model and facilities for the basic mapping of models (Part 10) A metamodel for ontology registration (Part 3) A metamodel for process model registration (Part 5) A metamodel for service model registration (Part 7) A metamodel for role and goal model registration (Part 8) A Technical Report describing on demand model selection based on RGPS (Part 9) A metamodel for information model registration (Part 12) A metamodel for form design registration (Part 13) A metamodel for a registry summary (Part 6) These parts are described in more detail in Annex A. 1.2 Exclusions The MFI does not specify any physical structure of the registry where model information is to be recorded. MFI metamodels define standard views as models to be used in the registering of model instances in a model registry while actual instance documents could be stored in a model repository. 146 ISO/IEC 2014 All rights reserved 1

147 148 149 2 Conformance ISO/IEC 19763-1 specifies no conformance requirements. Other parts of the ISO/IEC 19763 family of standards specify their own conformance requirements as appropriate. 150 151 152 153 154 155 156 157 158 159 160 161 3 Normative references The following referenced documents are indispensable for the application of this document. For dated references only the edition cited applies. For undated references the latest edition of the referenced document (including any amendments) applies. ISO/IEC 11179-3, Information technology Metadata registries (MDR) Part 3: metamodel and basic attributes ISO/IEC 11179-6, Information technology Metadata registries (MDR) Part 6: Registration ISO/IEC 19505-1:2012, Information technology -- Object Management Group Unified Modeling Language (OMG UML) -- Part 1: Infrastructure ISO/IEC 19505-2:2012, Information technology -- Object Management Group Unified Modeling Language (OMG UML) -- Part 2: Superstructure 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 4 Terms, definitions and abbreviated terms 4.1 Terms and definitions For the purposes of this document, the following terms and definitions apply. 4.1.1 concept unit of knowledge created by a unique combination of characteristics NOTE Concepts are not necessarily bound to particular languages. They are, however, influenced by the social or cultural background which often leads to different categorizations. [ISO 1087-1:2000, 3.2.1] 4.1.2 cloud computing paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand NOTE Examples of resources include servers, operating systems, networks, software, applications, and storage equipment. [ISO/IEC DIS 17788, 3.2.4] 2 ISO/IEC 2014 All rights reserved

179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 4.1.3 framework logical structure for classifying and organizing complex information [ISO/TS 27790:2009, 3.27] NOTE In MFI the framework is used to represent the architectural view of a set of metamodels for registration. 4.1.4 information model graphical and textual representation of entities and the relationships between them NOTE May also be known as a data model, a conceptual data model, a logical data model, an entity relationship model, an object class diagram or a database definition 4.1.5 interoperability capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units [ISO/IEC 2382-1] 4.1.6 metadata data which describes other data [ISO/IEC 11179-1:2004, 3.2.16] 4.1.7 metadata item instance of a metadata object (4.1.8) [ISO/IEC 11179-3:2013, 3.2.75] 4.1.8 metadata object object type defined by a metamodel (4.1.10) [ISO/IEC 11179-3:2013, 3.2.76] 4.1.9 metadata registry information system for registering metadata (4.1.6) NOTE the associated information store or database is known as a metadata register [ISO/IEC 11179-3:2013, 3.2.78] 4.1.10 metamodel model (4.1.11) that explains a set of related models (4.1.11) by defining the language for expressing such models (4.1.11) [ISO 14813-5:2010, B.1.84] ISO/IEC 2014 All rights reserved 3

217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 4.1.11 model representation of some aspect of a domain of interest using a normative modelling facility (4.1.17) and model constructs (4.1.12) NOTE models can be used to express a set of information requirements, processes, services, roles, goals or some other aspect of a domain of interest 4.1.12 model construct unit of notation to represent a model (4.1.11) NOTE This is a more generic term for model element. Sometimes the term is used to include metadata, code and object patterns rather than the notations of a particular modelling facility such as UML. 4.1.13 model element element or component in a model (4.1.11) NOTE Examples of model elements are representation of an entity type in an information model, representation of an event in a process model, representation of a service operation in a service model, or representation of an actor in a role and goal model. 4.1.14 model information information that describes characteristics of a model (4.1.11) to be registered NOTE In MFI, the model information about a model will be registered using instances of Registered_Item as specified in ISO/IEC 11179-3 4.1.15 model registry registry (4.1.23) where models (4.1.11) are registered 4.1.16 model repository repository (4.1.24) where models (4.1.11) are stored 4.1.17 modelling facility set of rules and notations for use when modelling NOTE 1 UML is a typical example of a modelling facility NOTE 2 May also be known as a modelling language 4.1.18 modelling language language or notation that is used to model some aspect of a domain of interest NOTE 1 UML is a typical example of a modelling language NOTE 2 May also be known as a modelling facility 4 ISO/IEC 2014 All rights reserved

255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 4.1.19 ontology specification of concrete or abstract things, and the relationships among them, in a prescribed domain of knowledge NOTE The specification should be computer processable [ISO/IEC 19763-3:2010] 4.1.20 process collection of related, structured activities or tasks that achieve a particular goal 4.1.21 process model representation of a process (4.1.20), using a specific process modelling language (4.1.18) 4.1.22 registration <generic> inclusion of a item in a registry (4.1.23) <metadata registry> inclusion of a metadata item (4.1.7) in a metadata registry (4.1.9) [ISO/IEC 11179-3:2013, 3.2.108] NOTE 1 In ISO/IEC 19763 a metadata item is a model or a model element and a metadata registry is a model registry. NOTE 2 Registration requires that a minimum set of administrative information about the metadata item (model) be specified, such that it becomes a registered item 4.1.23 registry information system for registration (4.1.22) [ISO/IEC 11179-3:2013, 3.2.113] NOTE In ISO/IEC 19763, the registry is a Model since the metadata items that are registered are models. This Model uses facilities provided by a Metadata as specified in ISO/IEC 11179-3 4.1.24 repository place where, or receptacle in which, things are or may be stored NOTE In MFI and MDR, a repository is recognized as a database that stores actual instances to conform to a particular metamodel or a particular set of metadata. 4.1.25 service kind of web based application, which encapsulates one or more computing modules and can be accessed through a specified interface 290 291 292 293 4.2 Abbreviated terms BPEL Business Process Execution Language ISO/IEC 2014 All rights reserved 5

294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 BPMN Business Process Model and Notation IDEF1X Integration DEFinition for Information Modeling IEC International Electrotechnical Commission LOD Linked Open Data ISO International Organization for Standardization MDR Meta Data MDR Metamodel ISO/IEC 11179-3, Information technology Metadata registries (MDR) Part 3: metamodel and basic attributes MDR Registration ISO/IEC 11179-6, Information technology Metadata registries (MDR) Part 6: Registration MFI Metamodel Framework for Interoperability (this family of standards (ISO/IEC 19763)) MFI Core and mapping ISO/IEC 19763-10, Information technology Metamodel framework for interoperability Part-10: Core model and basic mapping OMG Object Management Group RGPS Role, Goal, Process and Service ROR of Registries RS Summary SDO Standards Developing Organization UML Unified Modeling Language UN United Nations XML extensible Markup Language W3C World Wide Web Consortium 6 ISO/IEC 2014 All rights reserved

334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 5 Purpose and objectives of MFI 5.1 Purpose of MFI MFI provides a set of specifications that allow the registration of models to facilitate interoperability among systems or persons. In this context interoperability is interpreted in its broadest sense: the capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have little or no knowledge of the unique characteristics of those units (ISO/IEC 2382-1:1993). The models that are registered may be ontologies, information models, process models, service models, models of roles and goals or any other type of model specified within MFI. Models are used widely within the information technology community to represent system requirements and system specifications. These models can be expressed using a variety of notations or languages. An information model may be expressed in any one of a number of entity-relationship notations, from the simplicity of the original entity-relationship notation proposed by Dr Peter Chen through to the complexity of Express-G, as a UML Class Diagram, or even as a set of SQL CREATE TABLE statements. Similarly, process models may be expressed as BPMN models, as UML Activity Diagrams, or as a set of BPEL statements. The sharing of these models is essential if interoperability is to be achieved. If two systems are to exchange information then not only must the formats in which the information is represented as data in those systems be known but the semantics underpinning that data and the processes that the systems are designed to support must also be unambiguously understood. If services are to be shared between interoperating systems then the processes that these services execute, with their goals and the roles of the people or organisations associated with these processes and services, also need to be unambiguously understood. The underlying purpose of MFI is to allow the sharing of these models. Each of the main parts of MFI provides a specification, in the form of a metamodel, for a model registry where information about the models, and the things, processes, etc that they are describing, can be registered. Once models have been registered it is possible for the mappings between models, or parts of models, to also be registered. In addition, because models are registered in a registry they can be discovered. A metamodel in MFI is an information model that provides a conceptual view of the information that is recorded when a model is registered. Each of these metamodels is expressed as a UML Class Diagram. It is not sufficient to register a model in a registry. The registry must also be discoverable, and enabling this discoverability of registries is also an important element of MFI. 5.2 Strengthening interoperability and integration capability 5.2.1 Introduction High-level information sharing is necessary to achieve the integration of data or services described above. This relies upon the strengthening of the capabilities to discover models. This is underpinned by two types of interoperability, as follows: System interoperability Semantic interoperability This is illustrated in Figure 1 below. ISO/IEC 2014 All rights reserved 7

High-level information sharing System interoperability Semantic interoperability 374 Model sharing through registration 375 Figure 1 Two types of interoperability 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 5.2.2 System interoperability System interoperability in a heterogeneous network system requires the standardisation of the communication protocols to enable the lower level physical connection. It also requires the standardisation of both the message formats and the syntactic representation of the data to be exchanged. The syntactic representation of data is normally held as metadata. Many de jure and de facto Standards Developing Organizations (SDO), such as ISO, IEC, UN, OMG and W3C, have developed and enforced many industry-specific metadata or registry standards. Examples exist in the e-business, healthcare, electronic parts, electronic documents and library areas, but most of these industry sector metadata or registry standards are incompatible with each other. With this proliferation of standards it is not easy to share information across different industries or domains without any specific mapping or translation tools. This is made worse if the metadata is registered in different registries. For this reason it is almost impossible to have a global and dynamic supply chain that penetrates different industries across many countries. For example, an electronics manufacturing company will have their own product database to handle the development, manufacture and sale of their products while the retailer will have their own item database which will be used to manage their stock and their purchases. Each database will have been developed individually, with each following the particular metadata standards, if any, that were specified by the industry consortium or some other SDO. In this situation it is almost impossible to achieve interoperability between the manufacturer s system and the retailer s system. Figure 2 illustrates this problem. 8 ISO/IEC 2014 All rights reserved

Manufacturing sector standard for the manufacturing sector Electronic Parts Category Home electronic products Products Retail sector standard for the retail sector Home Electronics Category Metadata Product_Number Attributes for manufacturing Item_Number Attributes for retail 396 Part Master DB No interoperability Item Master DB 3 397 398 399 400 401 402 403 404 405 406 407 408 409 Figure 2 Current problems with cross-industries interoperation To overcome this problem there must be a mapping between the database structures of the two systems. To achieve this mapping the information models, and perhaps the process models, need to be understood and compared. The mappings themselves then need to be registered. In software development, information models are used to capture and document the information requirements that should then lead to the specification of a database design. Each of these information models will be expressed using one of the many notations available, for example as a UML Class Diagram or as an IDEF1X model. Since many engineers are normally involved in any software development the sharing of models is common. Where this development involves collaborating engineers in different countries and languages, this model sharing must be supported by a specific platform or infrastructure. In the model registry, MFI provides a basis for this model-sharing infrastructure. Model sharing can be made possible by registering these models in a model registry. This will make it easier to discover an appropriate model. See Figure 3 for an illustration of this concept. 410 411 412 Figure 3 Basic concept of model sharing through a model registry 413 ISO/IEC 2014 All rights reserved 9

414 415 416 417 418 419 420 421 422 5.2.3 Semantic interoperability Many terminology dictionaries are available, some on the internet. Some of these are generic dictionaries while the others each provide a set of technical terminologies in a specific domain, such as healthcare. By enabling the registration of ontologies, where each ontology is a set of inter-related concept definitions within a specific domain of knowledge, MFI provides the ability to annotate each model construct so that data sharing and model sharing can be based on the semantic understanding of the model or the information represented by the model. As well as aiding the understanding of the meaning of information, these facilities are also helpful in the definition of mapping rules between model constructs. 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 5.3 interoperability Another major purpose of MFI is to enable interoperability between registries. Many metadata registries or model registries are in existence, each designed to support industry-specific business domains in many different countries or territories. Most of these registries conform to industry-specific standards, such as for e-business, healthcare, or library operations. However, those standards themselves are incompatible with each other and they have been developed to meet the requirements specific to their own domains. It means that a single company or user who belongs to a particular domain experiences difficulties in accessing registries in other, different, domains. To enable system interoperability, it is necessary to share information registered in different registries across different domains. To achieve this MFI specifies, using a metamodel, a set of small XML artefacts, called a Summary (RS), which will record the nature of the registry and its content and also provide technical information to enable accessing the registry. The intention is that the RS should be attached to each registry. Figure 4 below illustrates a typical example of the use of Summaries. Each registry in a particular domain can make their Summary publically available. Users in different domains, such as Manufacturing or Retailing, can then build their own dedicated registry that is a collection of Summaries that are of interest to them. This special registry is called a of Registries (ROR). Registries in Retail domain Registries in Manufacturing domain RS RS Metadata Company Directory RS RS Products Catalogue Metadata Model RS ROR Orders ROR ROR ROR Customer Retailer Wholesaler Manufacturer 441 Supply chain Products 442 Figure 4 interoperability using RS and ROR 443 10 ISO/IEC 2014 All rights reserved

444 445 446 447 448 449 450 451 452 5.4 Model discovery There is a need for the smart and efficient discovery and integration of information objects that are available over networks. This is made more urgent in the era of the internet, cloud computing and Linked Open Data (LOD), where there is a requirement for more sophisticated knowledge and service discovery. MFI provides for this discovery through those parts that contribute to the Role, Goal, Process and Service (RGPS) facilities: the metamodel for process model registration, the metamodel for service model registration, and the metamodel for role and goal model registration. The use of these parts is brought together in the Technical Report that explains the on demand model selection based on RGPS, as illustrated in Figure 5. Process Model Process Model Process Model Service Service Role and Goal On Demand Discovery Model Selection 6 Based on RGPS Ontology 453 Service 454 Figure 5 Discovering services and processes based on RGPS 455 456 457 458 459 460 461 462 463 464 465 466 467 468 6 Model registration 6.1 Basic idea of the MFI metamodels A metamodel is a model that is used to explain a set of related models by defining the language that is used for expressing such models. In MFI the metamodels specified in the different parts define the set of concepts described in the models under consideration that are important for interoperability and, therefore, need to be registered. In MFI all of the metamodels are specified as UML Class Diagrams, which means that all of the MFI metamodels are described using the UML metamodel. However, UML is not the only set of notations used for domain modelling. Other languages, such as IDEF1X for information modelling and BPMN for business process modelling, are often used. All of the MFI metamodels, therefore, are not designed for a specific domain modelling language but are able to accommodate generic concepts covered by the type of model concerned (ontologies, information modelling, process modelling, etc). ISO/IEC 2014 All rights reserved 11

Metamodel for other language UML Metamodel use MFI Metamodel apply apply Domain Concept Domain Modelling Domain Model Model Registration Model 469 Scope of MFI 470 Figure 6 MFI metamodels and the UML metamodel 471 472 473 474 475 476 477 6.2 Basic concept of model registration MFI is a set of metamodels specifying the structure of registries that may be used to register various types of models. The use of these MFI metamodels makes the model registration process easier. They also enable consistency in the information to be registered about the models. Figure 7 shows the basic concept of the model registration. The MFI metamodels provide a registrar with a consistent view of model information that needs to be registered. 478 479 480 481 482 483 484 485 486 487 Figure 7 Basic concept of MFI registration One of the MFI metamodels is a core model that provides common features that are used by all the other parts. The model constructs in the metamodels in the other parts are all specialisations of model constructs defined in the core model. The metamodels for the other parts provide details of the information to be registered for: ontologies information models process models service models 12 ISO/IEC 2014 All rights reserved

488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 role and goal models form designs MFI does not specify any implementation requirements for a registry. Each metamodel only specifies the information that may be registered about a model. A registry does not store the actual model instance in its database; only the model information is stored. The model information stored in a registry provides information about: where the model exists, who is the owner, and when it is registered, what model elements are included in the model, and what are relationships between these model elements. MFI assumes that the actual models to be shared are stored outside of MFI. This storage may be electronic in a model repository or the models may be held as documents. An MFI registry uses the registration facilities that are specified in the MDR Metamodel. As such, for each model the following information may be recorded: details of the registration authority, including the registrar. the date of the registration. the submission status. the ownership of the model. the context of the model. the elements within the model. In terms of the MDR Metamodel, the registered model becomes a registered item, as shown in Figure 8. MFI Metamodel Model MI(1) Specification of structure for model information Model information for MI(1) Registered Item Order Customer Order Item Product Identification Naming Registration Authority Model representation based on MFI metamodel Order Customer Order Item Product 508 Example Information Model to be registered 509 Figure 8 Relationship between a model and its associated model information 510 ISO/IEC 2014 All rights reserved 13

511 512 513 514 515 516 517 518 519 520 521 522 523 524 7 MFI architecture 7.1 The overall structure of MFI This section specifies the architecture of MFI. All future developments of extra parts of MFI must adopt this architecture. The MFI family of standards consists of a number of parts, each of which (other than this part and any technical reports) specifies a metamodel. Most of these metamodels provide for the registration of a particular type of model. One part (Part 10) provides common facilities for the other parts: a core model and basic mapping facilities. In order to achieve the purpose set out in Clause 5 the MFI family of standards needs to be tightly harmonised with the MDR family of standards. This is because metadata is needed to define the model information that is to be registered in the MFI registries. MFI uses the registration procedure specified in MDR Registration. MFI can be considered to be an extension of MDR. Figure 9 shows the basic overall structure of the MFI standard, including its relationship to MDR and UML. UML2 (ISO/IEC 19505-2) Superstructure use use MDR Metamodel (ISO/IEC 11179-3) Basic Package MFI Core and mapping (ISO/IEC 19763-10) Core Model and Basic Mapping use Other parts of MFI use 525 MFI X (ISO/IEC MFI 19763-X) X (ISO/IEC MFI 19763-X) X (ISO/IEC 19763-X) 526 Figure 9 Overall structure of MFI and its relationships to MDR and UML 527 528 529 530 531 532 533 534 535 7.2 A common modelling facility for MFI To maintain consistency between the parts of the MFI family of standards, one of the parts (Part 10) provides common modelling facilities in addition to facilities to map models together. Figure 10 shows the core model concept. Central to the core model are three metaclasses: Modelling_Language, Model, and Model_Element. The inclusion of Modelling_Language allows models expressed in any modelling language to be registered. 14 ISO/IEC 2014 All rights reserved

Modelling Language use Modelling_Language 1..* 0..* 536 Customer Order Supplier Order Item Product Example Information Model Model 0..* 0..* Model_Element Core Model 537 538 539 540 Figure 10 Basic concept of the core model The metaclasses in the metamodels specified in the other parts are all specialisations of one of the metaclasses in the core model, as shown in Figure 11. As new parts are developed they will follow this structure, thus ensuring that the architecture is maintained. Modelling_Language 1..* 0..* Model Core Model 0..* 0..* Model_Element <<use>> 541 Metamodel in MFI Part 3 Metamodel in MFI Part 5 Metamodel in MFI Part 7... Metamodel in MFI Part N 542 Figure 11 Common base for MFI subparts 543 ISO/IEC 2014 All rights reserved 15

544 545 546 547 548 549 Annex A (informative) Internal structure of MFI The MFI family of standards is still evolving but this Annex describes the parts that are planned at the time of publication of this framework. ISO/IEC 11179-3 (MDR) Basic Package Part 6 Part 10 ISO/IEC 19763 (MFI) Part 1 Part 3 Part 5 Part 7 Part 12 Part 8 Part 13 Part 9 (TR) RGPS Family 550 Note: The Role-Goal-Process-Service (RGPS) Family forms a set of standards that together facilitate the discovery of services 551 Figure A.1 Relationship between parts within the MFI family of standards 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 MDR In order to maintain consistency in the registration of objects, such as models or model elements, all parts of MFI share the same administrative information that is defined in the basic package of ISO/IEC11179-3. This enables MFI registries to make use of the common facilities provided by metadata registries. Thus, a model or a model element may be registered as one or more of the types specified in ISO/IEC 11179-3, ie: an Identified_Item a Registered_Item an Administered_Item an Attached_Item a Designatable_Item a Classifiable_Item MFI Part 1: Framework Part 1 (this part) describes the concepts, including registration, and the overall architecture of the standard that is to be applied in the development of the individual metamodels specified in the other parts. MFI Part 10: Core model and basic mapping Part 10 specifies the core model that provides the framework for all other metamodels specified in the other parts. It also provides facilities to enable individual models and model elements to be annotated with constructs from ontologies and facilities to enable the mapping of models to other models. 16 ISO/IEC 2014 All rights reserved

571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 MFI Part 3: Metamodel for ontology registration Part 3 specifies a metamodel that provides for the registration of administrative information about ontologies. These ontologies may be used to annotate elements of other models. MFI Part 5: Metamodel for process model registration Part 5 specifies a metamodel that provides for the registration of administrative information about different kinds of process models. These process models may describe the processes supported by a system or may support the discovery of services through RGPS. MFI Part 6: summary Part 6 specifies a metamodel of the registry summary information that may be added to any type of registry. This summary information can be collected together into a of Registries (ROR). MFI Part 7: Metamodel for service model registration Part 7 specifies a metamodel for the registration of administrative information about services. The main focus of this part is on web services but the metamodel can be used to register any service that is supported by a set of processes. MFI Part 8: Metamodel for role and goal model registration Part 8 specifies a metamodel for the registration of administrative information about the roles and goals that are associated with processes and services. MFI Part 9: On demand model selection based on RGPS (Technical Report) Part 9 is a technical report that explains how a registry, or a collection of interconnected registries, that is based the metamodels specified in Parts, 5, 7 and 8 may be used together to discover models, particularly models that represent services. MFI Part 12: Metamodel for information model registration Part 12 specifies a metamodel for the registration of administrative information about information models, models that describe the information recorded in a system. These may be entity-relationship models, UML Class Diagrams or SQL table definitions. MFI Part 13: Metamodel for form design registration Part 13 specifies a metamodel for the registration of administrative information about the structure of forms, such as electronic health records or other legal or official forms. 599 ISO/IEC 2014 All rights reserved 17

600 601 602 603 604 605 606 607 608 Annex B (informative) Future harmonised structure for MFI and MDR MFI relies heavily on the common facilities provided by the MDR Metamodel. It is envisaged that at some stage in the future there should be even closer harmonisation of the MFI and MDR standards, the ISO/IEC19763 family of standards, the ISO/IEC11179 family of standards and their associated standards. This closer harmonisation will enable more effective and efficient use of both metadata and models. Figure B.1 illustrates the final target of the harmonisation on MFI and MDR. MDR/MFI Framework Model MFI Core Model MDR Metamodel Metadata ISO/IEC 24707 Common Logic MDR/MFI Registration MFI-3 MFI-5 MFI-7... MFI-N MFI-6 Summary ISO/IEC 20943 MDR Content Consistency ROR ROR Ontology Process Model Service Nnnn ISO/IEC 20944 MDR Interoperability and Bindings 609 MFI-9 On Demand Model Selection Based ON RGPS 610 Figure B.1 The future harmonisation target 611 18 ISO/IEC 2014 All rights reserved

612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 Bibliography [1] ISO/IEC TR 9007:1987, Information processing systems Concepts and terminology for the conceptual schema and the information base (ISO/IEC TR 9007 provides information on conceptual modelling) [2] ISO/IEC 10027:1990, Information technology Information Resource Dictionary System (IRDS) Framework (ISO/IEC 10027 describes the concept of levels of modelling) [3] ISO/IEC TR 20943-1, Information technology Achieving metadata registry content consistency Part 1: Data elements (ISO/IEC TR 20943-1 provides guidelines for recording data elements in a 11179-3 metadata registry) [4] ISO/IEC TR 20943-3, Information technology Achieving metadata registry content consistency Part 3: Value domains (ISO/IEC TR 20943-3 provides guidelines for recording value domains in a 11179-3 metadata registry) [5] [MDA] Policies and Procedures for MDA: OMG, 2001, pp/2001-09-01 [6] [ebrim] ebxml Information Model. Version 0.56. Working Draft. 2/28/2001. ebxml Project Team. [7] [ebrs] ebxml Services. Version 0.85. Working Draft. 2/28/2001. ebxml Project Team. ISO/IEC 2014 All rights reserved 19