一种模型驱动的工作流过程定义途径

传统的工作流管理系统在互操作性,可复用性,可移植性和开发效率等方面遇到了挑战,MDA是解决上述挑战和问题的一种途径。在模型驱动的工作流管理系统中,工作流模型处于核心地位,本文首先给出了扩展的工作流元模型和基于Petri网的形式化工作流模型过程网。其次,运用模型驱动的途径,依据给出的工作流模型,本文提出了一种模型驱动的,用于快速构造工作流管理系统的框架。针对工作流过程模型,着重讨论了从基于EPC的过程CIM到基于过程网的过程PIM的转换（转换过程和转换规则）,并以扩展的Petri网标注语言E-PNML规约了过程PIM。     

基于MDA的PIM到J2EE平台PSM的转换方法

MDA是解决基于不同中间件系统的集成问题。它将不同的系统都结构化成PIM和PSM并针对不同实现技术与平台制订多个映射规则,然后通过这些映射规则及辅助工具将PIM转换成PSM,再将PSM不断求精直至形成最后代码。MDA中的模型转换有4种：PIM到PIM,PIM到PSM,PSM到PSM以及PSM到PIM。其中的PIM到PSM转换是难点。本文提出了一种PIM到J2EE平台的PSM转换的方法：首先将一个用PIM配置图和类图描述的系统根据映射规则转换成J2EE平台下的PSM配置图、类图;然后根据精化规则对PSM模型进一步精化,生成不同的EJB以及构件图,为最后代码的自动生成打下基础。     

基于MDA的UML模型转换:从功能模型到实现模型

MDA（Model Drive Architecture）是OMG（Object Management Group）提出的解决系统集成问题的新途径,它以UML、MOF、CWM为核心,定义软件开发过程中的模型组织管理框架。本文探讨了MDA框架下在元模型层定义模型转换的方法。引入模型转换规则描述语言,给出模型转换规则应遵循的部分原则。以CORBA平台为例说明在元模型层用既定语言定义模型转换规则,从功能模型到实现模型的模型转换方法。基于以上方法构建相应的工具原型。     

模型转换过程中的映射发现方法

基于本体的计算无关模型到平台无关模型的转换过程,分为元本体映射规则的发现以及基于元本体映射规则的转换执行这2个部分,其中,映射发现是转换实现的基础。为此,提出一种映射发现方法以进行模型转换。该方法在已知计算无关模型和平台无关模型的元模型基础上,抽取各自的元本体,结合基于相似度的本体映射技术建立2种模型的元本体映射关系,并作为模型转换语义匹配推理的基础。通过实例验证该方法的可行性和实用性。     

MDA中PIM到PSM变换规则的研究

在MDA开发模式中,将模型分为PIM(平台独立模型)和PSM(平台相关模型),其目的在于通过一定的变换规则实现PIM到PSM的自动转换,从而可以方便地生成应用程序代码以及测试框架。要实现PIM到PSM的自动转换,关键在于变换规则的精确定义。本文对变换规则提出了一种形式化的定义,并结合特定的PSM给出了一个具体的转换实例,最后给出在此基础上设计的平台的实践结果。     

A complete approach for CIM modelling and model formalising

ContextComputation Independent Model (CIM) as a business model describes the requirements and environment of a business system and instructs the designing and development; it is a key to influencing software success. Although many studies currently focus on model driven development (MDD); those researches, to a large extent, study the PIM-level and PSM-level model, and few have dealt with CIM-level modelling for case in which the requirements are unclear or incomplete.ObjectiveThis paper proposes a CIM-level modelling approach, which applies a stepwise refinement approach to modelling the CIM-level model starting from a high-level goal model to a lower-level business process model. A key advantage of our approach is the combination of the requirement model with the business model, which helps software engineers to define business models exactly for cases in which the requirements are unclear or incomplete.MethodThis paper, based on the model driven approach, proposes a set of models at the CIM-level and model transformations to connect these models. Accordingly, the formalisation approach of this paper involves formalising the goal model using the category theory and the scenario model and business process model using Petri nets.ResultsWe have defined a set of metamodels and transformation rules making it possible to obtain automatically a scenario model from the goal model and a business process model from the scenario model. At the same time, we have defined a mapping rule to formalise these models. Our proposed CIM modelling approach and formalisation approach are implemented with an MDA tool, and it has been empirically validated by a travel agency case study.ConclusionThis study shows how a CIM modelling approach helps to build a complete and consistent model at the CIM level for cases in which the requirements are unclear or incomplete in advance.     

基于ASP.NET三层架构的MDA模型变换

MDA构建了PIM和PSM,定义了模型间的自动映射,这种映射即模型变换。模型变换分为模型到模型的变换和模型到代码的变换两大类。本文通过分析基于ASP.NET的三层架构,构建MDA框架,定义模型变换规则,组成模型变换定义,实现模型间的变换。     

Applying KADS to KADS: knowledge-based guidance for knowledge engineering

