Read The Zachman Framework text version

REVIEW OF ENTERPRISE ARCHITECTURE TOOLS LARKKI Project 2002-2004

Version: 1.0 Author: Tanja Ylimäki

Class: Public Date: 18.6.2004 Status: Final

Summary

This report reviews some of the available tools for enterprise architecture efforts. A web search was made to generate a list of tools that may be used in enterprise architecture design and management. This list was used to select tools for further review. The selection based on the availability of a demo or a trial version of the tool in addition to other material (white papers, brochures, web presentations, user manuals, etc.). The review process was adopted from the IEEE Recommended Practice for the Evaluation and Selection of CASE Tools (IEEE Std 1209-1992). The review was done by one reviewer only, and therefore any mistakes and misinterpretations of the tool functionalities are the ones made by the reviewer. The review was carried out between March and May 2004. The evaluation criteria were defined based on several references, e.g. TOGAF (its tools for architecture development section provides a set of proposed (generic) evaluation criteria for selecting architecture tools) and IEEE Std 1209-1992, which provides a basic set of criteria for evaluation and selection of CASE tools. The following evaluation criteria categories were defined: · · Tool overview Vendor qualities o General o Strategies, services o Financial considerations Tool qualities o Enterprise Architecture related issues o Modeling o Documentation o Usability o Architecture of the tool o Configuration, customizability, scalability, integration o Implementation and testing.

·

The following tools were reviewed: · · · · · · · ARIS Collaborative Suite 6.2 (IDS Scheer Inc.) Corporate Modeller Suite 9 (CASEwise Systems Inc.) MEGA version 6 (Mega) MetaEdit+ Method Workbench and MetaEdit+ 4.0 (MetaCase Consulting) METIS 3.4 (Computas) Rational Rose / XDE (Rational Rose Enterprise Edition) 2003 (IBM) System Architect 9.1 (Popkin).

In this report the following tool qualities were pointed out: the EA framework support, method support, metamodel support, modeling language support, custom diagram capability, import and export capabilities, documentation functionalities, usability, architecture, multi-user support and expandability of the tool. Other tool qualities are documented in the appendix 3.

Contents

1 2 INTRODUCTION .................................................................................................................................................... 4 EVALUATION APPROACH.................................................................................................................................. 5 2.1 2.2 2.3 3 EVALUATION PROCESS ........................................................................................................................................ 5 EVALUATION CRITERIA........................................................................................................................................ 9 TOOLS FOR ENTERPRISE ARCHITECTURE ........................................................................................................... 11

TOOL INFORMATION ........................................................................................................................................ 13 3.1 OVERVIEW OF THE TOOLS .................................................................................................................................. 13 3.2 VENDOR QUALITIES ........................................................................................................................................... 15 3.3 TOOL QUALITIES ................................................................................................................................................ 18 3.3.1 Framework support................................................................................................................................... 18 3.3.2 Method support......................................................................................................................................... 19 3.3.3 Metamodel support ................................................................................................................................... 20 3.3.4 Modeling language support ...................................................................................................................... 21 3.3.5 Custom diagram capability....................................................................................................................... 21 3.3.6 Reuse of existing constructs ...................................................................................................................... 22 3.3.7 Import/export capabilities......................................................................................................................... 23 3.3.8 Documentation capabilities ...................................................................................................................... 23 3.3.9 Usability.................................................................................................................................................... 24 3.3.10 Architecture .............................................................................................................................................. 25 3.3.11 Multi-user support .................................................................................................................................... 27 3.3.12 Expandability and integration .................................................................................................................. 27

4 5

EA TOOL SELECTION PROCESS ­ AN EXAMPLE ...................................................................................... 29 CONCLUSIONS..................................................................................................................................................... 31

REFERENCES ............................................................................................................................................................... 32 APPENDIX 1. POSSIBLE TOOLS FOR EA EFFORTS (IN ALPHABETICAL ORDER) ................................... 33 APPENDIX 2. VENDOR QUALITIES OF THE REVIEWED TOOLS................................................................... 39 APPENDIX 3. TOOL QUALITIES OF THE REVIEWED TOOLS ........................................................................ 44

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

4

1 Introduction

This report reviews some of the available tools for enterprise architecture efforts. The process of the review, as well as the structure of this report, is adopted from the IEEE Recommended Practice for the Evaluation and Selection of CASE Tools (IEEE Std 1209-1992). The evaluation criteria are derived from several resources, such as · · · · IEEE Std 1209-1992: IEEE Recommended Practice for the Evaluation and Selection of CASE Tools ISO 14102: Information Technology ­ Guideline for the evaluation and selection of CASE tools TOGAF 8.0: a set of proposed evaluation criteria for selecting architecture tools (The Open Group, 2002) DSTO-TR-1139: Review of architecture tools for Australian Defence Force by Prekop et al. (2001)

This report is part of the Larkki project's third year work related to the "Selection of Modelling Languages and Tools" section of the Larkki model for research and development of Enterprise Architecture Management (see Figure 1).

Preliminary Study: The Role of Architecture Management

Enterprise Architecture Management

Building the Metamodel: Components of Architecture Management

Building the Process Model: Processes of Architecture Management

Selection of Modelling Languages & Tools

Figure 1. Model for Research and Development of Enterprise Architecture Management in the Larkki project. Purpose of this review was to gain information about the tools that can be used in enterprise architecture management. The review was carried out between March and May in 2004. The results may be used e.g. as a starting point for an acquisition process of an enterprise architecture tool. The remainder of this report is organized as follows: Section 2 describes the evaluation process and evaluation criteria. In section 3 the main characteristics of the tools reviewed are presented. In section 4 a brief example of tool selection process is introduced. Finally, section concludes this study.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

5

2 Evaluation approach

In this chapter the evaluation approach is described. The evaluation was done by a single person and it was mainly based on the functionality of the tools. This is what Kitchenham (1996) calls the qualitative screening method and she describes it to be "a feature-based evaluation done by a single person who not only determines the features to be assessed and their rating scale but also does the assessment. For initial screening, the evaluations are usually based on literature describing the software methods/tools rather than actual use of the methods/tools."

2.1

Evaluation process The evaluation process is adopted from the IEEE Recommended Practice for the Evaluation and Selection of CASE Tools, IEEE Std. 1209-1992. It is a standard which provides guidance to individuals and organizations to evaluate and select CASE tools, and organized and comprehensive evaluation and selection processes. In this study the evaluation for future references process is applied (Figure 2). The perspective is the one of the tool user, and a number of tools are evaluated with the resulting data maintained for future reference. This evaluation is not leading directly to selection activities; in this case the evaluation is performed against the defined criteria representing all relevant criteria, in as much as the criteria of interest to future selection cannot be determined.

Figure 2. Process model for evaluation for future reference (IEEE Std. 1209-1992). The evaluation process is comprised of five phases. They are briefly described in the following (see also Figure 3). 1. Prepare the evaluation task definition statement · · Define the purpose of the evaluation (the goals and desired results). Define the scope of the evaluation (desired level of detail, necessary resources, and the extend to which the results are to be applied).

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

6

· ·

Identify assumptions and constraints (e.g. installation and training support will be available/not available, tool can be evaluated on existing hardware, or a demo version is available/not available). Define evaluation activities to be performed in order to complete the evaluation, e.g. tailor the criteria, identify and evaluate candidate tools, and report the results. Tailor the criteria, including e.g. · Selection of criteria for use · Identification of additional criteria for use · Determination of the use of each criterion for evaluation, selection, or both · Definition of one or more metrics for each criterion to be used in evaluation · Weighting of each criterion to be used in selection (not used in this evaluation) Review the criteria to ensure consistency with the task definition statement · · Create a list of candidate tools from various sources Obtain information about the software, or obtain the tool itself, or both. Information can be gathered from several sources: · Evaluations reports done by independent evaluators · Reports from tool vendors · Demonstration of the capabilities by the vendors (not used in this evaluation) · Information obtained from the users of the tools (not used in this evaluation) Collect data; a number of ways can be used: · Examine the tool and gathered documentation, · Interview the actual users (not used in this evaluation), · Examine sample output from projects that have used the software (not used in this evaluation), · View demonstrations and interview demonstrators (not used in this evaluation), · Execute test cases (not used in this evaluation), · Apply the tools in pilot projects (not used in this evaluation), · Examine previous evaluations.

2. Identify and select evaluation criteria: ·

·

3. Identify candidate tools:

4. Evaluate candidate tools: ·

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

7

5. Report the results: When an evaluation has completed, a report is developed containing e.g. the following information: · · · · · executive summary introduction (e.g. purpose, desired results, time frame, experience of the evaluators) evaluation approach (e.g. evaluation process, obtained tools, supporting data, context and scope of evaluation, assumptions and constraints) evaluation steps: Specific steps executed to illustrate the scope and depth of the evaluation and to repeat the evaluation if desired tool information/evaluation results · Case tool name and version · Vendor · Point of contact · Host configuration · Cost elements · Background as appropriate · Description of case tool · Software engineering processes for which the case tool is intended · Case tool software environment (e.g. programming language(s) supported, operating systems, database compatibility) · Relevant case tool functions · Input/output structure · Application domain · specific results: Results should be provided in terms of the evaluation criteria summary and conclusions appendixes · List of possible EA tools · Evaluation task force statement · Tailored criteria list

· ·

This outline of the report content was applied in this report with some alterations made to the section describing the tool information.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

Evaluation task definition statement: - Purpose - Scope - Assumptions and constraints - Evaluation activities

8

IEEE Std 1209-1992

Prepare the evaluation task definition statement

TOGAF Criteria

Review of architecture tools for Australian Defence Force ISO/IEC 14102

Identify and select the criteria

Tool Evaluation Criteria

List of possible canditates Web Search (both CASE and EA tools) Identify canditate EA tools Information about the tools and/or the tool itself

Data can be collected in a number of ways: - examine the tool and gathered documentation - interview the actual users - examine sample output from projects that have used the software - view demonstrations and interview demonstrators - execute test cases - apply the tools in pilot projects - examine previous evaluations

Evaluate canditate EA tools

Evaluation data

Report the results

-

Evaluation report: executive summary evaluation background evaluation approach tool information evaluation steps specific results summary and conclusions appendixes

Figure 3. The evaluation process is based on the process described in IEEE Std 12091992.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

9

2.2

Evaluation criteria Evaluation criteria used in this review were defined based on the following references: · · · · TOGAF's Tools for Architecture Development section provides a set of proposed (generic) evaluation criteria for selecting architecture tools. IEEE Std 1209-1992 provides a basic set of criteria for evaluation and selection of CASE tools ISO/IEC 14102 defines a set of characteristics and sub-characteristics that can be used in evaluation or selection process. A Review of Architecture Tools for Australian Defence Force (Prekop et al., 2001) includes a review template outlining the different areas to consider when reviewing architecture tools.

Examination of the above references led to the definition of the following evaluation criteria categories: · · Tool overview Vendor qualities o General o Strategies, services o Financial considerations Tool qualities o Enterprise Architecture related issues o Modeling o Documentation o Usability o Architecture of the tool o Configuration, customizability, scalability, integration o Implementation and testing

·

After several iterations the final set of evaluation criteria was generated. The set is as follows:

I TOOL OVERVIEW Type of tool (EA tool, general modeling tool, BPR tool) Tool description (e.g. purpose of tool, structure of tool, overall impression) II VENDOR QUALITIES General Vendor name Vendor site Location (address of the headquarters) History: e.g. how long has vendor existed in this arena, how long has the tool existed, size of vendor? Any other items of interest (e.g. any certifications received from a professionally recognized software engineering evaluation organization (e.g. SEI, ISO), that shows that the SE practices of the vendor meet some minimum level) Strategies, services Vision/mission/strategy (general) Product strategy (e.g. single product, product family, complementary products) Service strategy (e.g. availability, responsiveness) Training (e.g. availability of training materials, training courses, costs, style of learning) Channels/partners or geographic coverage

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

10

Customer references Any other items of interest Financial considerations Pricing Strategy (e.g. what is the acquisition cost/total cost of ownership including e.g. implementation, maintenance, equipment, support) Licensing policies III TOOL QUALITIES Enterprise Architecture related issues Supported frameworks and/or standards (related to enterprise architecture) Supported Methodologies (UP, OOA, etc) Supported Modeling languages (UML, IDEF0, BPMN etc.) If multiple methodologies are supported, how are the different approaches integrated? Is it possible to move data between different approaches? Metamodel support (ability to configure, tailor and/or import metamodels/frameworks) EA life-cycle support (Which phases are supported: requirements gathering, design, analysis, implementation, testing, maintenance, etc.?) Support for various architectural views/constructs out-of-the-box (e.g. business processes, data, application, technology) Support for creation of custom views/models/constructs Does it provide templates or patterns for constructs, which can be used to help organizations "jump start"? Any other items of interest Modeling Overview of the modeling interface (e.g. layout of the interface, how well uses the screen space, is the interface logical and consistent to navigate, how well it follows the conventions of the host operating system?) Diagram types supported (Block, Chen, control flow, data flow, ER-model, OO etc.) Requirements specification entry, editing and storing capabilities Requirements specification language (capability to import, export or edit requirements using a formal language) Design specification entry, editing and storing capabilities Design specification language (capability to import, export or edit design information using a formal language) Drawing support (auto draw, auto layout, auto connections etc.) Reuse of existing constructs (e.g. models/diagrams/data/objects) Customization of iconography (e.g. can the icons of the entities, relationships etc. be customized?) Traceability (of the requirements) Specifications consistency and completeness checking Simulation Customizable automation functions (e.g. scripts, macros; what elements are they used to automate?) Import/export of models/data Any other items of interest Documentation Editing functionality (enter and edit data in text/graphical/forms-based format) Publishing (output formats, hypertext support, customization etc.) Conformance to documentation standards (capability to produce output) Automatic extraction and document generation (the extent to which the tool can extract textual and graphical data and generate a document as specified by the user) Linking supporting documents or data to architecture constructs (e.g. reports, surveys) Any other items of interest Usability Consistency of user interface (consistency of the locations and representations of commonly appearing display elements and user input methods) An easy to follow "process map" guiding the use of the tool / ease of learning (the amount of time and effort required to understand normal tool operations and to become productive) On-line help / user guidance (e.g. availability, clarity, readability, usefulness). Searching/navigating/viewing capabilities of models/artifacts/components Knowledge requirements /user friendliness (the background and level of experience and

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

11

expertise required to effective use) Does it provide a way for consistently naming and organizing the artifacts? Any other items of interest Architecture of the tool (operating environment and repository) Deployment architecture (single tool, several closely related tools, single workstation, client/server, etc.) Web functionality (Is it accessible through web client?) Software/hardware supported/required Backwards compatibility with prior releases of the tool / ability to move data between versions of the tool Supported standards (e.g. database, repository, communication, GUI, configuration management, security, information interchange standards, APIs) Repository structure (structure between the tool and its repository) Supported databases Teamwork capabilities (Multi-user concept: is the repository capable of supporting concurrent multi-users?) Does the repository allow import/export of models/data? If so, can it deconflict the various models if needed? What kind of management functions does the repository provide (versioning and/or change control, ability to roll back/forward between different versions, tracking of modifications, access control, automatic backup, etc.)? Any other items of interest Configuration, customization, scalability and integration Internationalization / localization capability Expandability (e.g. add-ons) Does it integrate with other tools? Compatibility with other tools (capability to operate with other tools like word processors, databases, repositories, other case tools) Does the tool have capacity constraints (e.g. size of data, number of files, and number of data entries/records)? Any other items of interest (e.g. ease of installation, archival capability, administration tools) Implementation and Testing Code generation capabilities Prototyping Database schema generation capabilities Reverse engineering capabilities Debugging and testing capabilities Any other items of interest

2.3

Tools for Enterprise Architecture In the appendix 1 there is a list of possible tools that can be used in enterprise architecture efforts. The list is generated based on the information gathered by a web search. For example the following sources were found: · · · · · A Review of Architecture Tools for Australian Defence Force (Prekop et al., 2001) GEAO (Global Enterprise Architecture Organization), http://www.geao.org/resources/eatools.jsp Selecting an Enterprise Architecture Modeling Tool Category (Peyret, ?) Enterprise Architecture Tools, http://www.enterprisearchitecture.info/Architecture_Tools.htm Case tools, http://www.cs.queensu.ca/Software-Engineering/tools.html Case tools, http://www.compinfo-center.com/apps/case_tools.htm

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

12

· · ·

Business Process Modeling Tools, http://is.twi.tudelft.nl/~hommes/toolabc.html Data modeling tools, http://www.databaseanswers.com/modelling_tools.htm Government Computer News; Enterprise Architecture tools merge the real with the ideal, www.gcn.com/newspics/G07buyersp66.pdf

