以决策为中心的软件体系结构设计方法

提出针对体系结构层次设计的决策抽象和问题分解原则,以及基于该原则的一种以决策为中心的体系结构设计方法.该方法从决策的视角对体系结构进行建模,并通过一个从导出体系结构关键问题到对体系结构方案决策的过程完成设计,还在其中实现了候选体系结构方案的自动合成以及设计决策与理由的捕捉.这种以决策为中心的方法切合体系结构层次的特点,降低了体系结构设计的复杂性和设计决策与理由捕捉的代价.     

软件体系结构讲座：（八）体系结构设计工具

本讲介绍几个软件体系结构设计的工具系统,它们是:UniCon(一个体系结构描述的语言和工具集),Ae-sop(一个构造特殊风格的体系结构设计环境)和WRIGHT(一个支持体系结构规格说明的语言)。     

一种建模软件体系结构非功能属性的方法

非功能属性的处理一直是困扰着研究人员和实践者的难题.针对体系结构设计阶段早期,提出一种建模非功能属性的方法.该方法利用面向方面软件开发中的关注点多维分离原理,提出建模软件体系结构的\"1+X\"模型,并在此基础上进一步划分体系结构非功能属性的维度,归纳各个维度上的关注点,利用XML对维度和关注点进行规约.该模型为后续设计面向方面的软件体系结构奠定了基础,为体系结构设计人员提供了方法支持,而且该成果可以直接用于不同领域内的软件体系结构设计.     

软件体系结构建模研究

提出了软件体系结构工程的概念,建立了软件体系结构的生命周期模型并对软件体系结构进行了分类和建模,介绍了几种典型的软件体系结构语言,提出了一个基于时序逻辑的形式化体系结构语言－ＸＹＺ／ＳＡＥ．该语言可作为系列化时序逻辑语言族ＸＹＺ／Ｅ的子语言,支持对软件体系结构可的构件,连接件和配置的描述,并可在统一的框架下描述软件体系的结构静态行为和动态行为。     

开放式软件体系结构描述语言设计

本文针对软件体系结构描述语言的发展趋势和研究特点,提出并实现了一种开放式的软件体系结构描述语言ＣＯＡＤＬ,ＣＯＡＤＬ不仅使得工作人员可以方便的使用其对软件系统进行软件体系结构设计和开发,而且还为有关工作人员提供了进一步利用其它现有体系结构语言的扩展接口。     

一种总线型软件体系结构的设计与应用

在构造基于面向对象技术的软件系统中,采用良好的软件体系结构可以有效地提高整个系统的可扩展性、灵活性、可插入性,获得较好的可复用性。针对这一点,提出了一种基于组件和中间件技术的总线型软件体系结构,该结构以面向对象技术为基础,并借鉴了计算机硬件系统的设计思想。文中介绍了该体系结构的设计和应用情况,以实例说明了该结构有助于使系统的结构定义更加清晰和具备良好的“可拔插”特性。     

基于模式的软件体系结构建模

文中给出了一种应用程序组件的领域建模方法,将组件静态方面的面向对象建模(类图)、组件行为或功能等动态方面的基于模式的建模(模式实例模型)与代码生成实现技术结合起来。并试图用模式描述组件体系结构风格,指导如何构造和组织一个系统。基于模式的软件体系结构设计方法可在很短的时间内创建各种组件,并通过改变模型中的抽象体系结构特性来满足应用程序中的体系结构要求,因而该方法是切实可行的。     

基于反射机制的软件体系结构重用方法及工具

针对软件开发早期阶段软件资源重用进展缓慢,反射机制在代码重用方面取得成功但还没有用于软件体系结构及其组成元素的重用等问题,提出一种支持软件体系结构设计时重用的反射机制,概述基于反射机制的软件体系结构重用方法。给出基于反射机制的软件体系结构重用的支撑工具ArchBean Studio的设计和实施过程。利用该方法,设计人员通过重用软件体系结构及其组成元素能高效地完成软件设计任务。     

软件体系结构设计的团体特征

本文介绍了软件体系结构的研究现状,研究了软件体系结构设计的一般模型,概括和分析了设计过程的各个阶段以及它们之间如何组成一个团队,论述了设计过程各阶段协作表现出来的团体特征。     

一种基于进程代数的软件体系结构描述语言PEADL

对性能评价进程代数(PEPA)扩展,提出具有时序特征的随机进程代数(ESPA)。在此基础上进一步提出一种软件体系结构描述语言(PEADL)。介绍PEADL的语法和语义,并通过三层C/S结构应用系统展示PEADL的表述能力。     

Documenting after the fact: Recovering architectural design decisions

Software architecture documentation helps people in understanding the software architecture of a system. In practice, software architectures are often documented after the fact, i.e. they are maintained or created after most of the design decisions have been made and implemented. To keep the architecture documentation up-to-date an architect needs to recover and describe these decisions.This paper presents ADDRA, an approach an architect can use for recovering architectural design decisions after the fact. ADDRA uses architectural deltas to provide the architect with clues about these design decisions. This allows the architect to systematically recover and document relevant architectural design decisions. The recovered architectural design decisions improve the documentation of the architecture, which increases traceability, communication, and general understanding of a system.     

A framework for analysis and design of software reference architectures

Context

A software reference architecture is a generic architecture for a class of systems that is used as a foundation for the design of concrete architectures from this class. The generic nature of reference architectures leads to a less defined architecture design and application contexts, which makes the architecture goal definition and architecture design non-trivial steps, rooted in uncertainty.

Objective

The paper presents a structured and comprehensive study on the congruence between context, goals, and design of software reference architectures. It proposes a tool for the design of congruent reference architectures and for the analysis of the level of congruence of existing reference architectures.

Method

