TOGAF defines a balanced Enterprise Architecture practice as one that covers the four primary domains: Business, Data, Application, and Technology. Wanderlust’s practice already lists an Enterprise Architect and an Application/Technology focus, but lacks dedicated ownership for the Business and Data domains. Therefore, the missing roles are the Business Architect (to align architecture with business strategy) and the Data Architect (to govern information assets and data standards).

B. Architecture Board – Governance body, not an architecture role; Wanderlust already has an EA steering committee playing this function.

C. Application Architect – Explicitly present in Wanderlust’s current structure, so it is not missing.

1. The TOGAF® Standard

10th Edition

Part VI

chap. 32 “Establishing the Architecture Capability”

§32.4.1 (role descriptions for Business and Data Architects).

2. The TOGAF® Standard

10th Edition

Part VI

chap. 34 “Roles”

Table 34-1 (distinguishes architect roles vs. the Architecture Board).

3. MIT OpenCourseWare

“Enterprise Architecture for Managers

” Lecture 5 slides

pp. 7-9 (four-domain model and need for domain-specific architects).