Search Results Heading

MBRLSearchResults

mbrl.module.common.modules.added.book.to.shelf
Title added to your shelf!
View what I already have on My Shelf.
Oops! Something went wrong.
Oops! Something went wrong.
While trying to add the title to your shelf something went wrong :( Kindly try again later!
Are you sure you want to remove the book from the shelf?
Oops! Something went wrong.
Oops! Something went wrong.
While trying to remove the title from your shelf something went wrong :( Kindly try again later!
    Done
    Filters
    Reset
  • Discipline
      Discipline
      Clear All
      Discipline
  • Is Peer Reviewed
      Is Peer Reviewed
      Clear All
      Is Peer Reviewed
  • Series Title
      Series Title
      Clear All
      Series Title
  • Reading Level
      Reading Level
      Clear All
      Reading Level
  • Year
      Year
      Clear All
      From:
      -
      To:
  • More Filters
      More Filters
      Clear All
      More Filters
      Content Type
    • Item Type
    • Is Full-Text Available
    • Subject
    • Country Of Publication
    • Publisher
    • Source
    • Target Audience
    • Donor
    • Language
    • Place of Publication
    • Contributors
    • Location
21,097 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.
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.
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.
Bug Bounty from Scratch
Embark on your bug bounty journey by gaining practical skills and contribute to a safer digital landscape Key Features Prepare to participate in a bug bounty program Discover your first bug and claim your reward upon successful detection Go through core security concepts as well as advanced techniques for vulnerability identification Purchase of.
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.
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.
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.
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.
pytest Quick Start Guide
Learn the pytest way to write simple tests which can also be used to write complex tests Key Features * Become proficient with pytest from day one by solving real-world testing problems * Use pytest to write tests more efficiently * Scale from simple to complex and functional testing Book Description Python's standard unittest module is based on the xUnit family of frameworks, which has its origins in Smalltalk and Java, and tends to be verbose to use and not easily extensible.The pytest framework on the other hand is very simple to get started, but powerful enough to cover complex testing integration scenarios, being considered by many the true Pythonic approach to testing in Python. In this book, you will learn how to get started right away and get the most out of pytest in your daily workflow, exploring powerful mechanisms and plugins to facilitate many common testing tasks. You will also see how to use pytest in existing unittest-based test suites and will learn some tricks to make the jump to a pytest-style test suite quickly and easily. What you will learn * Write and run simple and complex tests * Organize tests in fles and directories * Find out how to be more productive on the command line * Markers and how to skip, xfail and parametrize tests * Explore fxtures and techniques to use them effectively, such as tmpdir, pytestconfg, and monkeypatch * Convert unittest suites to pytest using little-known techniques * Use third-party plugins Who this book is for This book is for Python programmers that want to learn more about testing. This book is also for QA testers, and those who already benefit from programming with tests daily but want to improve their existing testing tools.
Reliability assessment for multi-state automatic ticket vending machine (ATVM) through software and hardware failures
PurposeThis paper presents the performance analysis of the automatic ticket vending machine (ATVM) through the functioning of its different hardware and software failures.Design/methodology/approachFrequent failures in the working of ATVM have been observed; therefore, the authors of the paper intend to analyze the performance measures of the same. Authors have developed a mathematical model based on different hardware and software failures/repairs, which may occur during the operation, with the help of the Markov process. The developed model has been solved for two kinds of failure/repair rates namely variable failures (very much similar to real-time failure) and constant failures. Lagrange's method and Laplace transformation are used for the solution of the developed model.FindingsReliability and mean time to failure of the ATVM are determined. Sensitivity analysis for ATVM is also carried out in the paper. Critical components of the ATVM, which affect the performance of the same, in terms of reliability and MTTF are also identified.Originality/valueA mathematical model based on different hardware and software failures/repairs of ATVM has been developed to analyze its performance, which has not been done in the past.