软件体系结构风格研究现状及存在的问题

针对现有软件体系结构风格定义在客观性和全面性方面存在的不足,从客观角度出发,站在软件工程的高度从多个方面对软件体系结构风格进行定义;同时通过研究分析软件体系结构风格的研究现状,发现并指出其四个重点研究方向及各自存在的问题。     

基于消息总线的C3I系统软件体系结构研究

针对军用指挥自动化软件缺乏顶层设计、各种软件系统相互独立、综合集成难度大、不利于软件管理和维护等问题,提出一种以消息总线为核心的C^3I系统软件体系结构,并给出了消息总线和基于消息总线的应用软件设计方法,可以满足多兵种合成的C^3I系统软件的综合集成。该体系结构和实现方法已经在军队重点型号中得到应用。     

基于架构级容错的C2风格研究

为减少基于构件开发的软件系统中构件间的相互依赖,实现系统架构的动态演化,研究了一种被称为C2的软件体系结构风格.在C2风格的基础上,介绍并分析了通过对第三方构件进行保护包装,把这种现有的商用构件转换成一种理想化C2构件iC2C,以在架构级上达到系统容错的目的.通过研究iC2C的内部结构,提出了一种iC2C的实现架构.并结合实例把它应用在了具体的项目实践中,实验结果表明了该架构的可行性与可塑性.     

几种常见软件体系结构模型的分析

随着计算机科学技术的发展,软件的规模和应用领域迅速扩大,造成了软件复杂程度的不断加大,所以高效地开发出高质量的软件产品越来越困难,于是软件开发人员开始关注于如何找到理解软件的更好途径和是否存在更好的途径来构造复杂的大型软件系统。研究软件体系结构就是解决这些问题的有力方法,经过对常见软件体系结构模型的分析后提出：根据待开发软件的应用场合和所处理问题的特点选取合适的体系结构,有利于缩短开发周期、节约开发成本和软件维护。     

A style for integrating MS‐Windows software applications to client–server systems using Java technology

Developing software systems by integrating the existing applications/systems over the network has become an established and practical technique. The Microsoft (MS) Windows operating systems today support a huge number of software applications. If these commercial applications could be transformed to software components, this may accelerate the construction of new components. This paper proposes an architectural style to support a three‐phase process for integrating MS‐Windows applications in a distributed system using Java technologies. This style provides a solution with clear documentation and sufficient information that is helpful for the rapid integration of MS‐Windows applications. Finally, an exemplary graphical construction part management system that assembles two MS‐Windows applications was developed in this study to demonstrate the feasibility of this style. Copyright © 2006 John Wiley & Sons, Ltd.     

基于软件体系结构的可复用构件模型

在分析了构件间各种操作的基础上,将软件体系结构的概念引入现有的构件模型,用于对复合构件进行描述,从而改进了现有的构件模型,给出了一种基于软件体系结构的可复用构件模型,并给出了该模型的应用.     

构件层级开发模型的研究与应用

设计了构件层级开发模型,重点研究了模型中界面表现层、业务逻辑层和数据通道层,并结合构件层级开发模型给出了全景监测构件实例。构件层级开发模型采用层次化开发方法,明确了各层功能边界和实现方法,解决了构件内部组织和结构问题,确保清晰的功能职责划分,分离构件开发的关注点,提高了构件的可复用性以及软件的开发效率。     

面向构件的门诊部信息管理系统软件架构

构件化软件的设计集中于软件体系结构设计,其最主要的特征在于目标系统由大量可复用构件组成,这就要求在设计阶段应当设计出满足需求的软件体系结构。以一个门诊部信息管理系统软件架构为例,介绍了面向构件的软件架构方法,并对系统架构选型进行分析,提出了本系统的软件架构,为基于构件技术的系统实现提供良好的依据。     

基于Agent的软件体系结构研究

