Enhancing the semantics of UML association redefinition

Association redefinition is a UML construct that permits us to define an association end more specifically in a particular context. Concretely, it allows specifying some additional participation and cardinality constraints on the association. Association refinements, which have been studied and used by many authors in conceptual modelling languages prior to UML, are closely related to association redefinitions. They also permit to refine the ends of an association adding participation and cardinality constraints. In this paper, we analyze and compare the semantics of both concepts and propose to extend the semantics of association redefinitions in UML to cover all the constraints that may be expressed by association refinements in other conceptual modelling languages. Additionally, we present how to integrate previous results on validation of association refinements to UML and how to generate code for a relational technology platform. Finally, we provide a prototype tool to verify the feasibility of the approach.     

基于Object—Z的UML对象模型的形式化

1 引言 UML作为面向对象的可视化建模语言,己被对象管理集团(OMG)作为面向对象分析和设计的标准,获得了众多工具的支持。UML提供了不同抽象层次的描述以支持面向对象的分析、设计和实施,它从不同的视图描述软件系统,减少了建模的复杂度,更为重要的是建立了基于元模型的体系结构,提供了较为灵活的扩充机制,使开发人员可以根据不同的领域需求定制UML,也易于加入新的建模概念。     

关于统一建模语言——UML

ＵＭＬ是面向对象开发中一种通用的、图形化的模型语言,是近代软件工程环境中对象分析和设计的重要工具。ＵＭＬ严格地定义了对象无模型的语义,提供了描述对象结构和行为的表示法。本文介绍了ＵＭＬ产生的技术背景、无模型的主要思想、表示法,以及应用系统建模的一般过程和对ＯＯ世界的意义。     

Synthesizing object life cycles from business process models

Unified modeling language (UML) activity diagrams can model the flow of stateful business objects among activities, implicitly specifying the life cycles of those objects. The actual object life cycles are typically expressed in UML state machines. The implicit life cycles in UML activity diagrams need to be discovered in order to derive the actual object life cycles or to check the consistency with an existing life cycle. This paper presents an automated approach for synthesizing a UML state machine modeling the life cycle of an object that occurs in different states in a UML activity diagram. The generated state machines can contain parallelism, loops, and cross-synchronization. The approach makes life cycles that have been modeled implicitly in activity diagrams explicit. The synthesis approach has been implemented using a graph transformation tool and has been applied in several case studies.     

An object-oriented approach to formally analyze the UML 2.0 activity partitions

Nowadays, UML is the de-facto standard for object-oriented analysis and design. Unfortunately, the deficiency of its dynamic semantics limits the possibility of early specification analysis. UML 2.0 comes to precise and complete this semantics but it remains informal and still lacks tools for automatic validation. The main purpose of this study is to automate the formal validation, according a value-oriented approach, of the behavior of systems expressed in UML. The marriage of Petri nets with temporal logics seems a suitable formalism for translating and then validating UML state-based models. The contributions of the paper are threefold. We first, consider how UML 2.0 activity partitions can be transformed into Object Petri Nets to formalize the object dynamics, in an object-oriented context. Second, we develop an approach based on the object and sequence diagram information to initialize the derived Petri nets in terms of objects and events. Finally, to thoroughly verify if the UML model meets the system required properties, we suggest to use the OCL invariants exploiting their association end constructs. The verification is performed on a predicate/transition net explored by model checking. A case study is given to illustrate this methodology throughout the paper.     

Expert' voice: The BabyUML discipline of programming

I want increased confidence in my programs. I want my own and other people's programs to be more readable. I want a new discipline of programming that augments my thought processes. Therefore, I create and explore a new discipline of programming in my BabyUML laboratory. I select, simplify and twist UML and other languages to demonstrate how they help bridge the gap between me as a programmer and the objects running in my computer The focus is on the run time objects; their structure, their interaction, and their individual behaviors. Trygve Reenskaug is professor emeritus of informatics at the University of Oslo. He has 40 years experience in software engineering research and the development of industrial strength software products. He has extensive teaching and speaking experience including keynotes, talks and tutorials. His firsts include the Autokon system for computer aided design of ships with end user programming language, structured programming, and a data base oriented architecture from 1960; object oriented applications and role (collaboration) modeling from 1973; Model-View-Controller, the world's first reusable object oriented framework, from 1979; OOram role modeling method and tool from 1983. Trygve was a member of the UML Core Team and was a contributor to UML 1.4. The goal of his current research is to create a new, high level discipline of programming that lets us reclaim the mastery of software.     

