一种支持能力需求概念一致性和合理性分析的方法

针对C4ISR系统能力需求中存在的大量模糊信息以及需求模型中可能会存在的不一致性、不合理性问题,从体系结构能力相关概念出发,构建C4ISR领域特定的能力模糊本体,在模糊本体的引导下,获取应用系统的能力需求模型.在此基础上,研究了基于模糊描述逻辑符号推理的能力需求模型一致性、合理性验证技术,给出了能力需求模型向模糊描述逻辑知识库的转换算法,最终采用一个模型验证案例说明了方法的可行性.     

基于规则的用例规约验证方法

用例模型描述了参与者对系统功能的需求,在整个系统的开发过程中有着重要作用;用例描述若存在问题,会对系统开发造成很大影响。提出了一种用例规约的规则验证方法,通过分析用例规约中的错误类别,在特定的用例规约描述方法上设计了帮助发现规约中不完整性、不一致性错误的验证规则,并通过规则的形式化来支持需求的自动化验证。     

基于UML类图模型的一致性检查方法

UML中的类图采用直观的图形化表示方法,有效描述了待建系统的静态特征,为系统设计人员发现系统模型中存在的不一致性和冗余等问题,提供了有效的分析工具。但是对于复杂的系统,完全依靠系统分析人员发现模型中存在的不一致性和冗余等问题是不现实的,应当为建模工具赋以模型自动一致性检查功能。SHOIQ(D)是描述逻辑家族中可判定的子集,它在保证推理可判定的同时,具备较强的描述知识能力。鉴于上述特点,通过从UML类图图元中抽取语义,用SHOIQ(D)形式化描述类图图元,借助自动推理引擎,从而使基于UML类图模型的自动一致性检查功能得到实现。根据该方法改进后的建模工具,可以自动发现基于UML类图模型中存在的不一致性和冗余等问题。     

基于规则的UML设计模型的一致性检验

统一建模语言(UML)是业界公认的主流面向对象建模语言,为系统开发提供了丰富的建模元素。由于UML不同建模元素之间缺乏准确定义的关系,因此UML模型往往会出现不一致性问题。针对该问题,提出了一种基于规则的检验方法。该方法把UML设计模型和一致性条件分别映射为规则系统的事实库和规则库,如果事实库与规则库不匹配,则表示设计模型中存在不一致性。我们使用自主开发的一种“面向对象-规则语言系统”作为检验一致性的规则系统,它集成了面向对象语言和规则语言两种范型,有利于统一使用C++语言来设计并实现一致性检验工具,提高一致性检验效率。     

基于UML类图模型的一致性检查方法

UML中的类图采用直观的图形化表示方法,有效描述了待建系统的静态特征,为系统设计人员发现系统模型中存在的不一致性和冗余等问题,提供了有效的分析工具.但是对于复杂的系统,完全依靠系统分析人员发现模型中存在的不一致性和冗余等问题是不现实的,应当为建模工具赋以模型自动一致性检查功能.SHOIQ(D)是描述逻辑家族中可判定的子集,它在保证推理可判定的同时,具备较强的描述知识能力.鉴于上述特点,通过从UML类图图元中抽取语义.用SHOIQ(D)形式化描述类图图元,借助自动推理引擎,从而使基于UML类图模型的自动一致性检查功能得到实现.根据该方法改进后的建模工具,可以自动发现基于UML类图模型中存在的不一致性和冗余等问题.     

多视点中不一致性的处理：一种基于认知逻辑的方法

衡量一个软件系统是否成功,一个基本的要素就是看该软件系统是否满足了用户的要求。软件系统需求工程(RE)就是一个通过标识涉众及其需求并将其文档化以便于进行分析的过程。RE是一个跨学科,以人为中心的过程。多视点需求工程是需求工程的一个分支。多视点需求工程就是希望复杂系统中的不同参与者分别从自己的角度出发对预期系统进行描述,从而形成更完备的需求规约。由于多视点方法的这种特性,导致多个涉众有可能对同一问题进行描述,从而形成重叠的需求。这些重叠的需求就是涉众之间的公共知识,对公共知识的不同解释是导致需求规约中不一致问题的根源。不一致性是多视点需求工程中一个必须解决的问题。本文提出了基于问题域的多视点需求建模框架,并利用认知逻辑对该框架进行解释和推理,希望可以用形式化的方法来发现和解决存在于不同视点间的不一致性。     