软件体系结构的使用是提高软件质量、减少软件开销和促进软件生产率提高的最有效方法之一,面向Agent技术的提出为复杂分布式问题的求解找到了办法.分析了软件体系结构和软件Agent技术的主要内容,提出基于Agent的软件体系结构,阐明了基于Agent的软件体系结构的总体结构及其在大型软件开发中的应用.     

Using software evolution to focus architectural recovery

Ideally, a software project commences with requirements gathering and specification, reaches its major milestone with system implementation and delivery, and then continues, possibly indefinitely, into an operation and maintenance phase. The software system's architecture is in many ways the linchpin of this process: it is supposed to be an effective reification of the system's technical requirements and to be faithfully reflected in the system's implementation. Furthermore, the architecture is meant to guide system evolution, while also being updated in the process. However, in reality developers frequently deviate from the architecture, causing architectural erosion, a phenomenon in which the initial, “as documented' architecture of an application is (arbitrarily) modified to the point where its key properties no longer hold. Architectural recovery is a process frequently used to cope with architectural erosion whereby the current, “as implemented” architecture of a software system is extracted from the system's implementation. In this paper we propose a light-weight approach to architectural recovery, called Focus, which has three unique facets. First, Focus uses a system's evolution requirements to isolate and incrementally recover only the fragment of the system's architecture affected by the evolution. In this manner, Focus allows engineers to direct their primary attention to the part of the system that is immediately impacted by the desired change; subsequent changes will incrementally uncover additional parts of the system's architecture. Secondly, in addition to software components, which are the usual target of existing recovery approaches, Focus also recovers the key architectural notions of software connector and architectural style. Finally, Focus does not only recover a system's architecture, but may in fact rearchitect the system. We have applied and evaluated Focus in the context of several off-the-shelf applications and architectural styles to date. We discuss its key strengths and point out several open issues that will frame our future work.     

Assessing architectural drift in commercial software development: a case study

Objectives: Software architecture is perceived as one of the most important artefacts created during a system's design. However, implementations often diverge from their intended architectures: a phenomenon called architectural drift. The objective of this research is to assess the occurrence of architectural drift in the context of de novo software development, to characterize it, and to evaluate whether its detection leads to inconsistency removal. Method: An in vivo, longitudinal case study was performed during the development of a commercial software system, where an approach based on Reflexion Modelling was employed to detect architectural drift. Observation and think‐aloud data, captured during the system's development, were assessed for the presence and types of architectural drift. When divergences were identified, the data were further analysed to see if identification led to the removal of these divergences. Results: The analysed system diverged from the intended architecture, during the initial implementation of the system. Surprisingly however, this work showed that Reflexion Modelling served to conceal some of the inconsistencies, a finding that directly contradicts the high regard that this technique enjoys as an architectural evaluation tool. Finally, the analysis illustrated that detection of inconsistencies was insufficient to prompt their removal, in the small, informal team context studied. Conclusions: Although the utility of the approach for detecting inconsistencies was demonstrated in most cases, it also served to hide several inconsistencies and did not act as a trigger for their removal. Hence additional efforts must be taken to lessen architectural drift and several improvements in this regard are suggested. Copyright © 2010 John Wiley & Sons, Ltd.     

构件化软件演化信息建模和获取方法研究

为了清晰、全面地获取构件化软件的演化历史信息, 通常需要提供演化信息表示和建模的有效手段。分析了构件化软件演化信息获取所需解决的若干问题, 提出了在软件构件模型基础上, 增加建模元素以表示软件演化信息的方法; 通过结合软件配置管理系统, 实现对构件化软件变化过程的追踪和管理。基于该方法和相应的系统支持, 可以为实施软件重构和后期开发提供指导。     

支持构件演化的软件配置管理研究

