MVC architecture overview in PHP - Time & Space Complexity

Time Complexity: MVC architecture overview

O(n)

Understanding Time Complexity

We want to see how the time it takes to run parts of MVC grows as the app gets bigger.

How does the work change when we have more data or users?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Simple MVC controller method
class UserController {
    public function listUsers(array $users) {
        foreach ($users as $user) {
            echo $this->renderUser($user);
        }
    }

    private function renderUser(array $user) {
        return "<li>" . htmlspecialchars($user['name']) . "</li>";
    }
}

This code loops through a list of users and renders each one as HTML.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each user in the array.
• How many times: Once for every user in the list.

How Execution Grows With Input

As the number of users grows, the work grows in the same way.

Input Size (n)	Approx. Operations
10	10 render calls
100	100 render calls
1000	1000 render calls

Pattern observation: The work grows directly with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to list users grows in a straight line with how many users there are.

Common Mistake

[X] Wrong: "Rendering users is always fast and does not depend on the number of users."

[OK] Correct: Each user needs to be processed and shown, so more users mean more work.

Interview Connect

Understanding how MVC parts scale helps you explain how apps handle more data smoothly.

Self-Check

"What if the renderUser method also loops through a list of user roles? How would the time complexity change?"

Practice

1. In the MVC architecture, which component is responsible for handling user input and updating the model?

easy

A. Controller

B. Model

C. View

D. Database

Solution

1. Step 1: Understand MVC roles

   The Model manages data, the View displays data, and the Controller handles user input.

2. Step 2: Identify the component for user input

   The Controller receives user actions and updates the Model accordingly.

3. Final Answer:

   Controller -> Option A

4. Quick Check:

   Controller handles input [OK]

Hint: Controller connects user actions to data changes [OK]

Common Mistakes:

• Confusing Model with Controller
• Thinking View handles input
• Assuming Database is part of MVC

2. Which of the following is the correct way to describe the role of the Model in MVC?

easy

A. It processes user input and updates views.

B. It manages the data and business logic.

C. It displays data to the user.

D. It handles routing and URLs.

Solution

1. Step 1: Recall Model's responsibility

   The Model stores and manages data and business rules.

2. Step 2: Match description to Model

   Only It manages the data and business logic. correctly states that the Model manages data and logic.

3. Final Answer:

   It manages the data and business logic. -> Option B

4. Quick Check:

   Model manages data and logic [OK]

Hint: Model is about data and rules, not display or input [OK]

Common Mistakes:

• Mixing up Model and View roles
• Thinking Controller manages data
• Confusing routing with Model

3. Given this PHP MVC snippet:

<?php
class Controller {
  public function show() {
    $data = Model::getData();
    View::render($data);
  }
}

class Model {
  public static function getData() {
    return ['name' => 'Alice'];
  }
}

class View {
  public static function render($data) {
    echo 'Hello, ' . $data['name'];
  }
}

$controller = new Controller();
$controller->show();
?>

What is the output when this code runs?

medium

A. Hello, name

B. Array

C. Hello, Alice

D. Error: Undefined index

Solution

1. Step 1: Trace data flow in code

   The Controller calls Model::getData(), which returns ['name' => 'Alice'].

2. Step 2: Check View rendering

   View::render() echoes 'Hello, ' plus the value of $data['name'], which is 'Alice'.

3. Final Answer:

   Hello, Alice -> Option C

4. Quick Check:

   Output = 'Hello, Alice' [OK]

Hint: Follow data from Model to View for output [OK]

Common Mistakes:

• Printing the array directly
• Using wrong array key
• Confusing static method calls

4. Identify the error in this MVC PHP code snippet:

<?php
class Controller {
  public function display() {
    $data = Model::fetchData();
    View::show($data);
  }
}

class Model {
  public static function getData() {
    return ['age' => 30];
  }
}

class View {
  public static function show($data) {
    echo 'Age: ' . $data['age'];
  }
}

$controller = new Controller();
$controller->display();
?>

medium

A. Model::fetchData() method does not exist

B. View::show() method is missing

C. Controller class is not instantiated

D. Array key 'age' is incorrect

Solution

1. Step 1: Check method calls in Controller

   Controller calls Model::fetchData(), but Model only has getData() method.

2. Step 2: Verify Model methods

   Model::fetchData() does not exist, causing a fatal error.

3. Final Answer:

   Model::fetchData() method does not exist -> Option A

4. Quick Check:

   Model::fetchData() method does not exist [OK]

Hint: Match method names exactly between classes [OK]

Common Mistakes:

• Assuming method names are interchangeable
• Ignoring case sensitivity
• Overlooking missing methods

5. You want to add a feature in your PHP MVC app to display a list of users. Which MVC components should you update and how?

hard

A. Update Model to display list, View to fetch users, Controller to store data

B. Update View to fetch users, Controller to display list, Model to handle input

C. Update Controller to fetch users, Model to display list, View to handle input

D. Update Model to fetch users, Controller to pass data, View to display list

Solution

1. Step 1: Assign responsibilities per MVC

   The Model fetches data, Controller processes logic, View shows output.

2. Step 2: Map feature to components

   Model fetches users, Controller gets data and sends to View, View displays user list.

3. Final Answer:

   Update Model to fetch users, Controller to pass data, View to display list -> Option D

4. Quick Check:

   Model=data, Controller=logic, View=display [OK]

Hint: Model gets data, Controller links, View shows it [OK]

Common Mistakes:

• Letting View fetch data directly
• Making Controller handle display
• Confusing roles of MVC parts