National Enterprise Architecture Methodology

Define the scope of the EA development cycle to align with the entity's strategic directions, including identifying domains, viewpoints, and levels of detail based on implementation requirements. Relies on the business strategy, digital transformation strategy, and stakeholder requirements from business departments as primary inputs.

Document, understand, and evaluate the current state of EA components, collecting the information needed to comprehend existing components affected by the current development cycle. Accurate diagnosis of the current state leads to better future state design outcomes.

Define and agree on future development trends for the various EA domains by researching available information sources, local and global experiences, operational models, and relevant national requirements.

Define the initial vision for future EA domain components and align them based on current state diagnosis results and agreed-upon future trends, then detail the components and viewpoints.

Study differences between current and future EA components to identify gaps across various EA domains, and devise appropriate solutions to bridge those gaps.

Develop a list of initiatives and projects required to implement the future state and create a roadmap for their execution, based on future state design outputs and gap analysis results.

An ongoing process throughout the development cycle. Clarifies tasks for managing EA domain requirements and ensures follow-up across stages, updating and governing requirement status from initiation to closure.