The tools for further review were chosen from the list presented in the appendix 1. Selection was primarily based on the availability of a demo or a trial version of the tool in addition to other material (e.g. white papers, brochures, web demonstrations, user manuals). Tools were categorized roughly into three categories: BPR tools (meant primarily to business process (re)engineering), general modeling tools (meant primarily to software design), and EA tools (marketed primarily for EA design). The tools chosen for more detailed review are presented in the table 1. The review of the tools was done by one reviewer only, and any possible mistakes or misinterpretations of the tool functionalities are the ones made by the reviewer. Table 1. The list of tools selected for further review.

Product name 1 2 3 4 ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 MEGA version 6 MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4 Vendor IDS Scheer Inc., www.ids-scheer.com CASEwise Systems Inc., www.casewise.com Mega www.mega.com MetaCase Consulting, www.metacase.com Computas, http://www.computas.com www.metis.no IBM, www.ibm.com/rational Popkin, www.popkin.com Tool Category BPR tool EA tool BPR tool / EA tool General modeling tool EA tool

5

6

7

Rational Rose / XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

General modeling tool General modeling tool/ Ea tool

In the following chapter these tools are described in more detail.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

13

3 Tool information

In this chapter the main characteristics of the tools reviewed are presented organized by the tool evaluation criteria categories. First the overview of the tools is given, second vendor qualities are presented and third the main tool qualities are introduced. The complete review data can be found in the appendices 1 and 2.

3.1

Overview of the tools Brief descriptions, supported frameworks, standards and methodologies, and additional product information of each reviewed tool are presented in the following table (tools are in alphabetical order). Table 2. Overview of the reviewed tools.

Product name and vendor

Description

ARIS Collaborative Suite 6.2 IDS Scheer Inc., www.idsscheer.com

ARIS Collaborative Suite 6.2 consists of ARIS Easy Design, ARIS Toolset and ARIS Web Designer These are tools to design, analyze and optimize business processes. It also includes ARIS Business Server and ARIS Repository. ARIS products can be used to e.g. to generate company documentation (objectives, organization structure, functions, processes), database design, PC hardware and network management, activity-based cost calculation, quality management, introducing SAP R/3, software development and introduction. The Corporate Modeler Suite is a Windows-based enterprise modeling solution that enables you to visualize, communicate and optimize your organization's business processes and systems. Corporate Modeler can be used e.g. to process and application design, enterprise architecture, process/data analysis, ERP and consulting, IT architecture, cost reduction. The Suite consists of the following components: CorporateModeler: Capture, analyze, optimize, simulate and implement business processes and enterprise architecture. Corporate Publisher HTML: Manage process and enterprise architecture knowledge across the business Corporate Publisher Word: Automatically generate professional reports and procedure manuals Automodeler: Import existing knowledge to kickstart your modeling Links to development and BPR tools like RationalRose, ERWin, Oracle Designer, Visio.

Frameworks/ standards or methodologies supported e.g. UML

Other issues (e.g. additional products or services) ARIS = Architecture of Integrated Information Systems developed by professor Dr. August-Wilhelm Scheer

Corporate Modeller Suite 9 CASEwise Systems Inc., www.casewise. com

Casewise Framework based on the Zachman Framework

Other products: ITArchitecture Accelerator, Balanced Scorecard Accelerator

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor Description

Review of EA tools 18.6.2004

Frameworks/ standards or methodologies supported Zachman Framework, UML

14

Other issues (e.g. additional products or services) Technical modules complement MEGA's offering to customize the platform to customer's specific needs: MEGA Documentation, MEGA Intranet, MEGA Generation, MEGA Supervisor

MEGA version 6 Mega www.mega.co m

MEGA Software Suite is a integrated set of tools targeted at teams of business analysts and IT developers for business process modeling, enterprise architecture, model-based application development and data modeling. The suite consists of: MEGA Process: Business Process Analysis & Improvement MEGA Architecture: Map And Plan Business And Information Systems MEGA Integration: Business driven analysis and design for workflow and application integration projects MEGA Development: Software component specification & design MEGA Database: Database Analysis and Design MetaEdit+ metaCASE tool allows you to design your method and use it. First you design the method with Method Workbench and then all developers use the method with MetaEdit+. Many predefined methods available.

MetaEdit+ Method Workbench and MetaEdit+ 4.0 MetaCase Consulting, www.metacase .com METIS 3.4 Computas http://www.com putas.com, www.metis.no

e.g. UML, OMT, OOAD, IBM BSP

Rational Rose / XDE (Rational Rose Enterprise Edition) 2003 IBM, www.ibm.com/r ational

Metis is a family of client/server products for creating, visualizing, changing, sharing and managing enterprise models, e.g. Metis Model Browser, Metis Model Annotator Metis Modeling Workbench (Editor, Designer, Metamodel Developer) Metis Team Server Metis Business Solutions (templates) Object-oriented modeling tools, such as - IBM Rational Rose XDE Modeler: Enables to produce language-independent Unified Modeling Language (UML) models of software architecture, business needs, reusable assets and managementlevel communication. - IBM Rational Rose XDE Developer: Offers a set of model-driven development and runtime analysis capabilities for building software applications. - IBM Rational Rose Data Modeler: Provides the realization of the ER methodology using UML notation to bring database designers together with the software development team. - IBM Rational Rose Technical Developer: Supports the most advanced modeling constructs, including model execution and fully executable code generation.

Zachman, TOGAF 7(8), TEAF, FEAF, C4ISR (DoDAF), UML 2.0

IT Management template supports Zachman-like approach, DoDAF template, UML template (not available yet??)

UML, MDA

Many other tools for e.g. requirements and analysis, testing and software configuration management

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor Description

Review of EA tools 18.6.2004

Frameworks/ standards or methodologies supported Zachman Framework, TOGAF, DoDAF (C4ISR), BPMN, IDEF, RUP, Structured Analysis & Design

15

Other issues (e.g. additional products or services) Popkin Model Agency: a directory of industry and technology standard models, all of which are available as a Popkin encyclopedia.

System Architect 9.1 Popkin, www.popkin.co m

System Architect is a modeling solution designed to provide all of the tools necessary for development of enterprise systems. It integrates business process modeling, object-oriented and component modeling with UML, relational data modeling, and structured analysis and design.

3.2

Vendor qualities In this chapter the summary of vendor qualities (including e.g. product and service strategy) of each tool are presented. More details about the vendors can be found in the appendix 2. ARIS Collaborative Suite 6.2

Vendor name Vendor site Location History IDS Scheer Inc. www.ids-scheer.com Altenkesseler Straße 17, D-66115 Saarbrücken, Germany The company was founded in 1984 by Prof. August-Wilhelm Scheer. ARIS Toolset was launched in 1992, ARIS Reference Models in 1994, in 1996 ARIS is the de facto standard for process modeling: Gartner Group has certified leading worldwide market position among business process reengineering solutions. Develops corporate solutions for business process management. With its ARIS product family (ARIS Process Platform), the company offers a complete portfolio for developing, implementing, operating, controlling and evaluating business processes. Service Portfolio: - Training & Workshops - Project support - Individual development - Solution Packs - Technical support

Product strategy

Service strategy

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

16

Corporate Modeler Suite 9

Vendor name Vendor site Location History Casewise Systems Inc. www.casewise.com 100 Century Parkway, Mount Laurel, New Jersey, 08054, USA Founded in 1989, a privately owned company. It evolved from a company called Inforem, a consulting company which used an early version of the tool. Primary product is the Corporate Modeler Suite; which consists of several applications. Other products: IT Architecture Accelerator, Balanced Scorecard Accelerator. There are two versions of the core product: · Corporate Modeler ­ a limited version of the product which comes with Simulation and Visio Link, and · Corporate Modeler Enterprise ­ a complete version of the product that includes multiple extensions, including Corporate Publisher HTML, Corporate Publisher Word, Automodeler, Simulation, and Visio, Rational Rose, and Power Designer Links. Training, technical support, consulting (enabling consulting to define e.g. modeling standards and symbology for a modeling team in a customer organization; project consulting to improve customer organization's business processes).

Product strategy

Service strategy

MEGA

Vendor name Vendor site Location History MEGA www.mega.com 10 boulevard du Montparnasse, 75015 Paris, FRANCE Founded in 1991 headquartered in Paris; 170 employees, 100 consultants specialized in business process & enterprise architecture, 800 customers, 23,000 users worldwide. MEGA Suite first came into existence already in 1979 used by the consultants of Hay Group. MEGA is a dominant modeling tool vendor in France. Product family: Mega Process, Mega Architecture, Mega Integration, Mega Development, Mega Database and administration modules (Mega Documentation, Mega Intranet, Mega Generation, Mega Supervisor). MEGA products are built around the same repository-based structure and can easily be integrated if necessary to provide the user with a consistent desktop. Training, consulting, technical support. MEGA Consultant solutions include Business Process, Enterprise Architecture and Risk Management. Technical support is provided via telephone, email and web services.

Product strategy

Service strategy

MetaEdit+ Method Workbench and MetaEdit+ 4.0

Vendor name Vendor site Location History MetaCase Consulting www.metacase.com MetaCase, Ylistönmäentie 31, FIN-40500 Jyväskylä, Finland MetaCase is the leading provider of domain-specific modeling environments. Since 1991, MetaCase has been enabling customers to improve their productivity and competitiveness with development methods and tools that fit their needs. Two products: MetaEdit+ and MetaEdit+ Method Workbench Training, maintenance.

Product strategy Service strategy

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

17

METIS 3.4

Vendor name Vendor site Location History Computas www.computas.com Computas USA: 2721 226th Ave SE Sammamish, WA 98075. Computas Norway: P.O. Box 482, N-1327 Lysaker, Norway Computas was established in 1985 as Computas Expert Systems. Computas is a mixed product/consultancy-company, combining the product lines Metis and FrameSolutions with a highly educated workforce delivering solutions based on these products. In the early summer of 2000 Computas bought Metis AS from NCR Corp. Two product lines: Metis product family and FrameSolutions (to build knowledge-based systems for work process assistance) * Consulting, training and support * Model design and development * Metamodel design and development * Knowledge acquisition and engineering * Software design and development * Business process analysis and design * Project planning and management * Systems design and integration

Product strategy Service strategy

Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003

Vendor name Vendor site Location History IBM www.ibm.com Corporate offices: IBM Corporation, New Orchard Road, Armonk, New York 10504. IBM Finland:PL 265 (Laajalahdentie 23), 00101 Helsinki IBM was incorporated in the state of New York on June 15, 1911 as the Computing-Tabulating-Recording Company (C-T-R). Rational Software Corporation was founded in 1981. Its tools became IBM offerings by the acquisition of Rational Software Corporation by IBM Software Group in February 2003. In Finland IBM has been operated since 1936. Five primary software brands: DB2, WebSphere, Tivoli, Rational, Lotus E.g. consulting, training, support, outsourcing, security and privacy

Product strategy Service strategy

System Architect 9.1

Vendor name Vendor site Location History Popkin Software www.popkin.com 11 Park Place New York, NY 10007, USA Jan Popkin established the company in 1988, based on his recognition of the need for tools and techniques to utilize the software industry's technical and managerial resources. Since 1988, Popkin Software has developed and produced a portfolio of products that have evolved into the company's current flagship offerings: System Architect and XML Architect. In 1995 Popkin Software acquired its UK distributor and successfully integrated it into the company. It now serves as Popkin's European headquarters. Two main products; System Architect and XML Architect (XML schema editor). In addition, they provide Model Agency, which is directory of industry and technology standard models, all of which are available as a Popkin encyclopedia. Training, technical support, web site resources (e.g. tool tips).

Product strategy

Service strategy

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

18

3.3

Tool qualities In this chapter the summary of the tool qualities are presented. From the Enterprise Architecture related issues, the framework support, method support and metamodel support are covered. From the modeling issues modeling language support, custom diagram capability and import and export capability are covered. Other issues included are documentation, usability, architecture, multi-user support and expandability of the tool. The whole comparison table with the tool qualities in detail can be found in the appendix 3.

3.3.1

Framework support In table 3 the framework support of the tools is presented. In the comparison no profound evaluation was done on the quality or extension of the framework support. For example, in System Architect the Zachman Framework support basically means the ability to organize and access the diagrams and data through the Zachman Framework cells. In this comparison, METIS has the most extensive support of existing frameworks. MetaEdit+ does not support any of the frameworks out-of-thebox, but via its Method Workbench can different frameworks be applied by defining the models and model elements needed to implement those frameworks.

Table 3. Support of Enterprise Architecture related frameworks.

Other/proprietary X1 X X4 X C4ISR/DoDAF

Zachman

TOGAF

TEAF

FEAF X

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 (X)2 MEGA version 6 X X MetaEdit+ Method Workbench and MetaEdit+ 4.03 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1 X X5 X X X X X X

X

Aris Framework. The Casewise Framework of Corporate Modeller is based on the renowned Zachman Framework. 3 With MetaEdit+ Method Workbench any framework can be used if it defines models to be created. 4 ITM Template (EA template for Metis). 5 Zachman Framework is illustrated as packages.

2

1

MDA

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

19

3.3.2

Method support In table 4 the out-of-the-box method support of the tools is presented. Many tools provide an in-house method. For example, MEGA allows describing the interrelationships of the application integration, development, architecture, or organization projects using the MOKA (MEGA Open Kit Approach) methodology and System Architect introduces a Popkin process. MetaEdit+ supports various methodologies and any other methodology can be applied through its Method Workbench. METIS is methodology-neutral; appropriate method can be applied. METIS Metamodel Developer can be used to customize the existing methodologies or create tailored ones from scratch.

Table 4. Method support of the reviewed tools (out-of-the-box).

Other OO methods IDEF Methodology Other/proprietary X6 X7 X X X X9 X Structured methods Rational Unified Methodology X X X

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 MEGA version 6 MetaEdit+ Method Workbench and MetaEdit+ 4.08 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

10

X

TOGAF ADM

6 7

X

ARIS Method, The Balanced Scorecard method MOKA (MEGA Open Kit Approach) methodology 8 Predefined methods: UML, OMT, OOD, OOAD, Fusion, Moses, OOSA, SAD, Real-time SA/SD, IBM BSP, Porter's value chains & value systems, activity analysis 9 Other methodologies can be applied also (via the Framework Wizard). 10 IDEF methodology, SSADM, Gane&Sarson, Yourdon/DeMarco, Ward&Mellor, Information Engineering, TOGAF ADM, Rational Unified Process (RUP), The Popkin process

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

20

3.3.3

Metamodel support Metamodel support of each reviewed tool is presented in table 5. All the reviewed tools had some kind of ability to modify the metamodel or create new metamodels. Table 5. Metamodel support of the tools reviewed.

ARIS Collaborative Suite 6.2 ARIS Configuration allows you to adapt parts of the ARIS method to your own requirements. You can rename model types, object types, symbols, attribute types and attribute type groups. You can create your own symbols (graphics) for object types. You can also configure specific attributes individually and assign these attributes to any attribute type groups. Metamodel, i.e. Casewise framework, is customizable. The framework is not very explicit though. Metamodel defines the structure used to store the data managed in a repository. The metamodel is saved in the environment system repository. The metamodel contains all the object types used to model a system, and specifies their attributes and the possible links between these object types. The metamodel allows models to be built that describe the organization of the information system of an enterprise. Additional object types can be created and managed. Extracts from the metamodel are called Dialogs and these can be used to manipulate specific structures and objects within the metamodel. This can be useful in representing a structure in one way to one type of user and a different way to a manager for example. Metamodel (method) is customizable. With Method Workbench new methods can be created Metamodel can be modified or tailored models can be created with the Metis Metamodel Developer Frameworks can be modified or created with the help of the Framework wizard (an add-in available only on Windows, and only in some Rose editions). Before creating a new framework the following files must be created: A model file (.mdl) that defines the content of the framework, i.e. the template to be used when creating new models from this framework; an icon file (.ico) that contains the icon to be used as a symbol for the new framework in the Create new model box; a documentation file (.rtf) that contains the description of the framework. Frameworks can be modified with the help of Framework editor. A new framework can be created (a grid) also. Appropriate model types can be attached to the framework cells. The overall metamodel of the tool can be modified with the USRPROPS.TXT file; e.g. diagrams, symbols or definition types can be renamed or new ones created. Also new properties for diagrams, symbols or definition types can be added

Corporate Modeller Suite 9 MEGA version 6

MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003

System Architect 9.1

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

21

3.3.4

Modeling language support In table 6 the modeling language support of the tools is presented. It can be seen that UML is the most supported modeling language. Again, MetaEdit+ can support any modeling language through its Method Workbench. System Architect is also rather powerful with is modeling language support. Table 6. Modeling language support of the tools reviewed.

Other(s) X X X IDEF1X BPMN IDEF0 IDEF3

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 MEGA version 6 MetaEdit+ Method Workbench and MetaEdit+ 4.011 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

X

X X X X X X X

X

X

X

X

X

X

X

X

X

X

3.3.5

Custom diagram capability Support for creation of custom models/diagrams/constructs of each reviewed tool is presented in table 7. All the reviewed tools had some kind of ability to modify the diagrams elements and/or create new diagrams types and diagram elements. Table 7. Support for creation of custom diagrams of the reviewed tools.

ARIS Collaborative Suite 6.2 ARIS Model Generation allows you to generate new views of existing database contents. Existing models or objects may be combined according to specific rules, thus creating new models providing additional information. The source models or objects remain unchanged. ARIS Model Generation is a tool for generating new models based on existing information without having to model them manually. Also so called Quick model type allows the creation of models without any method restriction. Custom object types, custom object property types, custom association types can be created. Possibility to create user-defined notation style and symbology with generic modeler. Names of the predefined property types can't be changed. You can write your own help text for both user-defined and predefined design objects. Custom models (or other objects) can be defined through metamodel (See Metamodel support). With Method Workbench new methods and therefore new models/constructs can be defined. [Continues on the next page]

Corporate Modeller Suite 9

MEGA version 6 MetaEdit+ Method Workbench and MetaEdit+ 4.0

11

MetaEdit+ Method Workbench enables any modelling language to be used. Many predefined languages exist.

OMT

UML

Information Technology Research Institute LARKKI project Tanja Ylimäki

METIS 3.4

Review of EA tools 18.6.2004

22

Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

In Model Editor you can create a new model view from selected instances in your original model view or from the results of a visual query. The new model view will be independently modifiable, for quick customization/reporting to a specific target audience. Relocate model views, with or without underlying model data, to separate model files. With Developer you can modify, extend and define new types, criteria, methods, metamodels and templates, to create support for new modeling standards and methodologies. Free-form modeling is possible. If a new framework is created, it is possible to define new views/models (using UML notation, though).

Because a custom framework can be created, can also custom views be created.

3.3.6

Reuse of existing constructs Support for reuse of existing models/diagrams/constructs of each reviewed tool is presented in table 8. The concept and context of reuse varied within tools. Usually reuse of modeling data is possible within the borders of the database, like in ARIS and Corporate Modeller. System Architect claims all models and diagrams to be reusable. Table 8. Reuse of the existing constructs.

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 Data cannot be copied beyond borders of database. ARIS Merge can be used to merge the contents of multiple databases into one master database consistently and without generating redundant items. Data (i.e. objects) can be reused within a model (a collection of objects stored in a database). Auto Modeler can import existing process and system documentation held in Microsoft Word or Excel formats into an existing or new model. Objects can be copied from existing models to a new model. When you copy a diagram, you create a new diagram (i.e. it has a separate Id and must have a unique name). However, you do not create copies of the objects that appear on the diagram (you can have many instances of the same object on multiple diagrams). Transferring data between models is possible if you first export data (or the model design) to an external XML file and then import from that file into either a new or existing model. Objects that exist in a repository can be added (connected) to a new diagram. Contents of a diagram can be copied into a new diagram. Objects can be duplicated also (if they can appear multiple times within a diagram). Graphical objects can be added to diagrams. Components can be browsed, selected and reused with the Component Selection Tool. It is possible to copy, paste, duplicate and delete instances and views. The whole model can be used as a starting point for a new model. Reengineering capabilities allows using existing code or database schema as a starting point of developing new models. All existing models/diagrams are reusable

MEGA version 6

MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

23

3.3.7

Import/export capabilities Support for import and export capabilities of each reviewed tool is presented in table 9. All tools support XML import/export either out-of-the-box (like ARIS) or through an add-on product (like METIS). Usually models/diagrams can be exported and imported, but also the whole database content import/export can be possible (e.g. in System Architect). Table 9. Import and export capabilities of the reviewed tools.

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 MEGA version 6 XML import/export; UML Designer: XMI export/import. ASCII format data can be imported/exported from the repository. XML import/export of model (collection of objects) or selected model objects. CSV files can be loaded with Auto Modeler Data can be imported/exported in several formats (within MEGA Generation); e.g. Java, C++, RationalRose, VisualBasic, XMI, XMD. Exporting in MGR-format (MEGA format) allows to create a consistent set of objects and enables to transfer part of a design into another repository. For example, exporting MEGA objects from a diagram exports the objects found in this diagram, as well as the objects depending on them Diagrams can be exported to clipboard (GIF, PICT files). Matrices and tables can be exported to ASCII (tab-separated for pasting the matrix into a spreadsheet) and HTML. XML import/export CSV import/export facility. XML Interface is a new add-on product enabling import of any file-based XML data into Metis. XMI import capability, import of Rose files (.mdl, .ptl, .cat, .sub). Definition data of the dictionary can be imported/exported in CSV/text format. Import/export of diagrams and definition data via XML. From the repository encyclopedia files (i.e. databases or projects) can be imported/exported.

MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4 Rational Rose/XDE 2003 System Architect 9.1

3.3.8

Documentation capabilities Documentation capabilities of each reviewed tool are presented in table 10. All tools enable generation of HTML reports (pages) of the model content to be shared over the internet. Additional output formats are also provided by all tools, such as RTF (e.g. Mega) and Excel tables (e.g. Aris). Also definition of custom reports are possible e.g. in MetaEdit+ and in System Architect. Table 10. Documentation capabilities of the reviewed tools.

ARIS Collaborative Suite 6.2 ARIS Web Publisher (add-on) enables to communicate the process models globally via the Internet and intranet; In ARIS Toolset reports of models can be generated in several formats, e.g. RTF, word document (.doc), Excel document (.xls), HTML, text file Word documents, HTML document or multiple HTML pages can be generated with Corporate Publisher. Publication set object type in the Repository Explorer tree contains the templates for reports and they are customizable). It is possible to copy diagrams, or selected objects on diagrams, as graphic files or to embed them as pictures in MS Word documents. You can also copy matrices to spreadsheets. With Auto Modeler, you can download diagrams directly into PowerPoint. Diagrams can naturally be printed directly from the modelers.