Abstract: The KADS methodology (Schreiber et al. 1993; Tansley & Hayball 1993) and its successor, CommonKADS (Wielinga et al. 1992) have proved to be very useful approaches for modelling the various transformations involved between eliciting knowledge from an expert and encoding this knowledge in a computer program. These transformations are represented in a series of models. While it is widely agreed that these methods are excellent approaches from a theoretical viewpoint, the documentation provided concentrates on defining what models should be produced, with only general guidance on how the models should be produced. This has the advantage of making KADS and CommonKADS widely applicable, but it also means that considerable training and experience is required to become proficient in them. This paper reviews three projects that investigated the feasibility of producing specific guidance for certain decisions which are required when using KADS or CommonKADS to develop a knowledge-based system. Guidance was produced for the identification of the generic task addressed by a knowledge-based system; for the selection of appropriate AI techniques for implementing the analysed knowledge; and for selecting a suitable tool for implementing the system. Each set of guidance was encoded in its own knowledge-based system, which was itself developed with the assistance of KADS or CommonKADS. These projects therefore both studied and applied KADS and CommonKADS in order to produce knowledge-based guidance for knowledge engineers. The projects showed that it was feasible to produce heuristic guidance which could be understood, applied and occasionally overridden by knowledge engineers. The guidance provides reasonably experienced knowledge engineers with a framework for making the key decisions required by CommonKADS, in the same way that CommonKADS provides knowledge engineers with a framework for representing knowledge. The projects also produced some new insights about CommonKADS domain modelling and about the process of task identification.     

基于MDA的UML模型转换技术——从顺序图到状态图

为了实现不同中间件平台之间的集成和互操作,OMG提出了一个标准的基于模型的体系结构:MDA。MDA将应用模型划分成与平台无关的模型(PIM)和与平台有关的模型(PSM),并定义了PIM和PSM之间的4种映射关系。该文主要对PIM到PIM之间的映射进行了研究。该映射实质上是PIM模型的精化,其主要方面是分析模型和设计模型之间的转换。MDA使用UML来描述各种模型。UML是一种可视化的通用的面向对象的建模语言。UML顺序图主要用于需求分析,而状态图在系统设计阶段起重要作用。该文介绍了一种从UML顺序图中合成状态图的方法,合成的过程基本上是自动完成的,只需要很少的用户交互,从而为PIM模型的精化提供有力的支持。     

基于MDA的设计模式建模与模型转换

MDA(model driven architecture)的一个重要意图是将模型作为软件开发的基本单元,以进一步提高软件开发的抽象层次.为此,MDA划分了3种抽象级的模型,并通过建立高抽象级的模型和向低抽象级模型及代码的转换来构造可运行的应用程序.在MDA的框架下,将设计模式作为一种独立的建模和转换单元能够在较高的抽象层次上充分支持复用并提高建模粒度,从而进一步发挥设计模式的优点,提高软件开发效率、降低生产成本.然而,要在MDA的框架下将设计模式作为完整的开发单元来使用,必须解决以模式为单元的建模及转换两个具体问题.针对单元化模式建模的问题,通过扩展MOF(meta object facility)的方式定义了模式单元元模型,并提供了基于此元模型的单元化建模支撑机制,以分离业务模型与模式模型的方式解决了该问题.针对单元化模式模型转换问题,在模式单元元模型的基础上定义了向EJB平台的转换规则.该转换规则使用QVT标准描述,支持单元化的模式模型转换,并具有良好的复用性.     

模型驱动体系结构MDA的实例研究--病人观察系统的PIM模型建立和PIM到关系PSM模型转换

MDA是解决基于不同中间件系统的集成问题,它将不同的系统都结构化成PIM和PSM,并针对不同实现技术与平台制订多个映射规则,然后通过这些映射规则及辅助工具将PIM转换成PSM.本文应用MDA对病人观察系统进行PIM建模,并提出了一种PIM到关系数据库PSM的转换方法.     

Web平台无关模型到J2EE平台模型的转换

平台无关模型到平台相关模型的转换是OMG提出的模型驱动架构（MDA）中的关键技术。综合当前J2EE平台下广泛使用的多种应用框架，提出了一种包括静态模型、行为模型和展示模型3个部分的J2EE平台相关模型，将其作为目标模型并按结构定义、映射规则实现模型转换。该文描述了一种Web平台无关模型到J2EE平台模型的转换，体现了模型驱动开发的优点，提升了开发层次，由于受目标应用领域和特定技术对该模型限制较小，因此其具有较好的通用性。     

Model mapping using formalism extensions

The Object Management Group's model driven architecture defines a system development approach that formally separates system specification from platform implementations - in platform-independent models and platform-specific models, respectively. According to MDA, software development involves a sequence of model mappings that transform an initial PIM to a final PSM that is precise enough for direct translation into an executable program. A mapping is a set of rules and techniques for translating one model into another. When the starting and final models are expressed in the same formalism, the mapping is said to be intralanguage; otherwise, it is interlanguage. We focus here on interlanguage mapping, showing the central role of formalism extension mechanisms in managing the abstraction-level gap between languages as well as the platform-level details of specific implementations.     

一个MDA支撑工具的设计与实现

