面向对象软件开发过程中演化阶段的分类法

从逻辑设计的角度,研究了一种分类方法,用于对面向对象软件系统的演化过程进行分类.该方法基于UML区分算法,将系统的一系列相邻版本的源代码所对应的逻辑设计UML类模型进行比较,产生一组描述两个版本之间结构层面上所发生修改的变化记录.从系统中每一个独立的类的角度进行分析,为每一个类生成一个演化雏形.使用该分类方法将每个类的演化雏形高层次地抽象为若干独立的演化阶段.     

UML状态图切片系统的设计与实现

UMI．状态图切片系统是一个基于C＋＋程序UML状态图的切片生成系统。系统生成的LrML状态图切片可应用于C＋＋程序的测试、回归测试、排错、维护等方面。文章主要介绍UML状态图切片系统的设计思想、系统的结构、工作原理以及系统实现的重要技术细节。     

Decorating tokens to facilitate recognition of ambiguous language constructs

Software tools are fundamental to the comprehension, analysis, testing and debugging of application systems. A necessary first step in the development of many tools is the construction of a parser front‐end that can recognize the implementation language of the system under development. In this paper, we describe our use of token decoration to facilitate recognition of ambiguous language constructs. We apply our approach to the C++ language since its grammar is replete with ambiguous derivations such as the declaration/expression and template‐declaration/expression ambiguity. We describe our implementation of a parser front‐end for C++, keystone, and we describe our results in decorating tokens for our test suite including the examples from Clause Three of the C++ standard. We are currently exploiting the keystone front‐end to develop a taxonomy for implementation‐based class testing and to reverse‐engineer Unified Modeling Language (UML) class diagrams. Copyright © 2002 John Wiley & Sons, Ltd.     

DSMDiff: a differentiation tool for domain-specific models

Model differentiation techniques, which provide the capability to identify mappings and differences between models, are essential to many model development and management practices. There has been initial research toward model differentiation applied to Unified Modeling Language (UML) diagrams, but differentiation of domain-specific models has not been explored deeply in the modeling community. Traditional modeling practice using the UML relies on a single fixed general-purpose language (i.e., all UML diagrams conform to a single metamodel). In contrast, Domain-Specific Modeling (DSM) is an emerging model-driven paradigm in which multiple metamodels are used to define various modeling languages that represent the key concepts and abstractions for particular domains. Therefore, domain-specific models may conform to various metamodels, which requires model differentiation algorithms be metamodel-independent and able to apply to multiple domain-specific modeling languages. This paper presents metamodel-independent algorithms and associated tools for detecting mappings and differences between domain-specific models, with facilities for graphical visualization of the detected differences.     

基于UML实时系统的分析和设计

介绍了统一建模语言的最新版本UML2及应用UML2进行实时系统设计的作用及意义.探讨了UML2中用在实时系统设计中的概念.结合一个使用UML2为家庭安全系统设计的例子,着重分析了系统的静态结构和动态行为,通过类图、顺序图、状态图等UML图描述系统的方法从整体上对系统建模,说明实时系统分析与设计过程.使用UML分析和设计系统能够提高软件设计的效率和质量增强软件的维护性和复用性.     

基于UML的C++软件静态测试方法

提出一种基于UML的面向对象软件静态测试的方法，论述了方法的基本框架及针对C 的具体实现，使测试人员能直观地了解程序结构上的错误，并有效地设计测试用例。本静态测试方法是通过分析源程序文件，采用数据库来保存分析结果，并以UML类关系图显示出来。     

Measuring design-level cohesion

Cohesion was first introduced as a software attribute that, when measured, could be used to predict properties of implementations that would be created from a given design. Unfortunately, cohesion, as originally defined, could not be objectively assessed, while more recently developed objective cohesion measures depend on code-level information. We show that association-based and slice-based approaches can be used to measure cohesion using only design-level information. An analytical and empirical analysis shows that the design-level measures correspond closely with code-level cohesion measures. They can be used as predictors of or surrogates for the code-level measures. The design-level cohesion measures are formally defined, have been implemented, and can support software design, maintenance and restructuring     

基于UML的C3I系统软件建模

UML是一种通过面向对象分析确定由类图和行为图表述的逻辑体系结构和通过面向对象设计确定由构件图和配置图表述的物理体系结构的方法,目前已经成为面向对象分析与设计建模事实上的标准;首先介绍了UML技术及其在开发应用程序中的一般框架,并以此为依据,使用UML结合光电干扰武器系统C3I的建模应用实例对其进行了具体论述。     

