An architecture process or method is required to prescribe the way architectures should be developed. Not all frameworks provide a defined process, leaving it up to an organization to create and configure their own process. Enterprise Architect can be used to define a process at any level of detail and, using the drill-down to child diagram feature, more granular aspects of the process can be elaborated. UML Activity diagrams can be used to create a suite of diagrams that express the process of architecture creation, including the processes, the tasks, the inputs and outputs, and the people that perform the various steps in the process. Enterprise Architect also has an extension called the Software Process Engineering Metamodel (SPEM) that can be used to define the process with great rigor if required. In most cases the UML Activity diagram will be sufficient to create a detailed process.
Learn More: Activity Diagram
Baseline Architectures are often difficult to justify to executive and management level stakeholders who have a greater appetite for target architecture and roadmaps. The importance of the baseline architectures is to establish the starting point that will allow transitions to the target architectures to be defined. It is often the case that documentation and models will exist that can be mined to collect material to populate the baseline repository. For example most organizations have had at least a couple of attempts at modeling the existing processes, perhaps as part of a business re-engineering effort and one or more information models and hardware diagrams will often exist.
Enterprise Architect can be used to import existing content or models from other repositories and to reverse engineer data models that can form the basis of information architecture descriptions.
Target Architectures are vital for the executives and line managers because they define the architectures that will realize the business strategies and deliver value to the enterprise. Once these are known and there is enough elaborated in the baseline architectures, the architecture team can set about the more difficult task of defining the transition architectures and creating the roadmaps that will prescribe how the target architecture can be achieved in practice using transitional steps.
Enterprise Architect has a wide range of tools that allow the target architectures to be defined for all architecture domains, including Business, Information, Application, Technology, Security, Geospatial and Social architectures. Diagrams can be created and presented in a wide range of visualizations and styles, to be relevant to the executive and implementation stakeholders alike. Tools such as the Specification Manager and the List View enable you to work with catalogs in an appealing word processor or spreadsheet view. Impact and relationships can be analyzed using the Relationship and Gap Analysis Matrices and the Traceability window.
Transition Architectures are the stepping stones from a baseline architecture to a final target architecture, and are theoretically target architectures themselves. They represent the practical steps for moving from a current state to some aspired-to future state, and will often be represented as projects or phases in a project at an implementation level.
Enterprise Architect allows Transition Architectures to be defined and related in a sequence of Roadmaps to be created so the transitions from one state to the next can be visualized and planned. Any number of Roadmaps can be defined, and they can be used for all the architecture domains so there can be, for example, Capability, Application, and Technology Roadmaps.
Learn More: Roadmap Diagram