基于构件的软件开发作为一种全新的软件开发方法,与传统的软件开发方式不同,配置管理的需求与传统的配置管理方法也有了很大的不同.在基于构件软件开发的过程中,如何以一种良好的风格和技术来对构件变化进行控制,保持构件系统的一致性、稳定性是软件开发者历来追求的目标.分析了基于构件软件开发过程中构件演化对配置管理技术的新需求,探讨了配置管理的几个关键技术,并提出了一种度量构件演化过程的方法,从而把构件的整个演化过程置于配置管理的支持之下.     

软件体系结构模型单层化的一致性保障方法

在软件体系结构(software architecture,简称SA)设计中,复合构件是具有内部结构的构件,它可以对复杂的SA模型进行层次化的组织.尽管大多数体系结构描述语言都支持复合构件,但常见的SA模型分析与验证工具仅支持单层的SA模型作为输入,且目前的主流构件运行平台都不支持带有内部结构的复合构件模型.因此,有必要将多层的SA模型转化为单层的SA模型(即"单层化")."单层化"的关键在于如何保证"单层化"前后SA模型的一致性.对该问题及其解决方案进行了系统而深入的研究,给出了SA模型一致性的形式化定义.在此基础上,提出了SA模型"单层化"的基本原则以及过程指南,并以一个构件化的邮件客户端为例,验证了该方法的可行性.     

基于产品线体系结构的软件工程过程模型研究

在借鉴现代工业的组织体系、管理规范、生产流程的基础上,针对基于软件产品线体系结构的软件工程方法和开发过程进行了系统研究,提出了基于产品线体系结构而实现软件工程化生产的N-生命周期模型.该模型的建立,对研究基于软件产品线体系结构的集成化软件工程环境,进而实现软件产品的工业化生产是非常有益且重要的.     

一种软件体系结构复杂性的评价方法

为了满足软件体系结构复杂性的预测和评价需求,通过抽取构件之间的连接,提出了基于复合关系的分层式软件体系结构,从而能够清晰、准确地表达构件之间的关系。在该结构基础上,提出了基于加权图的复杂性评价模型,并结合实例分析了模型的使用效果。模型能够准确地刻画系统结构及构件关系,而且能够较为客观地定量评估系统结构复杂性。它具有实现过程简单、通用性强等特点。     

一种面向方面软件体系结构模型*

为了分离软件系统中的核心关注点和横切关注点,通过引入面向方面软件开发的思想设计了一种面向方面软件体系结构模型,并详细分析了该模型的三个基本构成单元,即构件、连接件和方面构件。最后通过一个网上支付实例验证了该模型具有一定的理论意义和实用价值。     

软件组件技术在商业连锁领域MIS中的应用

软件组件技术的应用有利于提高商业连锁企业MIS的开发效率，改良系统结构，文章探讨了软件组件技术在商业连锁MIS开发中应用的意义、规范及体系结构等方面的问题。     

RFDI软件架构设计及状态分析构件实现

RFDI(radar fault detection and isolation)软件通用性与雷达电路硬件及故障分析方法的不断更新是一对矛盾.如何设计一个通用的RFDI软件,以适应雷达电路的不断改进及诊断分析方法的不断更新是一个非常现实的课题.详细分析雷达故障检测和隔离的方法,将RFDI软件框架与故障状态分析方法及特征数据采集分离,给出了一种新的RFDI系统软件的架构,并对基于构件技术故障状态分析方法进行了研究,给出了一种故障状态分析构件的COM实现,其具有较强的可扩展性和继承性.     

支持动态负载平衡的分层消息队列模型

中间件技术为解决异构分布式环境下的负载平衡问题提供了有力的工具,但传统的消息中间件负载平衡的实现较为复杂,其动态参数繁多且容易带来额外开销。提出了一种分层消息队列模型,该模型中利用队列组管理器对分布式队列进行组管理,并提供了丰富的任务分配策略。在该模型的基础上提出动态负载平衡实现方案:通过基于队列的阈值阈长模型实时监控成员队列的负载情况,采用集中式调度进行负载信息搜集和负载平衡决策,结合负载迁移和队列组管理进行过载处理。