关于计算机软件可靠性设计的研究分析

本文介绍了软件可靠性设计的基本概念,软件故障产生的机理,软件质量的可靠性参数,并且着重介绍了软件可靠性设计方法。随着科学技术的不断进步,软件可靠性成为我们关注的一个问题,软件系统规模越做越大越复杂,其可靠性越来越难保证。应用本身对系统运行的可靠性要求越来越高。特别是软件可靠性比硬件可靠性更难保证,会严重影响整个系统的可靠性。     

一种多维度的软件系统可靠性测试方法研究

传统的软件可靠性测试更多偏重于软件的功能方面。针对于这个不足之处,提出了结合操作剖面和性能测试的一种相对完善、全面的软件可靠性测试方法。归纳总结软件内部可靠性设计、外部高可用技术以及容灾恢复规范等诸多影响软件系统可靠性的因素,设计可靠性操作剖面要全面考虑这些因素。此方法是对传统方法的有用补充。最后通过一个案例简要介绍了该方法。     

一种软件可靠性评估模型及其Petri网描述

通过提出k-可靠模型,对现有软件可靠性评估方法所依据的模型进行重构,并根据Petri网及软件可靠性的相关理论,对构成软件系统的各个组件进行可靠性评估,从而实现对软件系统的可靠性评估,并介绍一种自底向上的可靠性计算过程。该方法能对软件系统的进行分解和综合计算,达到对整个软件系统可靠性评估的目的。     

浅谈航天应用计算机软件的可靠性与安全性设计

简述软件可靠性与安全性的概念及其重要性，分别介绍软件在可靠性设计和安全性设计上常采用的方法。 详迷软件可靠性与安全性设计在各个研制阶段的要求与实施情况，包括需求阶段、设计与实现阶段和测试阶段，以及其它与可靠性、安全性相关的内容。 介绍软件可靠性与安全性的研制经验，包括过程管理、交付后的程序复查。     

政务服务平台的可靠性测试设计

本文根据对政务服务中心平台进行第三方测试中可靠性测试的要求,结合软件系统的特点和用户需求,运用 软件可靠性测试方法对政务服务平台进行了可靠性测试设计与评估,从成熟性、容错性、易恢复性三个方面的测试设计验证了 政务服务平台软件的可靠性。     

软件可靠性研究与进展

综述了软件可靠性研究的主要内容 ,包括软件可靠性设计、测试与管理 -软件可靠性数据收集以及硬软件系统可靠性等方面的发展现状 ,提出了软件可靠性研究有待于进一步探讨的主要问题     

软件可靠性研究与进展

综述了软件可靠性研究的主要内容,包括软件可靠性设计、测试与管理-软件可靠性数据收集以及硬软件系统可靠性等方面的发展现状,提出了软件可靠性研究有待于进一步探讨的主要问题.     

基于执行时间模型的航天飞控软件可靠性测试

航天飞行控制软件是一种具有高可靠性要求的软件系统,但是目前对航天飞控软件的可靠性还没有进行定量的度量和管理.尝试将软件可靠性的定量模型应用于航天飞控软件系统的测试过程.介绍了基本执行时间可靠性模型,提出了基于历史失效数据拟合的模型校准方法,讨论了基于基本执行时间可靠性模型的软件可靠性增长测试和可靠性检定测试.     

浅析计算机软件可靠性设计

伴随着计算机科学技术的飞速发展,计算机的网络通信也涉及了生活的各个方面,涉及到政府、企业、学校、通信、银行、军事等诸多领域,小到人们的日常生活,大到国家的军事,随着网络通信的普及,对于软件的使用也同时出现了很多的问题,有来自外界的恶意破坏,也有来自自身使用的错误操作等,那么,如何加强网络通信的可靠性就成为了当今社会的重要问题,它直接关系到所有网络用户的切身利益。针对这一问题,本文软件可靠性设计的基本概念,对可靠性的影响因素,软件质量的可靠性参数等做了基本的介绍,并且着重介绍了软件可靠性设计方法。     

基于失效分析的软件可靠性评估方法研究

基于用户运行剖面的软件可靠性测试理论广泛地应用在软件测试领域.然而,这种软件可靠性测试既耗时又昂贵.在国内,现在进行的软件黑盒测试主要是系统测试,对于高可靠性要求的软件,系统测试后也需要评估它的可靠性水平.介绍了一种基于失效分析的软件可靠性评估方法,这种方法利用了软件系统测试后得到的缺陷数据,对每一个缺陷导致失效的内外...     

