Define software reliability, Software Engineering

Assignment Help:

Define software reliability. What is the difference between hardware & software reliability?

Ans: Software reliability is the possibility that software will provide failure-free operation in a fixed environment for a fixed interval of time. Probability of failure is the possibility that the software will fail on the next input selected. Software reliability is usually measured per some unit of time whereas probability of failure is usually time independent. These two measures are able to be easily related if you know the frequency with which inputs are executed per unit of time. Mean-time-to-failure is an average interval of time between failures this is as well sometimes referred to as Mean-time-before-failure.

Software reliability is liable to change repeatedly during test periods. While hardware reliability may perhaps change during certain periods such as initial burn in or the end of useful life however it has a much greater tendency then software value.

Hardware faults aren't physical faults whereas software faults are design faults that are harder to classify, visualise, detect and correct. In reality the division among hardware and software reliability is somewhat artificial. Both perhaps defined in the same way therefore one may combine hardware and software reliability to get system reliability. The basis of failure in hardware has generally being physically deterioration.


Related Discussions:- Define software reliability

Equivalence class testing, Equivalence class testing Equivalence class ...

Equivalence class testing Equivalence class testing is based on partitioning the input domain of a program into a number of equivalence classes so that the test of a representa

Why software design improve when we use oops concepts, Q. Why does the soft...

Q. Why does the software design improve when we use object-oriented concepts? Ans. The software design gets betters when we use object-oriented concepts because 1.Object-o

Explain key process areas of cmm, Key process areas of CMM. 1.  Require...

Key process areas of CMM. 1.  Requirements management which establishes a common relationship among the customer and developer 2.  Software project planning where reasonable

Define verification and validation, Define Verification &Validation. V...

Define Verification &Validation. Verification: The set of activities that make sure that software correctly executes a specific function. Validation: The set of activiti

Explain the concept of bottom-up design, Q. Explain the concept of bottom-u...

Q. Explain the concept of bottom-up design? Bottom up design: This approach make possible a style of design where we decide how to combine these modules to provide larger ones

What is throw-away prototyping, Throw-away prototyping Objective: ...

Throw-away prototyping Objective: The principal objective of this model is to validate or to derive the system needs. It is developed to decrease requirement risks.

Define the computer based system, Define the computer based system. The...

Define the computer based system. The computer based system can be explained as "a set or an arrangement of elements that are organized to accomplish some predefined goal by pr

Constructor, what is constructor overloading

what is constructor overloading

Software requirements analysis, What types of models are formed during soft...

What types of models are formed during software requirements analysis?   Functional and behavioral

Assignment 2, I have to do an assignment. Can you help me to do it

I have to do an assignment. Can you help me to do it

Write Your Message!

Captcha
Free Assignment Quote

Assured A++ Grade

Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!

All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd