Catalogue Search | MBRL
Are you sure you want to remove the book from the shelf?
{{itemTitle}}
19,620
result(s) for
"Software failures"
Sort by:
Incremental software architecture : a method for saving failing IT implementations
\"This book will depict rare insights into actual failed-to-perform software systems, followed by comprehensive root-cause analyses identifying the reasons for their unsuccessful execution in production. Remedies will be provided that offer strategies to tackle the chief issues. Last, architecture and design best practices will conclude the discussion. The book will assist users to: Mitigate risks of software development projects Increase return on investments (ROI) Provide effective tools to assess technological achievability and viability Introduce software design best practices for enterprise architecture efforts Identify actual software construction value proposition Foster software assets reuse and consolidation Accelerate time-to-market \"-- Provided by publisher.
Book
Refactoring for Software Design Smells
Awareness of design smells - indicators of common design problems - helps developers or software engineers understand mistakes made while designing, what design principles were overlooked or misapplied, and what principles need to be applied properly to address those smells through refactoring.
eBook
Bugs that make your computer crawl : what are computer bugs?
\"Don't swat that bug--fix it! Author Brian P. Cleary, illustrator (and coding hobbyist) Martin Goneau, and the indefatigable CATegorical cats offer a fun and accessible introduction to computer bugs\"-- Provided by publisher.
Book
Noise Channels
To err is human; to err in digital culture is design. In the glitches, inefficiencies, and errors that ergonomics and usability engineering strive to surmount, Peter Krapp identifies creative reservoirs of computer-mediated interaction. Throughout new media cultures, he traces a resistance to the heritage of motion studies, ergonomics, and efficiency, showing how creativity is stirred within the networks of digital culture.
eBook
A new framework of complex system reliability with imperfect maintenance policy
The interactions and dependencies between software and hardware are often neglected in modeling system reliability in the past few decades due to the mathematical complexity. However, many system failures occurred from the interactions or simultaneous occurrences of software and hardware. This paper first proposes a new diagram of categorizing system-level failures and further incorporates such a diagram into the development of complex system reliability framework. System-level failures result from software subsystem, hardware subsystem, and the interactions of software and hardware subsystems. The focus of this study is on the investigation of the interactions failures generated from the interactions of software and hardware subsystems. In addition to the considerations of total hardware failures, software-induced hardware failures, and hardware-induced software failures introduced by Zhu and Pham (Mathematics 7(11):1049, 2019), we further introduce the partial hardware failures that can be respectively induced by hardware and software to explicitly demonstrate the dependencies and interactions between software and hardware. Hence, a new complex system reliability framework is developed based on such system-level failure categorization with the Markov process. Furthermore, the numerical examples are studied to illustrate the impacts on system reliability with the changes of state transition parameters that modeling the interactions of software and hardware subsystems. Finally, we have studied two maintenance policies of the proposed complex system reliability model.
Journal Article
Incremental Software Architecture
The best-practices solution guide for rescuing broken software systems
Incremental Software Architecture is a solutions manual for companies with underperforming software systems. With complete guidance and plenty of hands-on instruction, this practical guide shows you how to identify and analyze the root cause of software malfunction, then identify and implement the most powerful remedies to save the system. You'll learn how to avoid developing software systems that are destined to fail, and the methods and practices that help you avoid business losses caused by poorly designed software. Designed to answer the most common questions that arise when software systems negatively impact business performance, this guide details architecture and design best practices for enterprise architecture efforts, and helps you foster the reuse and consolidation of software assets.
Relying on the wrong software system puts your company at risk of failing. It's a question of when, not if, something goes catastrophically wrong. This guide shows you how to proactively root out and repair the most likely cause of potential issues, and how to rescue a system that has already begun to go bad.
* Mitigate risks of software development projects
* Increase ROI and accelerate time-to-market
* Accurately assess technological achievability and viability
* Identify actual software construction value propositions
Fierce competition and volatile commerce markets drive companies to invest heavily in the construction of software systems, which strains IT and business budgets and puts immense strain on existing network infrastructure. As technology evolves, these ever-more-complex computing landscapes become more and more expensive and difficult to maintain. Incremental Software Architecture shows you how to revamp the architecture to effectively reduce strain, cost, and the chance of failure.
eBook
A Novel System Reliability Modeling of Hardware, Software, and Interactions of Hardware and Software
In the past few decades, a great number of hardware and software reliability models have been proposed to address hardware failures in hardware subsystems and software failures in software subsystems, respectively. The interactions between hardware and software subsystems are often neglected in order to simplify reliability modeling, and hence, most existing reliability models assumed hardware subsystems and software subsystem are independent of each other. However, this may not be true in reality. In this study, system failures are classified into three categories, which are hardware failures, software failures, and hardware-software interaction failures. The main contribution of our research is that we further classify hardware-software interaction failures into two groups: software-induced hardware failures and hardware-induced software failures. A Markov-based unified system reliability modeling incorporating all three categories of system failures is developed in this research, which provides a novel and practical perspective to define system failures and further improve reliability prediction accuracy. Comparison of system reliability estimation between the reliability models with and without considering hardware-software interactions is elucidated in the numerical example. The impacts on system reliability prediction as the changes of transition parameters are also illustrated by the numerical examples.
Journal Article
Pytest Quick Start Guide
Python's built-in unittest module is showing it's age; hard to extend, debug and track what's going on. The pytest framework overcomes these problems and simplifies testing your Python software. Many users love to use pytest and the improvement in their testing shows! This book is the ideal introduction to pytest, teaching you how to write.
eBook
Digital literacy for dummies applications & troubleshooting course. Solving computer software and service problems
Maybe your computer starts fine, but your email doesn't work, a certain program is frozen, or your computer just acts slow. This video gives you tips on how to get you at optimal performance.
Streaming Video
Software Failure Log Analysis for Engineers—Review
The use of automated methods for log analysis is unavoidable in any large company; therefore, it has attracted attention from engineers and researchers. As a result, the number of articles in the field grows yearly and new approaches are frequently proposed. Unfortunately, published research works only sometimes meet the needs of engineers wishing to apply the methods in real-life systems. A common issue is that the method’s benefits often do not compensate for the effort required for its implementation and maintenance. Therefore, engineers must understand the pros and cons of full-scale applications, including the implementation details and the required effort. This work provides a comprehensive review of automated log analysis methods and aims to offer a guide for software engineers who fix integration and production failures. The article categorizes and provides an overview of existing methods and assesses their implementation and maintenance costs, as well as the feasibility of the methods. The article also identifies and describes the shortcomings of existing methods, including concept drift, which is not addressed with sufficient attention, as well as the lack of online benchmarks and the interpretation of the log sequence as a language, without an in-depth analysis of its properties. Despite growing efforts to provide feasible and widely adopted solutions, many reference implementations are unavailable. Consequently, the time and computation complexities differ between various implementations of the same approaches, making the results of research work difficult to replicate in real-life scenarios.
Journal Article