Technical foundations introduction software reliability and system reliability the operational profile software reliability modelling survey model evaluation and recalibration techniques practices and experiences best current practice of SRE software reliability measurement experience measurement-based analysis of software reliability software fault and failure classification techniques trend analysis in validation and maintenance software reliability and field data analysis software reliability process assessment emerging techniques software reliability prediction metrics software reliability and testing fault-tolerant SRE software reliability using fault trees software reliability process simulation neural networks and software reliability. Appendices: software reliability tools software failure data set repository.

/pdf/handbook-of-software-reliability-engineering-32dwvaljmm.pdf

Handbook of software reliability engineering

data types Sorting and searching parallel and distributed algorithms 3. [AR] Computer Architecture

/pdf/guide-to-the-software-engineering-body-of-knowledge-4x9ajlpq2m.pdf

Guide to the Software Engineering Body of Knowledge

This paper summarizes the current state of the art and recent trends in software engineering economics. It provides an overview of economic analysis techniques and their applicability to software engineering and management. It surveys the field of software cost estimation, including the major estimation techniques available, the state of the art in algorithmic cost models, and the outstanding research issues in software cost estimation.

Software engineering economics

In the context of process management, risk has been considered mainly from a project management perspective. But risk is an inherent property of every business process and techniques are needed to identify, represent and analyse business process risks. The absence of such techniques is a concern because both operational risk mitigation and legal compliance depend on the sufficient identification of corporate risk. This paper addresses the topic of risk management in the context of business process management. We present a taxonomy of processrelated risks and discuss how this taxonomy can be applied in the analysis and documentation of business processes. We demonstrate how a contemporary process modelling method can be extended to document process-related risks and their relationships with goals, other risks and processes. A critical administrative process in an university is used as an example.

/pdf/integrating-risks-in-business-process-models-4eb77v5x2t.pdf

Integrating Risks in Business Process Models

Business Process Management is considered an essential strategy to create and maintain competitive advantage by streamlining and monitoring corporate processes. While the identification of critical success factors for the management of business process related projects has been addressed by some research projects, the risks associated with these projects have received considerably less attention. This is a concern: Although BPM projects contain phases that relate to traditional software development and deployment projects, the application of risk mitigation strategies found in software engineering ignores the subsequent process management phases that follow upon the implementation and automation of processes. This paper provides an overview of risks associated with BPM projects along the phases of the BPM lifecycle. After a classification of the risks identified with individual lifecycle phases and transitions we discuss four strategies to deal with these risks: avoidance, mitigation, transfer, and acceptance. The outlook of this paper discusses how assessment frameworks such as CobIT and COSO can be applied to risk management in the context of BPM.

Risk management in the BPM lifecycle

This study has examined software reliability using a risk management framework to analyze popular risk management models with regard to their emphasis on risk avoidance. Too often, risk reduction occurs late in the software development life cycle when changes are costly and less effective. We suggest that early risk avoidance techniques, like the cleanroom software development process and its sub-process of software inspections, leads to superior products. Our approach is different from the current mainstream approach of testing to eliminate errors because we propose using risk models that emphasize preventive risk management early in development. We argue that the use of risk avoidance leads to benefits that far outweigh the cost of implementation.

John G. Leonard

Papers

Improving risk management: moving from risk elimination to risk avoidance