基于结构的软件可靠性建模研究进展

软件体系结构作为提高软件系统质量、支持复杂软件开发和复用的重要手段,已经成为软件工程的一个重要研究领域,软件结构的研究对软件可靠性度量也带来的新的问题。分析和总结近年来基于软件体系结构的可靠性建模方法,并对其今后若干研究方向进行了探讨。     

基于SVM的软件可靠性评估

软件可靠性评估是软件可靠性工程研究的一个重要方向。本文运用聚类思想对软件可靠性进行评估,在对软件可靠性因素进行编码的基础上,采用SVM(支持向量机)对其进行聚类研究,实现了软件可靠性的自动化评估。最后通过仿真测试,证明了此方法的有效性和可行性。     

一种基于场景的软件维护性需求分析方法

软件维护性是软件质量的重要属性之一,它在很大程度上决定了软件的后期维护成本。设计赋予软件良好的维护性是软件需求、设计和开发经常忽视的一个问题,也是一个难题。提出了一种基于场景的软件维护性需求分析方法,即通过对软件将来可能发生的维护场景进行分析以获取软件可维护性需求。     

Reliability and safety of real-time systems

Not a day goes by that the general public does not come into contact with a real-time system. As their numbers and importance grow, so do the stakes for software developers. A failure in a critical application may result in great financial loss-or even loss of life. More effort must be expended to analyze the reliability and safety of such systems. Analysis of hardware components in critical applications has matured over the years and commonly followed techniques have emerged. However, methods and techniques for analyzing the reliability and safety of the software part of critical applications are relatively new and still maturing. Yet the vulnerability of the system to software failures is on the rise and may (and in some cases does) exceed hardware failures. Software is not only becoming more prevalent in real-time systems, it is becoming a larger part of real-time systems, in the sense that the amount of effort expended in designing and implementing the software is a larger proportion of the total expended effort     

A Basis for Analyzing Software Architecture Analysis Methods

A software architecture is a key asset for any organization that builds complex software-intensive systems. Because of an architecture's central role as a project blueprint, organizations should analyze the architecture before committing resources to it. An analysis helps to ensure that sound architectural decisions are made. Over the past decade a large number of architecture analysis methods have been created, and at least two surveys of these methods have been published. This paper examines the criteria for analyzing architecture analysis methods, and suggests a new set of criteria that focus on the essence of what it means to be an architecture analysis method. These criteria could be used to compare methods, to help understand the suitability of a method, or to improve a method. We then examine two methods—the Architecture Tradeoff Analysis Method and Architecture-level Modifiability Analysis—in light of these criteria, and provide some insight into how these methods can be improved. Rick Kazman is a Senior Member of the Technical Staff at the Software Engineering Institute of Carnegie Mellon University and Professor at the University of Hawaii. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He also has interests in human-computer interaction and information retrieval. Kazman has created several highly influential methods and tools for architecture analysis, including the SAAM and the ATAM. He is the author of over 80 papers, and co-author of several books, including “Software Architecture in Practice”, and “Evaluating Software Architectures: Methods and Case Studies”. Len Bass is a Senior Member of the Technical Staff at the Software Engineering Institute (SEI). He has written two award winning books in software architecture as well as several other books and numerous papers in a wide variety of areas of computer science and software engineering. He is currently working on techniques for the methodical design of software architectures and to understand how to support usability through software architecture. He has been involved in the development of numerous different production or research software systems ranging from operating systems to database management systems to automotive systems. Mark Klein is Senior Member of the Technical Staff of the Software Engineering Institute. He has over 20 years of experience in research on various facets of software engineering, dependable real-time systems and numerical methods. Klein's most recent work focuses on the analysis of software architectures, architecture tradeoff analysis, attribute-driven architectural design and scheduling theory. Klein's work in real-time systems involved the development of rate monotonic analysis (RMA), the extension of the theoretical basis for RMA, and its application to realistic systems. Klein's earliest work involved research in high-order finite element methods for solving fluid flow equations arising in oil reservoir simulation. He is the co-author two books: “A Practitioner's Handbook for Real-Time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems” and “Evaluating Software Architecture: Methods and Case Studies”. Anthony J. Lattanze is an Associate Teaching Professor at the Institute for Software Research International (ISRI) at Carnegie Mellon University (CMU) and a senior member of the technical staff at the Software Engineering Institute (SEI). Anthony teaches courses in CMUs Masters of Software Engineering Program in Software Architecture, Real-Time/Embedded Systems, and Software Development Studio. His primary research interest is in the area software architectural design for embedded, software intensive systems. Anthony consults and teaches throughout industry in the areas of software architecture design and architecture evaluation. Prior to Carnegie Mellon, Mr. Lattanze was the Chief of Software Engineering for the Technology Development Group at the United States Flight Test Center at Edwards Air Force Base, CA. During his tenure at the Flight Test Center, he was involved with a number of software and systems engineering projects as a software and systems architect, project manager, and developer. During this time as he was involved with the development, test, and evaluation of avionics systems for the B-2 Stealth Bomber, F-117 Stealth Fighter, and F-22 Advanced Tactical Fighter among other systems. Linda Northrop is the director of the Product Line Systems Program at the Software Engineering Institute (SEI) where she leads the SEI work in software architecture, software product lines and predictable component engineering. Under her leadership the SEI has developed software architecture and product line methods that are used worldwide, a series of five highly-acclaimed books, and Software Architecture and Software Product Line Curricula. She is co-author of the book, “Software Product Lines: Practices and Patterns,” and a primary author of the SEI Framework for Software Product Line Practice.     

