元模型

元模型是关于模型的模型。这是特定领域的模型,定义概念并提供用于创建该领域中的模型的构建元素。例如,可以将 SPEM 视为流程工程元模型。  

四层元模型体系结构

  采用元模型驱动的体系结构对于企业建模有重要价值,它解决了产品数据一致性与企业信息共享问题。元建模理论是从80年代后期发展起来的,虽然起步晚,但发展速度很快。到目前为止,为了不同的目的,已经定义了很多元元模型和元模型,例如最早由 EIA(电子工业协会)定义的CIDF(CASE Data Interchange Format)元元模型,OMG(对象管理组织)定义的MOF(Meta Object Facility)元元模型等。这些元元模型的建立都是以经典的四层元数据体系结构为基础的。  

四层元模型是OMG组织指定的UML的语言体系结构。这种体系结构是精确定义一个复杂模型语义的基础。除此之外,该体系结构具有,通过递归地将语义应用到不同层次上,完成语义结构的定义,为UML的元模型扩展提供体系结构基础,为UML元模型实现与其他的基于四层元模型体系结构的标准相结合提供体系结构基础。  

OMG提出的MOF是一个标准。为了描述某一特定的模型,需要描述组成该类模型的建模结构集,MOF能对建模结构进行描述。MOF的4层元建模架构提供一组建模元素以及使用这些元素的规则[21]。  

典型的元模型结构可以描述为:实例层、模型层、元模型层和元元模型层。每一层描述如下[22]:  

1.信息层(information layer)  信息是由我们希望描述的数据组成,这些数据通常是一些用户数据(user data),主要职责是描述信息领域中的详细信息。  

2.模型层(model layer)  模型层是由元数据组成,元数据是描述信息层的数据,元数据的集合被称作为模型。  模型层的主要职责是为描述信息层而定义的一种“抽象语言”(即没有具体语法或符号的语言)。信息层的数据,即用户数据,是模型层的一个实例。  

3.元模型层(metamodel layer)  元模型层是由元一元数据组成,元一元数据定义了元数据的结构和语义,元一元数据的集合被称作为元模型。元模型层的主要职责是为了描述模型层而定义的一种“抽象语言”,是对模型层的进一步抽象。也就是说,模型层描述的内容通常要比元模型层描述的内容丰富、详细。一个模型是元模型的一个实例。数据词典中的元数据是对数据模型的描述[23]。  

4.元元模型层(meta-metamodel layer)  元元模型层是由元元数据的结构和语义的描述组成,这层的主要职责是为了描述元模型而定义的一种 “抽象语言”。元元模型的定义要比元模型更加抽象、简洁。一个元元模型可以定义多个元模型,而每个元模型也可以与多个元元模型相关联。通常所说的相关联的元模型和元元模型共享同一个设计原理和构造,这也不是绝对的准则。每一层都需要维护自己设计的完整性。一个元模型是元元模型的一个实例。  

下图进一步说明了四层元数据体系结构:该图只给出了一个模型和一个元模型作为例子。四层元模型的目的是为了支持多个模型和多个元模型。

  • 1
    点赞
  • 4
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 0
    评论
Ontology Definition Metamodel V1.1.pdf There are several compliance points distinguished for the Ontology Definition Metamodel. These include: 1. None or Not Compliant, meaning that the application in question is not compliant with a particular metamodel, as defined by the metamodel itself, the abstract syntax, well-formedness rules, semantics, and notation specified for a particular package or set of packages. 2. Compliant, meaning that the implementation fully complies with the abstract syntax, well-formedness rules, semantics and notation of a particular package or set of packages. 3. Interchange, indicating that the implementation provides compliance as specified in [2], and can exchange metamodel instances using ODM package conformant XMI. There are several possible entry points for implementations that want to provide/claim minimal compliance with the ODM. These require compliance with one of the following base metamodel packages: • RDFBase Metamodel Package (RDFBase is a sub package of the Resource Description Framework (RDF) Metamodel Package). • Topic Maps (TM) Metamodel Package. • Common Logic (CL) Metamodel Package. For a given implementation to claim ODM compliance, it must be Compliant, as defined in 2, above, with one of these three packages. There are several compliance options available to vendors for the RDF Metamodel Package. These include: • RDFBase Only - as implied above, this package contains the set of elements requ ired for core RDF support, such as is necessary to support a triple store implementation; the focu s here is on the set of constructs defined in the RDF Concepts and Abstract Syntax [RDF Concepts] document. • RDFBase + RDFWeb - provides core RDF support and fits these concepts to the World Wide Web. • RDFBase + RDFS - moves the implementation focus from core RDF to RDF Schema, as specified in [RDF Schema]. • RDF - meaning, the implementation supports all of the concepts defined in the three sub packages, which represents RDF Schema fitted to the Web. There are two possible compliance points for the OWL Metamodel Package. Each of these requires support for the entire RDF package, including the RDFWeb component. They include: • OWLBase + OWLDL - focus is on a description logics application that constrains an ontology in turn for DL decidability. • OWLBase + OWLFull - focus is on more expressive applications rather than on decidability of entailment. The complete set of ODM compliance options is summarized in Table 2.1.
Architecture-driven Modernization Abstract Syntax Tree Metamodel (ASTM) V1.pdf The purpose of the ASTM is to provide a framework that allows tool vendors and tool clients to build and use tools that conform to commonly agreed upon modeling specifications for the interchange of abstract syntax models of software. Interoperability is achieved when models can be interchanged using modeling elements that conform to those specified in the ASTM specification. The internal proprietary models of tools need not conform the ASTM for a tool to be considered compliant with the ASTM. To be considered compliant a tool need only adhere to the ASTM as a model interchange specification. Tool conformance is concerned solely with the ability of tools to interchange models that conform to the ASTM. • For a GAST model to conform with the ASTM it must conform to the GAST Metamodel provided by this specification. • For a SAST model to conform to the ASTM it must conform to both the GASTM model provided with this specification as well as the SASTM model provided by some future SASTM specification. The ASTM is a bi-dimension multi-layered modeling specification. The two dimensions of the ASTM define both syntactic as well as the semantic properties of software. The layers of the ASTM define a core set of modeling elements, the GASTM, that are common to many programming languages as well as a set of extensions, the SASTMs, that extend from the core for and are used in concert with the GASTM for defining models specialized to particular programming languages. Table 2.1 illustrates the Compliance Points of the ASTM.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

在键盘上跳舞

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值