Bird
Raised Fist0
DSA Javascriptprogramming~5 mins

Graph Terminology Vertices Edges Directed Undirected Weighted in DSA Javascript - Time & Space Complexity

Choose your learning style10 modes available
Time Complexity: Graph Terminology Vertices Edges Directed Undirected Weighted
O(E)
Understanding Time Complexity

Graphs are made of points and connections. We want to understand how the work grows when we look at all points and connections.

How does the time to check or use these parts grow as the graph gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.


// Simple graph representation
const graph = {
  vertices: ['A', 'B', 'C'],
  edges: [
    { from: 'A', to: 'B', weight: 5 },
    { from: 'B', to: 'C', weight: 3 }
  ]
};

// Function to print all edges
function printEdges(graph) {
  for (const edge of graph.edges) {
    console.log(`${edge.from} -> ${edge.to} (weight: ${edge.weight})`);
  }
}

printEdges(graph);
    

This code stores points and connections with weights, then prints each connection once.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

  • Primary operation: Looping through all edges in the graph.
  • How many times: Once for each edge in the edges list.
How Execution Grows With Input

As the number of edges grows, the time to print them grows directly with it.

Input Size (edges)Approx. Operations
1010 loops to print edges
100100 loops to print edges
10001000 loops to print edges

Pattern observation: The work grows in a straight line with the number of edges.

Final Time Complexity

Time Complexity: O(E)

This means the time grows directly with the number of edges in the graph.

Common Mistake

[X] Wrong: "The time depends on the number of vertices only."

[OK] Correct: The code loops over edges, so the number of edges controls the time, not just vertices.

Interview Connect

Understanding how time grows with vertices and edges helps you explain graph algorithms clearly and confidently.

Self-Check

"What if the graph was directed vs undirected? How would the time complexity of printing edges change?"

Practice

(1/5)
1. In graph terminology, what is a vertex?
easy
A. A line connecting two nodes
B. A point or node in the graph where edges meet
C. A graph with no edges
D. A graph that has weights on edges

Solution

  1. Step 1: Understand the definition of vertex

    A vertex is a fundamental unit in a graph representing a point or node.
  2. Step 2: Differentiate vertex from edges and graph types

    Edges connect vertices; weights and graph types describe edges, not vertices.
  3. Final Answer:

    A point or node in the graph where edges meet -> Option B
  4. Quick Check:

    Vertex = node/point [OK]
Hint: Vertices are points/nodes, edges are connections [OK]
Common Mistakes:
  • Confusing edges with vertices
  • Thinking weights define vertices
  • Mixing graph types with vertex definition
2. Which of the following is the correct way to represent a directed edge from vertex A to vertex B in JavaScript adjacency list?
easy
A. { A: ['B'], B: ['A'] }
B. { A: [], B: ['A'] }
C. { A: ['B'], B: [] }
D. { A: [], B: [] }

Solution

  1. Step 1: Understand adjacency list for directed edges

    In a directed graph, an edge from A to B means B is in A's adjacency list.
  2. Step 2: Check each option's adjacency list

    { A: ['B'], B: [] } shows B in A's list and empty list for B, correctly representing A -> B.
  3. Final Answer:

    { A: ['B'], B: [] } -> Option C
  4. Quick Check:

    Directed edge A->B means B in A's list [OK]
Hint: Directed edge means target vertex in source's adjacency list [OK]
Common Mistakes:
  • Adding reverse edge for directed graph
  • Leaving adjacency list empty for source vertex
  • Confusing undirected with directed representation
3. What will be the output of the following JavaScript code representing an undirected weighted graph adjacency list?
const graph = {
  A: [{ node: 'B', weight: 3 }, { node: 'C', weight: 5 }],
  B: [{ node: 'A', weight: 3 }],
  C: [{ node: 'A', weight: 5 }]
};

console.log(graph['A'][1].weight);
medium
A. 5
B. Error
C. undefined
D. 3

Solution

  1. Step 1: Access the adjacency list for vertex 'A'

    graph['A'] is an array with two objects: first with weight 3, second with weight 5.
  2. Step 2: Access the second element's weight

    graph['A'][1] is the second object { node: 'C', weight: 5 }, so weight is 5.
  3. Final Answer:

    5 -> Option A
  4. Quick Check:

    graph['A'][1].weight = 5 [OK]
Hint: Index 1 means second element; check its weight property [OK]
Common Mistakes:
  • Confusing index 0 and 1
  • Accessing weight on wrong node
  • Assuming undirected means no weights
4. Identify the error in this JavaScript code snippet representing a directed graph adjacency list:
const graph = {
  A: ['B'],
  B: ['C'],
  C: ['A']
};

// Add edge from B to A
graph.B.push('A');

// Add edge from C to B
graph.C.push('B');

console.log(graph);
medium
A. Edges added duplicate existing edges incorrectly
B. Edges added create a cycle, which is invalid
C. The graph object is mutated incorrectly causing unexpected behavior
D. No error, code correctly adds edges

Solution

  1. Step 1: Check initial graph structure

    Graph has directed edges A->B, B->C, C->A forming a cycle, which is allowed.
  2. Step 2: Verify edge additions

    Adding B->A and C->B edges extends the graph; push method correctly mutates adjacency lists.
  3. Final Answer:

    No error, code correctly adds edges -> Option D
  4. Quick Check:

    push adds edges correctly; cycles allowed [OK]
Hint: push adds edges; cycles allowed in directed graphs [OK]
Common Mistakes:
  • Thinking cycles are invalid in directed graphs
  • Assuming push does not mutate arrays
  • Confusing undirected with directed edge additions
5. You have an undirected weighted graph represented as an adjacency list in JavaScript:
const graph = {
  A: [{ node: 'B', weight: 2 }, { node: 'C', weight: 4 }],
  B: [{ node: 'A', weight: 2 }, { node: 'C', weight: 1 }],
  C: [{ node: 'A', weight: 4 }, { node: 'B', weight: 1 }]
};

Which of the following statements is true about the edge weights?
hard
A. Weights are symmetric; weight from A to B equals weight from B to A
B. Weights differ for edges in opposite directions
C. Weights are ignored in undirected graphs
D. Weights must be zero for undirected edges

Solution

  1. Step 1: Understand undirected weighted graph property

    In undirected graphs, edges have no direction, so weights between two vertices are equal both ways.
  2. Step 2: Check given adjacency lists for symmetry

    Weight from A to B is 2, and from B to A is also 2; similarly for other edges.
  3. Final Answer:

    Weights are symmetric; weight from A to B equals weight from B to A -> Option A
  4. Quick Check:

    Undirected edge weights are symmetric [OK]
Hint: Undirected edges have equal weights both ways [OK]
Common Mistakes:
  • Assuming weights differ by direction in undirected graphs
  • Ignoring weights in undirected graphs
  • Thinking weights must be zero
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard