Difference between revisions of "Design predicates"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (Created page with "'''Design predicates''' are a method invented by Thomas McCabe to quantify the complexity of the integration of two units of software. == Description == Each of the four...") |
Karl Jones (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | '''Design predicates''' are a method invented by Thomas McCabe to quantify the complexity of the integration of two units of [[software]]. | + | '''Design predicates''' are a method invented by Thomas McCabe to quantify the [[complexity]] of the integration of two units of [[software]]. |
== Description == | == Description == | ||
| Line 15: | Line 15: | ||
== See also == | == See also == | ||
| + | * [[Complexity]] | ||
* [[Cyclomatic complexity]] | * [[Cyclomatic complexity]] | ||
* [[Design pattern]] | * [[Design pattern]] | ||
Revision as of 09:03, 19 August 2016
Design predicates are a method invented by Thomas McCabe to quantify the complexity of the integration of two units of software.
Description
Each of the four types of design predicates have an associated integration complexity rating.
For pieces of code that apply more than one design predicate, integration complexity ratings can be combined.
The sum of the integration complexity for a unit of code, plus one, is the maximum number of test cases necessary to exercise the integration fully.
Though a test engineer can typically reduce this by covering as many previously uncovered design predicates as possible with each new test.
Also, some combinations of design predicates might be logically impossible.
See also
- Complexity
- Cyclomatic complexity
- Design pattern
- Integration testing
- Software engineering
- White box testing
External links
- Design predicates @ Wikipedia