MDA是OMG提出的用于解决中间件集成问题的软件开发方法。MDA开发方法以系统模型作为软件开发的主线。在这样的开发过程中,强有力的模型转换支撑工具是MDA思想能够得到广泛应用的关键。而从平台无关模型PIM到平台相关模型PSM的转换工具尤其重要。描述了一个从PIM自动转换到PSM的工具的设计思想。工具使用EDOC profile的一个子集作为PIM的描述方法,使用J2EE作为目标平台。基于一组从PIM到J2EE平台上软件模型的转换规则,工具实现了从PIM到J2EE平台上的PSM的自动转换。     

User interfaces metamodel based on graphs

Information systems are widely used in all business areas. These systems typically integrate a set of functionalities that implement business rules and maintain databases. Users interact with these systems and use these features through user interfaces (UI). Each UI is usually composed of menus where the user can select the desired functionality, thus accessing a new UI that corresponds to the desired feature. Hence, a system normally contains multiple UIs. However, keeping consistency between these UIs of a system from a visual (organisation, component style, etc.) and behavioral perspective is usually difficult. This problem also appears in software production lines, where it would be desirable to have patterns to guide the construction and maintenance of UIs. One possible way of defining such patterns is to use model-driven engineering (MDE). In MDE, models are defined at different levels, where the bottom level is called a metamodel. The metamodel determines the main characteristics of the models of the upper levels, serving as a guideline. Each new level must adhere to the rules defined by the lower levels. This way, if anything changes in a lower level, these changes are propagated to the levels above it. The goal of this work is to define and validate a metamodel that allows the modeling of UIs of software systems, thus allowing the definition of patterns of interface and supporting system evolution. To build this metamodel, we use a graph structure. This choice is due to the fact that a UI can be easily represented as a graph, where each UI component is a vertex and edges represent dependencies between these components. Moreover, graph theory provides support for a great number of operations and transformations that can be useful for UIs. The metamodel was defined based on the investigation of patterns that occur in UIs. We used a sample of information systems containing different types of UIs to obtain such patterns. To validate the metamodel, we built the complete UI models of one new system and of four existing real systems. This shows not only the expressive power of the metamodel, but also its versatility, since our validation was conducted using different types of systems (a desktop system, a web system, mobile system, and a multiplatform system). Moreover, it also demonstrated that the proposed approach can be used not only to build new models, but also to describe existing ones (by reverse engineering).     

一种结合MDA的高阶模型转换方法

模型转换是MDA的关键技术,也是MDA的研究热点。目前,不同的MDA开发平台都有一套相对独立的开发技术和转换框架,这使平台之间缺乏兼容性,模型转换代码重用困难。究其原因是缺少一种与具体转换语言相对应,且与平台无关的转换规则模型。为了解决以上问题,将高阶模型转换的思想与模型驱动软件开发相结合,提出了一种构造模型转换规则的高阶转换元模型,并以ATL语言为例展示了高阶转换元模型的使用方法;最后通过一个实例验证了该方法的可行性和可用性。该方法提高了模型转换语言的抽象层次,降低了模型转换语言的重用难度,在一定程度上解决了模型转换技术不兼容的问题。     

Manufacturing Data Analysis in Internet of Things/Internet of Data (IoT/IoD) Scenario

ABSTRACT

Computer integrated manufacturing (CIM) has enormous benefits as it increases the rate of production, reduces errors and production waste, and streamlines manufacturing sub-systems. However, there are some new challenges related to CIM operating in the Internet of Things/Internet of Data (IoT/IoD) scenarios associated with Industry 4.0 and cyber-physical systems. The main challenge is to deal with the massive volume of data flowing between various CIM components functioning in virtual settings of IoT. This paper proposes decisional DNA-based knowledge representation framework to manage the storage, analysis, and processing of data, information, and knowledge of a typical CIM. The framework utilizes the concept of virtual engineering object and virtual engineering process for developing knowledge models of various CIM components such as automatic storage and retrieval systems, automatic guided vehicles, robots, and numerically controlled machines. The proposed model is capable of capturing in real time the manufacturing data, information and knowledge at every stage of production, that is, at the object level, the process level, and at the factory level. The significance of this study is that it will support decision-making by reusing the experience, which will not only help in effective real-time data monitoring and processing, but also make CIM system intelligent and ready to function in the virtual Industry 4.0 environment.     

基于软件模式的PIM到PSM的模型变换

模型驱动体系结构(MDA)是一种以模型为中心的新的软件开发模式。MDA的基本思想是将模型主要分为平台无关模型(PIM)和平台相关模型(PSM),然后通过变换规则实现PIM到PSM的变换。文中将软件模式的概念引入到PIM到PSM模型变换中,从而提高模型变换效率和降低模型变换出错率。同时,设计了基于软件模式的PIM到PSM的模型变换方法的框架。     

模型驱动的测试用例自动生成框架

提出一个基于模型驱动架构(MDA)的测试用例生成框架,其中,平台无关的系统模型通过水平转换成平台无关的测试模型,平台无关的测试模型通过竖直转换生成相应的测试用例。利用MDA转换工具ATL和MOFScript制定相应的转换规则作用于元模型,使测试者只须提供源模型和测试数据即可生成相应的测试用例。