视点间的不一致性检查和视点集成

需求定义人员常从同的观察角度来定义大型软件系统的需求,从而形成多个部分需求说明（视点）。由于视点之间的相对独立性,多视点的集成是需求工程中一项重要而又困难的研究课题。使用形式化方法来描述视点需求和视点间的关系将使视点集成能自动进行。在此,使用SFSM状态转换图来描述视点需求,并将视点间的关系用谓词的形式表示在状态图中状态转换的卫士条件中,同时在此基础上提出了一种自动合成视点的方法,需求定义人员可以根据状态等价关系与合成后状态图的冲突来检查和解决两个视点之间的不一致性。通过重复视点合成和检查、处理视点间的不一致性这一过程,多个视点可以被集成为整个软件系统的需求说明,应用了一个电话系统的例子说明了此视点需求表示和视点集成方法。使用此方法,视点集成过程可以自动完成,同时还可以在一定程度上引导需求定义人员检查和解决视点间的不一致性。     

基于UML的软件形式化需求分析与验证

针对软件开发中传统的需求分析方法所存在的需求描述不完整、具有二义性和不一致性问题,提出一种形式化需求分析方法。介绍根据用户需求采用形式化方法获取软件需求说明书并设计软件的统一建模语言（UML）模型的过程,及对该UML模型进行形式化描述,采用形式化验证技术对形式化后的UML模型进行需求验证,以确保设计的UML模型的正确性。实验结果表明,形式化的需求分析方法克服了传统需求分析方法中存在的问题。     

基于局部特征的自适应快速图像分割模型

基于区域的活动轮廓模型如Chan-Vese(CV)模型等以其能较好的处理图像的模糊边界和复杂拓扑结构而广泛运用于图像分割中.然而基于灰度分布均匀假设,该模型对于含灰度不一致性的目标分割结果较差.此外,纹理是周期性重复出现的细节,依靠灰度信息无法正确检测.针对这些问题,提出一种基于局部特征的自适应快速图像分割模型.一方面,利用两种区域项检测卡通部分和纹理部分的特征信息,在自适应的局部块中提取局部统计信息以克服卡通部分的灰度不一致性;另一方面,利用自适应的局部块中的纹理特征来计算背景和目标区域的Kullback-Leibler (KL)距离以检测图像的纹理部分.进一步,基于分裂Bregman方法对该模型进行快速求解.分别对医学和纹理图像进行了实验,准确性和时效性都有显著提高.     

基于模型驱动元数据管理策略的研究

目前,元数据管理存在这样的问题,各开发商使用不同的元模型来设计自己的数据仓库工具,而且对元数据的描述往往不一致,这样给数据集成带来很大的问题。使用一种基于模型驱动的方式,将元数据描述规范化,并运用基于模型驱动的公共仓库模型CWM(Common Warehouse Metamodel)来实现这一过程。该模型可以充分发挥软件的复用性,使系统有良好的通用性,从而提高系统开发效率。     

Testing UML designs

Early detection and correction of faults in the software design phase can reduce total cost and time to market of a software product. In this paper we describe an approach for testing UML design models to uncover inconsistencies. Our approach uses behavioral views such as Sequence Diagrams to simulate state change in an aggregate model. The aggregate model is the artifact of merging information from behavioral and structural UML views. OCL pre-conditions, post-conditions and invariants are used as a test oracle.     

一种支持MDA的PIM建模方法

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

Development of logical and technical architectures for automotive systems