Corporate Modeller Suite 9

Information Technology Research Institute LARKKI project Tanja Ylimäki

MEGA version 6

Review of EA tools 18.6.2004

MEGA provides a mechanism to generate HTML pages directly from the repository to create a web site to share information. Also MS Word documents can be generated (RTF). Supports XML also. MetaEdit+ offers pre-built reports for model analysis, checking and documentation in Word, RTF, HTML, XML and XMI. Predefined reports are available for all graphs. MetaEdit+ comes with a set of standard reports which can be used to document and check the design results independently of the method in use (e.g. object list, property list, dictionary, object connections, checkings, graph documentation in HTML and RTF formats). Code generators and other custom reports are defined with MetaEdit+ Report Browser With Metis Editor (HTML Report Wizard) models can be published e.g. to local disk, CD, or web servers in full dynamic mode for use with Model Browser or Annotator, or as HTML pages for easy access from any web browser. Automatic generation of browsable HTML version of the model content. Word documents can be generated with SoDA.

24

MetaEdit+ Method Workbench and MetaEdit+ 4.0

METIS 3.4

Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

HTML, XML reports. Standard and ad hoc Word-reports can be generated. Automatic generation of browsable HTML version.

3.3.9

Usability Usability issues of each reviewed tool are presented in table 11. Only the ease of learning and the user guidance criteria are reported here. More usability criteria can be found in the appendix 3. All tools provide on-line help and tutorials or model examples to study the usage and the functionality of the tool. MetaEdit+ provides rather extensive overview of the predefined modeling techniques. Table 11. Usability of the reviewed tools.

ARIS Collaborative Suite 6.2 "Process map" guiding the use of the tool / ease of learning ARIS Method guides the use of the tools. Also Quick start guide available. Nevertheless, the broad functionality of the product has one down side; clarity and therefore intuitive use suffers Casewise framework (or the original Zachman Framework) can be used as a process map; a project kick off diagram combines elements from all columns in the appropriate level to show the scope of a project. The framework is not, however, explicit. At startup a window is opened to show links to explanatory wizards (guided tour, my first diagram, my first business process), and documentation files. On-line help / user guidance Online help introduces e.g. Aris House (the views and layers of the models); all models are described. Comprehensive Aris Method documentation. Some manuals available in pdf format. Online help includes quick references to start working with the Corporate Modeler (how to create models, how to draw diagrams, how to create templates etc.). Additional knowledge base is available in the web. On-line help available describing the basic functionalities and tools.

Corporate Modeller Suite 9

MEGA version 6

[continues on the next page]

Information Technology Research Institute LARKKI project Tanja Ylimäki

MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4 Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

Review of EA tools 18.6.2004

On-line help with graphics and hypertext features. Method support provides help about the modeling technique, its components, reports and links to other techniques. Tutorials available (for MetaEdit+ and Method Workbench; evaluation tutorial). Online help available + example models. Online help, user's guide, installation guide, licensing guide, online product tour and other tutorials, sample models available. Resources available on the web, e.g. UML Resource Center. Online-help and user guide available + tutorials (business process modeling, UML modeling, data modeling, simulation etc.).

25

No actual process maps; method support exists that can be utilized.

N/A The Rational Unified Process (RUP) framework model can be used as a process map guiding the use of the tool.

The Popkin process can be used to guide the use of the tool. Using e.g. the Zachman framework interface helps to find the appropriate models, diagrams or definitions.

3.3.10

Architecture Architecture, web functionality and repository structure of each reviewed tool are presented in table 12. The architecture of the tools is either 2-tier (client/server) or 3tier (client/server/repository). Stand-alone installations are also possible. Web access (read-write-delete) to the models is possible in e.g. Aris and Metis. Some tools support commercial databases (e.g. Aris, Corporate Modeller, Metis, System Architect), others provide a in-house repository (e.g. Mega). Table 12. Architecture of the reviewed tools.

Architecture ARIS Collaborative Suite 6.2 client/server/repository, i.e. 3-tier architecture; both the client and the server can reside on a single workstation or the server and repository can be placed in a network server. Web functionality ARIS Web Designer: worldwide and platformindependent use. The 3-level architecture, consisting of a browser-ready front-end application and database server. This allows company procedures to be designed by employees distributed around the globe, as well as access to the procedures via a central repository. Models can be published in HTML format. No web client exists to fully enable the use of the Corporate modeler through web. Repository ARIS server includes a repository (a standard database system). Another database can be connected to ARIS also, supports e.g. Oracle, MS SQL Server, IBM DB2.

Corporate Modeller Suite 9

client/server/repository. The client can run on a stand-alone PC using a local database.

three server options: DP4 Local Server (single user only), DP4 Network Server and Oracle [continues on the next page]

Information Technology Research Institute LARKKI project Tanja Ylimäki

MEGA version 6 MEGA is organized in 3 tiers: the site (the folder where programs files are located; on a network server), the environment (the system repository and work repositories) and the workstation. Also a standalone workstation installation is possible. Client/server. Can be used as a single user workstation environment also.

Review of EA tools 18.6.2004

HTML Portal available? Metamodel based repository; allowing customization of the metamodel. Supports a project per repository approach, or allows multiple projects in a single repository

26

MetaEdit+ Method Workbench and MetaEdit+ 4.0 METIS 3.4

N/A

N/A

Client/server

Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

standalone / multi-user installation

The Metis Web Forms allows users without Metis client software to have access to models in the Team Server using their web browser. The Team Server content is exposed as html, showing model content and allowing for updates. Models are controlled with the same permissions system and versioning schema used by other clients. Published models can be accessed over the internet also by using the Metis Model Browser (read only). The content can be shared through HTML reporting capability, but it is read-only.

Repository items are organized in, and navigated through, a standard, hierarchical folder structure. The Metis Team Server repository can store any digital content, not just Metis models. Versioning, checkout, check-in, export and import are available for any file. Supports MS SQL Server 2000, MSDE 2000 or Oracle 8.1.7 and higher.

File hierarchy?

