Strongly Connected Components: When to Use It

Start with the idea

A problem is a good match for Strongly Connected Components when it asks for dependency cycles, graph condensation, state machines. Here the concrete task is: Return strongly connected components with sorted members. The visible input edges=0->1,1->2,2->0,2->3,3->4,4->3 is an example, not a definition of the whole problem. Ask what operations the solution must support and what the input guarantees. Choose a representation for the operations first; when traversing, DFS explores depth and BFS follows equal-cost layers. Directed edges and disconnected components change the plan. The right choice follows from those guarantees, not from a familiar noun in the prompt.

The decisive invariant is: Use finish order plus reversed edges, or low links, to collapse mutual reachability. Try to say why it applies to the task without quoting the implementation. Which fact becomes known after one update, and which possible answers remain? A graph method needs an explicit vertex-and-edge representation. For traversal, define when a vertex becomes seen: on insertion into the frontier or on removal. If that claim cannot be maintained on a legal input, the pattern is wrong or one of its preconditions is missing. A counterexample is more useful than a vague warning: change one property of the sample, trace the first two steps, and identify the exact claim that fails.

Compare costs before committing. The advertised bound is O(V+E) time · O(V) space; identify the operation responsible for it and the extra memory it needs.