Best, average, and worst case analysis in Data Structures Theory - Time & Space Complexity

Time Complexity: Best, average, and worst case analysis

O(n)

Understanding Time Complexity

When we analyze time complexity, we want to know how long a task takes depending on the input. Sometimes, the time changes based on the input details.

We ask: What is the fastest, average, and slowest time this task can take?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

function findNumber(arr, target) {
  for (let i = 0; i < arr.length; i++) {
    if (arr[i] === target) {
      return i;
    }
  }
  return -1;
}
    

This code searches for a number in a list and stops when it finds it or reaches the end.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking each item in the list one by one.
• How many times: Up to the length of the list, depending on when the target is found.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	Between 1 and 10 checks
100	Between 1 and 100 checks
1000	Between 1 and 1000 checks

Pattern observation: The number of checks depends on where the target is. It can be very fast if found early or take longer if found late or not at all.

Final Time Complexity

Time Complexity: O(n)

This means in the worst case, the time grows linearly with the size of the input list.

Common Mistake

[X] Wrong: "The search always takes the same time no matter what."

[OK] Correct: The time depends on where the target is. If it is at the start, it's quick; if not found, it checks everything.

Interview Connect

Understanding best, average, and worst cases helps you explain how your code behaves in different situations. This shows you think about real-world use, not just theory.

Self-Check

"What if the list was sorted and you used a different search method? How would the time complexity change?"

Practice

1. Which case describes the fastest possible scenario for an algorithm's execution?

easy

A. Random case

B. Average case

C. Best case

D. Worst case

Solution

1. Step 1: Understand the definition of best case

   The best case is when the algorithm performs the minimum number of steps possible.

2. Step 2: Compare with other cases

   Average case is typical, worst case is the slowest, random case is not a standard term.

3. Final Answer:

   Best case -> Option C

4. Quick Check:

   Fastest scenario = Best case [OK]

Hint: Best case means fastest scenario for algorithm [OK]

Common Mistakes:

• Confusing best case with worst case
• Thinking average case is fastest
• Assuming random case is standard

2. Which of the following correctly represents the syntax to describe the worst case time complexity of an algorithm?

easy

A. Ω(n)

B. O(n)

C. Θ(n)

D. Δ(n)

Solution

1. Step 1: Recall notation meanings

   O(n) denotes worst case upper bound, Ω(n) is best case lower bound, Θ(n) is average case tight bound.

2. Step 2: Identify correct notation for worst case

   Worst case time complexity is expressed using Big O notation.

3. Final Answer:

   O(n) -> Option B

4. Quick Check:

   Worst case = Big O notation [OK]

Hint: Worst case uses Big O notation [OK]

Common Mistakes:

• Confusing Ω with worst case
• Using Θ for worst case
• Using undefined Δ notation

3. Consider a linear search algorithm on an array of 5 elements where the target is the last element. What is the worst case number of comparisons?

medium

A. 5

B. 3

C. 1

D. 0

Solution

1. Step 1: Understand linear search behavior

   Linear search checks elements one by one from start to end until it finds the target.

2. Step 2: Calculate comparisons when target is last

   It must check all 5 elements, so 5 comparisons in worst case.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Last element found after 5 checks = 5 [OK]

Hint: Worst case linear search checks all elements [OK]

Common Mistakes:

• Counting fewer comparisons
• Confusing best case with worst case
• Assuming target not found equals zero comparisons

4. A sorting algorithm has a worst case time complexity of O(n^2). Which of the following code snippets correctly represents a nested loop that causes this complexity?

medium

A. for i in range(n):\n for j in range(1):\n do_something()

B. for i in range(n):\n do_something()

C. for i in range(n):\n for j in range(10):\n do_something()

D. for i in range(n):\n for j in range(n):\n do_something()

Solution

1. Step 1: Analyze nested loops for complexity

   Two loops each running n times cause n * n = n^2 operations.

2. Step 2: Check each option's loop counts

   for i in range(n):\n for j in range(n):\n do_something() has two full loops of n iterations each, matching O(n^2). Others have fewer iterations.

3. Final Answer:

   for i in range(n):\n for j in range(n):\n do_something() -> Option D

4. Quick Check:

   Double loops with n iterations = O(n^2) [OK]

Hint: Nested loops both running n times cause O(n^2) [OK]

Common Mistakes:

• Ignoring inner loop range
• Assuming single loop is O(n^2)
• Confusing partial nested loops

5. You have a hash table with chaining for collision handling. If the hash function distributes keys evenly, what is the average case time complexity for search operations when there are n keys and m buckets?

hard

A. O(1 + n/m)

B. O(n)

C. O(m)

D. O(log n)

Solution

1. Step 1: Understand hash table with chaining

   Keys are distributed into m buckets; collisions stored in linked lists.

2. Step 2: Calculate average search time

   Average search is constant time plus time to search linked list of average length n/m.

3. Final Answer:

   O(1 + n/m) -> Option A

4. Quick Check:

   Average search = constant + average chain length [OK]

Hint: Average search time = O(1 + load factor) [OK]

Common Mistakes:

• Assuming always O(1)
• Confusing m with n
• Using O(log n) for chaining