standalone / multi-user installation (client/server (repository)

The content can be shared through HTML reporting capability (read-only). Also a SA Information Publisher (an add-on) is available

Work done in System Architect is stored in a project encyclopedia. You can create an encyclopedia for every project, or have multiple projects in one encyclopedia. Encyclopedias are created as databases in either MSDE or SQL Server 2000. Encyclopedia contains diagrams, symbols and definitions. A diagram contains symbols, each of which has an underlying definition. Some definitions exist without symbols (e.g. requirements, attributes). Supports MSDE, SQL Server 2000

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

27

3.3.11

Multi-user support Multi-user support of each reviewed tool is presented in table 13. All tools enable many users to work with the same model content for example through check-in/checkout capability (e.g. MEGA, Metis, System Architect) or through sub-models that are merged into the master model (e.g. Corporate Modeller, Rational Rose). Table 13. Multi-user support of the reviewed tools.

ARIS Collaborative Suite 6.2 Corporate Modeller Suite 9 Multi-user repository; client access through e.g. ARIS Web Designer The product can be used in a multi-user environment by fielding Corporate Modeller on Corporate Exchange - a server that supports multiple browser-based clients, up to 400 users can access the same diagram. A model can be divided into sub-models also, and each submodel can be worked on independently and finally merged back into the master model. However, managing these sub-models is a complex task and subject to various pitfalls. Multi-user environment available with check-in/check-out functionality, also private workspaces. Objects can be merged when needed. The Object Repository supports: * Multiple concurrent users * Long transactions (maintain locks while exiting MetaEdit+) * Lock at a fine level of granularity (single objects instead of whole graphs) * Storing billions of design objects * Modifications of methods, with models updating on the fly With the Metis Team Client add-on product, you will be able to use the Repository Tree to work against models in the Metis Team Server. Open specific versions, view version history, check out/check in/revert and set permissions. Multi-users are supported (via version control system). Allows parallel development of a model by supporting decomposition of the model into versionable units, called controlled units. In order to allow different users to access the model from different workspaces, virtual path maps are used as references to controlled units. Multi-users are supported through check-out/check-in capability.

MEGA version 6 MetaEdit+ Method Workbench and MetaEdit+ 4.0

METIS 3.4

Rational Rose/XDE (Rational Rose Enterprise Edition) 2003 System Architect 9.1

3.3.12

Expandability and integration Expandability and integration issues of each reviewed tool are presented in table 14 in the following page. Many tools provide add-on components to extend the tool functionality (like ARIS, Rational Rose, and System Architect). MetaEdit+ can be seen extendable through its Method Workbench, though. All tools have some kind of APIs to enable integration with other tools, or have pre-built interfaces to communicate with other tools.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

28

Table 14. Expandability and integration issues of the reviewed tools.

Expandability ARIS Collaborative Suite 6.2 e.g. ARIS Simulation, ARIS BSC (balanced scorecard), ARIS ABC, ARIS Process Cost Analyzer, ARIS BPML Interface (to export ARIS data to BPML files), ARIS WebPublisher, ARIS Connectivity components IT Architecture Accelerator (enterprisewide approach - a road map - to IT planning), Balanced Scorecard Accelerator (to add performance measurement to the Corporate Modeler Suite), Simulation Utilities, Links to thirdparty products (see below) Technical modules to customize the platform to customer's specific needs; MEGA Intranet, MEGA Documentation, MEGA Generation, MEGA API, MEGA Supervisor N/A Integration can be integrated with Lotus Notes, SAP (ARIS Connectivity for Lotus Notes, ARIS Connectivity for mySAP). Using ARIS Lotus Notes Connectivity you can create and run links from ARIS to Lotus Notes items. ARIS Lotus Notes Connectivity creates the link to Lotus Notes. can be integrated with Sybase's PowerDesigner, Rational Rose, Oracle Designer, Erwin, Telelogic's Doors, MS Visio, Requisite Pro, Tibco InConcert. Capable of import/export data between MS Office (Word, Excel) and Corporate Modeler. Integration possible through MEGA API (COMbased and includes full read/write capabilities). Additionally e.g. Matrixes can be exported to MS Excel, diagrams can be saved as multiple formats (e.g. png, jpeg, tif, svg, bmp, wmf) to enable viewing and editing with other software. The MetaEdit+ API allows to build tool integration between MetaEdit+ and other tools. The API provides the interface to read, create, and update model elements, as well as control MetaEdit+ for scripting or simulation support.The MetaEdit+ API uses the widely supported and open SOAP / Web Services / .NET standard for application integration. The Metis modeling kernel is exposed as a Windows COM component, so it is possible to create scripts (VBScript or Jscript) to interact with and pass data to/from e.g. the Microsoft Office tools or Crystal Reports. The Metis Database Interface makes it easy to create and refresh Metis models with data residing in relational databases Open API accessible via scripting. It can be integrated with other Rational products like RequisitePro, ClearCase, SoDA (Software Documentation Automation).

Corporate Modeller Suite 9

MEGA version 6

MetaEdit+ Method Workbench and MetaEdit+ 4.0

METIS 3.4

XML Interface allows any kind of filebased XML data to be imported into Metis

Rational Rose/XDE (Rational Rose Enterprise Edition) 2003

System Architect 9.1

Rational Rose provides several ways to extend and customize its capabilities to meet the specific software development needs; menus are customizable, manual functions can be automated with Rose Scripts (e.g. diagram and class creation, model updates, document generation), Rose functions can be executed from within another application by using the Rational Rose Automation object (RoseApp), Rose add-ins can be activated using the Add-In Manager. Add-ons: SA Information Publisher (to generate website from SA repositories), SA EnComp (to compare two SA repositories). Visio-to-System Architect Mapper macro (maps diagrams built in MS Visio to equivalent diagrams in SA)

System Architect XMI Interface to Rational Rose. An SA-DOORS Interface enables you to manage your requirements in Telelogic's DOORS requirements

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

29

4 EA tool selection process ­ an example

IEEE Std 1209-1992, as well as ISO 14102:1995, proposes a process for tool selection process. In this section yet another example for EA tool selection process is presented, namely the one provided by the META Group. In Figure 4 the META Group's method for tool selection (as presented in Handler, 2003) is depicted.

Figure 4. The Method for EA tool selection (Handler, 2003). First the objectives for acquiring and using a modeling tool must be articulated and agreed to by all stakeholders. Since the tool is to support enterprise architecture, enterprise-level objectives must be included. Once this is accomplished, the objectives must be translated into requirements for both vendor presence and performance. Also, the architectural principles (both high-level conceptual and domain-level detailed) should be included into the criteria. Criteria are decomposed into sub-criteria and weighted or ranked. The content for the enterprise technical architecture must be included in the decision criteria, because selection a modeling tool that violates the technical architecture of the enterprise erodes the credibility of the tool and the EA team. The resulting deliverable is a requirements document that will be the basis for an initial screen of vendors. Some vendors may be eliminated by identifying critical or technical design requirements that are not provided by those vendors. The requirements document can be subsequently converted into a questionnaire and sent to

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

30

the remaining vendors. Based on the responses to the questionnaire the candidate list can be further refined. Once the final candidate list has been accomplished, vendor demonstrations can be requested. Vendors should be invited to demonstrate their software, but organizations should ask to see the functionality that it requires. After the vendors' product demonstrations, a selection is generally possible. A primary and a backup vendor should be selected. Organizations should begin negotiating prices with both, check references on the primary vendor, and (if feasible) perform some kind of pilot to actually test the product's abilities and usability. If the primary vendor shows in a positive light, the contract can be negotiated, leveraging pricing information from the secondary vendor.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

31

5 Conclusions

In this report we described the vendor qualities and main functionalities of seven tools that can be used for EA purposes. The evaluation criteria were derived from several sources, such as TOGAF, IEEE Std 1209-1992, ISO/IEC 14102, and a Review of Architecture Tools for Australian Defence Force (Prekop et al., 2001). The resulting set of criteria was not weighed in any way, and no scaling of the criteria was done. The functionalities of the tools were captured in written form providing basic information about the tools. This means, that not profound analysis was not made about the functionalities, e.g. no evaluation was made how well or strictly a tool implements a certain framework or methodology. Using a test case (an example of the enterprise architecture model) would have helped comparing the tools. In this report the review is primarily listing the features and functionalities of the tools rather than analyzing or ranking them. All reviewed tools possessed a wide range of functionalities needed in EA modeling and management. Visual models illustrate all the pieces and interrelationships between the components of the architecture providing the holistic view of the enterprise, repositories provide a controlled way to store the data and reporting and publishing capabilities support the communication of the model content. Selection of an appropriate EA tool is a complicated issue, but using a comprehensive selection approach (e.g. the one provided by the META Group), the probability of selecting a tool that will meet current and future needs and requirements increases. It is also possible that one tool is not enough. The Open Group (2002) claims that "successful enterprise architecture teams are often those that harmonize their architecture tools with their architecture maturity level, team/organizational capabilities, and objective or focus. If different organizations within an enterprise are at different architecture maturity levels and have different objectives or focus (e.g. enterprise vs. business vs. technology architecture), it becomes very difficult for one tool to satisfy all organization's needs."

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

32

References

Handler, R., Selecting Architecture Modeling Tools: 2003. EA Community Articles, URL: http://www.eacommunity.com/articles/openarticle.asp?ID=1835 IEEE Std 1209-1992, IEEE Recommended Practice for the Evaluation and Selection of CASE tools, 1993. ISO/IEC 14102, Information technology ­ Guideline for the evaluation and selection of CASE tools, 1995. Kitchenham, B., Evaluating Software Engineering Methods and Tool. Part 1: The Evaluation Context and Evaluation Methods. Software Engineering Notes, vol. 21, no. 1, 1996. Peyret, H., Selecting an Enterprise Architecture Modeling Tool Category. Available at URL: http://www.gigagroup.net/WEB/CONTENT.NSF/html/887F950649E9C197C1256D2 C002EB388/$File/SelectinganEnterpriseArchitectureModeling.pdf Prekop, P., Kingston, G., Chin, M., McCarthy, A., A Review of Architecture Tools for the Australian Defence Force. Joint Systems Branch, Electronics and Surveillance Research Laboratory, DSTO-TR-1139, 2001. Available at URL: http://www.enterprisearchitecture.info/Images/Documents/Review%20Tools%20defense.pdf, Accessed 16.6.2003. The Open Group, TOGAF Version 8, The Open Group Architecture Framework, Enterprise Edition, 2002. Available at URL: http://www.opengroup.org/architecture/togaf/, Accessed 28.1.2003.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

33

APPENDIX 1. Possible tools for EA efforts (in alphabetical order)

Product name and vendor 1 Adaptive / Adaptations Adaptive, www.adaptive.com Tool category EA tool? Description Adaptations are web-based solutions-oriented applications built with the Adaptive Reference Model to solve focused business problems; Adaptive IT Portfolio Manager Adaptive Business Process Manager Adaptive Enterprise Architecture. These can be further customized to the clients' individual requirements using the Adaptive Designer toolkit. Adaptive Foundation is the base technology upon which Adaptations are built (Adaptive Repository and Adaptive PortalPro ­ a browser based GUI). Adaptive Integrated Enterprise Architecture consists of: Adaptations Reference Model reflecting all the domains required to make informed, enterprise-wide management decisions Adaptive Designer Adaptive Foundation: a flexible, scalable, open and standards-based knowledge repository Methods that guide professionals through the fact-finding, modeling, analysis and decision-making required to plan and implement change and run the business. ARIS Process Platform provides integrated tools for designing, implementing and controlling business processes: ARIS Design Platform (Web Designer, Toolset, Easy Design, Simulation, Balanced Scorecard, Web Publisher) ARIS Implementation Platform (ARIS fo mySAP, UML Designer, Processes to Applications etc.) ARIS Controlling Platform (Process Cost Analyzer, Process Performance Manager) ARIS Scout solutions (e.g. quality management, software engineering) ARIS Collaborative Suite 6.2 consists of ARIS Easy Design, ARIS Toolset and ARIS Web Designer. Frameworks/ standards or methodologies supported Adaptive RealChange Method, The Adaptive Reference Model (framework for EA), UML, Zachman Framework? Other issues (e.g. additional products or services) Professional Consulting Service practice Adaptive Solutions; consultants can be used to design and implement solutions to meet customer specific needs.

2

ARIS Process Platform 6.2 (a product family) IDS Scheer Inc., www.ids-scheer.com

BPR tool

e.g. UML

ARIS = Architecture of Integrated Information Systems developed by professor Dr. August-Wilhelm Scheer

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor 3 BOTiCMAP suite of enterprise modelling tools BOTiC Ltd., www.botic.demon.co.uk Tool category EA tool

Review of EA tools 18.6.2004

Description

34

4

Corporate Modeller Suite version 9 CASEwise Systems Inc., www.casewise.com

BPR tool?

5

EA WebModeler Agilense Inc., www.Agilense.com

EA tool

Enterprise modeling tools that builds on the features of Visio, MS Access, and MS Excel: BOTiCMAP db - database approach to managing Enterprise Processes and to generating a visual model BOTiCMAP MatrixBuilder: matrix reporter BOTiCMAP QuickModel :to create models from existing data BOTiCMAP MeasuredViews: to keep the measures on models up-to-date with BOTiCMAP ProgrammeMilestones: to map out a Change Programme The Suite consists of the following components: CorporateModeler: Capture, analyze, optimize, simulate and implement business processes and enterprise architecture. Corporate Publisher HTML: Manage process and enterprise architecture knowledge across the business Corporate Publisher Word: Automatically generate professional reports and procedure manuals Automodeler: Import existing knowledge to kick-start your modeling Links to development and BPR tools like RationalRose, ERWin, Oracle Designer, Visio The Agilense EA WebModeler is a solution comprising an enterprise architecture "knowledge" repository, a web-based user-interface software tool, and sets of metadata. It resides behind a standard web server (e.g. Websphere, Ms IIS, Apache) and stores information in a standard relational database management system (e.g. Oracle, SQL Server, DB2, Access etc. ).

Frameworks/ standards or methodologies supported BOTiCMAP metamodel (framework)

Other issues (e.g. additional products or services)

Casewise Framework based on the Zachman Framework

Other products: ITArchitecture Accelerator, Balanced Scorecard Accelerator

6

Enterprise Architect 3.6 Enterprise Architect, www.sparxsystems.com. au Enterprise FrameWork 6.0 Ptech Inc., www.ptechinc.com

general modeling tool

UML modeling and design tool

has an own framework based on the Zachman framework, but other metamodels can be imported too. Supports e.g. DoDAF (C4ISR), MDA?, UML UML

7

EA tool

8

Enterprizer Intelligent Tools S3 International (S3i) LLC, www.s3inter.net

EA tool?

Modeling software solution for automating the development of an organization's Enterprise Architecture: KnowledgeEngine KnowledgeBase (the repository) AbstractGenerator Customization Kit enterprise modeling software platform

full support for Zachman Framework, IBM Enterprise Architecture Method?, UML

additional tools available, e.g. TeamWork, Accelerators (domain-specific methods)

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor 9 Enterprise Modeller 4.2c Enterprise Modeller Solutions Limited (EMS), http://www.enterprisemo deller.com Tool category BPR tool

Review of EA tools 18.6.2004

Description

35

Frameworks/ standards or methodologies supported

Other issues (e.g. additional products or services) a number of applications based on Enterprise Modeller providing solutions to specific business needs, e.g. Risk Manager, Process Improvement Manager, Business Integration Manager

10

Firststep 5.0 Interfacing Technologies Corporation, www.interfacing.com

BPR tool?

11

MEGA version 6 MEGA, www.mega.com

Enterprise Modeller is a flexible business process modeling toolset. At the heart of the tool is a powerful object database that is a repository for the organization's information. The toolset consists of the following components: Builder: modeling tool Developer: builder functionality + ability to design custom business model frameworks Net Publisher Interrogator: "manager's too" with reporting capabilities Viewer Components: FirstSTEP Designer is the comprehensive business process management tool, FirstSTEP Process Modeler ­ a CIMOSA Compliant Modeling Tool, and FirstSTEP Charter is the Microsoft Visio-integrated tool that allows users across an enterprise to cooperatively create, view, edit and publish structured process models MEGA Process: Business Process Analysis & Improvement MEGA Architecture: Map And Plan Business And Information Systems MEGA Integration: Business driven analysis and design for workflow and application integration projects MEGA Development: Software component specification & design MEGA Database: Database Analysis and Design MetaEdit+ metaCASE tool allows you to design your method and use it. First you design the method with Method Workbench and then all developers use the method with MetaEdit+.

The Enterprise Process Center (EPC) is a web-based portal that provides structured and simplified access to the enterprise processes, process-related content, projects and applications. Zachman Framework, UML Technical modules complement MEGA's offering to customize the platform to customer's specific needs: MEGA Documentation, MEGA Intranet, MEGA Generation, MEGA Supervisor

12

MetaEdit+ (Method Workbench and MetaEdit+) MetaCase Consulting, www.metacase.com METIS 3.4 product family Computas, www.metis.no, http://www.computas.co m

general modeling tool

e.g. UML, OMT, OOAD, IBM BSP

13

EA tool?

Metis is a family of client/server products for creating, visualizing, changing, sharing and managing enterprise models, e.g. Metis Model Browser, Metis Model Annotator Metis Modeling Workbench (Editor, Designer, - Metamodel Developer) Metis Team Server Metis Business Solutions (templates) Oracle Designer is Oracle's model-driven development tool based on the wellfounded principles of Information Engineering. Oracle9i Designer is sold as part of Oracle9i Developer Suite (Oracle9iDS).

Zachman, TOGAF 7(8), TEAF, FEAF, C4ISR (DoDAF), UML 2.0

IT Management template supports Zachman-like approach, DoDAF template, UML template (not available yet??)

14

Oracle Designer 9i Oracle Corporation, www.oracle.com

general modeling tool

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor 15 ProCap 7 / ProSim 7 Knowledge Based Systems Inc., www.kbsi.com Provision 4.3 Proforma Corp, www.proformacorp.com Tool category

Review of EA tools 18.6.2004

Description

36

ProCap: Process modeling and analysis ProSim: Process modeling and analysis with simulation model generation

Frameworks/ standards or methodologies supported IDEF3

Other issues (e.g. additional products or services) Other tools available, e.g. AIØ Win that combines IDEF0 function modeling with ABC modeling and analysis.

16

BRP tool?

The ProVision modeling suite provides an enterprise-wide process modeling environment, e.g. EnterprisePro can be used for Process Improvement and Quality Initiatives, Six Sigma, ISO Certification, Process/ Workflow Documentation, Strategic Planning, Enterprise Architecture Frameworks (C4ISR, Zachman), Business Requirements & UML Modeling for Application Development projects

C4ISR, Zachman, UML

17

Rational Rose IBM, www.ibm.com/rational

general modeling tool?

18

Silverrun ModelSphere 2.1 Magna Solutions, www.silverrun.com

BPR tool

Object-oriented modeling tools, such as IBM Rational Rose XDE Modeler: Enables to produce language-independent Unified Modeling Language (UML) models of software architecture, business needs, reusable assets and management-level communication. IBM Rational Rose XDE Developer: Offers a set of model-driven development and runtime analysis capabilities for building software applications. IBM Rational Rose Data Modeler: Provides the realization of the ER methodology using UML notation to bring database designers together with the software development team. IBM Rational Rose Technical Developer: Supports the most advanced modeling constructs, including model execution and fully executable code generation. Modeling tool that combines features like business process modeling, data modeling and UML class modeling

UML, MDA

Options: AnalyzerPlus TeamWork WebVision DataExchange JDEExchange ProGuide (best practices process models) Many other tools for e.g. requirements and analysis, testing and software configuration management

UML

Silverrun Professional and Enterprise Series 2.8: SILVERRUN RDM is a data modeling tool SILVERRUN ERX (Entity Relationship Expert) is a conceptual data modeling tool SILVERRUN BPM (business process modeler) is a tool for modeling, documenting and analyzing business processes and for integrating the business perspective with the enterprise data architecture SILVERRUN REPOSITORY SILVERRUN DBMS plug-ins (e.g. DB2, Oracle, Informix, MS SQL Server)

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor 19 Structure 2001 Suite Framework Software Inc., www.frameworksoft.com 20 Strategic IT Management (SITM) Generation 5 Alfabet, www.alfabet.de 21 System Architect 9.1 Popkin, www.popkin.com EA tool EA tool? Tool category EA tool

Review of EA tools 18.6.2004

Description

37

Structure 2001 Suite is an enterprise architecture document and model management software. It consists of two products: Structure 2001: an enterprise document and model management PC/LAN software application Structure.Net 2001: a web-based product that allows you to browse and access enterprise documents and models from the Internet, intranet, or extranet. SITM offers combined (IT) architecture, program, and value management for better management of the ongoing change processes. It consists of the following modules: IT Architecture Explorer IT Architecture Manager IT Program Manager IT Value Manager System Architect is a tool for modeling and developing enterprise architecture.

Frameworks/ standards or methodologies supported Zachman Framework, FEAF, TEAF

Other issues (e.g. additional products or services) BRS RuleTrack is aimed at coordinating business rules from the business perspective, and is independent of particular implementation environments.

Zachman Framework, TOGAF, DoDAF (C4ISR), BPMN, IDEF, RUP, Structured Analysis & Design

Popkin Model Agency: a directory of industry and technology standard models, all of which are available as a Popkin encyclopedia, making the comparison and selection process of adopting a predefined model simple and efficient.

22

Troux 4 Platform Troux Technologies, www.troux.com

EA tool

23

Visible Advantage 7 / Visible Analyst 7.6 Visible Systems Corporation, www.visible.com

general modeling tool

Troux 4 Platform consists of Troux Reference Model Troux Blueprinting System (Troux Blueprinting Engine, Troux Repository, Troux Collectors, Troux Bridges) Troux Reporting System Troux IT Portal Visible Advantage Enterprise Architecture Edition: Enterprise Architecture management tool for building systems, redeveloping legacy systems, and reengineering business processes Visible Analyst Enterprise Framework Edition: a modeling tool that incorporates strategic planning, data modeling, object modeling, process modeling, and the Universal Data Model, driven by an easy to use framework interface (Zachman Framework) diagramming tool, includes several diagram types/templates, e.g. block diagrams, brainstorming, business processes, flowchart, database, software (e.g. UML).

IDEF1X, IDEF0

.

Zachman Framework

24

Visio Enterprise Modeling Microsoft, www.microsoft.com

general modeling tool

Information Technology Research Institute LARKKI project Tanja Ylimäki

Product name and vendor 25 VizdomWorks! Wizdom Systems Inc., www.wizdom.com Tool category BPR tool

Review of EA tools 18.6.2004

Description

38

Frameworks/ standards or methodologies supported

Other issues (e.g. additional products or services) Analysis tools: FlowWIZard generates process flow models for process mapping CostWIZard for Activity Based Costing (ABC) TimeWIZard for project management and timeline analysis QualWIZard for quality function deployment and TQM (Total Quality Management) SimWIZard for simulation analysis What-if Analysis comparing Cost and Cycle Time Also other products are available, e.g. WizdomLive! Web-based business management software

The WizdomWorks! suite of Business Process Management solutions is comprised of: Document Manager: For defining and managing electronic documents ProcessWorks!: For process and activity modelling DataWorks!: For data and information modelling Analysis Tools: For process analysis

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

39

APPENDIX 2. Vendor qualities of the reviewed tools

(N/A = information not available) General Vendor name and location ARIS Collaborative Suite 6.2 IDS Scheer Inc. Altenkesseler Straße 17, D-66115 Saarbrücken, Germany Corporate Modeler Suite 9 Casewise Systems Inc. 100 Century Parkway, Mount Laurel, New Jersey, 08054, USA. MEGA MetaEdit+ Method Workbench and MetaEdit+ 4.0 MetaCase Consulting Ylistönmäentie 31, FIN-40500 Jyväskylä, Finland METIS 3.4 Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003 IBM Corporate offices: IBM Corporation, New Orchard Road, Armonk, New York 10504. IBM Finland:PL 265 (Laajalahdentie 23), 00101 Helsinki IBM was incorporated in the state of New York on June 15, 1911 as the ComputingTabulating-Recording Company (C-T-R). Rational Software Corporation was founded in 1981. Its tools became IBM offerings by the acquisition of Rational Software Corporation by IBM Software Group in February 2003. In Finland IBM has been operated since 1936. System Architect 9.1

MEGA 10 boulevard du Montparnasse, 75015 Paris, FRANCE

Computas Computas USA: 2721 226th Ave SE Sammamish, WA 98075. Computas Norway: P.O.Box 482, N-1327 Lysaker, Norway Computas was established in 1985 as Computas Expert Systems. Computas is a mixed product/consultancycompany, combining the product lines Metis® and FrameSolutionsTM with a highly educated workforce delivering solutions based on these products. In the early summer of 2000 Computas bought Metis AS from NCR Corp.

Popkin Software 11 Park Place New York, NY 10007, USA

History: e.g. how long has vendor existed in this arena, how long has the tool existed, size of vendor?

Founded in 1984 by Prof. August-Wilhelm Scheer. ARIS Toolset was launched in 1992, ARIS Reference Models in 1994, in 1996 ARIS is the de facto standard for process modeling: Gartner Group has certified leading worldwide market position among business process reengineering solutions.

Founded in 1989, a privately owned company. It evolved from a company called Inforem, a consulting company which used an early version of the tool.

Founded in 1991 headquartered in Paris; 170 employees, 100 consultants specialized in business process & enterprise architecture, 800 customers, 23,000 users worldwide. MEGA Suite first came into existence already in 1979 used by the consultants of Hay Group. MEGA is a dominant modeling tool vendor in France.

MetaCase is the leading provider of domain-specific modeling environments. Since 1991, MetaCase has been enabling customers to improve their productivity and competitiveness with development methods and tools that fit their needs. MetaEdit+ has been winning awards since its first version, which was ranked as Best Application Development Software at CeBIT '95. In 2000 the President of Finland presented MetaCase with the National Prize for Innovation. Most recently MetaEdit+ was voted Best Commercial Tool, at Net.Object Days / GPCE 2003.

Any other items of interest

-

-

-

Computas is a member of the DSDM-consortium (www.dsdm.org), having early in its history come to regard the "waterfall"-method of project execution as too rigid. An iterative approach has been employed in order to minimize risk.

For the tenth consecutive year, IBM received the most U.S. patents over any other company; 3,288 U.S. patents in 2002, nearly double the number of the next closest company. Over the past decade, the U.S. Patent Office has issued IBM 22,357 patents.

Jan Popkin established the company in 1988, based on his recognition of the need for tools and techniques to utilize the software industry's technical and managerial resources. Since 1988, Popkin Software has developed and produced a portfolio of products that have evolved into the company's current flagship offerings: System Architect and XML Architect. In 1995 Popkin Software acquired its UK distributor and successfully integrated it into the company. It now serves as Popkin's European headquarters. -

Information Technology Research Institute LARKKI project Tanja Ylimäki

(N/A = ARIS Collaborative information not Suite 6.2 available) Strategies, services Vision/mission/ IDS Scheer stands for strategy Business Process (general) Excellence. It is the promise of service, and it relates to their dealings with every customer, from the moment they become involved.

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+ 4.0 N/A

40

Corporate Modeler Suite 9 Casewise believes that maintaining an enterprise model is key to achieving strategic goals and minimizing costs.

METIS 3.4

Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003 IBM Rational Software (unit) aims to provide the organizations with a complete solution for developing software and software-based systems; The IBM Software Development Platform. It allows organizations to operate more efficiently and deliver innovative products and services that set them apart from their competitors. By defining, automating and integrating the strategic business process of software development in an open, proven and yet modular manner, companies can e.g better respond to competitive and customer demands, maximize output, improve time-to-value, increase business agility. Five primary software brands: DB2, WebSphere, Tivoli, Rational, Lotus

System Architect 9.1

MEGA offerings improve an organization's competitiveness by helping them understand, analyze and design new and enhanced business processes and enterprise architecture.

Computas supplies products and solutions to organizations and individuals that wish to enhance efficiency through innovative use of information and communication technology. In cooperation with our partners, we help knowledge-based companies to transform their knowledge from passive insight into competent action. The company's core expertise is focused on knowledge management, procedure support and the implementation of intelligent systems that promote knowledge-based performance and operations. Computas has won a leading role in the Norwegian market, and is now seeking to expand internationally. Two product lines: Metis product family and FrameSolutions (to build knowledge-based systems for work process assistance)

Popkin Software's corporate mission is to provide the marketplace with powerful, flexible and affordable business and application modeling and design tools. Their approach is ""Real tools for the Real World". Popkin Software highlights four key elements of the company's strategy: Technology Leadership, Price Performance, Consulting Services, and Low Cost Corporate Structure.

Product strategy (e.g. single product, product family, complementary products)

Develops corporate solutions for business process management. With its ARIS product family (ARIS Process Platform), the company offers a complete portfolio for developing, implementing, operating, controlling and evaluating business processes.

Primary product is the Corporate Modeler Suite; which consists of several applications. Other products: IT Architecture Accelerator, Balanced Scorecard Accelerator. There are two versions of the core product: · Corporate Modeler ­ a limited version of the product which comes with Simulation and Visio Link, and · Corporate Modeler Enterprise ­ a complete version of the product that

Product family: Mega Process, Mega Architecture, Mega Integration, Mega Development, Mega Database and administration modules (Mega Documentation, Mega Intranet, Mega Generation, Mega Supervisor). MEGA products are built around the same repository-based structure and can easily be integrated if necessary to provide

Two products: MetaEdit+ and MetaEdit+ Method Workbench

Two main products; System Architect and XML Architect (XML schema editor). In addition, they provide Model Agency, which is directory of industry and technology standard models, all of which are available as a Popkin encyclopedia.

Information Technology Research Institute LARKKI project Tanja Ylimäki

(N/A = information not available) ARIS Collaborative Suite 6.2

Review of EA tools 18.6.2004

MEGA the user with a consistent desktop. Mega 6.1 merges three modules -- MEGA Integration, Database and Development -into a single product called MEGA Designer. Training, consulting, Training, technical support. maintenance. MEGA Consultant solutions include Business Process, Enterprise Architecture and Risk Management. Technical support is provided via telephone, email and web services. MetaEdit+ Method Workbench and MetaEdit+ 4.0

41

Corporate Modeler Suite 9 includes multiple extensions, including Corporate Publisher HTML, Corporate Publisher Word, Automodeler, Simulation, and Visio, Rational Rose, and Power Designer Links.

METIS 3.4

Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003

System Architect 9.1

Service strategy Service Portfolio: (e.g. availability, Training & responsiveness) Workshops Project support Individual development Solution Packs Technical support

Training, technical support, consulting (enabling consulting to define e.g. modeling standards and symbology for a modeling team in a customer organization; project consulting to improve customer organization's business processes).

Training (e.g. availability of training materials, training courses, costs, style of learning)

Different kind of training courses, workshops available focusing on e.g. strategy, design, implementation. Training centers in Saarbrücken, Hamburg and Munich. Price example: 1 day course 350 EUR. On-site training possible at client company too (1,800.00 EUR/day for standard courses plus traveling expenses).

Training courses available, held in New Jersey, USA. E.g. courses on foundation (technical modeling skills), corporate publisher, simulation, repository and model management. Also online training is available (consisting of 2 parts), each part is priced at $399.00 per person.

MEGA training is available to qualified business and IT professionals. Training may be offered at the client's site or at MEGA's facilities. Education centers in Europe and North America

Consulting, training and support Model design and development Metamodel design and development Knowledge acquisition and engineering Software design and development Business process analysis and design Project planning and management Systems design and integration MetaCase offers Training is available trough consulting and training practical courses and in the areas of documentation. Standard implementing and courses: Basic modeling, using the domainUsing ITM, Using Team specific modeling Server, Team Server languages and Administration generators in MetaEdit+.

-

E.g. consulting, training, support, outsourcing, security and privacy

Training, technical support, web site resources (e.g. tool tips).

Training is available on several topics, e.g. configuration management, rational unified process, requirements and analysis, software quality, visual modeling and development. Web-based courses are also available. Specified training paths are available for certain skills or certification. On-site training is also possible.

Training courses (public or individualized) available. Also on-site training is possible given by the Popkin consultants. Examples of training courses: System Architect for business process modeling (3 days), System Architect for IDEF0 and IDEF3 (2 days), C4ISR method (5 days), System Architect customization (2 days).

Information Technology Research Institute LARKKI project Tanja Ylimäki

(N/A = information not available) Channels/ partners or geographic coverage ARIS Collaborative Suite 6.2 Branches in addition to Germany in e.g. Great Britain, France, Canada, USA, Brazil. Partners in 50 countries; in Finland CWG Change Ware Group Oy (http://www.changeware. net) and Synchro Technology Group Oy (http://www.synchrotech group.com). IDS Scheer is also an SAP Global Services Partner. e.g. ABB, Bayer, DaimlerChrysler, Deutsche Bahn, Deutsche Telekom, Goodyear, KPN Telecom, Lufthansa, Nestlé, Volkswagen in Central and South America.

Review of EA tools 18.6.2004

MEGA Offices in USA, UK, Italy, Portugal, and representative in Mexico. Furthermore many consulting, technology and solution partners, e.g. Microsoft, Business Rules Solution. MetaEdit+ Method Workbench and MetaEdit+ 4.0 Partners: Applied Formal Methods (Switzerland), RSM Salustro Reydel (France), SOSM Software Tools (The Netherlands)

42

Corporate Modeler Suite 9 Offices in USA, UK, France and Germany. Several distribution partners around the world, e.g. in France, Germany, Australia, Austria. Technology partners (e.g. Sybase, Rational/IBM). Consulting partners (e.g. PA Consulting, Cap Gemini Ernst & Young, Deloitte&Touche) e.g. Clarks Shoes, DHL, Deloitte&Touche, Swiss Re, GlaxoSmithKline, Pfizer, Royal Bank of Scotland

METIS 3.4 Offices in USA and Norway. Partners e.g. Adaptive Inc., Telelogic North America, Inc., Excelon Solutions, TietoEnator Corp. (Norway), WM-data Consulting AS

Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003 90 000? partners worldwide, offices in over 100 countries

System Architect 9.1 Offices in USA, UK and Netherlands. Many technical, solutions and value added partners, e.g. Telelogic, Integrated Knowledge Systems Inc., AKMA. Strategic alliances, e.g. Microsoft, Other partnerships, e.g. OMG, BPMI, Telemanagement Forum

Customer references

E.g. American Electric Power, AGF Insurance, Airbus Industries, Alstom Power, AT&T Labs, Banque de France, Bell Canada, Credit Lyonnais, France Telecom, Givaudan, Lucent Technologies, MBDA, Microcell, Pennzoil-Quaker State, Southwestern Bell and Target Corporation Prices started at 3,000$ (Mega Suite 6.1)

E.g. British Telecom, Nokia, Deloitte & Touche, Digia, SysOpen, TeliaSonera, TietoEnator, Metso, Fuji Xerox, Italia Telecom

E.g. Boeing, SKANSKA AB, Environmental Protection Agency (USA), EDS Corporation

Success stories (i.e. customer references) for IBM Rational can be found at URL: http://www306.ibm.com/software/succ ess/cssdb.nsf/topstoriesFM ?OpenForm&Site=rational

E.g. Bank of Canada, Bank of England , US Navy, US Airforce, NASA, IBM, GlaxoSmithKline, several US Universities, AT&T, KLM, British Airways, BMW, Boeing, Pfizer, Accenture, Deloitte & Touche, Price Waterhouse, Ernst & Young, UNISYS, Ericsson, Panasonic, Compaq

Financial considerations Pricing Strategy N/A (e.g. what is the acquisition cost/total cost of ownership)

Corporate Modeler $3,800 per license (Including MS Visio interface and simulation tools)

E.g. MetaEdit+ Method Workbench and MetaEdit+ 11500 euros, MetaEdit+ 5500 euros

Metis Enterprise 3.4 costs about US$20,000 as an installation of the repositorybased server and the minimum 20 log-in licenses. The designer and editor tools, with templates, cost $9,500 per developer seat.

Examples: Rational Rose 2003 Enterprise Edition $3495 (node locked)/ $6115 (floating). Rational Rose 2003 Professional J Edition $1995 (node locked)/ $3490 (floating); prices do no include support.

$5250 per single concurrent license (year 2002)

Information Technology Research Institute LARKKI project Tanja Ylimäki

(N/A = information not available) Licensing policies ARIS Collaborative Suite 6.2 N/A

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+ 4.0 Volume discounts and academic licenses are available.

43

Corporate Modeler Suite 9

METIS 3.4 N/A

Corporate Modeler can be N/A licensed in two different ways: 1) Client licenses can be used in both single-user and network server configurations. Each license works on one particular work station only and is not transferable. 2) Concurrent licenses can only be used with network servers and are held on the database server. When a user logs on, a free license, if available, is allocated to that user. That license is unavailable to other users until the user logs off, when it is released. Concurrent licenses are more expensive than client licenses as each concurrent license may be used by more than one user (though not simultaneously).

Rational Rose / XDE Developer (Rational Rose Enterprise Edition) 2003 Single licensing mechanism for all Rational products, floating and node-locked licenses.

System Architect 9.1 Licenses are sold either singularly or concurrently to run on your network. Corporate Site Licenses are available.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

44

APPENDIX 3. Tool qualities of the reviewed tools

Enterprise Architecture related issues (N/A = information ARIS Collaborative not available) Suite 6.2 Supported frameworks and/or standards (related to enterprise architecture) ARIS Framework Corporate Modeler Suite 9 Casewise Framework based on the renowned Zachman Framework MEGA MetaEdit+ Method Workbench and MetaEdit+ METIS 3.4 Rational Rose Enterprise Edition / Rational Rose XDE Developer OMG's Model Driven Architecture (MDA toolkit for Rational XDE Java), Zachman Framework (illustrated by packages), C4ISR. Rational Unified Process (RUP). Other methodologies can be applied also (see metamodel support) System Architect 9.1

TOGAF, Zachman Can support various Framework (see details in frameworks (see "Any other items of interest" metamodel support) within below)

Zachman Framework, DoDAF, TEAF, FEAF, TOGAF 7(8), ITM-template (Enterprise Architecture Template for Metis)

Supported Methodologies (UP, OOA, etc)

ARIS Method, The Balanced Scorecard method

N/A

MEGA allows to describe the interrelationships of the application integration, development, architecture, or organization projects using the MOKA (MEGA Open Kit Approach) methodology.

Supported Modeling UML, OMT, BPMN languages (UML, IDEF0, BPMN etc.)

If multiple methodologies are supported, how are the different approaches integrated? Is it possible to move data between different approaches?

N/A

UML use case UML (MEGA Development) diagrams can be drawn with Generic Modeler. Business processes are described with a "common" notation. N/A N/A

MetaEdit+ Method Workbench allows you to build your own CASE tool (without writing any code). Predefined methods: UML, OMT, OOD, OOAD, Fusion, Moses, OOSA, SAD, Real-time SA/SD, IBM BSP, Porter's value chains & value systems, activity analysis UML, OMT etc. (see above)

Metis is methodologyneutral; appropriate method can be applied. Metis Metamodel Developer can be used to customize existing methodologies or create tailored ones from scratch.

Framework interfaces for Zachman Framework, TOGAF, DoDAF (C4ISR) - an option. The default framework is defined during the installation, it can be changed later. IDEF methodology, SSADM, Gane&Sarson, Yourdon/DeMarco, Ward&Mellor, Information Engineering, TOGAF ADM, Rational Unified Process (RUP), The Popkin process BPMN, OMT, UML 1.4, IDEF0, IDEF1X, IDEF3 + many structured analysis and design techniques are supported. A diagram contains symbols each of which have an underlying definition, and these definitions can be (re)used in several diagrams.

UML 2.0 (available through UML template), IDEF0, IDEF1X, BPMN

UML

N/A

N/A

N/A

Information Technology Research Institute LARKKI project Tanja Ylimäki

Enterprise Architecture related issues (N/A = information ARIS Collaborative not available) Suite 6.2 Metamodel support (ability to configure, tailor and/or import metamodels/ frameworks) ARIS Configuration allows you to adapt parts of the ARIS method to your own requirements. You can rename model types, object types, symbols, attribute types and attribute type groups. You can create your own symbols (graphics) for object types. You can also configure specific attributes individually and assign these attributes to any attribute type groups.

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Metamodel, i.e. Casewise framework, is customizable. The framework is not very explicit though. MEGA MetaEdit+ Method Workbench and MetaEdit+

45

METIS 3.4

EA life-cycle support (Which phases are supported: requirements gathering, analysis, design, implementation, testing, maintenance, etc.?)

supports designing, implementing and controlling business processes

design, analysis

Metamodel defines the structure used to store the data managed in a repository. The metamodel is saved in the environment system repository. The metamodel contains all the object types used to model a system, and specifies their attributes and the possible links between these object types. The metamodel allows models to be built that describe the organization of the information system of an enterprise. Additional object types can be created and managed. Extracts from the metamodel are called Dialogs and these can be used to manipulate specific structures and objects within the metamodel. This can be useful in representing a structure in one way to one type of user and a different way to a manager for example. requirements (to some extent), analysis and design

Metamodel (method) is customizable. With Method Workbench new methods can be created.

Metamodel can be modified or tailored models can be created with the Metis Metamodel Developer

Rational Rose Enterprise Edition / Rational Rose XDE Developer Frameworks can be modified or created with the help of the Framework wizard (an add-in available only on Windows, and only in some Rose editions). Before creating a new framework the following files must be created: A model file (.mdl) that defines the content of the framework, i.e. the template to be used when creating new models from this framework; an icon file (.ico) that contains the icon to be used as a symbol for the new framework in the Create new model box; a documentation file (.rtf) that contains the description of the framework.

System Architect 9.1

Frameworks can be modified with the help of Framework editor. A new framework can be created (a grid) also. Appropriate model types can be attached to the framework cells. The overall metamodel of the tool can be modified with the USRPROPS.TXT file; e.g. diagrams, symbols or definition types can be renamed or new ones created. Also new properties for diagrams, symbols or definition types can be added.

requirements (to some extent), analysis and design, implementation (code generation)

requirements (to some Requirements Requirements extent), analysis and design gathering (with Rational gathering, desing, RequisitePro), analysis, partially implementation design, implementation, testing, deployment

Information Technology Research Institute LARKKI project Tanja Ylimäki

Enterprise Architecture related issues (N/A = information ARIS Collaborative not available) Suite 6.2 Support for various architectural views/constructs out-of-the-box (e.g. business processes, data, application, technology) Organization view, product/service view, data view, function view, process view

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Business processes, organizations, locations, data, applications, technology views that are linked together MEGA MetaEdit+ Method Workbench and MetaEdit+

46

METIS 3.4

business processes, data, application, technology

Depends on the modeling language / method chosen.

Support for creation of custom views/models/ constructs

ARIS Model Generation allows you to generate new views of existing database contents. Existing models or objects may be combined according to specific rules, thus creating new models providing additional information. The source models or objects remain unchanged. ARIS Model Generation is a tool for generating new models based on existing information without having to model them manually. Also so called Quick model type allows the creation of models without any method restriction.

Custom object types, custom object property types, custom association types can be created. Possibility to create user-defined notation style and symbology with generic modeler. Names of the predefined property types can't be changed. You can write your own help text for both userdefined and predefined design objects.

Custom models (or other objects) can be defined through metamodel (See Metamodel support).

With Method Workbench new methods and therefore new models/constructs can be defined.

Views of the chosen framework are available (see supported frameworks). New views can be created from selected instances in the original model view or from the results of a visual query. The new model view will be independently modifiable. In Model Editor you can create a new model view from selected instances in your original model view or from the results of a visual query. The new model view will be independently modifiable, for quick customization/reporting to a specific target audience. Relocate model views, with or without underlying model data, to separate model files. With Developer you can modify, extend and define new types, criteria, methods, metamodels and templates, to create support for new modeling standards and methodologies.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Kruchten's 4+1 views; logical view, process view, development view, physical view, scenarios can be applied. The UML model is usually divided into use case view, logical view, component view and deployment view. Free-form modeling is possible. If a new framework is created, it is possible to define new views/models (using UML notation).

System Architect 9.1

Views of the chosen framework are available (see Supported Frameworks)

Because a custom framework can be created, can also custom views be created.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Enterprise Architecture related issues (N/A = information ARIS Collaborative not available) Suite 6.2 Does it provide templates or patterns for constructs, which can be used to help organizations "jump start"? Using the Template Wizard, you can create templates to enhance your models with more individual graphic designs. Use a template to specify the graphic properties of symbols and connections. Only the configuration administrator is authorized to create, edit, export, import templates.

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Some ready-made templates. Possibility to create own templates for models (i.e. for collection of objects within a repository), diagrams and other objects. An example model is included into Corporate Modeler. For example a new model based on the framework template includes the following object types: application, attribute, business goal, calendar, critical success factor, data store, diagram, documentation, domain, entity, event/result, external entity, framework guide, framework help, issue, key, location, organization, picture, probability function, process, product, project, publication set, relationship, schedule period, style, technology, time period. All objects are stored in respective object type "folders". MEGA MetaEdit+ Method Workbench and MetaEdit+

47

METIS 3.4

Has some predefined project types and related methods that can be used as guidance when starting a new project.

Method support provides help about the modeling technique, its components, reports and links to other techniques.

Computas and its partners offer a selection of Metis templates, metamodels and starter models, minimizing the time and resources required to create business solutions for one's modeling needs. Metis templates support Enterprise Architecture, Process Modeling, Business Strategy, IT Architecture, Project Management, Document Knowledge Management, etc. For example Metis Generic Enterprise Modeling (GEM) template is bundled with the Model Editor, Designer and Metamodel Developer. The GEM template contains sufficient modeling primitives to run tutorials and build useful high-level enterprise models.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Design Patterns can be utilized.

System Architect 9.1

The Popkin Model Agency is a directory of industry and technology standard models, all of which are available as a Popkin encyclopedia, making the comparison and selection process of adopting a predefined model simple and efficient. The list of available models can be found on the website.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Enterprise Architecture related issues (N/A = information ARIS Collaborative not available) Suite 6.2 Any other items of interest -

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Support for generic SAP framework, the TeleManagement Forum's eTOM framework, and in the future support for Six Sigma and Balanced Scorecard frameworks. MEGA MetaEdit+ Method Workbench and MetaEdit+

48

METIS 3.4

MEGA comes with an HTML service that acts as a Zachman Portal onto the repository. For each Zachman cell, a mapping window is provided that describes the concept used in MEGA, along with a query that selects the corresponding model objects in the current repository. It can be used as a basis to create new portals or to adapt the Zachman framework to enterprise specific requirements.

A Metis model comprises groups of related objects that represent information and knowledge about an enterprise. It's typically based on a template. An object is a component of a model representing a specific "thing" in an enterprise or the real world (information, knowledge). A relationship links two objects together to show a dependency. A container is a special type of object that is used to group related objects, including other containers. A view is the graphical or textual representation of objects and relationships in a model.

Rational Rose Enterprise Edition / Rational Rose XDE Developer -

System Architect 9.1

-

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) Overview of the modeling interface (e.g. layout of the interface, how well uses the screen space, is the interface logical and consistent to navigate, how well it follows the conventions of the host operating system?)

