UML/OCL工具的一致性检查研究

UML作为一种通用的可视化建模语言已被广泛应用,但UML模型的一致性问题一直限制着在软件开发中更有效地应用UML。本文阐述了UML模型一致性的相关概念,介绍了一种以OCL表示模型的一致性规则、并基于这些对模型进行一致性检查的方法。将此方法实现为一致性检查工具,提供了模型分析、语法检查和模型一致性检查等功能。     

基于PDA的生猪溯源管理系统对象模型设计

采用面向对象的软件工程方法对基于PDA的生猪溯源管理系统进行建模,通过用例图、类图、协作图和状态图的设计,用统一建模语言UML实现了对系统对象的建模。该面向对象的模型为基于PDA的生猪溯源管理系统的实现提供了稳定性好、可重用性高、适应性强、易于维护的软件蓝图。     

基于UML和OCL的类间交互测试用例生成算法研究

针对面向对象软件的类、封装、继承、动态连接等特性,对对象建模语言(UML模型)中的顺序图添加对象约束语言(OCL约束),做类间交互的软件测试。提出执行图EG生成算法,将顺序图SD转换为EG,解决UML2.0顺序图新增特性中的alt,loop,opt,break这4种常见组合片段及其嵌套和多态性问题;为得到最小完备的测试路径,提出EG的遍历策略和测试路径生成算法;确定测试场景,生成测试用例。经实例分析,它可以基于UML顺序图与OCL作系统地测试。     

嵌入式系统描述与验证环境的实现

首先，用统一建模语言(UML)中的状态图描述系统在整个活动周期中所处的不同的状态，活动图表示状态图中每个进程的功能，对象约束语言(OCL)描述系统中的约束条件；然后，用自行开发的软件UML2SC将UML描述的系统转换成SystemC代码，以完成系统的模拟验证；并介绍了该方法的一个应用实例。     

从UML建立的模型中得到需求目标

UML已经被软件工程实践者广泛地使用，但是，就其本质而言，它并没有清晰地描述出需求目标。该文介绍一种方法试图在UML模型与软件需求目标之间建立语义上的联系。     

基于UML模型的统计测试方法研究

为增强统计测试的可行性、可测试性,降低建立使用模型的难度,通过研究作为工业标准的统一建模语言UML,提出了一种基于UML模型的统计测试方法。论文首先建立了基于UML模型的统计测试过程,然后结合扩展的UML模型和使用模型的形式化描述,给出了从UML模型导出使用模型的一种形式化算法,并以工控机器人软件为例说明了应用该方法的完整过程。     

教务管理系统的UML建模

统一建模语言UML是一种面对对象的可视化建模语言,也是近代软件工程环境中对象分析和设计的重要工具.在简述UML软件建模技术的基础上.结合教务管理系统的实际需求,给出了UML系统建模的详细设计应用实例,并绍系统开发方案.     

基于UML的图形界面系统对象模型的研究

按照面向对象软件工程的思想,以UML建模语言,以Visio2003为建模工具,研究与建立了小型监控组态软件图形界面系统的对象模型,并且研究和建立了对象模型内部的各子模型,以及各子模型之间的关系。该对象模型已借助面向对象编程语言VisualC＋＋6．0实现。模型的建立过程对于同类软件模型的研究和开发具有参考价值。     

基于UML的软件Markov链使用模型构造研究

软件统计测试要求基于软件使用模型产生测试例对软件系统进行测试,并根据测试结果评价软件可靠性,是高可靠软件测试的重要组成部分.由于统一建模语言(unified modeling language,简称UML)已经成为事实上的面向对象标准建模语言,因此,从软件UML模型构造软件使用模型就成为面向对象软件统计测试的关键.为此,定义了加入统计测试约束的UML用例图、序列图以及用例执行顺序关系,为基于UML的软件统计测试提供了一个形式化描述基础.在此基础上,给出一个从软件UML模型构造软件Markov链使用模型的算法,并给出了自动化支持工具UMGen的类图结构,基于一个卫星控制系统,说明了所提出方法的有效性.     

UML在仓库管理系统中的应用

UML(统一建模语言)是以对象模型为基础的适用于编制软件蓝图的标准化语言，其提供了软件方法和过程的描述基础。UML可以对大型复杂的系统的各种成分可视化，说明并构造系统模型。以及建立各种所需的文档。以仓库管理系统为例，通过采用UML建模实现该系统，介绍UML在软件工程方面的应用。     

On OCL-based imperative languages

The Object Constraint Language (OCL) is a well-accepted ingredient in model-driven engineering and accompanying modeling languages such as UML (Unified Modeling Language) and EMF (Eclipse Modeling Framework) that support object-oriented software development. Among various possibilities, OCL offers the formulation of class invariants and operation contracts in form of pre- and postconditions, and side-effect free query operations. Much research has been done on OCL and various mature implementations are available for it. OCL is also used as the foundation for several modeling-specific programming and transformation languages. However, an intrusive way of embedding OCL into these language hampers us when we want to benefit from the existing achievements for OCL. In response to this shortcoming, we propose the language SOIL (Simple OCL-like Imperative Language), which we implemented in the UML and OCL modeling tool USE to amend its declarative model validation features. The expression sub-language of SOIL is identical to OCL. SOIL adds imperative constructs for programming in the domain of models. Thus by employing OCL and SOIL, it is possible to describe any operation in a declarative way and in an operational way on the modeling level without going into the details of a conventional programming language. In contrast to other similar approaches, the embedding of OCL into SOIL is done in a careful, non-intrusive way so that purity of OCL is preserved.     

