MFI Metamodel for Information Models

Transcription

1 ISO/IEC JTC1/SC32/WG2 N1529 MFI Metamodel for Information Models Keith Gordon

2 Purpose Registry Information model expressed in IDEF1X Register MFI Core and Mapping MFI Information Models Register Information model expressed as UML Class Diagram Design Design System A Interface Interoperation Interface System B

3 Scope Within scope: Ellis-Barker notation IDEF1X notation Information Engineering notation Chen notation Express-G notation UML Class Diagram notation Out of scope: Database schemas Object Role Modelling

4 Ellis-Barker notation ORDER part of made up of PARTY ROLE - number - date cited in reference to made up of reference to reference to part of ORDER LINE - number - cited in PARTY ROLE TYPE - code - cited in PARTY - number - name OTHER ORDER LINE - comment PRODUCT ORDER LINE - quantity cited in for for SERVICE - code - cited in PRODUCT - code -

5 IDEF1X notation includes ORDER-LINE order-line-number order-number (FK) order-line- order-line-type order-line-type includes ORDER order-number order-date parent-order-number (FK) PRODUCT-ORDER-LINE order-line-number order-number (FK) in P PARTY-ROLE party-role-type-code (FK) party-number (FK) order-number (FK) product-order-line-type SERVICE service-code describes in PARTY party-number party-name PARTY-ROLE-TYPE party-role-type-code party-role-type- PRODUCT product-code product-order-line-quantity product-order-line-type service- describes product- describes OTHER-ORDER-LINE order-line-number order-number (FK) other-order-line-comment SERVICE-PRODUCT-ORDER-LINE order-line-number order-number (FK) service-code (FK) PRODUCT-PRODUCT-ORDER-LINE order-line-number order-number (FK) product-code (FK)

6 Information Engineering notation included in includes ORDER PARTY PARTY ROLE TYPE is part of has Number Date references cites references is quoted in Number Name references is quoted in Code Description ORDER LINE Order Number Number Description PARTY ROLE Party Role Type Code Party Number Order Number OTHER ORDER LINE PRODUCT ORDER LINE Order Line Number Order Number Comment Order Line Number Order Number Quantity is for is quoted in SERVICE Code Description is for is quoted in PRODUCT Code Description

7 Chen notation number date code 0 includes n ORDER 1 0 has role as PARTY ROLE TYPE 1 number 0 name contains number n ORDER LINE PARTY comment is a 0 0 quantity is a n describes 1 SERVICE code 1 1 OTHER ORDER LINE PRODUCT ORDER LINE n describes 1 PRODUCT code

8 Express-G notation date_and_time STRING received date number code comprised_of L(0:?) (ABS) order party_order_involvement order_party_involvement S(0:?) S(0:?) party role party STRING name role party_role composite order single order line_items L(1:?) INTEGER STRING number (ABS) order line code other order line comment (ABS) product order line quantity product product order line service product order line ordered_product S(0:?) ordered_service S(0:?) product service STRING code STRING STRING INTEGER

9 UML Class Diagram notation 1..* Composite Order Order number : String receiveddate : Date Single Order Party Role Party number : String name : String Party Role Type code : String : String line items 1..* Order Line number : Integer : String Product code : String : String Product Product Order Line Service code : String : String Other Order Line comment : String Product Order Line quantity : Integer Service Product Order Line

10 The metamodel INFORMATION MODEL comprised of comprised of UNIQUE IDENTIFIER of part of 1..* ENTITY TYPE with instances identified by comprised of ATTRIBUTE of with instances described by values of part of 1..* UNIQUE IDENTIFIER ELEMENT ATTRIBUTE UNIQUE IDENTIFIER ELEMENT role of NON KEY ATTRIBUTE KEY ATTRIBUTE NATIVE KEY ATTRIBUTE category discriminator for 0..1 categorised by assigned with values from constraint on DOMAIN CONTINUOUS DOMAIN ENTITY SPECIALISATION HIERARCHY part of 1..* comprised of ENTITY SUBTYPE use of further of further defined with used as used as RELATIONSHIP END UNIQUE IDENTIFIER ELEMENT FOREIGN KEY ATTRIBUTE DISCRETE DOMAIN role of in sequence forming representation of constrained to ENTITY TYPE ALIAS synonym for known alternatively as for 2..* used as RELATIONSHIP END represented by sequence of mutually exclusive with others in 1..* part of VALID VALUE defined to include RELATIONSHIP END GROUP as viewed from related to others through part of 1..* RELATIONSHIP 2..* comprised of

11 Outstanding issues 1) Is it necessary to distinguish between key and non-key attributes? 2) Can the domain concept be used for data types? 3) Is it necessary to recognise that there are sub-domains? 4) Is it OK to handle UML association classes as intersection entity types? 5) Do we need to be able to recognise sub-types of UML associations? 6) How do we handle the objects and roles of ORM within this metamodel? 7) Which notation should be used for the metamodel? (What are the WG2 standards)? 8) What are the metaclasses in MFI Core and Mapping?

12 Any questions?

13