面向服务架构软件实现前的可靠性评价方法

为了在软件实现前评估其可靠性,针对基于面向服务架构(SOA)设计的软件提出了一种可靠性评价方法：用OWL-S描述软件的需求和设计信息,利用Maude为OWL-S过程模型的控制结构定义形式化语义,使用分布函数构建软件的操作剖面,在Maude中增加软件的操作剖面信息和体系结构信息如何参与可靠度计算的描述,在Maude系统的支持下,通过重写得到软件的可靠度,并基于此方法设计开发了一个软件可靠性预计工具——SRPT。所提出的软件可靠性评价方法综合考虑了数据流、控制流、构件和软件操作剖面信息以及体系结构信息对软件可靠性的影响,能够在软件实现前根据软件设计预测其可靠度,为软件的开发设计提供了工程指导。     

A Framework for Design Tradeoffs

Designs almost always require tradeoffs between competing design choices to meet system requirements. We present a framework for evaluating design choices with respect to meeting competing requirements. Specifically, we develop a model to estimate the performance of a UML design subject to changing levels of security and fault-tolerance. This analysis gives us a way to identify design solutions that are infeasible. Multi-criteria decision making techniques are applied to evaluate the remaining feasible alternatives. The method is illustrated with two examples: a small sensor network and a system for controlling traffic lights. Dr. Anneliese Amschler Andrews is Professor and Chair of the Department of Computer Science at the University of Denver. Before that she was the Huie Rogers Endowed Chair in Software Engineering at Washington State University. Dr. Andrews is the author of a text book and over 130 articles in the area of Software Engineering, particularly software testing and maintenance. Dr. Andrews holds an MS and PhD from Duke University and a Dipl.-Inf. from the Technical University of Karlsruhe. She served as Editor-in-Chief of the IEEE Transactions on Software Engineering. She has also served on several other editorial boards including the IEEE Transactions on Reliability, the Empirical Software Engineering Journal, the Software Quality Journal, the Journal of Information Science and Technology, and the Journal of Software Maintenance. She was Director of the Colorado Advanced Software Institute from 1995 to 2002. CASI's mission was to support technology transfer research related to software through collaborations between industry and academia. Ed Mancebo studied software engineering at Milwaukee School of Engineering and computer science at Washington State University. His masters thesis explored applying systematic decision making methods to software engineering problems. He is currently a software developer at Amazon.com. Dr. Per Runeson is a professor in software engineering at Lund University, Sweden. His research interests include methods to facilitate, measure and manage aspects of software quality. He received a PhD from Lund University in 1998 and has industrial experience as a consulting expert. He is a member of the editorial board of Empirical Software Engineering and several program committees, and currently has a senior researcher position funded by the Swedish Research Council. Robert France is currently a Full Professor in the Department of Computer Science at Colorado State University. His research interests are in the area of Software Engineering, in particular formal specification techniques, software modeling techniques, design patterns, and domain-specific modeling languages. He is an Editor-in-Chief of the Springer journal on Software and System Modeling (SoSyM), and is a Steering Committee member and past Steering Committee Chair of the MoDELS/UML conference series. He was also a member of the revision task forces for the UML 1.x standards.     

Higher Order Software—A Methodology for Defining Software

The key to software reliability is to design, develop, and manage software with a formalized methodology which can be used by computer scientists and applications engineers to describe and communicate interfaces between systems. These interfaces include: software to software; software to other systems; software to management; as well as discipline to discipline within the complete software development process. The formal methodology of Higher Order Software (HOS), specifically aimed toward large-scale multiprogrammed/multiprocessor systems, is dedicated to systems reliability. With six axioms as the basis, a given system and all of its interfaces is defined as if it were one complete and consistent computable system. Some of the derived theorems provide for: reconfiguration of real-time multiprogrammed processes, communication between functions, and prevention of data and timing conflicts.     

Software architecture reliability analysis using failure scenarios

With the increasing size and complexity of software in embedded systems, software has now become a primary threat for the reliability. Several mature conventional reliability engineering techniques exist in literature but traditionally these have primarily addressed failures in hardware components and usually assume the availability of a running system. Software architecture analysis methods aim to analyze the quality of software-intensive system early at the software architecture design level and before a system is implemented. We propose a Software Architecture Reliability Analysis Approach (SARAH) that benefits from mature reliability engineering techniques and scenario-based software architecture analysis to provide an early software reliability analysis at the architecture design level. SARAH defines the notion of failure scenario model that is based on the Failure Modes and Effects Analysis method (FMEA) in the reliability engineering domain. The failure scenario model is applied to represent so-called failure scenarios that are utilized to derive fault tree sets (FTS). Fault tree sets are utilized to provide a severity analysis for the overall software architecture and the individual architectural elements. Despite conventional reliability analysis techniques which prioritize failures based on criteria such as safety concerns, in SARAH failure scenarios are prioritized based on severity from the end-user perspective. SARAH results in a failure analysis report that can be utilized to identify architectural tactics for improving the reliability of the software architecture. The approach is illustrated using an industrial case for analyzing reliability of the software architecture of the next release of a Digital TV.     

Specifying the system

Software components of microprocessor systems now consume a major part of development costs. This has meant that there is a growing trend for software to be designed with a view to future extension, which places constraints on the structure of the design if any extension is to be achieved with a minimum of restructuring. Software validation — verifying each function of the system against performance requirements — is also becoming increasingly important. These requirements must be made explicit at the start of the design process. This article considers the requirements analysis techniques and design methodologies which should be applied to system design to allow the production of software that carries out the specified functions while being amenable to future extension without completely redesigning the system.     

提高嵌入式系统可靠性的软件技术

软件抗干扰技术是提高嵌入式系统可靠性的重要手段。结合实践,文章分析了嵌入式系统软件的基本要求及软件抗干扰的特点,并从软件工程开发方法和故障自诊断技术等方面提出了若干行之有效的软件抗干扰技术。     

The Software Development System

This paper contains a discussion of the Software Development System (SDS), a methodology addressing the problems involved in the development of software for ballistic missile defense systems. These are large real-time, automated systems with a requirement for high reliability. The SDS is a broad approach attacking problems arising in requirements generation, software design, coding, and testing. The approach is highly requirements oriented and has resulted in the formulation of structuring concepts, a requirements statement language, process design language, and support software to be used throughout the development cycle. This methodology represents a significant advance in software technology for the development of software for a class of systems such as BMD. The support software has been implemented and is undergoing evaluation.     

航天测控系统数据处理软件的设计与实现

本文设计的航天测控系统数据处理软件充分借鉴了成熟软件的设计经验,以实时性和可靠性为设计重点,充分考虑软件通用性和适用性统一化为指导思想,具有较高的自动化水平,可靠性、实用性、可扩展性强,并通过了分系统测试、系统联试以及外场联试等多种测试的考核验证,从试验数据的接收和处理结果来看,系统在数据存储、显示、通信、挑路处理等方面都达到技术指标要求,技术状态受控,满足试验需要。     

Software reliability — what is it?

Software has become a household necessity in today's world but little has been done to measure its reliability for the consumer. Since software failure has a different basis than hardware failure, existing reliability theory cannot be applied directly: a new software unique theory needs to be defined. Current software practice relies on software quality measures to describe software reliability but recent work has identified both theory and practice for appropriate software reliability analysis. This paper discusses: the need for software reliability analysis in order to more accurately describe system reliability, the shortcomings of current practice, and both the direction of new work in, and the future roles for, software reliability analysis.     

T-CBESD:一个构件化嵌入式软件设计模型验证工具

现代复杂嵌入式软件系统的高可靠性需要有效的基于模型的设计与分析技术.传统的嵌入式软件可靠性保障技术主要关注于系统开发后期.本文在Eclipse平台上设计并实现了一个基于接口自动机模型的构件化嵌入式软件设计的形式化验证原型工具T-CBESD(Tool for Component-Based Embedded Software Designs).工具直接使用UML顺序图模型作为系统规约,可以检验系统设计模型与场景式规约之间多种行为一致性问题;并使用消息事件的时间约束不等式,检验实时接口自动机网络与带时间约束的顺序图模型之间的实时行为一致性问题.工具设计与实现内容包括:输入输出接口、顺序图模型的预处理转换、状态空间数据结构设计、抽象验证算法的实现以及通信构件组合系统的实例应用分析.