Toward a discipline of scenario‐based architectural engineering

Software architecture analysis is a cost‐effective means of controlling risk and maintaining system quality throughout the processes of software design, development and maintenance. This paper presents a sequence of steps that maps architectural quality goals into scenarios that measure the goals, mechanisms that realize the scenarios and analytic models that measure the results. This mapping ensures that design decisions and their rationale are documented in such a fashion that they can be systematically explored, varied, and potentially traded off against each other. As systems evolve, the analytic models can be used to assess the impact of architectural changes, relative to the system's changing quality goals. Although scenarios have been extensively used in software design to understand the ways in which a system meets its operational requirements, there has been little systematic use of scenarios to support analysis, particularly analysis of a software architecture's quality attributes: modifiability, portability, extensibility, security, availability, and so forth. In this paper we present a unified approach to using scenarios to support both the design, analysis and maintenance of software architectures, and examples from large‐scale software development projects where we have applied the approach. We also present a tool, called Brie, that aids in: scenario capture, mapping scenarios to software architectures, and the association of analytic models with particular portions of architectures. The approach that we have devised, and that Brie supports, is a foundation for a discipline of architectural engineering. Architectural engineering is an iterative method of design, analysis and maintenance where design decisions are motivated by scenarios, and are supported by documented analyses.     

基于BP神经网络的软件可靠性模型选择

软件可靠性模型是软件可靠性工程研究的一个重要方面.如何在缺乏可靠性数据的情况下,选择合适的软件可靠性模型是对软件可靠性进行量化分析的关键.参照软件可靠性模型评价准则,根据聚类思想,对失效数据编码,采用反向传播神经网络进行聚类计算,从而实现了软件可靠性模型的选择.最后通过仿真实验证明了该方法的正确性和有效性.     

考虑故障相关的软件可靠性增长模型研究

软件可靠性增长模型是用来评估和预测软件可靠性的重要工具.目前,绝大多数的软件可靠性增长模型并没有考虑故障之间的相关性,也没有考虑测试环境和运行环境的区别.文中提出了一种随机过程类非齐次泊松过程(NHPP)中的考虑故障相关性、测试环境和运行环境差别的模型.在两组失效数据上的实验分析表明:对这两组失效数据,文中提出的模型比其他一些非齐次泊松过程类模型的拟合效果和预测效果更好.     

面向机载软件的预期功能安全分析验证过程及方法研究

预期功能安全（Safety of the Intended Functionality,SOTIF）关注系统与外界环境、交联设备、任务场景和操作人员交互时,由自身功能设计不足而导致的安全隐患,非常适用于具有复杂功能逻辑的系统和软件研制过程。但目前尚未见到SOTIF在机载软件安全性分析验证工作中的研究与应用,导致机载软件安全性分析验证过程难以适用于复杂失效的分析识别。因此借鉴SOTIF在汽车领域的成功应用经验,开展面向机载软件的SOTIF分析验证过程与方法研究。首先,参考ISO 21448标准,提出机载软件SOTIF分析验证框架。然后,借助功能危险分析、故障树模型、场景驱动等理论,针对过程中涉及的SOTIF分析验证技术进行研究,识别机载系统危险,分析软件异常控制行为及其原因,构建SOTIF测试场景与测试用例,形成基于SOTIF的机载软件安全性分析验证完整闭环。最后,通过SOTIF技术在机轮转弯控制软件的典型工程应用,验证了该研究成果的有效性和可行性,形成了面向机载软件的SOTIF分析验证过程与能力,可支撑研制人员充分识别机载软件运行过程中软硬耦合冲突、人机交互异常、场景切换异常等复杂失效模式,确保机载软件满足高安全、高可靠研制要求。     

Graph transformation approaches for diverse routing in shared risk resource group (SRRG) failures