An experimental investigation of formality in UML-based development

The object constraint language (OCL) was introduced as part of the Unified Modeling Language (UML). Its main purpose is to make UML models more precise and unambiguous by providing a constraint language describing constraints that the UML diagrams alone do not convey, including class invariants, operation contracts, and statechart guard conditions. There is an ongoing debate regarding the usefulness of using OCL in UML-based development, questioning whether the additional effort and formality is worth the benefit. It is argued that natural language may be sufficient, and using OCL may not bring any tangible benefits. This debate is in fact similar to the discussion about the effectiveness of formal methods in software engineering, but in a much more specific context. This paper presents the results of two controlled experiments that investigate the impact of using OCL on three software engineering activities using UML analysis models: detection of model defects through inspections, comprehension of the system logic and functionality, and impact analysis of changes. The results show that, once past an initial learning curve, significant benefits can be obtained by using OCL in combination with UML analysis diagrams to form a precise UML analysis model. But, this result is however conditioned on providing substantial, thorough training to the experiment participants.     

Reconstructing a formal security model

Role-based access control (RBAC) is a flexible approach to access control, which has generated great interest in the security community. The principal motivation behind RBAC is to simplify the complexity of administrative tasks. Several formal models of RBAC have been introduced. However, there are a few works specifying RBAC in a way which system developers or software engineers can easily understand and adopt to develop role-based systems. And there still exists a demand to have a practical representation of well-known access control models for system developers who work on secure system development. In this paper we represent a well-known RBAC model with software engineering tools such as Unified Modeling Language (UML) and Object Constraints Language (OCL) to reduce a gap between security models and system developments. The UML is a general-purpose visual modeling language in which we can specify, visualize, and document the components of a software system. And OCL is part of the UML and has been used for object-oriented analysis and design as a de facto constraints specification language in software engineering arena. Our representation is based on a standard model for RBAC proposed by the National Institute of Standards and Technology. We specify this RBAC model with UML including three views: static view, functional view, and dynamic view. We also describe how OCL can specify RBAC constraints that is one of important aspects to constrain what components in RBAC are allowed to do. In addition, we briefly discuss future directions of this work.     

对象约束语言及其在精化PIM中的应用

为了应用精确、完备的PIM自动进行模型转换、校验及编译,分析了OCL元模型与UML元模型间的关系,在此基础上对OCL在精确化平台无关模型(PIM)方面的应用进行了研究,指出OCL面临的挑战,并对OCL的研究方向提出了几点建议。对象约束语言OCL可以对模型中的元素进行约束和查询,可以在MOF的任意一层上定义模型语言,还可以通过各种方法定义模型的转换规则。     

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.     

一种状态图到B规格说明的自动转换方法研究实现

状态图是UML动态视图之一,主要描述对象的动态行为,但缺乏形式化的动态语义,不利于软件从需求到代码的自动化转换。B语言支持形式化规格说明,在MDA转换过程中,把UML状态图转换为B规格说明,可以使MDA中的需求表达得更为精确。基于此,提出了一种基于EMF的状态图到B规格说明的转换方法,设计了状态图和B抽象机的元模型,定义了元模型之间的转换规则,给出了该规则的ATL描述,最后在Eclipse平台实现了状态图到B规格说明的自动转化。该方法为MDA过程中获取形式化需求提供了一种新的途径。     

一种基于规则的模型转换方法*

尽管模型驱动开发(MDD)代表软件工程的发展方向,但是目前MDD还缺乏一套完整的转换规则描述方法和相应的实现机制,难以实现模型的自动转换。为此定义了一个平台独立模型到平台相关模型的转换框架,采用UML活动图说明模型转换的实现机制;基于OCL定义了转换规则的表示法,并结合UML模型到Java模型的转换给出了转换规则的定义。最后在一个具体的实例中验证了此方法的合理性和易用性。     

Applying black-box testing to UML/OCL database models

Most Unified Modeling Language (UML) computer-aided software engineering tools have been insufficient in the development process because they provide little support for conceptual model testing. Model testing aims to ensure the correctness of a UML/OCL class diagram, or, in other words, that a given class diagram can perfectly meet the user’s requirements. This study proposes the validation of class diagrams with black-box testing, a technique used to test software without focusing on the software’s implementation or structure. An approach is proposed for the automatic transformation of the constraints of a UML/OCL class diagram into test cases. Following the creation of the test cases, they are executed with JUnit and the results produced are shown to the tester. To demonstrate the applicability of this approach, an effectiveness evaluation and an efficiency evaluation are performed here. Evaluation studies show that all faults included in a class diagram have been detected within an efficient time.     

带OCL约束条件的类图到object—Z规格说明的转换

如何提高软件的可靠性是目前软件研究领域的一个热点。将形式化方法和主流的软件开发方法相结合是一个可行的方法。本文研究UML语言和Object-Z语言相结合的方法，为主流的软件开发人员所使用的图形化规格说明技术与形式方法提供的精确的分析和验证技术架起了一座桥梁。本文定义如何将带0CL约束条件的类图转换到Object-Z规格说明的方法。这样不仅可以通过支持Object-Z语言的工具采对UML语言描述的系统性质进行验证和确认，而且能够帮助规格说明人员方便地构造Object-Z规格说明。