Review of EA tools 18.6.2004

49

ARIS Collaborative Suite 6.2 ARIS uses a large number of Microsoft Windows properties and standards; e.g. menu structure, online help. Application/model windows can be moved/resized, models can be zoomed.

Corporate Modeler Suite 9

MEGA

MetaEdit+ Method Workbench and MetaEdit+ Diagram Editor is a tool for creating, managing and maintaining design information as diagrams. It supports visual modeling of graphs and linking of several graphs through explosions, decompositions and reused components. Browsers can be used to navigate through the content of the selected project (i.e. the collection of graphs that make up the whole model) Depending on the method used various diagram types are available, e.g. UML diagrams, ERmodels, value chain models (see Supported Methodologies).

METIS 3.4

Diagram types supported (Block, Chen, control flow, data flow, ER-model, OO etc.)

All modelers look similar; on the left side there are the available drawing symbols and on the right side there is the modeling area. When Corporate Modeler is opened Repository Explorer is launched to act as a "homepage" providing access to the repository. It has the hierarchical tree of models (including the object types) on the left and the objects on the right side. Accessing the repository content e.g. through the Casewise framework interface might ease the adoption of the tool. Several diagrams types of a Hierarchical diagrams certain level (requirements (e.g. organizations), data definition, design flow diagrams (DFD), specification, process diagrams, ERimplementation) or view diagrams, matrixes (e.g. (e.g. data, process), e.g. CRUD matrix), generic OMT Functional model, diagrams (user-defined) OMT dynamic model, OMT Object model, UML class model, UML activity diagram, UML component diagram, value added chain diagram, organization chart and many different process models.