We define a framework for congruent reference architectures. The framework is based on state of the art results from literature and practice. We validate our framework and its quality as analytical tool by applying it for the analysis of 24 reference architectures. The conclusions from our analysis are compared to the opinions of experts on these reference architectures documented in literature and dedicated communication.

Results

Our framework consists of a multi-dimensional classification space and of five types of reference architectures that are formed by combining specific values from the multi-dimensional classification space. Reference architectures that can be classified in one of these types have better chances to become a success. The validation of our framework confirms its quality as a tool for the analysis of the congruence of software reference architectures.

Conclusion

This paper facilitates software architects and scientists in the inception, design, and application of congruent software reference architectures. The application of the tool improves the chance for success of a reference architecture.     

Past and future of software architectural decisions – A systematic mapping study

ContextThe software architecture of a system is the result of a set of architectural decisions. The topic of architectural decisions in software engineering has received significant attention in recent years. However, no systematic overview exists on the state of research on architectural decisions.ObjectiveThe goal of this study is to provide a systematic overview of the state of research on architectural decisions. Such an overview helps researchers reflect on previous research and plan future research. Furthermore, such an overview helps practitioners understand the state of research, and how research results can help practitioners in their architectural decision-making.MethodWe conducted a systematic mapping study, covering studies published between January 2002 and January 2012. We defined six research questions. We queried six reference databases and obtained an initial result set of 28,895 papers. We followed a search and filtering process that resulted in 144 relevant papers.ResultsAfter classifying the 144 relevant papers for each research question, we found that current research focuses on documenting architectural decisions. We found that only several studies describe architectural decisions from the industry. We identified potential future research topics: domain-specific architectural decisions (such as mobile), achieving specific quality attributes (such as reliability or scalability), uncertainty in decision-making, and group architectural decisions. Regarding empirical evaluations of the papers, around half of the papers use systematic empirical evaluation approaches (such as surveys, or case studies). Still, few papers on architectural decisions use experiments.ConclusionOur study confirms the increasing interest in the topic of architectural decisions. This study helps the community reflect on the past ten years of research on architectural decisions. Researchers are offered a number of promising future research directions, while practitioners learn what existing papers offer.     

Enriching software architecture documentation

The effective documentation of Architectural Knowledge (AK) is one of the key factors in leveraging the paradigm shift toward sharing and reusing AK. However, current documentation approaches have severe shortcomings in capturing the knowledge of large and complex systems and subsequently facilitating its usage. In this paper, we propose to tackle this problem through the enrichment of traditional architectural documentation with formal AK. We have developed an approach consisting of a method and an accompanying tool suite to support this enrichment. We evaluate our approach through a quasi-controlled experiment with the architecture of a real, large, and complex system. We provide empirical evidence that our approach helps to partially solve the problem and indicate further directions in managing documented AK.     

An Empirical Method for Selecting Software Reliability Growth Models

Estimating remaining defects (or failures) in software can help test managers make release decisions during testing. Several methods exist to estimate defect content, among them a variety of software reliability growth models (SRGMs). SRGMs have underlying assumptions that are often violated in practice, but empirical evidence has shown that many are quite robust despite these assumption violations. The problem is that, because of assumption violations, it is often difficult to know which models to apply in practice. We present an empirical method for selecting SRGMs to make release decisions. The method provides guidelines on how to select among the SRGMs to decide on the best model to use as failures are reported during the test phase. The method applies various SRGMs iteratively during system test. They are fitted to weekly cumulative failure data and used to estimate the expected remaining number of failures in software after release. If the SRGMs pass proposed criteria, they may then be used to make release decisions. The method is applied in a case study using defect reports from system testing of three releases of a large medical record system to determine how well it predicts the expected total number of failures.     

Model driven architecture: Principles and practice

Model Driven Architecture (MDA) is an approach to application modeling and generation that has received a lot of attention in recent months. Championed by the Object Management Group (OMG), many organizations are now looking at the ideas of MDA as a way to organize and manage their application solutions, tool vendors are explicitly referring to their capabilities in terms of MDA compliance, and the MDA lexicon of platform-specific and platform-independent models is now widely referenced in the industry. In spite of this interest and market support, there is little clear guidance on what MDA means, where we are in its evolution, what is possible with todays technology, and how to take advantage of it in practice. This paper addresses that need by providing an analysis of how modeling is used in industry today, the relevance of MDA to todays systems, a classification of MDA tooling support, and examples of its use. The paper concludes with a set of recommendations for how MDA can be successful in practice.     

一种基于C#的通用软件安装程序的架构设计与实现

可以说每个商业化软件都必须具备安装工具,使用系统软件自带的打包程序有时很难满足实际需求,为此提出了一种基于C#的通用软件安装程序的架构,给出了实现这一架构的设计方法和关键代码.通过该架构,可以非常容易地实现安装程序的功能扩展和代码维护.     

建筑体系结构与软件构架

一个好的软件构架可以促进应用系统的开发,文中建筑体系结构的一些重要概念引出了软件的构架的重要概念并举出一些例子加以分析说明。     

A pattern language for designing e-business architecture

The pattern language for e-business provides a holistic support for developing software architectures for the e-business domain. The pattern language contains four related pattern categories: Business Patterns, Integration Patterns, Application Patterns, and Runtime Patterns. These pattern categories organise an e-business architecture into three layers—business interaction, application infrastructure and middleware infrastructure—and provide reusable design solutions to these layers in a top-down decomposition fashion. Business and Integration Patterns partition the business interaction layer into a set of subsystems; Application Patterns provide a high-level application infrastructure for these subsystems and separate business abstractions from their software solutions; Runtime Patterns then define a middleware infrastructure for the subsystems and shield design solutions from their implementations. The paper describes, demonstrates and evaluates this pattern language.