Enterprise Architecture tools
Tools to support the Strategic Dialog
To support the Strategic Dialog Enterprise Architects offers the following tools:
Several Assessments on Value Creation via surveys and special statics, like | |
Treacy & Wiersema | |
|
Osterwalder |
Van Wely | |
|
|
|
|
|
Defining and managing the Core Competences of the organization |
Tools to support Product Lifecycle Management
To support Product Lifecycle Management Enterprise Architects offers the following tools:
|
Modeling Capabilities |
|
Managing Capabilities |
|
Designing the Business Service Delivery Model |
|
Define adjustments and improvements on the Product and Delivery specifications. Register Product Owners, Suppliers and Design teams for Delivery |
|
Designing the Proposition Model |
|
Generating the maintenance apps for the Proposition components |
|
Generating the conceptual KFM based on the Proposition Model |
|
Generating the Conceptual Object model based on the Proposition Model |
|
Designing the Conceptual Object Model |
Tools to support Impact of Change Analysis
To support the Impact of Change Analysis Enterprise Architects offers the following tools:
|
Impact of Change Analysis suite |
|
Module to register the actual hours spent per profession |
Tools to support Architecture Concept Development
To support Architecture Concept Development Enterprise Architects offers the following tools:
Several Assessments on Value Creation via surveys and special statics, like | |
Treacy & Wiersema | |
|
Osterwalder |
Van Wely | |
|
Van Wely |
|
|
|
|
|
Defining and managing the Core Competences of the organization |
|
Modeling the Proposition Model |
|
Generating the Knowledge Function Model based on the Proposition Model |
|
Generating the Conceptual Model based on the Proposition Model and Elaborate |
|
Mapping the strategic choices on the Knowledge Function Model |
|
Designing Architecture Models, defining PROSA, etc. based on (extended) Archimate |
Tools to support Architecture Continuum Development
To support the Architecture Continuum Development Enterprise Architects offers the following tools:
|
Modeling and Managing all Arcitecture components in Archimate 3.0+ |
|
Design to Architecture: based on the different Transition Support tool designs it is possible to retrieve the designs in Archimate models to check the results of the developments against the PSA or generate the PEA |
|
Storing the Designs from the Design Continuum into the Architecture Continuum |
Tools to support Transition
To support the Transition Enterprise Architects offers the following solutions and tools:
|
Defining the PROSA requirements for each Knowledge Function of the solution |
|
Defining the details of Principles, Requirements, design Objectives, Standards & Agreements for the solution |
|
Generating the PSA based on the modeling the Product Service Delivery and the Information Service Delivery |
|
Generating the PID based on the PSA |
|
Supporting the Transition during different phases |
The Transition Support tools help architects in aligning the conceptual components with the logical components and the logical components with the physical components. Also, patterns within the Service delivery can be found.
|
Support pattern recognition and design of the Product Service Delivery components Actor,LifeEvent, Business Service, Contracts, Business Processes, Knowledge Functions, etc.) |
|
Support (pattern recognition and) design of the Information Service Delivery components (Knowledge Functions, Application Functions, Technical Services, etc.) |
|
Supporting modeling EPICs, User Stories, Interaction Design and Presentation Services – Also see ISE |
|
Supporting Data Management and Information & Data Service Generation – Also see AOM and ISE |
|
Supporting Business Rule Management – Also see ARM |
|
Supporting Knowledge Function Management – Also see AFM |
|
Supporting Value Creation for Process Models |
|
Supporting Competences for Actor/Role combinations with Process Activities |
Tools to support Optimization of the Design Continuum
Enterprise Architects delivers methodologies, techniques and tools to accept (or reject) the delivered components with the following tools:
|
Generating the PEA based on the delivered components and checking the PEA against the PSA |
|
Checking the PROSA requirements for each Knowledge Function of the solution components |
|
Checking the Business Objects and generalizing/specializing them against Enterprise Objects. Checking the Business to Data mapping and optimizing the mapping |
|
Generalization and Specilization of Service types |
|
Checking the details of the Principles, the Requirements, design Objectives, Standards & Agreements for the solution components |
|
Moving accepted components from one environment (Acceptance) to the other (Operations) |
Tools to support Information Lifecycle Management
Enterprise Architects delivers methodologies, techniques and tools to accept (or reject) the delivered components with the following tools:
|
Supporting Application Lifecycle Management for Architects by delivering information from the Product and Information Interaction Models, use of Service Types etc. to be able to initiate optimization requests for supply and demand chain cooperation and efficiency improvements |
|
Suite with tools for Application Rationalization. For Enterprise Architecture the following tools are relevant: |
|
Developing surveys for specific stakeholders within the Rationalization context |
|
Mapping applications against Knowledge Functions to distinguish duplications of applications that support business functionalities in which case they are candidates for rationalization |
|
Weighing the technical and business value, including the risks and criticality for the business with contract managers, financial managers. super users, information managers and technology consultants |
|
Delivering information tools and presentations to collectively weigh each application/information system individually and within selected sets of applications from several viewpoints and map them (Performance vs. Significance and Information vs. Knowledge) based on general, financial, contractual, technical, responsibility, usage, and strategy issues as displayed in text, maps, and graphs. Mapping the different applications/information systems grouped per set for their technology vs. business value and chose the strategies for rationalization (abandon, source code conversion, modernization, migration, etc.). |
|
Defining the necessity and priority of each strategy for information planning and issuing the results for Information Planning. |