What is a boundary value analysis, Software Engineering

What is a boundary value analysis?

A boundary value analysis is a testing method in which the elements at the edge of the domain are selected and tested. It is a test case design method that complements equivalence partitioning method. Here instead of focusing on input conditions only, the test cases are derived from the output domain.

 

Posted Date: 7/23/2013 8:33:49 AM | Location : United States







Related Discussions:- What is a boundary value analysis, Assignment Help, Ask Question on What is a boundary value analysis, Get Answer, Expert's Help, What is a boundary value analysis Discussions

Write discussion on What is a boundary value analysis
Your posts are moderated
Related Questions
A test method satisfying coverage criteria that needs each decision point at every possible branch to be implemented at least once.

Define the Prototyping Model In this model, a working model of actual software is developed originally. Prototype is just like a sample software having low reliability and les

using a dfd and a processing narrative,describe computer based system that can distinct transform flow characteristics.Define flow boundaries map the dfd into a software architectu

Q. What is verification? Ans. Verification is the procedure of determining whether the output of one phase of software development conforms to that of its previous phase wh

What is 4Test? 4Test is a test scripting language which is used by SilkTest to compose test scripts to perform automated tests. It's an object-oriented fourth-generation langua

Q. Explain the bath tub curve of hardware reliability? Ans: As indicated in the diagram below there are three phasing in the life of whichever hardware component that is burn

A strategy for software testing integrates software test case design methods into a well - planned series of steps that result in the successful construction of software. Common

Q. Define Software testability? Software testability is the degree to which a software artifact (i.e. a software system, software module, requirements- or design document) su

Justify the term "Software is engineered" Software is engineered not manufactured. Although some similarities exist between software development and hardware manufacture, the t

Importance of function point:    This is independent of the languages tools, or methodology used for execution. They can be estimated from requirement specification or desig