Object Oriented Software Engineering   View all facts   Glossary   Help
subject > problem > defect > defect in an ordinary algorithm > use of an inappropriate standard algorithm > use of an inefficient search algorithm
Next use of an inappropriate standard algorithm: use of an inefficient sort algorithm    Up: use of an inappropriate standard algorithm    Previous use of an inappropriate standard algorithm: use of a search or sort that is not case sensitive when it should be   

use of an inefficient search algorithm
subjectfact 
use of an inefficient search algorithmhas testing strategy
  • create a big enough list (e.g. 1 million elements) so that an unordered search should take some measurable time
  • sort the data, and measure how much time searching takes
  • double the number of sorted elements and measure the search time again
  • both searches should take negligible time; if they do take measurable time, then the time should be almost equal
2001-08-30 14:58:14.0
is a subtopic of 10.3 - Defects in Ordinary Algorithms2001-08-30 14:58:14.0
is a kind of use of an inappropriate standard algorithm2001-08-30 14:58:14.0
defecthas example the absence of code to handle an exception2001-08-30 14:55:12.0
problemhas solution which will normally entail developing software, although you may decide that it is better to purchase software or to develop a non-software solution2001-08-30 14:57:03.0
should be written as a simple problem statement in one or two sentences2001-08-30 14:57:03.0