Enterprise architecture (EA) management is a commonly accepted instrument for modern organizations to deal with today's challenging environment. E ectively designed an organization-speci c EA management function can improve the overall agility of an organization. The design of such management function is a challenging task, in which the di erent process steps, information ows, and roles that constitute such function have to be shaped and aligned. The complexity of the management subject EA and the high number of involved stakeholders further aggravate the creation of a consistent but organizationspeci c EA management, and call for tool support during the design phase. In this phase, the designer selects the goals to be pursued, the concerns to be addressed, and the roles to be involved. Based on this selection, the user is supplied with re-usable and practice-proven building blocks that can be integrated into a tailored EA management function for the using organization. Di erent sources for such building blocks exist, namely the EA management pattern catalog [1] or TOGAF [5], although the latter does not explicitly state such blocks. After the organization-speci c EA management function has been de ned, it must be enacted in the organization. For the conduction phase, i.e. for managing the EA, the tool must provide support by initializing the corresponding processes and process steps, informing the relevant stakeholders, and ensuring that their information demands are ful lled. For the latter, the tool must support the generation of EA views that correspond to well-de ned viewpoints [1, 3]. These viewpoints prescribe which architectural information is conveyed to which stakeholder. Building on the prefabricates of [2], where a tool for exibly visualizing EAs is presented, we subsequently outline the core idea behind an EA management design tool that further allows to enact the designed process, sketch realization ideas, and give an outlook on future developments. Approach Central idea behind the design tool is the understanding that reusable building blocks for an EA management function may be extracted from di erent EA management approaches in literature as well as observed in practical cases. These building blocks are then aligned to a common terminology and their underlying organizational contexts as well as their pursued management goals are elicited. Thereby, the di erent possibly competing building blocks are interlinked into a nexus (cf. Figure 1) that backs the design tool. Implementation While EA management is a collaborative function, the design phase can be considered a single user task. The design tool should hence
be implemented as standalone application, e.g. based on the Eclipse Rich Client
Platform [
Goals
Outlook Building block-based modeling of EA management processes is in many ways di erent from typical process modeling. The above tool can therefore greatly bene t from using a modeling language appropriate for this purpose, i.e. a language especially supporting the composition of process building blocks. Further challenges arise from integrating the process with other building blocks, e.g. the viewpoints. In each integration, consistency must be veri ed and minor user-speci c adaptations should be supported.