一种支持MDA的PIM建模方法

为解决MDA开发过程中平台无关模型(PIM)的描述方面存在的问题，从软件体系结构建模出发，通过对UML进行扩展并引入界面展示视图，提出了一种平台无关的Web应用建模方法。该方法保持了PIM平台无关的特性，并能充分利用体系结构在软件开发各阶段间保持的良好可追踪性，能够对模型驱动的软件开发提供有力的支持。以J2EE目标平台为例说明了用该方法建立的PIM模型到平台相关模型(PSM)的转换。     

一种支持MDA的模型转换方法

平台无关模型(PIM)到平台有关模型(PSM)的转换是模型驱动体系结构(MDA)中的关键技术，但目前还没有针对该转换的有效的解决方案。从软件工程的实施出发，以抽象代数理论为基础，同时考虑建模元素的语法结构和语义特性，该文提出了一种基于体系结构映射的、可支持模型间自动转换的方法。该方法充分利用软件体系结构在软件开发各阶段间保持的良好可追踪性，使其同时成为系统分析和模型转换的基础。以J2EE目标平台为例说明了该方法的应用。     

从EDOC的业务过程建模到J2EE应用程序框架的MDA转换

OMG（Object Management Group，对象管理组织）提出的模型驱动架构（MDA，Model Driven Architecture）是解决不同中间件平台之间的集成以及技术升级所引起的问题的软件开发方法。MDA的基本思想是将系统的模型作为软件开发过程的核心制品，并且将模型区分为描述系统业务功能的平台独立模型（PIM，Platform Independent Model）和描述系统在特定技术平台上实现细节的平台相关模型（PSM，Platform Specific Model）。模型转换是MDA开发的核心内客。MDA的开发效率依赖于良好的支撑工具，特别是支持模型转换的工具的涌现。本文介绍一种对业务过程建模并将模型转换成程序代码的设计恩想和实现方法。开发者可以用该工具对企业的业务过程建模。这个工具能将建立的模型自动转换成J2EE平台上的程序代码。     

基于UML的软件体系结构建模方法研究

模型的有效集成是软件系统建模的关键。然而,通常基于UML的软件系统的四个模型中,从用例分析模型到其它设计模型之间存在一条很难逾越的鸿沟。本文通过引入软件体系结构模型,提出了基于UML的软件体系结构建模方法,进一步完善了软件系统的建模。     

基于UML的软件体系结构开发方法

模型间的平稳过渡是软件系统开发的关键。然而,通常基于UML的软件系统的四种模型中,从用例分析模型到其它设计模型之间存在一条很难逾越的鸿沟。本文通过引入软件体系结构模型,提出了基于UML的软件体系结构开发方法,改进了模型间的平稳过渡问题。为了表明这个方法的可用性和有效性,我们陈述了库存管理系统应用的案例研究。     

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

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

Parallel Programming of Multi-processor SoC: A HW–SW Interface Perspective

For the design of classic computers the parallel programming concept is used to abstract HW/SW interfaces during high level specification of application software. The software is then adapted to existing multiprocessor platforms using a low level software layer that implements the programming model. Unlike classic computers, the design of heterogeneous MPSoC includes also building the processors and other kind of hardware components required to execute the software. In this case, the programming model hides both hardware and software refinements. This paper deals with parallel programming models to abstract both hardware and software interfaces in the case of heterogeneous MPSoC design. Different abstraction levels will be needed. For the long term, the use of higher level programming models will open new vistas for optimization and architecture exploration like CPU/RTOS tradeoffs.     

代码走查辅助工具的MDA开发模式

研究和分析了软件代码走查问题域，提取出软件代码走查辅助工具的基本功能。使用模型驱动体系结构方法，结合软件代码走查辅助工具的特点，逐步构建软件代码走查辅助工具的平台无关模型、平台相关模型与代码模型，并对不同模型之间的转换规则进行了初步研究。     

An open platform for developing multiprocessor SoCs

Nanometer technologies integrate hundreds of millions of transistors in a single chip. Opportunities provided by these technologies, combined with the consolidation of platform-based design approaches, the evolution toward multiprocessor architectures, and consideration of the network-on-chip (NoC) paradigm suggest new methods for designing and verifying embedded systems. Clearly, a pure software simulation platform can't provide the performance required for developing multiprocessor system-on-chip (MPSoC) designs. One of the main design risks for today's systems is the architecture, which developers must validate as early as possible in the overall system design cycle because it has the biggest impact on system dimensioning and performance. To solve these problems, we've studied a reconfigurable MPSoC emulation platform and developed the main emulation subsystem and board. A low-cost modular approach that uses emulation offers an alternative to software simulation for the design and verification of complex multiprocessor system-on-chip (MPSoC) designs.     

CHARMY: A Framework for Designing and Verifying Architectural Specifications

Introduced in the early stages of software development, the Charmy framework assists the software architect in making and evaluating architectural choices. Rarely, the software architecture of a system can be established once and forever. Most likely poorly defined and understood architectural constraints and requirements force the software architect to accept ambiguities and move forward to the construction of a suboptimal software architecture. Charmy aims to provide an easy and practical tool for supporting the iterative modeling and evaluation of software architectures. From an UML-based architectural design, an executable prototype is automatically created. Charmy simulation and model checking features help in understanding the functioning of the system and discovering potential inconsistencies of the design. When a satisfactory and stable software architecture is reached, Java code conforming to structural software architecture constraints is automatically generated through suitable transformations. The overall approach is tool supported.     

面向方面软件体系结构建模研究

用面向方面编程思想研究软件体系结构,提取体系结构中的横切属性,并以方面连接件的形式对其进行建模,然后提出基于UML的面向方面体系结构元模型,最后通过图书管理系统实例说明具体建模过程,对传统体系结构模型和面向方面体系结构模型进行比较分析,结果表明了面向方面软件体系结构模型具有更高的实际应用价值.     