This paper presents a modeling approach for the development of software for electronic control units in the automotive domain. The approach supports the development of two related architecture models in the overall development process: the logical architecture provides a graphical, quite abstract representation of a typically large set of automotive functions. On this abstraction level no design decisions are taken. The technical architecture provides a software and a hardware representation in separated views: the software architecture describes the software realization of functions as software components, whereas the hardware architecture models hardware ntities, on which the software components are deployed. Logical as well as technical architectures only model structural information, but no behavioural information. A tight integration of both architecture levels—on the conceptual and on the tool level—with related development phases such as requirements engineering, behaviour modeling, code generation as well as version and configuration management resulting in a seamless overall development process is presented. This architecture modeling approach has been developed within a safety-relevant project at BMW Group. Positive as well as negative experiences with the application of this approach are described.     

Towards an Integrated View on Architecture and its Evolution

Information about the evolution of a software architecture can be found in the source basis of a project and in the release history data such as modification and problem reports. Existing approaches deal with these two data sources separately and do not exploit the integration of their analyses. In this paper, we present an architecture analysis approach that provides an integration of both kinds of evolution data. The analysis applies fact extraction and generates specific directed attributed graphs; nodes represent source code entities and edges represent relationships such as accesses, includes, inherits, invokes, and coupling between certain architectural elements. The integration of data is then performed on a meta-model level to enable the generation of architectural views using binary relational algebra. These integrated architectural views show intended and unintended couplings between architectural elements, hence pointing software engineers to locations in the system that may be critical for on-going and future maintenance activities. We demonstrate our analysis approach using a large open source software system.     

Modeling Multi-agent systems with ANote

An important issue in getting the agent technology into mainstream software development is the development of appropriate methodologies for developing agent-oriented systems. This paper presents an approach to model distributed systems based on a goal-oriented requirements acquisition. These models are acquired as instances of a conceptual meta-model. The latter can be represented as a graph where each node captures a concept such as, e.g., goal, action, agent, or scenario, and where the edges capture semantic links between such abstractions. This approach is supported by a modeling language, the ANote, which presents views that capture the most important modeling aspects according to the concept currently under consideration.     

AML模型导航工具的设计与实现

基于面向对象建模语言AML ,开发了一种在软件模型中实现动态导航的方法。这种方法通过将软件模型不同侧面的视图映射到一种集成支撑表示中 ,提供动态导航算法 ,从而实现软件开发者同时对软件系统不同侧面模型的访问     

Intelligent approaches for generating assembly drawings from 3-D computer models of mechanical products

In order to reduce the time of mechanical product design and ensure the high quality of their assembly drawings, this paper develops an intelligent approach for generating assembly drawings automatically from three-dimensional (3-D) computer assembly models of mechanical products by simulating the experienced human designer's thinking mode with the aid of computer graphics and knowledge-based expert system. The key issues include the strategies and methods for selecting the necessary views in an assembly drawing, determining necessary sectional views in each view, eliminating the unreasonable projective overlap of the components in each view, and minimizing the numbers of both the views in an assembly drawing and the sectional views in each view. Based on the approach, corresponding software prototype was developed. Finally, it is demonstrated, from an example of the fixture in a modularized drilling machine, that its assembly drawing was generated successfully using this intelligent software prototype.     

Semi-automated architectural abstraction specifications for supporting software evolution

In this paper we present an approach for supporting the semi-automated architectural abstraction of architectural models throughout the software life-cycle. It addresses the problem that the design and implementation of a software system often drift apart as software systems evolve, leading to architectural knowledge evaporation. Our approach provides concepts and tool support for the semi-automatic abstraction of architecture component and connector views from implemented systems and keeping the abstracted architecture models up-to-date during software evolution. In particular, we propose architecture abstraction concepts that are supported through a domain-specific language (DSL). Our main focus is on providing architectural abstraction specifications in the DSL that only need to be changed, if the architecture changes, but can tolerate non-architectural changes in the underlying source code. Once the software architect has defined an architectural abstraction in the DSL, we can automatically generate architectural component views from the source code using model-driven development (MDD) techniques and check whether architectural design constraints are fulfilled by these models. Our approach supports the automatic generation of traceability links between source code elements and architectural abstractions using MDD techniques to enable software architects to easily link between components and the source code elements that realize them. It enables software architects to compare different versions of the generated architectural component view with each other. We evaluate our research results by studying the evolution of architectural abstractions in different consecutive versions of five open source systems and by analyzing the performance of our approach in these cases.