软件体系结构风格的实例研究

软件体系结构研究领域中，风格的研究与应用是一个重要的领域。本文讨论了软件体系结构的概念和风格，在此基础上特别对CORBA，基于Web的分布式系统结构，领域专家系统，基于商业背景的可重用软件体系结构等内容进行了讨论，并给出了它们相关风格。     

几种新型软件体系结构风格的分析

软件体系结构的提出对软件重用机制和软件开发效率的提高具有非常重要的意义。软件体系结构的使用是提高软件开发质量、减少软件开销和促进软件生产率提高的最有效方法之一。采用定性分析、比较研究等多种方法,实现了几种新型软件体系结构风格的剖析。给出了软件体系结构及软件体系结构风格的定义,阐述了几种新型软件体系结构风格中关键要素的定义及特性及其风格的主要内容,分析了几种新型软件体系结构风格的特点。     

几种新型软件体系结构风格的分析

软件体系结构的提出对软件重用机制和软件开发效率的提高具有非常重要的意义.软件体系结构的使用是提高软件开发质量、减少软件开销和促进软件生产率提高的最有效方法之一.采用定性分析、比较研究等多种方法,实现了几种新型软件体系结构风格的剖析.给出了软件体系结构及软件体系结构风格的定义,阐述了几种新型软件体系结构风格中关键要素的定义及特性及其风格的主要内容,分析了几种新型软件体系结构风格的特点.     

软件体系结构的发展与研究

该文介绍了软件体系结构的概念、目前的研究方向、几种软件体系结构风格和它们各自的优缺点,分析了用软件体系结构指导软件开发的优点,最后介绍了软件体系结构的理论在一个实际应用系统的设计开发中的运用。     

一种基于PLM系统的软件体系结构风格的研究

一个良好的软件体系结构对一个应用软件系统起着决定性的作用.软件体系结构风格决定着一个系统的软件体系结构.本文通过比较C/S和正交两种常见的软件体系结构风格,指出这两种体系结构风格可以混合使用,并给出基于PLM系统的实例.     

软件体系结构（风格）综述

报告了当前行业内对软件体系结构的研究情况．结合典型的软件体系结构概念,给出了软件体系结构的定义和研究意义。目的在干展示软件体系结构及其风格在实践项目中的应用。对当前主流风格的多种软件体系结构在原理、特点方面进行了仔细的研究,并阐述了各体系结构的优缺点。     

基于进程代数的安全软件体系结构建模

分析了基于进程代数的软件体系结构模型的安全性,将相容性检查和互操作性检查从单个软件体系结构推广到不同风格的体系结构风格,扩展基于进程代数的软件体系结构描述语言,通过顺序进程代数项族和预定义的体系结构类型调用对软件体系结构安全建模。通过一个例子介绍了这种建模方法。     

"平台/插件"软件体系结构风格

体系结构发现是软件体系结构研究领域的一个重要方向.近年出现的“平台 插件”软件设计方法,使得发布后的软件产品可以方便地通过安装插件模块而扩展其功能.然而,迄今为止,未见资料将这种结构从软件体系结构的高度进行提炼和描述.本文提出“平台 插件”的软件设计方法是一种软件体系结构风格,并将其称为“平台/插件(Platform/Plug-in)”风格,简写为“P/P风格”.由于软件体系结构和体系结构风格的概念还没有一个标准的定义,文中首先定义了本文使用的模型和概念;研究了“平台/插件”结构应用程序的特点和分类,分析了该类程序的架构,在本文定义的软件体系结构模型的基础上,用统一建模语言UML描述了P/P体系结构风格及P/P风格软件的开发过程.本文工作为需要动态扩展功能的大型软件开发提供了一种可复用的体系结构风格,可以认为,P/P风格是可扩展和可增量升级软件系统的领域体系结构模型.     

软件体系结构及其风格的现状与发展①

软件体系结构是软件工程领域中一个重要的研究课题,是大型软件开发中的关键技术。经过十多年的发展,软件体系结构也超出了传统的对软件设计阶段的支持,逐渐扩展到整个软件生命周期。通过对现有软件体系结构和风格的归纳总结,描述了软件体系结构的主要发展方向及其应用的重要意义。     

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

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

Multi-Agent Architectures as Organizational Structures

A Multi-Agent System (hereafter MAS) is an organization of coordinated autonomous agents that interact in order to achieve common goals. Considering real world organizations as an metaphor, this paper proposes architectural styles for MAS which adopt concepts from organizational theories. The styles are modeled in i*/Tropos, using the notions of actor, goal and actor dependency and are intended to capture needs/wants, delegations and obligations. The proposed architectural styles are evaluated with respect to a set of software quality attributes, such as predictability and adaptability. In addition, we report on a comparative study of organizational and conventional software architectures using a mobile robot control example from the Software Engineering literature. The research reported here was conducted within the scope of the Tropos project, whose objective is to develop a comprehensive agent-oriented software development methodology.     

