A clear definition
Enterprise architecture designs the relationship among business, capabilities, processes, data, applications, and integrations. Its job is to make change decisions understandable and governable.
What it does not do
It does not replace executive leadership, guarantee delivery by itself, or mean drawing architecture layers disconnected from business decisions.
Questions it answers
Which capabilities are required? Which applications support them? Where is the data source? How do systems integrate? Who approves exceptions? What should be delivered first?
When it is needed
When replacing ERP or CRM, building an operating platform, unifying data, addressing complex integration, or rationalizing overlapping applications.
AETF connection
Within AETF, architecture sits in Design: after understanding the business and current state, before turning decisions into build scope or delivery waves.