{"id":352321,"date":"2024-10-20T00:51:53","date_gmt":"2024-10-20T00:51:53","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-iso-iec-19763-122015\/"},"modified":"2024-10-26T00:51:17","modified_gmt":"2024-10-26T00:51:17","slug":"bs-iso-iec-19763-122015","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-iso-iec-19763-122015\/","title":{"rendered":"BS ISO\/IEC 19763-12:2015"},"content":{"rendered":"
The primary purpose of the multipart standard ISO\/IEC 19763 is to specify a metamodel framework for interoperability. This part of ISO\/IEC 19763 specifies a metamodel for registering information models. This metamodel was developed taking into account two distinct types of information models such as<\/p>\n
those that are used to document the information requirements of a particular area of interest, and<\/p>\n<\/li>\n
those that represent the structure of a database which are often expressed using a Database Definition Language (DDL).<\/p>\n<\/li>\n<\/ul>\n
Information models that represent information requirements can be developed using a number of different common diagramming techniques and notations. The metamodel specified in this part of ISO\/IEC 19763 was developed to cover the registration of models expressed using the following techniques and notations:<\/p>\n
Express-G, an ISO standard entity-relationship modelling notation, as described in Reference [8];<\/p>\n<\/li>\n
IDEF1X, a US Federal standard entity-relationship modelling notation, as described in References [6] and [12];<\/p>\n<\/li>\n
the entity-relationship modelling notation first developed by Harry Ellis and Richard Barker and later adopted by Oracle for its CASE*Method and by the UK’s CCTA for SSADM (Structured Systems Analysis and Design Method), as described in Reference [2];<\/p>\n<\/li>\n
the UML Class Diagram notation, as described in References [13] and [14];<\/p>\n<\/li>\n
the original entity-relationship modelling notation proposed by Peter Chen, as described in Reference [4];<\/p>\n<\/li>\n
the Information Engineering entity-relationship modelling notation, as described in Reference [11].<\/p>\n<\/li>\n<\/ul>\n
It is understood that these selected techniques represent all of the essential features of all information modelling techniques used to represent information requirements.<\/p>\n
The registration of information models that represent the structure of a database is limited in the metamodel specified in this part of ISO\/IEC 19763 to those database structures that conform to the Core SQL specification. Core SQL is the set of features defined in the conformance requirements specified in ISO\/IEC 9075-2 and ISO\/IEC 9075-11.<\/p>\n
The registration of information models that are expressed using notations such as Object Role Modeling (ORM) and “Natural language Information Analysis Method” (NIAM), collectively known as fact-based models, is out of scope for this part of ISO\/IEC 19763.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
6<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
7<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
9<\/td>\n | 1\tScope <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 2\tConformance 2.1\tGeneral 2.2\tDegree of conformance 2.2.1\tGeneral 2.2.2\tStrictly conforming implementation 2.2.3\tConforming implementation 2.3\tImplementation Conformance Statement (ICS) 3\tNormative references <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4\tTerms, definitions, and abbreviated terms 4.1\tTerms and definitions 4.2\tTerms for concepts used in this part of 19763 <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 4.3\tAbbreviated terms <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5\tStructure of MFI Information model registration 5.1\tOverview of MFI Information model registration <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 5.2\tAssociation between MFI Information model registration and MFI Core and mapping <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.3\tMetaclasses in MFI Information Model Registration 5.3.1\tAttribute <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.3.2\tAttribute_Unique_Identifier_Element 5.3.3\tDescribed_Domain <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.3.4\tDiagram 5.3.5\tDomain <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.3.6\tEntity_Specialisation_Hierarchy <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 5.3.7\tEntity_Specialisation_Hierarchy_Foreign_Key_Attribute 5.3.8\tEntity_Type <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.3.9\tEnumerated_Domain 5.3.10\tForeign_Key_Attribute 5.3.11\tGeneral_Constraint <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.3.12\tInformation_Model 5.3.13\tInformation_Modelling_Language 5.3.14\tKey_Attribute <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.3.15\tNative_Key_Attribute 5.3.16\tNon_Key_Attribute 5.3.17\tRelationship <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.3.18\tRelationship_End <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.3.19\tRelationship_End_Foreign_Key_Attribute <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 5.3.20\tRelationship_End_Group 5.3.21\tRelationship_End_Unique_Identifier_Element <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5.3.22\tUnique_Identifier 5.3.23\tUnique_Identifier_Element <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.3.24\tValid_Value <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Annex\u00a0A (informative) Description of the metamodel <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Annex\u00a0B (informative) Relationship of metaclasses to the MDR Metamodel <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Annex\u00a0C (informative) Applicability of information modelling concepts to techniques <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Annex\u00a0D (informative) Examples of information model registration <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Information technology. Metamodel framework for interoperability (MFI) – Metamodel for information model registration<\/b><\/p>\n |