MFI Core model and basic mapping Keith Gordon WG2 N1602.

Slides:



Advertisements
Similar presentations
Author: Graeme C. Simsion and Graham C. Witt Chapter 8 Organizing the Data Modeling Task.
Advertisements

Software Engineering-II Sir Zubair Sajid. 3 Data Flow Diagrams (DFD)  DFDs describe the flow of data or information into and out of a system what does.
MFI-8: Changes based on Comments from Wuhan Meeting Peng Liang, Keqing He, Zaiwen Feng, Jian Wang Huafeng Chen, Chong Wang, Yangfan He SKLSE, Wuhan University,
Edition 3 Metadata registry (MDR) Ray Gates May 12, /05/20151.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
1 Lecture 2: Elaboration Tasks and Domain Modeling.
Tutorial 2 DT228/3 Database Technology. Joe’s Yard Take the following documents: –The script as prepared –The docket –The diary in the yard –The list.
Copyright W. Howden1 Lecture 2: Elaboration Tasks and Domain Modeling.
Accounting Information Systems, 1st Edition
Context Diagrams There are three symbols used in these diagrams: Context Diagrams are used in the Analysis and Design phases as an analysis and design.
Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,
1 Business Documents Geoff Leese. 2 Objectives n Be able to ä recognise ä describe the purpose of ä describe the source and destination of ä describe.
Final Report on MFI & MDR Harmonization Hajime Horiuchi May 2010 SC32WG2 N1425.
1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.
Structured Analysis Techniques
Systems Analysis and Design in a Changing World, Fifth Edition
MFI Part-1: Reference Model 2 nd Edition Overview Co-editor: Hajime HORIUCHI Co-editor Keith GORDON For the discussion at Krakow: SC32WG2.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
CS 310 Ch8: System models Abstract descriptions of systems being analyzed to help the analyst understand the system functionality communicate with customers.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
DOMAIN MODEL— PART 2: ATTRIBUTES SYS466. Looking For Potential Classes “Know the business”. Ask Questions Identify business concepts; filter nouns (person,
5 Systems Analysis and Design in a Changing World, Fourth Edition.
1 MFI-5: Metamodel for Process models registration HE Keqing, WANG Chong State Key Lab. Of Software Engineering, Wuhan University
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
2010/11/16 OKABE, Masao 1 Issues to be discussed on MFI-Part10 Core model and basic mapping and transformation OKABE, Masao Editor MFI Part
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
INFO 620Lecture #81 Information Systems Analysis and Design Class Diagram Refinement INFO 620 Glenn Booker.
5 Systems Analysis and Design in a Changing World, Fifth Edition.
Advanced Accounting Information Systems Day 7 Database Modeling.
Burapha University, 2003 Object-Oriented Analysis Basic of Object Mapping to Relational Database.
1 Data Modeling : ER Model…. Lecture Summary so for …. ER Model Entity, Attribute, Key Relationships Instance Diagram.
Design Model Lecture p6 T120B pavasario sem.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2: Associations and Attributes.
Domain Model—Part 2: Attributes.  A logical data value of an object  (Text, p. 158)  In a domain model, attributes and their data types should be simple,
LexEVS Value Domains. LexGrid Definitions Value Domain Definition – the description of the contents Value Domain Resolution – the actual contents –The.
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2A: Attributes.
44220: Database Design & Implementation Conceptual Data Modelling Ian Perry Room: C49 Tel Ext.: 7287
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
BTS430 Systems Analysis and Design using UML Domain Model—Part 2: Associations and Attributes.
Repository of people and organizations and their relationships to each other whether they are internal or external to the enterprise. Customer.
Analysis of Use Cases (and to some extent, standards) - Keith G Jeffery, Rebecca Koskela.
Entity Relationship Diagrams (ERDs)
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
MFI Metamodel for Information Models Keith Gordon ISO/IEC JTC1/SC32/WG2 N1529.
Database Management COP4540, SCS, FIU Database Modeling Using the Entity- Relationship Model (Continued)
Lecture 5 Entity Relationship Modeling
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
OO DomainModeling With UML Class Diagrams and CRC Cards Chapter 6 Princess Nourah bint Abdulrahman University College of Computer and Information Sciences.
DOMAIN MODEL—PART 2: ATTRIBUTES BTS430 Systems Analysis and Design using UML.
Project Based on fictitious Coffee Roasting CompanyCoffee Roasting Company Automatic Order Processing System – –Process “projected” Accept order from customer.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
OO Domain Modeling With UML Class Diagrams and CRC Cards
Context and Data Flow Diagrams
Eugenia Fernandez IUPUI
Abstract descriptions of systems whose requirements are being analysed
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
The Fulfillment Process
Data Modelling Introduction
What is a Relationship Map?
Edition 3 Metadata registry (MDR)
Issues to be discussed on MFI-New-Part2
RDA Community and linked data
Mapping an ERD to a Relational Database
Understanding MFI? More mapping requirements
Presentation transcript:

MFI Core model and basic mapping Keith Gordon WG2 N1602

Roles  Editor: Masao Okabe  In support: Keith Gordon

Packages > CoreModelBasicMappingModel

Core Model Model * ModellingLanguage ▲expressedIn describingLanguage expressedModel ModelElement 0..* 1..* ▼comprises containingModel containedModelElement

Relationship to MDR * ModellingLanguage Model ModelElement 0..* 1..* ▲expressedIn ▼comprises describingLanguage expressedModel containingModel containedModelElement > Attached_Item > Administered_Item > Identified_Item > Registered_Item 0..* 1..1 > Designatable_Item 0..* 1..1 DesignationDefinition Context 0..* 1..*

Core Model and Mapping * ModellingLanguage Model ModelElement 0..* 1..* ▲expressedIn ▼comprises describingLanguage expressedModel containingModel containedModelElement mappedElementelementSet ModelElementSet ◄mappedThrough 1..*0..* * ModelMapping subjectModelmappingFrom ◄subjectOf objectModelmappingTo ◄objectOf * subjectSetmappingFrom ◄subjectOf * objectSetmappingTo ◄objectOf * ModelElementSetMapping modelElementSetMappingDegree [1..1] 0..1containingModelMapping ▼comprises 1..* containedModelMappingComponent ModelElementSetMappingType * describedComponent description ▲describes > ModelElementSetMappingDegree semanticallyEquivalent semanticallySimilar

Mapping example #1 PRODUCT product-description product-code Product code : String description : String Object Class to Entity Type Object Class to Entity Type mapping Object Class to Entity Type Semantically Equivalent

Mapping example #2 Product code : String description : String Supplier number: String name: String address: Address 0..* 1..* ◄supplies ProductSupplier startDate: Date rating: Integer SUPPLIER supplier-name supplier-address supplier-number PRODUCT product-description product-code PRODUCT-SUPPLIER product-supplier-start-date product-supplier-rating product-code (FK) supplier-number (FK) acts-assupplied-by P Object Class to Entity Type Many-to-many association replaced by an intersection entity type Object Class to Entity Type Semantically Equivalent

Mapping example #3 Department name : String ExternalCustomer number: String name: String address: Address * ◄places Order number: String startDate: Date ExternalOrder DepartmentalOrder * ◄places Object Class to Entity Type Exclusive Arc replaced by Sub- classes Object Class to Entity Type Semantically Equivalent ORDER (m) number (m) date placed by placer of EXTERNAL CUSTOMER (m) number (m) name (m) address placed by DEPARTMENT (m) name placer of

Mapping example #4 Object Class to Entity Type Process decomposed Object Class to Entity Type Semantically Equivalent FULFILL ORDER ISSUE INVOICE RECORD PAYMENT Object Class to Entity Type Process amalgamation Object Class to Entity Type Semantically Equivalent CHECK ORDER PICK GOODS DESPATCH GOODS HANDLE PAYMENT StartStop

Mapping example #5 Object Class to Entity Type Sequence dependency replacement Object Class to Entity Type Semantically Similar FULFIL ORDER ISSUE INVOICE RECORD PAYMENT Order Received Payment Recorded FULFIL ORDER ISSUE INVOICE RECORD PAYMENT Order Received Payment Recorded Payment Received Invoice Issued

Mapping example #6 Concept Union Object Class to Entity Type Semantically Equivalent Ontology A Scotch Whisky Ontology B Single Scotch Whisky Blended Scotch Whisky

Mapping example #7 Concept Intersection Object Class to Entity Type Semantically Equivalent Ontology A axiom1: “Scotch whisky is whisky made in Scotland. Ontology B axiom2: “Scotch whisky is a kind of whisky.” axiom3: “Scotch whisky is made in Scotland.”

Where we agree  The metaclasses (and their names) - generally  The attributes (and their names) - generally  The associations (and their multiplicities and names)

Where we disagree  Whether to use separators or camel case for names. (recommendation: upper camel case for metaclasses, lower camel case for attributes, associations, etc)  How to document associations in the text:  with one reference?  with two references?  (CA prefers associations documented separately) (recommendation: two references)  How and where to explain the relationship to MDR-3.  Okabe-san is not too happy with “model mapping”.  Whether a model must have an IRI.

Any questions?