基于可集成性的细粒度结构演化

软件结构为达到软件系统质量属性的一种手段，对于基于可集成性的软件结构研究，提出小粒度结构演化（FGSAE，Fine-Grained Architectural Evolution)，改变既有系统的软件结构，增加模块独立性，显示表达可集成性的模块接口，满足质量属性需求，为黑盒开发策略的大粒度复用做预备，可以延伸软件功能，延长软件生命周期，达到提高开发效益的目的，以2个相关概念模型－软件结构（Software Architecture,SA），FGSAE，说明FGSAE如何指导软件变换，满足可集成性的需求，并提出关键活动内容，最后以一个成功的案例，即在Internet上运行的西洋棋艺游戏系统，验证FGSAE的有效性。     

基于DVB数据广播系统的软件结构

根据DVB数据广播的标准，设计了底层数据广播的软件结构，以提供独立于硬件平台的软件接口。介绍了DVB数据广播标准，并讨论了系统的设计思路，软件结构及具体应用实例。     

IP交换机中关键软件的研究与实现

IP交换机是宽带高速智能网络中的重要设备，本文综合对比了几款IP交换机，给出了IP交换机中的一般软件结构．对软件中最为关键的操作系统、路由软件和驱动程序作了详细的分析．并在此基础上阐述了选择、设计的一般方法，以LT-501IP交换机的设计实现为实例，描述了重点函数和功能模块的设计实现的算法和流程．     

多层软件结构技术及其实现

软件的系统结构在软件的开发中越来越重要,它可以分为单层、二层、三层或多层。基于COM的多层软件结构是一种典型的应用,多层软件结构的关键技术是分布式事物处理技术和MTS。文章最后给出了一个多层软件的应用实例。     

SAIS:一个基于规则的软件结构分析集成系统

作为软件工程研究的领域之一,软件再工程(Re-Engineering)在最近几年引起了人们广泛的关注,软件再工程的关键是:从现有原代码所提供的信息中去获得和恢复丢失的系统设计和规格说明信息的能力。本文介绍了SAIS,一个基于规则的软件结构分析集成系统,它被设计用于提供对软件维护和软件逆向工程活动的部分支撑。文章简要描述了SAIS的设计、实现、应用和特点。     

小型电源监控系统软件的设计和实现

介绍了一套监控系统的软件结构的设计与实现，从软件角度介绍了各个模块从设计到实现的全过程，并针对电源监控的特殊要求给出了具体的解决方法。     

活塞自动测量系统的软件结构

针对活塞自动测量系统的特点和设计要求，讨论了该系统的组成、软件结构、数据库设计以及软件的开发平台。     

基于WindowsDNA框架的GIS软件结构初探

GIS软件结构体系作为GIS研究的个重点,日益受到们人们的重视。本文简介WindowsDNA结构体系后,提出了一种GIS的软件结构框架,并详述该结构的逻辑组成及物理配置。这种结构的GIS软件可以封装异地GIS数据和快速的添加及删除GIS功能组件,是快速开发GIS软件的一个途径。     

H20—20交换机的测试系统设计

文章主要介绍了H20—20交换机系统测试设备(STE)的总体设计，就STE的应用与功能、硬件结构以及各硬件组成模块实现的功能、软件结构以及各软件组成模块实现的功能、传统测量仪器和虚拟测量仪器的特点和应用进行了一定的介绍和分析。     

面向对象软件度量工具的软件结构

利用软件度量工具度量程序源码的各类质量属性是提高程序质量的一个重要方法．目前,面向对象语言已逐渐成为主流编程语言,度量基于对象技术的软件成为必然的需求．然而,由于面向对象语言数目众多,许多面向对象语言又都在发展中,用户所需要的度量也不尽相同,各种分散的需求对度量工具的灵活性与通用性提出了挑战．首先给出了一个适用于ＯＯ语言软件度量工具的一个灵活的软件结构,然后在分析了各类软件度量的基础上,解析了该结     

An optimization framework for “build-or-buy” decisions in software architecture

Building a software architecture that meets functional requirements is a quite consolidated activity, whereas keeping high quality attributes is still an open challenge. In this paper we introduce an optimization framework that supports the decision whether to buy software components or to build them in-house upon designing a software architecture. We devise a non-linear cost/quality optimization model based on decision variables indicating the set of architectural components to buy and to build in order to minimize the software cost while keeping satisfactory values of quality attributes. From this point of view, our tool can be ideally embedded into a Cost Benefit Analysis Method to provide decision support to software architects. The novelty of our approach consists in building costs and quality attributes on a common set of decision variables related to software development. We start from a special case of the framework where the quality constraints are related to the delivery time and the product reliability, and the model solution also devises the amount of unit testing to be performed on built components. We generalize the framework formulation to represent a broader class of architectural cost-minimization problems under quality constraints, and discuss advantages and limitations of such approach.     

Architecting Fault Tolerance with Exception Handling: Verification and Validation

When building dependable systems by integrating untrusted software components that were not originally designed to interact with each other, it is likely the occurrence of architectural mismatches related to assumptions in their failure behaviour. These mismatches, if not prevented during system design, have to be tolerated during runtime. This paper presents an architectural abstraction based on exception handling for structuring fault-tolerant software systems. This abstraction comprises several components and connectors that promote an existing untrusted software element into an idealised fault-tolerant architectural element. Moreover, it is considered in the context of a rigorous software development approach based on formal methods for representing the structure and behaviour of the software architecture. The proposed approach relies on a formal specification and verification for analysing exception propagation, and verifying important dependability properties, such as deadlock freedom, and scenarios of architectural reconfiguration. The formal models are automatically generated using model transformation from UML diagrams: component diagram representing the system structure, and sequence diagrams representing the system behaviour. Finally, the formal models are also used for generating unit and integration test cases that are used for assessing the correctness of the source code. The feasibility of the proposed architectural approach was evaluated on an embedded critical case study. Patrick Brito is supported by Fapesp/Brazil under Grant No. 06/02116–2 and CAPES/Brazil under Grant No. 0722–07–3. Cecília Rubira is partially supported by CNPq/Brazil under Grant Nos. 301446/2006–7 and 484138/2006–5.     

