Explain predictive validity, Software Engineering

Assignment Help:

Q. Explain Predictive validity?

Predictive validity: It is the potential of the model to predict future failure behaviour from present and past failure behaviour. This capability is important only when failure behaviour is changing. There are two universal ways of viewing predictive validity based on the two equivalent approaches to characterizing failure random process namely

1. The number of failure approach as well as

2. The failure time approach.

We can visually ensure the predictive validity by plotting the relative error against the normalised test time.


Related Discussions:- Explain predictive validity

What is upward compression, What is Upward compression? Ans) In software...

What is Upward compression? Ans) In software design, "upward compression" means a type of demodularization in which a subordinate module is copied into the body of a better modu

Describe the importance of function point, Q. Describe the Importance of fu...

Q. Describe the Importance of function point? - This is independent of the languages tools or else methodology used for implementation. - They are able to be estimated from

Describe the object interface design, Question 1 Explain Iterative Develop...

Question 1 Explain Iterative Development Model in detail Question 2 Describe the Object Interface Design Question 3 Explain why it is important to describe softwar

Explain the modularity concept mean, What does Modularity concept mean? ...

What does Modularity concept mean? Software architecture embodies modularity; i.e. Software is named in to addressable components called modules, which are integrated finally.

Explain equivalence class partitioning, Q. Explain Equivalence Class Partit...

Q. Explain Equivalence Class Partitioning ? Equivalence Class Partitioning : It is a method in black box testing. It is designed to reduce the number of test cases by dividing

What are 5 common problems in software development process, What are 5 comm...

What are 5 common problems in software development process? 1. Bad requirements - These requirements are unclear, too general, incomplete, or not testable. They cause problem

What is fan-in and fan-out, Define Fan-in and Fan-out Fan-out: A measu...

Define Fan-in and Fan-out Fan-out: A measure of the number of modules which are directly maintained by another module. Fan-in: Indicates that how many modules directly main

Software Engineering environments, 1.1 Discuss possible ramifications of th...

1.1 Discuss possible ramifications of these opposing objectives on the project. What would you do if you were the manager?

XML, Ask Create an XML file with markup tags and some sample data to repres...

Ask Create an XML file with markup tags and some sample data to represent a list of invoices.

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