基于UML的分布式软件体系结构中部件交互模式的复用

以客户／服务器系统为例，说明基于UML的分布式软件体系结构中部件交互模式的复用技术。用UML中的类图描述了模式中的部件，用合作图 部件喑的交互，同时也对同步方式、异步方式和代理通讯方式进行了建模。最后对前面所建模型进行了实例化，说明本模式的复用有着较大的实用价值。     

Modeling and validating Mondex scenarios described in UML and OCL with USE

This paper describes the Mondex case study with UML class diagrams and restricting OCL constraints. The constraints have been formulated either as OCL class invariants or as OCL pre- and postconditions. The proposed two models include UML class diagrams and OCL constraints which have been checked by the UML and OCL tool USE (UML-based Specification Environment). USE allows validation of a model by testing it with scenarios. The Mondex case study has been validated by positive and negative test cases. The test cases allow the validity of the various constraints to be traced and checked. Validation results are presented as textual protocols or as UML sequence diagrams where starting, intermediate, and resulting system states are represented by UML object diagrams. UML sequence diagrams, UML object diagrams, and textual protocols are shown with varying degrees of detail for the attributes, constraints, and executed commands. J. C. P. Woodcock     

On challenges of model transformation from UML to Alloy

The Unified Modeling Language (UML) is the de facto language used in the industry for software specifications. Once an application has been specified, Model Driven Architecture (MDA) techniques can be applied to generate code from such specifications. Since implementing a system based on a faulty design requires additional cost and effort, it is important to analyse the UML models at earlier stages of the software development lifecycle. This paper focuses on utilizing MDA techniques to deal with the analysis of UML models and identify design faults within a specification. Specifically, we show how UML models can be automatically transformed into Alloy which, in turn, can be automatically analysed by the Alloy Analyzer. The proposed approach relies on MDA techniques to transform UML models to Alloy. This paper reports on the challenges of the model transformation from UML class diagrams and OCL to Alloy. Those issues are caused by fundamental differences in the design philosophy of UML and Alloy. To facilitate better the representation of Alloy concepts in the UML, the paper draws on the lessons learnt and presents a UML profile for Alloy.     

Analyzing the evolutionary history of the logical design of object-oriented software

Today, most object-oriented software systems are developed using an evolutionary process model. Therefore, understanding the phases that the system's logical design has gone through and the style of their evolution can provide valuable insights in support of consistently maintaining and evolving the system, without compromising the integrity and stability of its architecture. In this paper, we present a method for analyzing the evolution of object-oriented software systems from the point of view of their logical design. This method relies on UMLDiff, a UML-structure differencing algorithm, which, given a sequence of UML class models corresponding to the logical design of a sequence of system code releases, produces a sequence of "change records" that describe the design-level changes between subsequent system releases. This change-records sequence is subsequently analyzed from the perspective of each individual system class, to produce the class-evolution profile, i.e., a class-specific change-records' sequence. Three types of longitudinal analyses - phasic, gamma, and optimal matching analysis - are applied to the class-evolution profiles to recover a high-level abstraction of distinct evolutionary phases and their corresponding styles and to identify class clusters with similar evolution trajectories. The recovered knowledge facilitates the overall understanding of system evolution and the planning of future maintenance activities. We report on one real-world case study evaluating our approach.     

System-level functional testing from UML specifications in end-of-production industrial environments

The goal of this research is the study of a methodology to convert design-level specifications of complex embedded systems to system-level functional tests for direct instrumentation; the general context is industrial end-of-production environment (EOP) and the approach uses official and de facto industrial standards (e.g., Unified Modeling Language, UML) and advanced techniques from academic research. The research suggests process guidelines, exploring the generation of the timed test sequences from a UML model, the translation phases, and addressing the problem of timing and environment creation. A case study of a significantly complex application is provided directly from the industrial world thanks to an agreement between Politecnico’s Testgroup and Magneti Marelli Electronic Systems, research and development site of Venaria Reale, an international leader in automotive applications.     

基于UML的CORBA/Java分布式应用系统的领域模型设计

探讨了一种借助UML构建的基于CORBA/Java的分布式应用系统建模方法以及相关技术.研究设计了分布式应用系统的软件模型,使用UML建模方法完成了系统分析、设计和建立领域模型的全过程.通过一个具体实例给予详细说明,实例表明,利用UML对复杂的软件系统建模,有助于实现软件的重组和复用,为快速、高效地构建系统提供了一种可行的解决方案.     

Using patterns for the refinement and translationof UML models: A controlled experiment

This paper presents a controlled experiment, conducted at the University of Kaiserslautern which evaluates an approach known as SORT, for the systematic refinement and translation of UML Diagrams. Specifically, the experiment investigates the effects of SORT, with respect to the mapping of object-oriented UML design models to source code, by comparing the effects of different approaches to such mappings (SORT and ad-hoc¹) on the quality attributes understandability, verifiability, and effort (time). The experimental results demonstrate that OO systems developed by applying SORT are more understandable and verifiable. In summary, SORT can help to improve the quality of software systems, but its application alone does not guarantee quality. Editor: Murray Wood ¹The mapping strategy followed by most mainstream methods is based on personal experience and general mapping guidelines. Thus, mappings are performed on an individual basis without systematic guidance (i.e., these approaches can be characterized as “ad-hoc” mapping approaches).     

基于知识的UML图形文档自动生成

基于领域本体的需求获取使得用领域术语描述用户需求,并进行应用模型的自动分析成为可能,以尽可能地保证需求描述的正确性和完整性。从以领域概念为背景的应用模型,到以软件概念为基础的应用软件模型,是需求工程要完成的一个实质性跨越。UML是目前软件需求描述的一个实际上的标准。该文主要论述了从基于领域本体的应用需求描述到基于UML的软件需求文档的自动转换过程,文章提出建立从领域本体概念到UML概念映射规则库,以及根据UML概念填写用XML表示的UML图元模板的规则库,设计并实现了一个基于规则的,从应用需求概念到UML图元模板的自动转换工具。     

Source-code comprehension tasks supported by UML design models: Results from a controlled experiment and a differentiated replication

Objective: The main objective is to investigate whether the comprehension of object-oriented source-code increases when it is added with UML class and sequence diagrams produced in the software design phase.Methods: We conducted a controlled experiment and a differentiated replication with young software maintainers. In particular, groups of Bachelor and Master students were involved.Results: The results show that more experienced participants better comprehend source-code when added with UML design models. An average improvement (or benefit) of circa 12% was achieved when the participants accomplished the comprehension task with UML class and sequence diagrams. The results of an analysis on the time to accomplish comprehension tasks showed that less experienced participants significantly spent more time when comprehending source-code with UML design models. This kind of participants spent on average 44.8% of the time to accomplish the same task with source-code alone.Implications: It is useless to give UML design models to comprehend source-code in case maintainers are not adequately experienced with the UML. Furthermore, the less the experience of participants, the more the time to accomplish a comprehension task with UML diagram is.     

Aspectual templates in UML

UML Templates allow to capture reusable models through parameterization. The construct is general enough to be used in many ways, ranging from the representation of generic components (such as Java generics or C++ templates) to aspectual usage, including pattern-, aspect- and view-oriented modeling. We concentrate on this last usage and so-called aspectual templates which require that parameters must form a model of systems in which to inject new functionalities. Starting from this strict constraint, we derive an in-depth semantic enhancement of the standard. It is formalized as a fully UML-compliant interpretation in OCL of the template construct and its binding mechanism. In particular, this aspectual interpretation must be ensured in case of partial binding (not all parameters are valued). Partial binding of UML is a powerful technique which allows to obtain richer templates from the composition of other ones. As a major result, the present semantic enhancement is consistent with this capacity so that partial binding of aspectual templates produces aspectual templates. Finally, at an operational level, an algorithm for aspectual template (partial) binding operation is formulated and consequent reusable technology made available in EMF (Eclipse Modeling Framework) is presented.     

How are UML class diagrams built in practice? A usability study of two UML tools: Magicdraw and Papyrus

Software modeling is a key activity in software development, especially when following any kind of Model Driven Software Engineering (MDSE) process. In this context, standard modeling languages, like the Unified Modeling Language (UML), and tools for supporting the modeling activities become essential.The aim of this study is to analyze how modelers build UML models and how good modeling tools are in supporting this task. Our goal is to draw some useful lessons that help to improve the (UML) modeling process both by recommending changes on the tools themselves and on how UML is taught so that theory and practice of UML modeling are better aligned.Our study employs two research approaches. The main one is an empirical experiment (which analyzes screen recordings registered by undergraduate students during the construction of a UML class diagram). An analytical analysis complements the previous experiment. The study focuses on the most frequent type of UML diagram, the class diagram, and on two tools widely used by the modeling community: MagicDraw and Papyrus.