Model-Based Verification and Validation of Properties

One of the key issues in software development, like in all engineering problems, is to ensure that the product delivered meets its specification. Verification and validation are well-established techniques for ensuring the quality of a product within the overall software development lifecycle. With models being expressed in the Unified Modeling Language, the application of verification and validation is complicated. Firstly, concerning verification, a UML model is typically not the input language of a verification tool. Secondly, with regards to validation, a UML model is also not directly executable.In this paper, we show how verification and validation can be achieved for UML models. Within our approach, graph transformation techniques are applied for automated translation of UML models into a language understood by a verification tool or directly into an implementation. By the use of such semantic-preserving transformations, both verification and validation can be lifted up to the model level, allowing for a seamless integration of verification and validation into a UML-based development process.     

PKUMoDEL:模型驱动的开发和语言家族支持环境

OMG发布的UML语言家族和MDA架构促进了模型驱动软件开发的思想成为现实.建模语言版本升级或者面向不同领域的语言家族新增成员的不断出现,要求模型驱动开发环境除了使得模型成为软件开发生命周期中的主体之外,还应该具有元模型的定义和操纵能力.模型驱动的开发和语言家族支持环境PKUMoDEL是基于MOF的元建模环境和基于UML2.0的建模环境的集成体,很好地解决了诸如元模型的定义、扩展和评估、建模工具的自适应和演化、不同类型工具之间的集成、模型复用、从模型到运行环境的直接映射和部署等问题.     

基于UML的测试用例生成方法研究

基于模型的软件测试是由软件需求分析模型与设计模型中生成一套测试用例的技术.随着基于UML模型的软件开发与RUP(Rational Unified Process)开发过程的广泛应用,基于UML模型的软件测试逐渐成为基于模型软件测试的主要研究方向.结合UML模型中的测试信息,结合并改进了传统的测试用例生成方法,如场景法、判定表法等,提出了一套较合理的基于UML的测试用例生成方法,使得基于UML的测试用例生成方法的流程更加规范,更加易于生成满足很高覆盖要求的测试用例,并运用实例对其进行了验证.     

基于UML的多视图软件体系结构描述方法研究*

提出一种新的基于UML(unified modeling language)的多视图模型,即“6＋1”视图模型,从场景、概念视图、框架视图、过程视图、数据视图、构件视图、物理视图七个视角完整地描述一个系统的体系结构,并将该视图模型应用到钢材库管理系统的体系结构描述中。实践表明,它是面向对象软件开发方法中高效而实用的软件体系结构建模方法。     

MDA的设想与实现

模型驱动体系结构(MDA)提出了一种利用模型进行软件开发的方法，它将模型作为软件开发过程的关键，MDA的基本思想是将模型区分为平台独立模型(platform independent model)和平台相关模型(platform specific model)，通过不同抽象层次模型之间的转换完成软件开发过程。介绍了MDA的设想，包括MDA的基本概念，基于MDA的开发过程，讨论了实现MDA所涉及的几个重要问题。     

A compiler infrastructure for embedded heterogeneous MPSoCs

Programming heterogeneous MPSoCs (Multi-Processor Systems on Chip) is a grand challenge for embedded SoC providers and users today. In this paper, we argue the need for and significance of positioning the language and tool design from the perspective of practicality to address this challenge. We motivate, describe and justify such a practical design of a compilation framework for heterogeneous MPSoCs targeting the domain of streaming applications, named MAPS (MPSoC Application Programming Studio). MAPS defines a clean, light-weight C language extension to capture streaming programming models. A retargetable source-to-source compiler is developed to provide key capabilities to construct practical compilation frameworks for real-world, complex MPSoC platforms. Our results have shown that MAPS is a promising compiler infrastructure that enables programming of heterogeneous MPSoCs and increases productivity of MPSoC software developers.     

A multi-criteria assessment tool for screening preliminary product platform concepts

Platform concept evaluation is a more challenging task than evaluating a single product concept since a platform must effectively support multiple product variants over a prolonged period of time. Existing platform methods develop specific criteria in depth, yet an evaluation of alternative platforms should be based on a broad set of criteria. Based on expert interviews, personal experience, and a literature search we propose a platform assessment tool consisting of 19 criteria for platform evaluation. The criteria are group into six categories: customer satisfaction, variety, after-sale, organization, flexibility, and complexity. The tool is focused on the early platform architecture phase, before proof-of-concept prototyping. However, it can also be used subsequently for platform refinement when more data becomes available. We demonstrate our platform assessment tool through an example with a cordless drill platform.     

基于模型驱动的软件体系结构

介绍了一种基于模型驱动的软件体系结构。该体系结构将与实现技术无关的功能模型及基于某一特定技术的实现模型分离 ,通过不同模型之间的变换 ,使系统能适应技术的进步 ,解决系统在不同中间件平台上的集成、互操作性、可移植性等问题。此外 ,也讨论了这种体系结构的优缺点及今后需要解决的问题。     

A model-driven approach for the derivation of architectural requirements of software product lines

The alignment of the software architecture and the functional requirements of a system is a demanding task because of the difficulty in tracing design elements to requirements. The four-step rule set (4SRS) is a unified modeling language (UML)-based model-driven method for single system development which provides support to the software architect in this task. This paper presents an evolution of the 4SRS method aimed at software product lines. In particular, we describe how to address the transformation of functional requirements (use cases) into component-based requirements for the product line architecture. The result is a UML-based model-driven method that can be applied in combination with metamodeling tools such as the eclipse modeling framework (EMF) to derive the architecture of software product lines. We present our approach in a practical way and illustrate it with an example. We also discuss how our proposals are related to the work of other authors.