An empirical investigation of architectural prototyping

Architectural prototyping is the process of using executable code to investigate stakeholders’ software architecture concerns with respect to a system under development. Previous work has established this as a useful and cost-effective way of exploration and learning of the design space of a system and in addressing issues regarding quality attributes, architectural risks, and the problem of knowledge transfer and conformance. However, the actual industrial use of architectural prototyping has not been thoroughly researched so far. In this article, we report from three studies of architectural prototyping in practice. First, we report findings from an ethnographic study of practicing software architects. Secondly, we report from a focus group on architectural prototyping involving architects from four companies. And, thirdly, we report from a survey study of 20 practicing software architects and software developers. Our findings indicate that architectural prototyping plays an important and frequent role in resolving problems experimentally, but less so in exploring alternative solutions. Furthermore, architectural prototypes include end-user or business related functionality rather than purely architectural functionality. Based on these observations we provide recommendations for effective industrial architectural prototyping.     

Architecture for embedded open software ecosystems

Software is prevalent in embedded products and may be critical for the success of the products, but manufacturers may view software as a necessary evil rather than as a key strategic opportunity and business differentiator. One of the reasons for this can be extensive supplier and subcontractor relationships and the cost, effort or unpredictability of the deliverables from the subcontractors are experienced as a major problem.The paper proposes open software ecosystem as an alternative approach to develop software for embedded systems, and elaborates on the necessary quality attributes of an embedded platform underlying such an ecosystem. The paper then defines a reference architecture consisting of 17 key decisions together with four architectural patterns, and provides the rationale why they are essential for an open software ecosystem platform for embedded systems in general and automotive systems in particular.The reference architecture is validated through a prototypical platform implementation in an industrial setting, providing a deeper understanding of how the architecture could be realised in the automotive domain.Four potential existing platforms, all targeted at the embedded domain (Android, OKL4, AUTOSAR and Robocop), are evaluated against the identified quality attributes to see how they could serve as a basis for an open software ecosystem platform with the conclusion that while none of them is a perfect fit they all have fundamental mechanisms necessary for an open software ecosystem approach.     

Software Quality Evaluation Based on Expert Judgement

A method using expert judgement for the evaluation of software quality is presented. The underlying principle of the approach is the encoding of experts' tacit knowledge into probabilistic measures associated with the achievement level of software quality attributes. An aggregated quality measure is obtained based on preference statements related to the quality attributes. The technical objectives of the paper are to develop of a generic and operationally feasible measurement technique to transform the tacit knowledge of a software expert to a probability distribution depicting his/her uncertainty of the level of achievement related to a quality attribute; to develop rules for the construction of a consensus probability measure based on expert-specific probability measures; to derive a framework for specifying software quality strategy and for evaluating the acceptance of a software produced in a software development process;The above technical developments are used to support group decision-making regarding the launch or implementation decision of a software version; the allocation of resources during the software development process.     

一种新的面向方面的架构描述概念模型研究*

软件架构的描述和设计决定了软件的质量和生命。作为方面的横切关注点横跨在多个架构组件中,影响了模块间的内聚性和耦合度,从而降低了软件的可重用性,增加了维护的难度。目前提出的许多架构描述方法均未能对存在的横切关注点进行恰当的描述和定位,所以在软件的架构描述方法中引入了方面的概念机制来解决这些问题。基于IEEE 14712000中提出的架构描述概念模型,引入用例视图提出了一种新的面向方面的架构描述概念模型。该模型能够在架构描述中精确地描述和处理横切关注点即增加方面这一抽象层,从而提高软件系统的维护性、重用性和     

面向对象软件度量工具的研究与实现

利用软件度量工具对程序源代码的各类质量属性度量已是提高程序质量的一个重要方法,文章提出了一个以中间件为核心适用于多种面向对象程序设计语言的软件度量工具的灵活的软件结构,同时介绍了自行设计实现的度量工具,最后指出了下一步的的研究方向。     

Playing Detective: Reconstructing Software Architecture from Available Evidence

Because a system's software architecture strongly influences its quality attributes such as modifiability, performance, and security, it is important to analyze and reason about that architecture. However, architectural documentation frequently does not exist, and when it does, it is often out of sync with the implemented system. In addition, it is rare that software development begins with a clean slate; systems are almost always constrained by existing legacy code. As a consequence, we need to be able to extract information from existing system implementations and utilize this information for architectural reasoning. This paper presents Dali, an open, lightweight workbench that aids an analyst in extracting, manipulating, and interpreting architectural information. By assisting in the reconstruction of architectures from extracted information, Dali helps an analyst redocument architectures, discover the relationship between as-implemented and as-designed architectures, analyze architectural quality attributes and plan for architectural change.     

面向对象软件度量工具的设计实现

利用软件度量工具对程序源代码的各类质量属性度量，对于提高程序质量具有重要意义。提出了一个适用于多种面向对象程序设计语言的软件度量工具的灵活软件结构，该结构的核心是以数据库为中间件。给出了该工具的结构，总结了该结构的特点和实用性，给出了以图形形式显示的分析结果和度量指标与质量特征之间关系的实验结果。