component-flattening-analysis

Map the namespace tree to identify root namespaces that have been extended by child nodes, then scan those namespaces for source files. Any source file in an extended namespace is an orphaned class that should be moved to a leaf node component.

Component flattening is the process of ensuring components exist only as leaf nodes in a namespace hierarchy. It removes orphaned classes from root namespaces by consolidating leaf code down, splitting root code into new leaf components, or extracting shared code into a dedicated component.

Consolidate down when leaf nodes contain small, related functionality that can merge into the root namespace. Split up when the root namespace contains distinct functional areas, such as separating ticket maintenance from ticket completion logic.

Yes, the methodology applies to both. For Java it analyzes package structures like com.company.survey, and for Node.js it analyzes directory structures like services/survey, detecting orphaned files in either case.

Do not use it for dependency or coupling analysis between components, or for grouping components into business domains. Those tasks belong to dedicated coupling-analysis and domain-identification skills in the decomposition sequence.