Select the appropriate sequence for developing an enterprise architecture plan:

Select the appropriate sequence for developing an enterprise architecture plan:

• A. Information architecture, business process, technology architecture
• B. Technology architecture, information architecture, business process
• C. Business process, technology architecture, information architecture
• D. Business process, information architecture, technology architecture

Answer: (D)

A business-driven sequence is used: begin by mapping the organization’s business processes and goals, then design the information architecture to support those processes, and finally define the technology architecture that will enable the information and workflows. Starting with how the business operates ensures you capture the actual needs, constraints, and value streams. With that context, you can model data and information flows that truly support decision-making and process execution. Only after the information needs are clear do you select and align the appropriate technologies, ensuring platforms, applications, and infrastructure fit the defined processes and data requirements. If you start with technology, you risk committing to solutions before understanding process needs or data requirements, leading to misaligned or wasted investments. If you jump to information architecture without grounding it in real business processes, the data models may not reflect how work is actually performed. This ordered approach—process first, information second, technology third—helps ensure coherence, traceability, and effective implementation.

A business-driven sequence is used: begin by mapping the organization’s business processes and goals, then design the information architecture to support those processes, and finally define the technology architecture that will enable the information and workflows. Starting with how the business operates ensures you capture the actual needs, constraints, and value streams. With that context, you can model data and information flows that truly support decision-making and process execution. Only after the information needs are clear do you select and align the appropriate technologies, ensuring platforms, applications, and infrastructure fit the defined processes and data requirements.

If you start with technology, you risk committing to solutions before understanding process needs or data requirements, leading to misaligned or wasted investments. If you jump to information architecture without grounding it in real business processes, the data models may not reflect how work is actually performed. This ordered approach—process first, information second, technology third—helps ensure coherence, traceability, and effective implementation.