Failure resilience is a desired feature of the Internet. Most traditional restoration architectures assume single failure assumption, which is not adequate in present day WDM optical networks.Multiple link failure models, in the form of shared risk link groups (SRLG’s) and shared risk node groups (SRNG’s) are becoming critical in survivable optical network design. We classify both of these form of failures under a common scenario of shared risk resource groups (SRRG) failures. We develop graph transformation techniques for tolerating multiple failures arising out of shared resource group (SRRG) failures.Diverse routing in such multi-failure scenario essentially necessitates finding out two paths between a source and a destination that are SRRG disjoint. The generalized diverse routing problem has been proved to be NP-Complete. The proposed transformation techniques however provides a polynomial time solution for certain restrictive failure sets. We study how restorability can be achieved for dependent or shared risk link failures and multiple node failures and prove the validity of our approach for different network scenarios. Our proposed technique is capable of improving the diverse route computation by around 20–30% as compared to approaches proposed in the literature.     

基于Petri网的软件体系结构可靠性分析

近年来,软件体系结构已成为软件工程领域的研究热点以及大型软件系统与软件产品线开发中的关键技术之一。对软件体系结构的可靠性分析是进行软件开发的一个重要依据,为了提高软件系统的性能,一个可靠的体系结构是整个软件系统的基础。文章通过分析体系结构的特征和可靠性因素,提出了一种基于Petri网的体系结构可靠性分析方法,对软件体系结构的各因素的可靠性进行分析评估,从而推导出整个软件体系结构的可靠性,并对软件体系结构可靠性进行实例研究。     

软件可靠性工程框架和评估系统实现

给出了软件可靠性工程的实施框架,它规范了软件可靠性评估的过程.文章还提出一个软件可靠性评估系统的体系结构,并给出了实现所需要的一些关键技术.已经依此实现了一个软件可靠性评估系统CaSoR(Computer aid Software of Reliability),并已经被实际     

Development of a Software Engineering Ontology for Multisite Software Development

This paper aims to present an ontology model of software engineering to represent its knowledge. The fundamental knowledge relating to software engineering is well described in the textbook entitled Software Engineering by Sommerville that is now in its eighth edition [1] and the white paper, Software Engineering Body of Knowledge (SWEBOK), by the IEEE [2] upon which software engineering ontology is based. This paper gives an analysis of what software engineering ontology is, what it consists of, and what it is used for in the form of usage example scenarios. The usage scenarios presented in this paper highlight the characteristics of the software engineering ontology. The software engineering ontology assists in defining information for the exchange of semantic project information and is used as a communication framework. Its users are software engineers sharing domain knowledge as well as instance knowledge of software engineering.     

软件可靠性工程学综述

软件可靠性工程学定量评价软件系统的可靠性,是开发并维护软件系统的一种工程学技术.回顾了软件可靠性工程学的历史、目前的趋势以及现存的问题和困难.提出了软件可靠性工程学中未来可能的方向和有前景的研究课题.     

软件体系结构分析及场景技术在其中的应用

计算机应用系统的日益复杂和庞大,使得软件体系结构的研究成为当前的研究热点。软件体系结构设计已经成为软件生命周期中的一个重要环节。但是,如果无法对一个软件体系结构进行客观的、可行的定量和定性分析和评价,那么这种软件体系结构是不可靠的。现代软件的需求不断变化、业务规则和新的软件技术变化不停,要求软件体系结构在高层上必须考虑软     

基于构架的软件可靠性分析及优化研究

文章通过对基于构架的软件可靠性模型进行估算和分析,提出了一套分析和优化基于构架的软件可靠性的方案,并利用ATM银行系统实例给出了具体分析方法和步骤。同时,根据分析出来的可靠性瓶颈进行了一定的结构优化,优化后整个软件构架的可靠性有了显著提高。     

基于MVC的软件界面体系结构研究与实现*

软件体系结构研究是目前软件工程领域研究的新一轮热潮,是对软件的更高层次抽象。在分析MVC（Model/View/Controller）模式机理的基础上,给出了基于MVC的软件界面体系结构及其工作机理。软件界面体系结构带来了软件设计的灵活性和高度重用性。最后,以软件界面体系结构为指导,分析了MFC（Microsoft Fundament Class）的文档视图结构,并给出了软件界面体系结构的具体设计和实现。     

基于Kohonen网络的软件可靠性模型选择

软件可靠性模型是软件可靠性工程的一个重要方面。现在还没有一个通用的模型,模型选择问题已成为模型研究的重点。运用聚类思想对软件可靠性模型的选择进行研究。在对软件失效数据进行编码的基础上,采用Kohonen神经网络对其进行聚类分析,从而实现了可靠性模型的选择。最后通过仿真测试,证明了此方法的有效性和可行性。