RM方法在基于HLA的分布式仿真系统中的应用

角色建模（Role Modeling,简称RM）技术是一种着眼于刻画对象间动态协作关系的建模方法。针对HLA强调联邦成员之间互操作和服务重用性的特点,将角色建模技术与统一建模语言（Unified Modeling Language,简称UML）相结合,应用于基于HLA的分布式仿真系统开发中,既提高了仿真系统的服务重用性,又弥补了UML在联邦成员之间协作表达能力上的不足。     

统一建模语言UML述评

最近由美国Ｒａｔｉｏｎａｌ公司发起并与其它十几家公司共同的“统一模型语言”ＵＭＬ在ＯＯ领域受到广泛的关注。     

扩展UML语义以支持并行和分布式仿真系统设计

标准UML中不包含虚拟时间和时间同步语义，因而缺乏对并行和分布式仿真(parallel and distributed simulation，PADS)系统设计的支持，对标准UML语义进行扩展以支持PADS领域的概念并降低PADS系统构造的复杂性．主要的工作包括在UML，中引入虚拟时间语义，用包含虚拟时间标记和约束的状态图和交互图来描述仿真实体的功能属性，另外，通过创建虚拟时间同步构造型(stereotype)，提出“分离法”将时间同步细节与仿真模型内部的功能属性逻辑地分离，不仅使得仿真对象建模更加容易，而且使仿真模型和时间同步策略两者的重用性大大提高。     

基于COOZ对UML的类结构的形式化

为面向对象的模型建立坚实的形式化基础是近年形式化研究的热点。一旦提供了对面向对象模型概念的精确描述后,就可以对OO模型的行为和结构进行清晰的分析。统一模型语言（UML）是为建立统一的面向对象开发方法的有益偿试,它是在已有的三大OO方法学的基础上抽象出来的模型语言。文章结合作者正在进行的对Z语言的OO扩展COOZ,对UML的类层次结构进行精确的形式化描述。     

UML建模技术在医院奖金核算系统中的应用

针对当前医院信息管理系统没有科室奖金核算的缺点,结合医院奖金核算复杂性和特殊性的特点,提出应用UML建模技术设计开发的系统解决方案．本文分析面向对象的UML建模技术,从系统开发过程的视角着重介绍了UML建模技术在需求分析和结构设计层次中的应用,提出了医院奖金核算管理系统开发问题的新思路．根据建模的用例图、活动图和序列图描述出系统设计的构架,用类图反映出数据对象的属性和操作．最终实现一个功能完善,性能可靠的医院奖金核算管理系统．     

WCET分析中面向对象程序多态性问题的解决方法

用面向对象建模语言(如统一建模语言UML)设计并用面向对象程序设计语言(如C )实现实时系统是实时系统开发领域的一个趋势,但面向对象的主要特征(如多态性)却使程序最差情况执行时间(Worst-Case ExecutionTi me,WCET)更加难以分析。本文通过把UML设计信息引入WCET分析来解决此问题。考虑到UML关联关系描述了两个或多个具体类之间的对应关系,因此本文要求指定关联角色的多重性,并假定能够建立关联关系与其在程序中表示的对应关系。在已知关联角色多重性的基础上,本文计算特定循环的执行计数并确定在超(虚)类调用位置上每个具体类的对象个数,该循环使用超类变量遍历统一表示的关联角色对象。通过和Corti等人方法的结合,本文方法能够自动计算具有多态性特征的面向对象程序的WCET。实验结果表明,本文研究的情形在面向对象程序中普遍存在。     

A synergistic model-driven approach for persistence modeling with UML

