Component Identifier

When to Use

You're designing a system and need to figure out what the building blocks should be — what components, modules, or services to create and how they relate. Typical situations:

• New system from requirements — "we have these user stories, what components do we need?"
• Monolith restructuring — "our code is a mess, how should we reorganize?"
• Pre-requisite for architecture style selection — components feed into quantum analysis
• Team is falling into the Entity Trap — creating UserManager, OrderManager instead of real components

Before starting, verify:

• Do you have requirements, user stories, or at least a domain description? If not, help gather them first.
• Do you know the architecture characteristics? If not, use architecture-characteristics-identifier first — characteristics affect component division.

Context & Input Gathering

Input Sufficiency Check