Target architecture
A target architecture describes the intended structure of a system through its main building blocks, relationships and boundaries.
Make the future structure understandable
A target architecture describes how a system should be structured in the future. It connects key building blocks and interfaces with requirements and quality goals. In a fictional example, the shop and catalogue should use the same approved product dataset rather than needing separate maintenance paths.
This includes explaining where data responsibility sits and how the parts should collaborate. A list of selected software products alone is insufficient. Mark which parts already exist, are merely planned or remain unresolved. The target architecture is not automatically the current system state. The steps and intermediate states toward it also need a traceable transition plan.
Sources
Related terms
- Architecture principleAn architecture principle provides a reasoned guideline for recurring decisions about system design.
- Architecture decisionAn architecture decision establishes a significant aspect of software structure. Context and consequences explain why the choice was made.
- Target-state conceptA target-state concept describes the intended future process or system through tasks, rules and checkable expectations.
- Exit strategyA prepared route to switch, take over or retire an IT service in an orderly way.
- Migration costsEffort and expenditure for the planned move of data or functions to another environment.
- Investment costsCosts of building a new or expanded IT capability, as considered in project planning.
Articles on this topic
IT Consulting & Strategy with ASES
Strategy, architecture and technology choice