Interface is divided into three parts: main MEGA bar with distinctive icons, current repository tree and the standard desktop. By clicking the icons in the MEGA bar, a corresponding menu tree is obtained to enable access to e.g. objects in the repository, projects, utilities (descriptors, dialogs, matrices, etc.), available documentation (Web sites, documents, matrices, external references), the company dictionary, (keywords) and diagrams (organized by diagram types).

Graphical interface; drawing workspace on the right and a browser on the left.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Customizable GUI; drawing workspace on the right and a model browser on the left.

System Architect 9.1

Graphical interface: drawing workspace on the right and a browser on the left. The browser is a multipurpose navigation interface that displays, in a hierarchical tree, the content of an encyclopedia, i.e. diagrams and definitions. Alternatively e.g. the Zachman framework or TOGAF interface can be used without the browser to navigate through the content.

e.g. flowcharts, data model (simplified UML), application architecture diagrams, organisational charts, business process diagrams, business function hierarchy diagrams, workflow diagrams, UML diagrams (e.g. use case diagrams, sequence diagrams, class diagrams)

E.g. organisational charts, business process diagrams. UML diagrams are available through UML template.

UML diagrams; use case, activity, sequence, collaboration, class, state, component, deployment, and data model diagrams (data modeling is enabled with Data Modeler Edition)

Data Flow Diagrams (Gane & Sarson, Yourdon/DeMarco, or SSADM IV), Ward & Mellor DFDs and State Transition Diagrams for real-time applications, CRUD matrix, IDEF3 Process models, IDEF1x data model, IDEF0 functional decomposition model, network concept diagram, ER models (e.g. Booch, Jaccobson, OMT), etc.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) Requirements specification entry, editing and storing capabilities ARIS Collaborative Suite 6.2 Se design specification entry

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 No actual requirements specification functionality exists; requirements can be specified using a custom object type (user can create a new object type called requirements -> a new "folder" in explorer tree) and model requirements using appropriate modeler tool. MEGA MetaEdit+ Method Workbench and MetaEdit+

50

METIS 3.4

Requirements can be defined (as objects with properties) and they can be assigned and achieved by business processes, procedures, applications, databases, packages, etc. Also a requirements diagram can be created.

Requirements specification capability depends on the method that is used, e.g. using UML requirements can be described to some extent with the use case model.

Requirements can be defined as objects within a container. These requirement objects can be linked to other objects.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Rational RequisitePro can be used to manage requirements. Integration between RequisitePro and Rose is possible to enable keeping the design activities in-line with the requirements.

System Architect 9.1

Requirements specification language (capability to import, export or edit requirements using a formal language) Design specification entry, editing and storing capabilities

ASCII import/export, XML import/export (not in all versions of the product)

XML import/export of model (collection of objects) or selected model objects. CSV files can be loaded with Auto Modeler. Modeling objects are stored as independent entities in the repository. Each object is described by properties. To update any part of the model you only have to update the object on any one diagram (or directly in the repository). All other instances of that object within the model are then automatically updated. Pictures (or graphics) can be added to diagrams as well as links (or shortcuts) to other diagrams and external documents.

N/A

XML import/export

CSV import/export.

See above.

Requirement definitions may be added directly into System Architect. New requirement types can be added in addition to the predefined ones. The properties of each requirement itself can also be customized. Integration of the project with requirements captured in Microsoft Word, Excel, or 3rd-party Requirements Tracing tools (e.g. Doors) is also possible. Import/export of requirements is possible with comma separated value (CSV) or ASCII format.

Each modeling object (e.g. function, person, application, event) is described by attributes and properties. An existing or new model (to be created) is possible to assign (i.e. link) to an object within a model. Proposals for change and improvement can be made for all database objects and models with ARIS Change management tool.

Specification of the objects is defined within properties dialog box. The content of the properties depends on the type of the currently selected object.

All design information can be accessed from property dialogs + visual modeling

Data can be entered and edited in the Property Dialog or in the Property List for multiple similar instances + visual modeling

Data can be entered and edited e.g. through property dialogs. Unlimited undo functionality.

Design specification is entered and edited in forms-based format + visual modeling

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) ARIS Collaborative Suite 6.2

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Because of the repository-based architecture, there are no files to save. The diagrams are saved automatically as the user works with the diagram. MEGA MetaEdit+ Method Workbench and MetaEdit+

51

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer

System Architect 9.1

Design specification language (capability to import, export or edit design information using a formal language)

ASCII import/export, XML import/export (not in all versions of the product)

XML import/export of model (collection of objects) or selected model objects. CSV files can be loaded with Auto Modeler.

N/A

XML import/export

Drawing support (auto draw, auto layout, auto connections etc.)

Auto layout function, layout wizard function to modify layout options. The ARIS Modeling Guidelines (can be found in the on-line help) provide orientation for creating consistent (process) models.

Layers (i.e. groupings of objects) can be used on diagrams; layers can be visible or invisible enabling to focus on certain parts of the diagram (can be used in presentations etc.). No auto layout functionality; with Auto Modeler can the hierarchy diagrams be reorganized.

No automatic layout; diagram objects can be grouped, ordered (bring to front, send to back etc.), aligned etc.

Model creation is automated with context sensitive relationship and role selection. Auto layout.

Import/export data into N/A Metis from/to different data sources/sinks (e.g. Excel sheets) using comma-separated value text files. Generate views for imported instances. Specify advanced options for import/export using CSV rules. Apply automatic layouts N/A in order to arrange a group of objects visually in a matrix or hierarchy. Define your own automatic layout strategies, including sort-by-property options. Generate default views on instances that for some reason lack a visualization, either because of deletion, or because they have been created nonvisually through data import etc.

see above

