《GEIA-EIA-IS-114-1996.pdf》由会员分享,可在线阅读,更多相关《GEIA-EIA-IS-114-1996.pdf(261页珍藏版)》请在三一文库上搜索。
1、Interim Standard . EIMS-114 . . . . . CASE Data Interchange Format A Division of Electronic Industrie Association . . ,.:.:. . .; . . . . :. . . . . . . . . CDIF Integrated Meta-model Data Modeling Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . : : . . . . Decem
2、ber 1996 . . . . . . . . . . Electronic Industries Association CDIF Technical Committee . . . . . . . . . . . . . . . . :$ . : . . . . . . . . Copyright Government Electronics the first letter of each word is upper-case, the rest are lower-case. These names are shown in italic (e.g., MetaAttribute,
3、AttributeDerivation, IsDrawnUsing, Isoptional) The names of objects and values for meta-attributes that appear in examples and instance diagrams are shown in bold italic (e.g., Cwtumer, True, 100) Full details of the CDIF Graphical Notation used in the Meta-model and Meta-meta-model can be found in
4、EWIS-IO7 CDIF - Framework for Modeling and Extensibility. A summary of the major concepts is given in Section 3.2.3, Diagram(s). - Introduction Copyright Government Electronics all names indented below a given name are subtypes of that meta-object. For example, if Car and Truck are both subtypes of
5、Vehicle, this would be shown as follows: Vehicle Cm Truck A meta-entity or meta-relationship and all its subtypes can be duplicated in the hierarchy due to multiple inheritance. Where this occurs, the duplicate entries are shown in italics. The overall AttributableMetaObject supertype, Rootobject, d
6、efined in EWIS-II I CDIF - Integrated Meta-rnodel- Foundation Subject Area, is shown at the top of the hierarchy. Where a page break occurs in the list, all the supertypes of the first meta-entity or meta- relationship on the new page are repeated for clarity with a shaded background. 3.2.5 MetaEnti
7、ty and MetaRelationship Summaries Summaries are given of all the meta-entities and meta-relationships used in the Subject Area. The meta-entity definitions are given first, in alphabetical order, followed by the meta- relationship definitions, also in alphabetical order. For each meta-entity used in
8、 the subject area, all the meta-attributes, both inherited and local, are listed. The inherited meta-attributes are shown first, in italics, sequenced alphabetically within parent meta-entity. The local meta-attributes are then listed alphabetically in normal font. The optionality, whether mandatory
9、 or optional, of each meta-attribute is given. For each meta-relationship all the meta-attributes are listed sequenced alphabetically. Inherited and local meta-attributes are shown in the same way as for meta-entities. The optionality of each meta-attribute is given. Structure of Subject Area Defini
10、tion Copyright Government Electronics both meta-entity and meta-relationship definitions follow the same layout as that defined for the Subject Area Detailed Definitions section. Structure of Subject Area Defmition Copyright Government Electronics clear keys are foreign keys and indented items are k
11、ey components. For example, Figure 5 reads, “Orders have a primary key called Order-Key that consists of a foreign key called CuscFkey and an attribute OrderNo. CusLFkey consists of a single attribute called CustomrNo.“ 4.1.2 Entities The concept of an “Entity,“ or object to be modeled, is represent
12、ed directly by the meta-entity called Entity. A relational “Table“ is also represented by Entity. A Table is a more concrete representation of an Entity. Subject Area Overview Copyright Government Electronics in a ternary relationship there are three roles (Figure 7); and in an n-ary relationship th
13、ere are “n“ roles. In Figure 10, Order plays the role of set and Lineltem plays the role of member. I Role Role LineItem set member Order t Relationship Figure 10 Roles The object playing a role in the relationship is represented by DataModelObject. The DutaModelObject can be another Relationship, a
14、n Entity or a Cluster. A relationship must have at least two roles to be meaningful (a binary relationship). Incomplete relationship definitions are not supported. The same DatuModelObject can play both (binary) or many (n-ary) Roles in a Relationship as depicted in Figure 1 I. This is called a “Ref
15、lexive“ or “Recursive“ relationship. In this example, the relationship being modeled is that of a Person managing another Person. However, each Person instance plays only one role w i t h respect to another Person instance - either taking the role of Manager or that of Subordinate. Subject Area Over
16、view Copyright Government Electronics cardinality values are properties of the RoZePZayer meta-entity, and thus in this case the RoZePZayers called ServiceProvider and reference both contain the same cardinality values. Subject Area Overview Copyright Government Electronics the Data Definition subje
17、ct area is used to describe this. The connections between the Data Modeling subject area and the Data Definition (see EWIS-113 CDIF - Integrated Meta-model- Data DeJinition Subject Area) subject area is shown in Figure 46. Roles, RolePlayers, and Relationships may also have attributes defined for th
18、em using the meta- relationship DeJinitionObject. Contains. Componentobject. Figure 2 l illustrates the use of each of these. This models how an Employee is recruited by a Company. The Relationship called Recruited has an Attribute of ApprovedBy. Sometimes the services of a Recruiter are used and so
19、metimes an existing Employee refers someone. In the case of the former the RolePlayer called serviceProvfer is paid a Fee and the RolePlayer called reference is paid a Bonus. Subject Area Overview Copyright Government Electronics the foreign key is simply composed of the RolePluyer reference. Figure
20、 23 illustrates this where Employee-FKq in Software is described by the RolePluyer version and Employee-FKq in Hardware is described by the RolePlayer model. This means that both Hardware and Software are not described by the attribute Name that is the description of the primary key in Employee. Sub
21、ject Area Overview Copyright Government Electronics Tota I !, I , 1 Lineltem =sum(Totai) I /Onkrn IsRojectionOf Projected Attribute Figure 39 Instance Diagram showing Complex Projection A full projection, such as the “select *I1 i n SQL is provided by the meta-relationship IsConstnictedWith / Projec
22、tion I J Aitribute Attribute Name Number I ProjectionComponent. IsFullProjectionOJDefiPiitionObject. -This provides the capbility to fully project a DeJnitionObject i n terms of its currenty defined Attributes, without the need to enumerate them. Subject Area Overview Copyright Government Electronic
23、s others are defined in Section 6. Subject Area Overview Copyright Government Electronics others are defined i n Section 6. Subject Area Overview Copyright Government Electronics this indicates that the component of the table is optional. USAGE . For example, w i t h i n a relational database enviro
24、nment, ALIASES . CONSTRAINTS Isoptional shall not be specified w i t h a value of TRUE DATATYPE . Boolean DOMAIN . LENGTH . ISOPTIONAL . True when a value is supplied for Defaultvalue. META-ATTRIBUTE NAME . Name CDIFM,ETAIDENTIFIER 2 1 DESCRIPTION . This is the name ofthe Attribute, which may be dis
25、tinct USAGE . CONSTRAINTS DATATYPE . String DOMAIN. LENGTH . 256 ISOPTIONAL . True from the name of the underlying data type of the Attribute. ALIASES . Meta-entity Definition - Attribute Copyright Government Electronics (meta-attribute IsPrimary). with ForeignKeys provides referential integrity. US
26、AGE . It is used as the basis of normalization and in conjunction ALIASES . CONSTRAINTS TYPE Characteric INHERITED META-AITRIBUTES CDIFIdenti fier Datecreated Dateupdated Timecreated TimeUpdated BriefDescription FullDescription Name SpecificationLanguage SpecificationText f i o m Rootobject f r o m
27、Rootobject f i o m Rootobject f r o m Rootobject fiom Rootobject not in this SA not in this SA , notinthisSA not in this SA not i n this SA from SemanticInformationObject in this SA from SemanticInfoxmationObject in this SA from Key f r o m Key from Key i n this SA in this SA in this SA LOCAL META-A
28、TTRIBUTES IsPrimary Meta-entity Definition - CandidateKey Copyright Government Electronics they are used to resolve many-to-many relationships et al. Entity instances cannot exist withoui the existence of instances of the related entity types. Le. a Key that is a CandidateKey in one Entity that is i
29、nstantiated in another related Entity is called a ForeignKey. USAGE . This provides the mechanism for implementing referential integrity between two Entities (or the same Entity using a reflexive relationship). ALIASES . TYPE Characteristic CONSTRAINTS INHERITED SU ETA-ATTRIBUTES CDIFIdentifier Date
30、created Dateupdated Timecreated Timeupdated BrieDescription FullDescription Name SpecificationLanguage SpecificationText the objects shall be classified as one of the subtypes. Kernel INHERITED META-ATlRIBUTES CDIFIdentifier f i o m Rootobject not in this SA Datecreated f i o m Rootobject not in thi
31、s SA Dateupdated fiom Rootobject not in this SA Timecreated f i o m Rootobject not in this SA Timeupdated from Rootobject not in this SA BriefDescription f i o m SemanticInformationObject in this SA FullDescription f i o m SemanticInfonnationObject in this SA LOCAL META-ATTRIBUTES Is Abstract _ Meta
32、-entity Definition - inheritableDaaModelObject Copyright Government Electronics TYPE Characteristic the objects shall be classified as one of the subtypes. INHERITED META-ATTRIBUTES CDIFIdentifier fiom Rootobject Datecreated fiom Rootobject Dateupdated from Rootobject Timecreated f i o m Rootobject
33、Timeupdated fiom Rootobject not in this SA not in this SA not in this SA not in this SA not in this SA BriefDescription f i o m SemanticInfonnationObject in this SA FullDescription fiom SemanticIdormationObject in this SA . . LOCAL WTA-ATTRIBUTES Name SpecificationLanguag e SpecificationText 1“ERITE
34、D META-RELATIONSHIPS Meta-entity Definition - Key Copyright Government Electronics this is ALIASES . DOMAIN . LENGTH . 256 ISOPTIONAL . True considered to be the name of the group. CONSTRAINTS DATATYPE . string Meta-entity Definition - Roleconstraint Copyright Government Electronics the list is clos
35、ed. If it has the value FASE, new subtypes may be defined; the list is open. USAGE . ALIASES . CONSTRAINTS DATATYPE . Boolean DOMAIN . LENGTH . ISOPTIONAL . True Meta-entity Definition - SubtypeSet Copyright Government Electronics RootEntity.IsRe1atedTo.RootEntity not i n this SA subtype set) in whi
36、ch it is a member. InheritableDataModelObject. IsSupertypeForSubsypeSet) to provide subtypes or subtype sets for InheritableDataModelObjects. Subtype sets are orthogonal. ALIASES . CONSTRAINTS INHERITED META-ATTRIBUTES not in this SA not in this SA CDIFIdentifier from Rootobject Datecreated from Roo
37、tobject DteUpClateCl from Rootobject not in this SA Timecreated from Rootobject not in this SA TimeUpate f r o m Rootobject not in this SA LOCAL META-ATTRIBUTES SpecificationLanguage S pecificationText StoreWithSupertype Meta-relationship Definition - hheritableDataModelObject.IsSubtypeln.SubtypeSet
38、 Copyright Government Electronics they may be derived f r o m other sources, such as system functions. hJHEFUTED META-ATTRIBUTES CDIFIdentifier f i o m Rootobject Datecreated f i o m Rootobject DateUpdated from Rootobject Timecreated f i o m Rootobject Timeupdated f i o m Rootobject not in this SA .
39、 notiathisSA not in this SA not in this SA not in this SA LOCAL META-ATTRIBUTES Meta-relationship Definition - ProjecteAttribute.IsProjectionOf.Attribute Copyright Government Electronics all the RoIePIayers and RoleConstrants contained in a single RoleConstraint are related in the manner defined by
40、the Operator value of the owning RoIeConstraint. groups. USAGE . This allows complex nesting and overlapping of constraint ALIASES . CONSTRAINTS INHERITED META-A“RIBUTES CDIFIdentifier from Rootobject Datecreated from Rootobject Dateupdated from Rootobject Timecreated from Rootobject Timeupdated fro
41、m Rootobject not in this SA not in this SA not in this SA not in this SA not in this SA LOCAL META-ATTRIEJUTES Meta-relationship Defmition - RoleConstraint.incorporates.Ro1eConstraint Copyright Government Electronics all the Roles and RoleConsraints contained i n a single RoleConsraint are related i
42、 n the manner defined by the Operator value of the containing RoleConsraint. MINSOURCECARD . 0 USAGE . Mutually exclusive relationships are an example of a simple ALIASES . constraint group. C0NS“TS INHERITED MF.“A-A?TRIBUTES CDIFIdentifier f i o m Rootobject Datecreated f i o m Rootobject Dateupdat
43、ed f i o m Rootobject Timecreated fiom Rootobject Timeupdated fiorn Rootobject not i n this SA not in this SA not in this SA not i n this SA not i n this SA LOCAL META-ATTRIBUTES Meta-relationship Dehition - RoleConstraint.incorporates.RolePlayer Copyright Government Electronics SUBTYPEOF . RootEint
44、ity.1sRelatedTo.RootEntty not in this SA RoleConstraint.Incorporates.Ro1eConstraint MAXSOURCECARD N RoleConstraint containment. groups comprised of heterogeneous components - RoleConstraints and RolePlayers. the objects shall be classified as one of the subtypes. INHERITED META-ATMUBUTES CDIFIdentif
45、ier from Rootobject Datecreated from Rootobject DateUpated fiom Rootobject Timecreated from Rootobject TimeUpated fiom Rootobject not in this SA not in this SA not in this SA not in this SA not in this SA LOCAL META-ATIRBUTES Meta-relationship Definition - RoleConstraint.incorporates.Semanticuiforma
46、tionObject Copyright Government Electronics no information is given where there is no value defined. A2. Details of Example Figure AI shows a simple Entity-Relationship-Attribute diagram. The information content of the resulting CDIF Transfer File for the semantics covered in the example is then giv
47、en in the next section. 1 This appendix is not a formal part of the attached EM Standard but i s included for the purposes of information only. - Appendix A - Example Copyright Government Electronics there are no local atibutes on CarRetenton and Single Account Transaction. Table Al Attribute List f
48、or Example rrausaction Transactiodd TransactionDate TransactionTime Customer Account Accound CustAccountType CurrentBalance ransfer Amount Appendix A - Example Copyright Government Electronics .ENTlO Meta-relationship . 1nheritableDataModelObject.IsSubtypeIn.SubtypeSet Meta-attributes CDIFIdentifier
49、 RELID52 SourceEnti ENTO8 DestinationEntity . ENTlO . Meta-relationship . InheritableDataModelO bject.IsSubtypeIn.SubtypeSet Meta-attributes CDIFIdentifier L53 SourceEntity .ENTO9 DestinationEntity . ENTlO A3.4 Relationships There are two relationships defined in the data model. The relationship called Carried Out has two roles, and the relationship called Movement has three roles. First, the relationship called Carried Out is defined, and related to the data model. Meta-en tity. . Relation
链接地址:https://www.31doc.com/p-3764939.html