Effective Knowledge Management: Knowledge, Thinking and the Personal—Corporate Knowledge Nexus Problem

We argue that the intimate relationship between computer architecture and software has produced a professional mindset that is unsuited to the newer, knowledge-based business paradigms. Major software projects are ending in failure or do not yield their maximum potential and we suggest reasons why this is the case. In conclusion, we propose that Management Information Systems Curricula need to be revised to provide students with exposure to and practice in a variety of thinking styles. Organisations must change their structures and management styles if they are serious about managing knowledge. In making our case we briefly review the development of information systems as a discipline and the role of methodologies in the articulation of its paradigm. We end our paper with suggestions for future research.     

Level of detail in UML models and its impact on model comprehension: A controlled experiment

Previous studies have shown that the style and rigor used in UML models vary widely across software projects [1], [2] and [3]. However, notwithstanding the varying use of styles and rigor, little research has been conducted to investigate the drivers and effects of using different styles and rigor in modeling on software development. In this paper, we evaluate Level of Detail (LoD) in UML models as a form of style and rigor in UML modeling. Using a UML model of a library system, we experimentally investigate the impact of LoD on model comprehension. More specifically, we explore whether LoD in UML models affects the correctness and efficiency in comprehending UML models. Using two independent groups of graduate students majoring in computer science, we performed a controlled experiment. The results of the experiment confirm the significant effect of LoD in UML models on model comprehension. Nevertheless, replication of this study is necessary, especially in contexts that involve professional software engineers, to improve the generalizability of the results.     

Architectural styles for distributed processing systems and practical selection method

The software architecture of a system has influences against various software characteristics of the system such as efficiency, reliability, maintainability, etc. For supporting to design the software architecture, we have developed architectural styles for distributed processing systems. The styles classify the architecture for distributed processing systems into nine categories based on the location of data storage and the type of processing between a client and a server. This paper describes our architectural styles and proposes a simple but practical method to select an appropriate architectural style for developing an application system. The selection method introduces the characterization of architectural styles and the characteristic charts to visualize their characteristics of architectural styles. Next, we propose a method to select an appropriate architectural style using the conformity between characteristic charts of a system and architectural styles. We have verified the applicability of this selection method using our customers' real application systems.     

软件体系结构研究与实践

软件体系结构的使用是提高软件开发质量、减少软件开销和促进软件生产率提高的最有效方法之一。对软件体系结构的研究也开始超出传统的对软件设计阶段的支持,并逐步扩展到整个软件生命周期。采用定性分析、比较研究等多种方法,阐述软件体系结构研究的基本内容及软件体系结构实践等相关内容。首先给出了软件体系结构的定义,介绍了软件体系结构风格,然后从软件生命周期的角度阐述了软件体系结构实践及相关内容,最后总结了软件体系结构的研究现状与发展趋势。     

软件体系结构研究与实践

软件体系结构的使用是提高软件开发质量、减少软件开销和促进软件生产率提高的最有效方法之一。对软件体系结构的研究也开始超出传统的对软件设计阶段的支持，并逐步扩展到整个软件生命周期。采用定性分析、比较研究等多种方法，阐述软件体系结构研究的基本内容及软件体系结构实践等相关内容。首先给出了软件体系结构的定义，介绍了软件体系结构风格，然后从软件生命周期的角度阐述了软件体系结构实践及相关内容，最后总结了软件体系结构的研究现状与发展趋势。     

The links between human error diversity and software diversity: Implications for fault diversity seeking

Software diversity is known to improve fault tolerance in N-version software systems by independent development. As the leading cause of software faults, human error is considered an important factor in diversity seeking. However, there is little scientific research focusing on how to seek software fault diversity based on human error mechanisms. A literature review was conducted to extract factors that may differentiate people with respect to human error-proneness. In addition, we constructed a conceptual model of the links between human error diversity and software diversity. An experiment was designed to validate the hypotheses, in the form of a programming contest, accompanied by a survey of cognitive styles and personality traits. One hundred ninety-two programs were submitted for the identical problem, and 70 surveys were collected. Code inspection revealed 23 faults, of which 10 were coincident faults. The results show that personality traits seems not effective predictors for fault diversity as a whole model, whereas cognitive styles and program measurements moderately account for the variation of fault density. The results also show causal relations between performance levels and coincident faults: coincident faults are unlikely to occur at skill-based performance level; the coincident faults introduced in rule-based performances show a high probability of occurrence, and the coincident faults introduced in knowledge-based performances are shaped by the content and formats of the task itself. Based on these results, we have proposed a model to seek software diversity and prevent coincident faults.