e.g. Auto layout, auto connections

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) Reuse of existing constructs (e.g. models/diagrams/ data/objects) ARIS Collaborative Suite 6.2 Data cannot be copied beyond borders of database. ARIS Merge can be used to merge the contents of multiple databases into one master database consistently and without generating redundant items.

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Data (i.e. objects) can be reused within a model (a collection of objects stored in a database). Auto Modeler can import existing process and system documentation held in Microsoft Word or Excel formats into an existing or new model. Objects can be copied from existing models to a new model. When you copy a diagram, you create a new diagram (i.e. it has a separate Id and must have a unique name). However, you do not create copies of the objects that appear on the diagram (you can have many instances of the same object on multiple diagrams). Transferring data between models is possible if you first export data (or the model design) to an external XML file and then import from that file into either a new or existing model. Icons are customizable. MEGA MetaEdit+ Method Workbench and MetaEdit+

52

METIS 3.4

Objects that exist in a repository can be added (connected) to a new diagram. Contents of a diagram can be copied into a new diagram. Objects can be duplicated also (if they can appear multiple times within a diagram). Graphical objects can be added into diagrams.

Components can be browsed, selected and reused with the Component Selection Tool.

It is possible to copy, paste, duplicate and delete instances and views.

Rational Rose Enterprise Edition / Rational Rose XDE Developer The whole model can be used as a starting point for a new model. Reengineering capabilities allows using existing code or database schema as a starting point of developing new models.

System Architect 9.1

All existing models/diagrams are reusable

Customization of iconography (e.g. can the icons of the entities, relationships etc. be customized?)

Icons can be customized

Allows for the appearance of all object types to be defined in a manner that suits a particular organization. Includes Shapes Editor to define custom shapes.

All symbols are customized with the Method Workbench and its Symbol Editor tool.

Possible through Metis Designer; Drag & Drop symbols from palettes onto objects or relationships to change their appearance. Drag & drop a view style to change the appearance of your entire model.

User-definable color for all modeling elements

Model symbols can be formatted

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) Traceability (of the requirements) ARIS Collaborative Suite 6.2 N/A

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 N/A MEGA MetaEdit+ Method Workbench and MetaEdit+

53

METIS 3.4

Requirements diagrams can be seen as a traceability tool

Connections between design information can be inspected and navigated with the Info Tool; no actual trace tool.

N/A

Specifications consistency and completeness checking

ARIS Semantic Check is a control instrument for modeling in the ARIS system. Models can be tested using the ARIS Semantic Check rules. These rules ensure that diagrams of the company processes are logically structured in ARIS and are meaningful. ARIS Simulation is a tool for the analysis of business processes. ARIS Simulation is integrated in the ARIS Toolset; you can use the data relating to the processes, recorded in the ARIS Toolset as a basis for the simulation of business processes.

Consistency N/A check/verification can be done to diagrams. Consistency of a diagram indicates whether the diagram is consistent with reference to certain validation rules set as standard by the particular organization that is using Corporate Modeler. Simulation Pack includes Analyzer, Financial and Grapher tools. Simulator Analyzer is an optional component of Corporate Modeler that can be used to measure the effect of changing one, two or all object properties on selected simulation output variables. Simulator Financial is an optional component of Corporate Modeler that It is possible to simulate and animate procedures.

Models can be checked with predefined reports and own checking reports can be made.

With Model Designer you can validate models; Lists any inconsistencies in the model and provides suggestions on how to fix them.

Rational Rose Enterprise Edition / Rational Rose XDE Developer In RequisitePro traceability matrices link requirements to other requirements. Also an audit trail (who, what, when, why) of every requirement change is stored in the database. Requirements in RequisitePro can be linked to the design elements in Rose XDE Developer (i.e. add traceability function). A model can be checked (the UML syntax), error messages are given in the log. Also access violations can be reported/viewed.

System Architect 9.1

SA provides Requirements as definition types. These can be related to diagram symbols (Addresses functionality). Built-in requirement types are e.g. business objective, business process, change request, critical success factor, deliverable, information requirement, organizational goal). Built-in consistency checks exist, e.g. when drawing a relation line on a drawing.

Simulation

An emulator or a programming environment can use the MetaEdit+ API to trace or animate model execution. Execution of the code highlights the corresponding model element in MetaEdit+ with a red outline.

N/A

N/A

SA Simulator (integrated into the System Architect); e.g. what-if scenarios, workflow and bottlenecks, spreadsheet reports (exportable to MS Excel)

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) ARIS Collaborative Suite 6.2

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 can be used to exchange data between the Simulator and Excel spreadsheets. Simulator Grapher is an optional component of Corporate Modeler that can be used to graphically monitor the results of a simulation run while the Process Dynamics Simulator is running. N/A MEGA MetaEdit+ Method Workbench and MetaEdit+

54

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer

System Architect 9.1

Customizable automation functions (e.g. scripts, macros; what elements are they used to automate?) Import/export of models/data

ARIS Script is based on Visual Basic for Applications.

Macros (VB script code) can be used to create objects, retrieve data from the repository, run the MEGA explorer, generate a Web site, etc. Data can be imported/ exported in several formats (within MEGA Generation); e.g. Java, C++, RationalRose, VisualBasic, XMI, XMD. Exporting in MGR-format (MEGA format) allows to create a consistent set of objects and enables to transfer part of a design into another repository. For example, exporting MEGA objects from a diagram exports the objects found in this diagram, as well as the objects depending on them.

Possible with the MetaEdit+ API

N/A

VBScript Environment

Macros can be defined

XML import/export; UML Designer: XMI export/import

XML import/export of model (collection of objects) or selected model objects. CSV files can be loaded with Auto Modeler.

Diagrams can be exported to clipboard (GIF, PICT files). Matrices and tables can be exported to ASCII (tab-separated for pasting the matrix into a spreadsheet) and HTML. XML import/export.

CSV import/export XMI import capability, facility. XML Interface is import of Rose files a new add-on product (.mdl, .ptl, .cat, .sub). enabling import of any file-based XML data into Metis.

Definition data of the dictionary can be imported/exported in CSV/text format. Import/export of diagrams and definition data via XML.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Modeling (N/A = information not available) ARIS Collaborative Suite 6.2

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 There is a concept in Corporate Modeler called "explosions", also known as "drill-downs". This is when a process is decomposed into a detail diagram to create multilevel models. Objects that are detailed in another diagram are marked with a dot. Links can also be created between models (object link functionality). MEGA MetaEdit+ Method Workbench and MetaEdit+

55

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer

System Architect 9.1

Any other items of The main components of interest ARIS Process Platform differ in their range of functions and their areas of use. ARIS Easy Design is aimed at staff in the company's operational departments - places where process knowledge resides. ARIS Toolset (including Easy Design) is suitable for comprehensive business process management. ARIS Web Designer has a browser-capable front end for those who need Webbased access to process information.

Any object can be edited using API even if the contextual menu does not include an Edit command.

Metis Model Editor supports model breakdown and decentralized data ownership by giving access to specific cross-sections of the overall model. Modelers that don't necessarily know the full picture of the model or the entire capabilities of Metis modeling will be able to update their part of the model in a circumscribed manner.

Diagrams can be leveled by linking diagrams together in parent-child relationships.

Documentation (N/A = information not available) Editing functionality (enter and edit data in text/graphical/for ms-based format)

ARIS Collaborative Suite 6.2 Free-form text can be inserted into models

Corporate Modeler Suite 9

MEGA

Free-form text can be inserted into Most MEGA comments diagrams. Descriptions of objects are defined in RTF are defined within properties. format. Description field allows you to add 32kb of text. You can also use these fields to: create links to external files (similar to the way object links work but with the advantage of making the external document a property of the object), add HTML tags (which you can use to improve formatting or to add graphics in any Corporate Publisher HTML output), use Casewise markup language to control the formatting of the output.

MetaEdit+ Method Workbench and MetaEdit+ Supports modeling with tables, forms and text; the Table Editor is a tool for providing a tabular or form-based view on design information.

METIS 3.4 Definition data is entered and edited in forms-based format. The fields of the forms can be modified with the Metis Metamodel Developer.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Data can be entered into diagrams using text in addition to the properties of diagrams elements.

System Architect 9.1 Definition data is entered and edited in forms-based format. The fields of the forms can be modified.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Documentation (N/A = information not available) Publishing (output formats, hypertext support, customization etc.) ARIS Collaborative Suite 6.2 ARIS Web Publisher (add-on) enables to communicate the process models globally via the Internet and intranet; In ARIS Toolset reports of models can be generated in several formats, e.g. RTF, word document (.doc), Excel document (.xls), HTML, text file see publishing

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Word documents, HTML document or multiple HTML pages can be generated with Corporate Publisher. Publication set object type in the Repository Explorer tree contains the templates for reports and they are customizable) MEGA MEGA provides a mechanism to generate HTML pages directly from the repository to create a web site to share information. Also MS Word documents can be generated.

56

MetaEdit+ Method Workbench and MetaEdit+ MetaEdit+ offers prebuilt reports for model analysis, checking and documentation in Word, RTF, HTML, XML and XMI. Predefined reports are available for all graphs.

METIS 3.4 With Metis Editor (HTML Report Wizard) models can be published e.g. to local disk, CD, or web servers in full dynamic mode for use with Model Browser or Annotator, or as HTML pages for easy access from any web browser. HTML

Rational Rose Enterprise Edition / Rational Rose XDE Developer HTML. Word documents can be generated with SoDA.

System Architect 9.1 HTML, XML reports. Standard and ad hoc Word-reports can be generated

Conformance to documentation standards (capability to produce output)

It is possible to copy diagrams or RTF, XML, HTML selected objects on diagrams, as graphic files or to embed them as pictures in MS Word documents. You can also copy matrices to spreadsheets. With Auto Modeler, you can download diagrams directly into PowerPoint. Diagrams can be printed directly from the modelers. see publishing see publishing

see above

Automatic see publishing extraction and document generation (the extent to which the tool can extract textual and graphical data and generate a document as specified by the user)

MetaEdit+ comes with a set of standard reports which can be used to document and check the design results independently of the method in use (e.g. object list, property list, dictionary, object connections, checkings, graph documentation in HTML and RTF formats). Code generators and other custom reports are defined with MetaEdit+ Report Browser.

Models can be published with Metis Editor (see Publishing)

Automatic generation of browsable HTML version of the model content.

Automatic generation of browsable HTML version of the repository content.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Documentation (N/A = information not available) Linking supporting documents or data to architecture constructs (e.g. reports, surveys stored outside the repository) ARIS Collaborative Suite 6.2 OLE (Object Linking and Embedding) is available to link various objects, e.g. Word documents, Excel tables, PowerPoint presentations, HTML documents or Paintbrush graphics directly with ARIS models (model components).

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Files and URLs can be linked to diagrams. MEGA External references can be associated with all objects: In the Properties dialog box of the object the location of the document or the URL is entered.

57

MetaEdit+ Method Workbench and MetaEdit+

METIS 3.4 External documents/applicatio ns can be linked to Metis models.

Rational Rose Enterprise Edition / Rational Rose XDE Developer External documents/URL attachments can be linked to diagrams.

System Architect 9.1 N/A

Usability (N/A = information not available) Consistency of user interface (consistency of the locations and representations of commonly appearing display elements and user input methods)

ARIS Collaborative Suite 6.2 ARIS uses a large number of Microsoft Windows properties and standards; e.g. menu structure, online help.

Corporate Modeler Suite 9 Uses the Windows properties and standards.

MEGA Navigator is the interface that opens up when launching a MEGA repository. The content of the repository can be organized within user desktop using folders as shortcuts to e.g. diagrams. Only one diagram editor; the content of the tool bar depends on the diagram type selected. At startup a window is opened to show links to explanatory wizards (guided tour, my first diagram, my first business process), and documentation files.

MetaEdit+ Method Workbench and MetaEdit+ MetaEdit+ automatically creates a default user interface for your method: menus, toolbars and dialogs. The default dialogs can be modified to change their layout, size, widgets, scaling and functionality. You can have nested dialogs, links to external files and documents ­ or just change the tab order.

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer

System Architect 9.1

An easy to follow "process map" guiding the use of the tool /ease of learning (the amount of time and effort required to understand normal tool operations and to become productive)

ARIS Method guides the use of the tools. Also Quick start guide available. Nevertheless, the broad functionality of the product has one down side; clarity and therefore intuitive use suffers.

Casewise framework (or the original Zachman Framework) can be used as a process map; a project kick off diagram combines elements from all columns in the appropriate level to show the scope of a project. The framework is not, however, explicit.

The Rational Unified Process (RUP) framework model can be used as a process map guiding the use of the tool.

The Popkin process can be used to guide the use of the tool. Using e.g. the Zachman framework interface helps to find the appropriate models, diagrams or definitions.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Usability (N/A = information not available) On-line help / user guidance (e.g. availability, clarity, readability, usefulness). ARIS Collaborative Suite 6.2 Online help introduces e.g. Aris House (the views and layers of the models); all models are described. Comprehensive Aris Method documentation. Some manuals available in pdf format. Searching of models/objects from the selected database(s). Navigation is done via tree structure. Each component can be viewed in ARIS Explorer; its properties, relationships to other objects within the model, variants and assignments (links to other models). There is a option to show models and/or objects in the tree structure. You can also select to view only the models and/or objects of a certain view (organization, data, control, function, product/service) The basics of business process modeling required.

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Online help includes quick references to start working with the Corporate Modeler (how to create models, how to draw diagrams, how to create templates etc.). Additional knowledge base is available in the web. Navigation within models can be done in Repository Explorer. A right-click popup menu includes navigating commands; e.g. diagrammed on (showing the diagrams the object is used in), explode (if a diagram is decomposed into a more detailed diagram) or diagram-open (to open the diagram) depending on the object type selected. MEGA On-line help available describing the basic functionalities and tools.

58

Searching/navigatin g/viewing capabilities of models/artifacts/co mponents

Search within diagrams, search (query or explore) objects within repositories. Navigating the projects, diagrams, objects, etc. can be done via navigation tree.

MetaEdit+ Method Workbench and MetaEdit+ On-line help with graphics and hypertext features. Method support provides help about the modeling technique, its components, reports and links to other techniques. Tutorials available (for MetaEdit+ and Method Workbench; evaluation tutorial). Connections between design information can be inspected and navigated with the Info Tool. Several browsers for viewing and editing the repository contents. The Type Browser can be used both for working with methods and for working with graphs and their elements. The Graph Browser provides you a hierarchy-based view of your graphs: you can choose between decomposition or explosion-based hierarchies, and access design elements of each graph. The Metamodel Browser shows modeling techniques and the method components they contain.

METIS 3.4 Online help available + example models.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Online help, user's guide, installation guide, licensing guide, online product tour and other tutorials, sample models available. Resources available on the web, e.g. UML Resource Center. Navigation through the content can be done via the Model Explorer.

System Architect 9.1 Online-help and user guide available + tutorials (business process modeling, UML modeling, data modeling, simulation etc.).

The Model Browser for Metis allows you to e.g. browse, zoom/pan models which have been published on the World Wide Web, an Intranet, or LAN. It provides searching capability also (e.g. search for objects and relationships). In Model Editor you can also browse and search submodels and instances in the model as a tree structure, browse and search the types and symbology used in your model.

Navigating through the content can be done e.g. with the help of the browser or e.g. the Zachman framework interface or TOGAF interface.

Knowledge requirements /user friendliness (the background and level of experience and expertise required to effective use)

The basics of business process modeling required. To be able to use the tool effective a training course may be needed.

Training is needed to fully exploit the functionality of the tools

UML modeling experience

Modeling experience (business, UML, data modeling)

Information Technology Research Institute LARKKI project Tanja Ylimäki

Usability (N/A = information not available) Does it provide a way for consistently naming and organizing the artifacts? ARIS Collaborative Suite 6.2 Models are organized in a hierarchical tree, the root node is called ARIS Network and the databases are below it. Each model component is also presented in the tree structure (in the model view).

Review of EA tools 18.6.2004

Corporate Modeler Suite 9 Objects are organized as models (i.e. a collection of objects), a hierarchical tree structure. Names of the objects can be modified. MEGA Business Function, Activity, Operation, Application, Service and Diagram metaclasses have a namespace. A city planning metaphore for organizing the models can be used (three city planning levels: areas, districts, blocks) MetaEdit+ Method Workbench and MetaEdit+

59

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer The content is organized according to the hierarchical structure (use case view, logical view, component view, deployment view). Artifacts (diagrams) can be named appropriately.

System Architect 9.1 The content is organized into diagrams and definitions. If e.g. the Zachman framework interface is used, it provides the organization for the content (it is attached to appropriate cells of the framework). Organization of the content can be modified through the framework editor.

Any other items of interest

Through its variant concept, ARIS lets you consider models under various initial conditions by creating variants of the models and varying the conditions through changes in the attributes.