The Model Driven Development (MDD) approach proposes that models (and model-to-model transformations) play the main role on system development. However, there is not a consensual notation to model persistence based upon object-relational mapping frameworks: while UML lacks specific resources for persistence modeling, the entity-relationship model does not make reference to the dynamic concepts existing in UML.This paper proposes MD-JPA, a UML profile for persistence modeling based on the well-known Java Persistence API 2 (JPA) standard for object-relational mapping, pursuing the modeling of transient and persistent elements in a more coherent and synergistic way. This paper describes the main characteristics of MD-JPA as well as the way that models that adopt such profile can them be used to generate a Java implementation by the application of the proposed model transformations on a MDD approach. Finally, an open source tool was developed to make the results of this work available to the community.     

DPMAS:一种多主体系统设计方法

提出一种多主体系统设计方法DPMAS。首先,该方法以对象作为主体实现的基础,以UML作为基本的建模语言,保证了与面向对象方法的延续性。同时,该方法提供了新的图来表示多主体系统中的知识模型和主体间交互模型,并对UML符号进行了一些改进以表示主体特有的概念。     

Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML

Despite the status of united modeling language (UML) as the de facto standard for object oriented modeling, it has received controversial reviews. The most controversial diagram in UML is the use case diagram. Some practitioners claim that use case diagrams are not valuable in requirements analysis and some have even argued that use case diagrams should not be part of UML. This research examined the values of use case diagram in interpreting requirements when use case diagrams are used in conjunction with class diagrams. In other words, the study investigated the possible synergetic values and relationships between the use case and class diagrams in the context of requirements analysis. This study used theories from cognitive psychology as its theoretical and conceptual foundation. The data collection utilized the verbal protocol technique in which subjects were asked to think aloud as they interpreted the use case and class diagrams. The results show that the use case diagrams were more completely interpreted than the class diagrams. The presence or absence of one diagram when interpreting another diagram had no effect on the outcome of the interpretation. From the results, we argue that the use case diagrams and class diagrams depict different aspects of the problem domain, they have very little overlap in the information captured, and both are necessary in requirements analysis.     

Extending the Unified Modeling Language for ontology development

There is rapidly growing momentum for web enabled agents that reason about and dynamically integrate the appropriate knowledge and services at run-time. The dynamic integration of knowledge and services depends on the existence of explicit declarative semantic models (ontologies). We have been building tools for ontology development based on the Unified Modeling Language (UML). This allows the many mature UML tools, models and expertise to be applied to knowledge representation systems, not only for visualizing complex ontologies but also for managing the ontology development process. UML has many features, such as profiles, global modularity and extension mechanisms that are not generally available in most ontology languages. However, ontology languages have some features that UML does not support. Our paper identifies the similarities and differences (with examples) between UML and the ontology languages RDF and DAML+OIL. To reconcile these differences, we propose a modification to the UML metamodel to address some of the most problematic differences. One of these is the ontological concept variously called a property, relation or predicate. This notion corresponds to the UML concepts of association and attribute. In ontology languages properties are first-class modeling elements, but UML associations and attributes are not first-class. Our proposal is backward-compatible with existing UML models while enhancing its viability for ontology modeling. While we have focused on RDF and DAML+OIL in our research and development activities, the same issues apply to many of the knowledge representation languages. This is especially the case for semantic network and concept graph approaches to knowledge representations. Initial sbmission: 16 February 2002 / Revised submission: 15 October 2002 Published online: 2 December 2002     

从UML顺序图生成状态图的一个方法

UML (Unified Modeling Language) is a visual modeling language used for specifying,visualizing,constructing,and documenting the artifacts of software systems by various diagrams.It has been widely accepted as a standard modeling language in both academic and industrial areas.UML sequence diagrams are mostly used in specifying system requirements.By representing interactions,which are arranged in time sequence,between the objects in a system,sequence diagrams can construct scenarios indicating the system‘‘s functions.A UML statechart diagram is a graph shows the sequences of states that an object or an interaction goes through during its life in response to received stimuli,together with its responses and actions.It‘‘s useful in the design stage of system development.This essay discusses the computer-aided transformation from sequence diagrams to statechart diagrams,which can offer strong support for the transfering from requirement analysis to system design in the software development process.With OCL (Object Control Language) semantic constrain,a transform algorithm is provided in the paper.And the differences with the related works are also mentioned.