MEGA City Planning Approach: City planning is the splitting of the information system according to a particular criterion. This splitting can be by main enterprise functions, by origin of applications as the result of a merger, by type of system environment or by any other criterion pertinent to the context of the enterprise.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

60

Architecture of the tool (operating environment and repository) (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 Deployment architecture (single tool, several closely related tools, single workstation, client/server, etc.) client/server/repository, i.e. 3-tier architecture; both the client and the server can reside on a single workstation or the server and repository can be placed in a network server. client/server/repository. The client can run on a stand-alone PC using a local database.

MEGA

MetaEdit+ Method Workbench and MetaEdit+ Client/server. Can be used as a single user workstation environment also.

METIS 3.4

MEGA is organized in 3 tiers: the site (the folder where programs files are located; on a network server), the environment (the system repository and work repositories) and the workstation. Also a standalone workstation installation is possible. HTML Portal available?

Client/server

Rational Rose Enterprise Edition / Rational Rose XDE Developer standalone / multi-user installation

System Architect 9.1

standalone / multi-user installation (client/server (repository)

Web functionality (Is it accessible through web client?)

ARIS Web Designer: worldwide and platformindependent use. The 3level architecture, consisting of a browser-ready front-end application and database server. This allows company procedures to be designed by employees distributed around the globe, as well as access to the procedures via a central repository.

Models can be published in HTML format. No web client exists to fully enable the use of the Corporate modeler through web.

N/A

Software/hardware supported/required

Client installations: Win XP, Win NT 4.0, Win 2000. ARIS Business Server: Win NT 4.0 Server (+service pack 6a), Win 2000 Server (+service pack 2), HP UX 11.11

Client: Win NT, 98, 2000 or XP. Server: Win NT or UNIX

Win NT/2000/XP, Win 98/ME/XP, Citrix

The Metis Web Forms allows users without Metis client software to have access to models in the Team Server using their web browser. The Team Server content is exposed as html, showing model content and allowing for updates. Models are controlled with the same permissions system and versioning schema used by other clients. Published models can be accessed over the internet also by using the Metis Model Browser (read only). Windows 98, ME, 2000, Team Server is based on XP. Linux (e.g. Redhat .Net and runs on Windows 6.0 or later). Solaris 2.5 2000/2000 Advanced or later, HP-UX 10.02 Server, and SQL Server or later 2000. For client products Windows 2000 Professional SP 1+ or Windows XP and Internet Explorer 5.0+ are recommended.

The content can be shared through HTML reporting capability, but it is read-only.

The content can be shared through HTML reporting capability (read-only). Also a SA Information Publisher (an add-on) is available.

Windows NT 4.0 (with SP6a), 2000 Professional (with SP2), 2000 server (SP2), XP Professional

Windows 98, NT (with SP6), 2000, XP, ME, MS Explorer 5.0 or higher, MS Office 97 (with SP2) or higher

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+ N/A

61

Architecture of the tool (operating environment and repository) (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 Backwards compatibility with prior releases of the tool / ability to move data between versions of the tool Time limitation with support between versions. E.g. in Aris 6.2. there is no possibility for database migration from ARIS 5.0x (or older) Models that were originally created in Corporate Modeler 2000 can be imported to Corporate Modeler 2001. First, you must use CM 2000 to export a model, or selected objects in a model, to a PAG file. Then, you must create a new model in CM 2001 and import the PAG file into that new model. COM, ODBC (support for Datafit DP4). Casewise is also active in the BPM initiative (BPMI.org) promoting and developing standards for BPM tools. three server options: DP4 Local Server (single user only), DP4 Network Server and Oracle

METIS 3.4

N/A

Restricted compatibility, e.g. Metis Model Browser 3.4 can be used with the existing models published for Model Browser 3.3, but it cannot be used to view the models published for Mode Browser 3.2.3 or older.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Models created with earlier versions (e.g. Rose98i, Rose2000, Rose2001) can be imported into Rose/XDE (2003).

System Architect 9.1

Encyclopedias from version 8 can be converted to version 9 before they can be used. A conversion guide is available.

Supported standards (e.g. database, repository, communication, GUI, configuration management, security, information interchange standards, APIs) Repository structure (structure between the tool and its repository)

e.g. OLE, XML, XMI, BPMN, LDAP, SSL, TCP/IP

OMG's MOF, BPMI (see bpmi.org), UDDI (see uddi.org), ISO 9000-2000 (MEGA Process tool)

SOAP / Web Services / .NET standard for application integration

SVG (for all graphics), COM, HTTP/SSL/XML/SOAP/ WebDAV

XMI

eTOM?

ARIS server includes a repository (a standard database system). Another database (see below) can be connected to ARIS also.

Metamodel based repository; allowing customization of the metamodel. Supports a project per repository approach, or allows multiple projects in a single repository.

N/A

Repository items are File hierarchy? organized in, and navigated through, a standard, hierarchical folder structure. The Metis Team Server repository can store any digital content, not just Metis models. Versioning, checkout, check-in, export and import are available for any file.

Work done in System Architect is stored in a project encyclopedia. An encyclopedia can be created for every project, or have multiple projects in one encyclopedia. Encyclopedias are created as databases in either MSDE or SQL Server 2000. Encyclopedia contains diagrams, symbols and definitions. A diagram contains symbols, each of which has an underlying definition. Some definitions exist without symbols (e.g. requirements, attributes).

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+ N/A The Object Repository supports: * Multiple concurrent users * Long transactions (maintain locks while exiting MetaEdit+) * Lock at a fine level of granularity (single objects instead of whole graphs) * Storing billions of design objects * Modifications of methods, with models updating on the fly

62

Architecture of the tool (operating environment and repository) (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 Supported databases Teamwork capabilities (Multiuser concept: is the repository capable of supporting concurrent multiusers?) Oracle, MS SQL Server, IBM DB2 multi-user repository; client access throug e.g. ARIS Web Designer Oracle, Datafit DP4 The product can be used in a multi-user environment by fielding Corporate Modeler on Corporate Exchange - a server that supports multiple browser-based clients, up to 400 users can access the same diagram. A model can be divided into submodels also, and each sub-model can be worked on independently and finally merged back into the master model. However, managing these sub-models is a complex task and subject to various pitfalls. XML import/export, with Auto Modeler data can be converted into MS Office data and vice versa. Match by Name Utility can be used to match the UUIDs of objects in different models, so that when they are imported from one model to another they are merged into a single object.

METIS 3.4

N/A Multi-user environment available with checkin/check-out functionality, also private workspaces. Objects can be merged when needed.

MS SQL Server 2000, MSDE 2000 or Oracle 8.1.7 and higher With the Metis Team Client add-on product, you will be able to use the Repository Tree to work against models in the Metis Team Server. Open specific versions, view version history, check out/check in/revert and set permissions.

Rational Rose Enterprise Edition / Rational Rose XDE Developer N/A Multi-users are supported (via version control system). Allows parallel development of a model by supporting decomposition of the model into versionable units, called controlled units. In order to allow different users to access the model from different workspaces, virtual path maps are used as references to controlled units.

System Architect 9.1

MSDE, SQL Server 2000 Multi-users are supported through check-out/check-in capability.

Does the repository allow import/export of models/data? If so, can it deconflict the various models if needed?

ASCII format data can be imported/exported, also XML import/export possible

see above

XML import/export

Models can be exported to/imported from standard file systems, for use with Metis installations not connected to the Metis Team Server.

Models (=files) in Rose format (.mdl, .ptl, .cat, .sub) can be imported/exported into workspace/Rose. Models can be integrated into one model with Rational Rose Model Integrator.

Encyclopedia files (i.e. databases or projects) can be imported/exported.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+ Commited modifications are automatically reflected to all users, quaranteeing consistency and up to date information. MetaEdit+ gives you full support for dividing your work into multiple projects, with different access rights assigned to different users. You can have many projects open at a time and reuse and link data between projects in just the same way as within a single project.

63

Architecture of the tool (operating environment and repository) (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 What kind of management functions does the repository provide (versioning and/or change control, ability to roll back/forward between different versions, tracking of modifications, access control, automatic backup, etc.)? Access control (no acces, read/write, read/write/delete), priviledges assigned to users to enable/disable certain functions (e.g. database export, change management, method changes). User groups can be defined. Manual backup/restore of databases. Copy databases to different servers, reorganize databases.ARIS Consolidation allows you to remove redundant data from your database. You can consolidate equivalent objects that have different or identical names under one object definition within a database. ARIS Merge helps you to merge the contents of multiple databases into one master database consistently and without generating redundant items. In multi-user operation, for example, operational departments can record their business processes in various databases and the contents of the various databases are merged consistently into a master database from a coordination point in the Access control (different priviledges for different user levels; system manager, project manager, normal user and read only user). A user can lock a model, he/she is working on and other team members can't see the model in their Repository Explorer tree (this can be used e.g. when doing an import or merge). A model can be freezed and no changes can be made to it. There is no specific backup or restore functionality.

METIS 3.4

Backup (i.e. copying files of a repository from their original location to another one), access control (read/write/delete/no access to repositories; access to all MEGA tools or defined tools), tracking of modifications (history text within object properties indicates modifications carried out on an object since the last reinitialization of its history), checking and reorganizing of the repository.

* Versioning * Concurrency control (check-out/ check-in) * Flexible retrieval of versions based on version policies * Maturity levels on content * Flexible permission management * Team Server supports all basic model management processes, including support for model versioning and reviewcycles * Dependency tracking on Metis models. Metis Team Server tracks how Metis distributes a model on multiple files (sub models, model data in separate files). Version policies are used to control the model configuration.

Rational Rose Enterprise Edition / Rational Rose XDE Developer The Version Control Add-In provides integration between Rational Rose and any SCC -compliant version control system. It makes the most frequently used version control commands accessible directly from the Tools menu and from shortcut menus in Rose. For example, you use the Version Control Add-In to: Add packages to version control, which you must do before you can check out or check in the packages; Check out and check in packages; Start your SCC-compliant version control system.

System Architect 9.1

SA EnComp add-on is the encyclopedia comparison utility; it can be used to compare the models in two encyclopedias.

Any other items of interest

Support for older versions is provided for one year after the release of a new version. Support for version 2.5 ended November 1999. MetaEdit Personal 1.2 is not supported any more.

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

MEGA MetaEdit+ Method Workbench and MetaEdit+

64

Architecture of the tool (operating environment and repository) (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 company using ARIS Merge. During the merge, ARIS Merge recognizes identical items in the databases and you can decide which item is to be transferred.

METIS 3.4

Rational Rose Enterprise Edition / Rational Rose XDE Developer

System Architect 9.1

Configuration, customization, scalability and integration (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 Internationalization / localization capability Possible languages for GUI: German, English, Spanish, French Product available in several language; English, German, Spanish, French

MEGA

Expandability (e.g. add-ons)

e.g. ARIS Simulation, ARIS BSC (balanced scorecard), ARIS ABC, ARIS Process Cost Analyzer, ARIS BPML Interface (to export ARIS data to BPML files), ARIS WebPublisher, ARIS Connectivity components

IT Architecture Accelerator (enterprisewide approach - a road map - to IT planning), Balanced Scorecard Accelerator (to add performance measurement to the Corporate Modeler Suite), Simulation Utilities, Links to third-party products (see below)

Repository is capable of handling data in several languages, e.g. English, German, Spanish, French, Dutch, Italian, Chinese, Czech, Korean, Portuguese, Hungarian. Technical modules to N/A customize the platform to customer's specific needs; MEGA Intranet, MEGA Documentation, MEGA Generation, MEGA API, MEGA Supervisor

MetaEdit+ Method Workbench and MetaEdit+ English version

METIS 3.4 N/A

Rational Rose Enterprise Edition / Rational Rose XDE Developer English and Japanese versions are available.

System Architect 9.1 English and German versions are available.

XML Interface allows any kind of file-based XML data to be imported into Metis

Rational Rose provides several ways to extend and customize its capabilities to meet the specific software development needs; menus are customizable, manual functions can be automated with Rose Scripts (e.g. diagram and class creation, model updates, document generation), Rose functions can be executed from within another application by using the Rational Rose Automation object (RoseApp), Rose add-ins can be activated using the Add-In Manager. It can be integrated with other Rational products like RequisitePro, ClearCase, SoDA (Software Documentation Automation).

Add-ons: SA Information Publisher (to generate website from SA repositories), SA EnComp (to compare two SA repositories). Visioto-System Architect Mapper macro (maps diagrams built in MS Visio to equivalent diagrams in SA)

Information Technology Research Institute LARKKI project Tanja Ylimäki

Review of EA tools 18.6.2004

MEGA integration possible through MEGA API (COM-based and includes full read/write capabilities)

65

Configuration, customization, scalability and integration (N/A = information not ARIS Collaborative Corporate Modeler available) Suite 6.2 Suite 9 Does it integrate with other tools? can be integrated with Lotus Notes, SAP (ARIS Connectivity for Lotus Notes, ARIS Connectivity for mySAP). Using ARIS Lotus Notes Connectivity you can create and run links from ARIS to Lotus Notes items. ARIS Lotus Notes Connectivity creates the link to Lotus Notes. can be integrated with Sybase's PowerDesigner, Rational Rose, Oracle Designer, Erwin, Telelogic's Doors, MS Visio, Requisite Pro, Tibco InConcert

Compatibility with other tools (capability to operate with other tools like word processors, databases, repositories, other case tools) Capacity constraints

N/A

capable of import/export data between MS Office (Word, Excel) and Corporate Modeler.

N/A

N/A

E.g. Matrixes can be exported to MS Excel, diagrams can be saved as multiple formats (e.g. png, jpeg, tif, svg, bmp, wmf) to enable viewing and editing with other software. N/A N/A

MetaEdit+ Method Workbench and MetaEdit+ The MetaEdit+ API allows to build tool integration between MetaEdit+ and other tools. The API provides the interface to read, create, and update model elements, as well as control MetaEdit+ for scripting or simulation support. The MetaEdit+ API uses the widely supported and open SOAP / Web Services / .NET standard for application integration. N/A

METIS 3.4 The Metis modeling kernel is exposed as a Windows COM component, so it is possible to create scripts (VBScript or Jscript) to interact with and pass data to/from e.g. the Microsoft Office tools or Crystal Reports.

Rational Rose Enterprise Edition / Rational Rose XDE Developer Open API accessible via scripting.

System Architect 9.1 System Architect XMI Interface to Rational Rose

The Metis Database Interface makes it easy to create and refresh Metis models with data residing in relational databases. N/A

see above

An SA-DOORS Interface enables you to manage your requirements in Telelogic's DOORS requirements management tool N/A

N/A

Information Technology Research Institute LARKKI project Tanja Ylimäki

Implementation and Testing (N/A = information not ARIS Collaborative available) Suite 6.2 Code generation capabilities (not evaluated)

Review of EA tools 18.6.2004

66

Corporate Modeler Suite 9 Data can be exported to Rational Rose (Rational Rose Link is needed) and use Rose's code generation capabilities

MEGA (not evaluated)

MetaEdit+ Method Workbench and MetaEdit+ MetaEdit+ supports code generation for predefined and user-defined programming languages. Predefined: Smalltalk, C++, Java, Delphi (object pascal), SQL, CORBA IDL N/A SQL generation

METIS 3.4 N/A

Rational Rose Enterprise Edition / Rational Rose XDE Developer Yes, e.g. Java, C++, Visual Basic (separate editions), CORBA, Ada

System Architect 9.1 Code generation is provided from objectoriented class diagrams (e.g UML class diagram). C++, Java, Visual Basic, CORBA IDL and JavaScript languages can be generated. N/A Database schemas (DDL statements) can be generated for several SQL and nonSQL DBMS products.

Prototyping Database schema generation capabilities

(not evaluated) (not evaluated)

Reverse engineering capabilities

(not evaluated)

N/A An Entity Diagram shows the entities within a business and their relationships to each other. Underlying information such as attributes, domains and key data can be used to generate SQL definition scripts. ?? N/A

(not evaluated) (not evaluated)

N/A N/A

N/A In Data Modeler it is possible to forward engineer from object model to data model to database or to DDL script.

(not evaluated)

No

N/A

Debugging and testing capabilities

(not evaluated)

N/A

(not evaluated)

N/A

N/A

Yes, in Rose XDE Developer Java code and models can be automatically synchronized; change in one is automatically done to another. E.g. visual tracing in Developer Plus Edition. QualityArchitect is a collection of integrated tools for testing middleware components built with technologies such as Enterprise JavaBeans (EJB) and COM.

C++ or Java code can be reverse engineered into SA. Also several SQL Schema and databases can be reverse engineered into SA. N/A

Information

The Zachman Framework

66 pages

Find more like this

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

839