rochade-powered enterprise architecture environment · enables other enterprise metadata management...

Rochade-Powered

Enterprise Architecture

Environment

Enterprise Architecture Environment

12700 Sunrise Valley Drive, Reston, Virginia 20191, USA | Tel: 703.464.1305 | Fax: 703.464.4905 | Toll Free: 1.800.Rochade Allen Systems Group, Inc. | www.asgfederal.com/rochade | [email protected]

Table of Contents

1. Rochade EAE Overview.....................................................................................................................2 2. Rochade EAE Functions ....................................................................................................................4 3. Rochade EAE Architecture ................................................................................................................5 4. Rochade EAE Components ...............................................................................................................6

4.1. Rochade Repository..................................................................................................................7 4.1.1. Rochade Server ......................................................................................................................8 4.1.2. Rochade APIs..........................................................................................................................8 4.1.3. Rochade RIMs.........................................................................................................................8

4.2. Rochade Manager...................................................................................................................10 4.3. Rochade Interfaces .................................................................................................................10 4.4. Rochade Portal........................................................................................................................11 4.5. Modeling Tools .............................................................................................................................13 4.6. Other Repositories........................................................................................................................13 4.7. SW Component Engineering Tools ..............................................................................................13

5. Rochade EAE Scenario ...................................................................................................................13 5.1. Roles:............................................................................................................................................13 5.2. Overview:......................................................................................................................................13 5.3. Tasks: ...........................................................................................................................................14

6. Rochade EAE Support Roles...........................................................................................................15 7. Rochade EAE – “An Industrial-Strength, High-Powered Solution” ..................................................15

Rochade™ Enterprise Architecture Environment November, 2003

2

1. Rochade EAE Overview Every Enterprise Architecture (EA) will eventually reach a level of maturity and complexity that requires a repository-based EA environment that integrates EA tools, frameworks, methodologies, models, and artifacts. Rochade, the world’s most powerful metadata engine, is the only commercially available, advanced repository management product with the power and flexibility to deliver a complete, “industrial strength,” integrated Enterprise Architecture Environment. Rochade allows models and artifacts from multiple EA frameworks and methodologies to be managed in a single, central repository. For example, the same artifacts used to produce DoDAF/CADM work products can be used to produce FEAF work products, including OMB 300B’s. Rochade allows all artifacts, models and model elements to be linked to one another. These relationships form the basis for work product production and provide the ability to trace requirements and business rules, from strategic to implemented, in an “adaptable” Enterprise Architecture. These links also allow detailed impact analysis as part of an enterprise change management program. In addition, Rochade provides the ability to integrate and manage multiple hierarchies of models in the same repository and in multiple repositories. This means that the models for an enterprise and all its subordinate elements can be managed independently and still be interoperable with other repositories [e.g., Rochade can power a federated Enterprise Architecture Environment for the Department of Defense and its subordinate Agencies and Services – allowing each to be independent and yet collaborative.] Rochade supports a wide-range of standard modeling notations (IDEF, process, ER, DFD, UML, etc.). Rochade can also be used to transform objects from one notation to another where there is a sufficient amount of “sameness.” Rochade also complements and supports most modeling tools. It has the ability to import/export models from any tool and it can even transform models from one tool's format to another’s. This flexibility is due, in part, to the ability to exchange metadata via XML/XMI along with extensive busses and scanners. Rochade can even be configured to automatically “harvest” metadata from tools, databases and other repositories at regular intervals. The key to Rochade’s extensibility is the ability to define multiple sets of meta-metamodels (Rochade Repository Information Models) describing both physical and logical characteristics of models and model elements.


3

The key to Rochade's power is a network-centric meta-database and unique architecture that is robust, scaleable, and extensible, can be implemented in multiple environments (Unix, Linux, Windows NT, MVS). Rochade’s MDBMS is designed to provide superior performance regardless of the amount of metadata and models stored in the repository. Rochade’s core functionality lets you store all artifacts and work products in a single place with version control and configuration management. Rochade provides role-based levels of security for artifacts and models – even to individual “attributes.” Rochade delivers true 24x7 operation by providing on-line and off-line backup facilities, activity logging and recovery from a failed event or to a given point in time, and operation of mirrored environments to support disaster recovery. Rochade repository contents can be viewed via both feature-rich client and web-based applications. Repository content views can be tailored to specific roles and communities of interest. Rochade’s accessibility is further strengthened by built-in reporting capabilities and the ability to export models and other work products to both traditional and web publishing tools. The benefits of a Rochade-Powered Enterprise Architecture Environment include: Fully supported EA engineering process Increased architecture and artifact quality Integration of EA methodologies, frameworks, artifacts, models and tools Interoperability of hierarchical architectures

Rochade not only powers a world-class Enterprise Architecture Environment, it also facilitates and enables other enterprise metadata management initiatives that are driven/governed by an “actionable” Enterprise Architecture. These include: Data/Information Integration Application Integration/Modernization Data Warehouse and Portal Engineering Integrated Data/Development Environments Modernization/Transformation/Consolidation Software Component Engineering XML Metadata Management

Figure 1 graphically depicts the multiple dimensions of Rochade-powered enterprise architecture solutions. The pages that follow address how Rochade powers an Enterprise Architecture Environment (EAE).


4

Figure 1. Rochade Solution Architecture

2. Rochade EAE Functions The Rochade-Powered Enterprise Architecture Environment integrates multiple tools on multiple platforms. It also provides the capability to integrate EA artifacts, both primitive and complex, required by multiple frameworks and methodologies. These artifacts range from documents and spreadsheets to models of logical and physical enterprise elements in various modeling notations. Rochade provides the “glue” that holds the domain environment together. This has the advantage of simplifying the environment and thus simplifying all interactions. The core functions of the Rochade-Powered EAE include:

Artifact check-in/check out Metadata describing all of the relevant domain integration information, regardless of structure or source, is collected in the Repository. This metadata is used to support content capture, integration, and management as well as content distribution services such as searching, categorization and reporting. Any artifact that can be created digitally can be stored in the Rochade Repository. External artifacts can also be imported into the repository and managed as independent “subject areas.” This allows actual linking of external and internal artifacts for traceability and certification. It also allows aggregation of internal and external artifacts into complex components and reports. Versioning and configuration management One major benefit is that versioning and configuration management is limited to one and only one process/repository/data store. Change management and communication functions can be implemented that allow artifact stewards/owners to be notified when changes are being considered

Rochade Enterprise Architecture Integration technology is critical for mature, complex EA environments.

Support for multiple EA methodologies – DODAF, CIO Council, Spewak, BCM, In-house developed

Supports any rule-based standard notation – IDEF’s, UML’s, SSA, etc.

Supports multiple frameworks RIMS, often integrated in a single repository – Zachman, FEAF, CADM, NASCIO, in-house.

“Out-of-the-box” integration of dozens of tools and databases, includingPopkin, Rational, XMI.

Web InterfaceDiscoverySecurityVersioningBackup & RecoveryCollaborative Repositories

Rochade Enterprise Architecture Integration technology is critical for mature, complex EA environments.

Support for multiple EA methodologies – DODAF, CIO Council, Spewak, BCM, In-house developed

Supports any rule-based standard notation – IDEF’s, UML’s, SSA, etc.

Supports multiple frameworks RIMS, often integrated in a single repository – Zachman, FEAF, CADM, NASCIO, in-house.

“Out-of-the-box” integration of dozens of tools and databases, includingPopkin, Rational, XMI.

Web InterfaceDiscoverySecurityVersioningBackup & RecoveryCollaborative Repositories


5

that will impact them. They and all stakeholders can be notified when the new versions are integrated and published.

Viewing and reporting Rochade has comprehensive search facilities that allow searches based on object type, name, alias name, contents, date, time and owner related info. These complex queries can either be defined and saved by an administrator for reuse or dynamically generated through a supplied html form. Rochade also has a sophisticated and powerful built-in reporting capability. In addition, when additional reporting capabilities are needed, Rochade can export repository content in multiple formats as input to other publishing or reporting tools.

Change impact analysis Impact analysis is enabled through the capability to link any repository element to any other element and to many other elements. This capability also facilitates traceability and certification. The Rochade APIs and open nature of the Rochade DBMS allow it to be fully integrated into an automated process/program management system. When the system infrastructure includes messaging and change/issue management capabilities, Rochade analysis and metadata harvesting functions can be fully integrated into the PM system.

A Rochade-Powered EAE provides a single point of understanding to a broad set of information from multiple sources. By adding a messaging infrastructure, EA engineering teams are able to:

Develop a consistent, coherent, integrated, interoperable, adaptable, and actionable Enterprise Architecture

Identify and remove redundancies in models Manage change in a single repository. Work on artifacts without altering configured versions. Use any technology infrastructure.

3. Rochade EAE Architecture Figure 2 illustrates the technology architecture we recommend for the Enterprise Architecture Environment. The underlying design philosophy is that there is a “single source of truth” in the Environment. No matter what tools are used to create artifacts; no matter who creates them; and no matter when, where, or how they are created, there is only one “industrial strength” repository where the approved versions of the artifacts are captured, stored, and managed. The repository is also the source of all “published” versions of artifacts, deliverables, work products and reports. Rochade facilitates an integrated Enterprise Architecture Environment, providing a single point of communication for managing critical artifacts, regardless of source or structure. Rochade supports all the latest Information Technology environments including client/server architectures, Internets/Intranets (including Web browsers), object orientation, and graphical user interfaces (GUIs) utilizing TCP/IP, APPC, and NETBIOS. Rochade also supports all platforms, from laptops to mainframes, with the same architecture and the same level of functionality.


6

Figure 2: Rochade-Powered EAE

4. Rochade EAE Components Rochade uses instances of a generalized layered architecture to implement the essential functions of metadata collection, storage, management and provision. This approach provides for a maximum of component reuse, and wide flexibility in deployment. At the center of the technology architecture is the Rochade Repository. This is where all artifacts are stored and managed. All versioning and configuration management for artifacts occurs in the repository – not in any of the other repositories or tools that may be part of the Enterprise Architecture Environment. This is also where links between artifacts are established and maintained. Artifact building and maintenance is done using the most appropriate tools for the artifacts. The artifacts checked in to the repository via the Artifact Staging area. When artifacts are completed, validated and approved, the artifact owner exports it to the staging area. A repository Librarian checks the artifact into the repository and establishes configuration management. When changes are required, the artifact is checked out via the staging area and imported into the appropriate modeling tool. Once approved, the changes are exported from the modeling tool and imported into the repository via the staging area. The changes are used to create a new version, which is then placed under configuration management. Architects and a limited set of stakeholders, managers and executives access artifacts directly from the Development Repository. All others access artifacts from a separate Production Repository in which the current versions of artifacts are “published.” The development and production repositories can be separated either logically or physically. The Rochade-Powered EAE technology architecture is composed of multiple components from ASG and other vendors. The following section and graphic describes EAE components. Those that are based upon Rochade are clearly identified.

SW ComponentEngineering

Tools

GeneralConsumer

Stakeholder

Executive

Manager

Architect

Librarian

Engineer

Metadata Server

Artifact Staging

DevelopmentRepository

ModelingTools

Other MetadataRepositories

ProductionRepository

External Repositories

XML


Tools

GeneralConsumer

Stakeholder

Executive

Manager

Architect

Librarian

Engineer

Metadata Server

Metadata Server

Artifact Staging


ModelingTools

Other MetadataRepositories


External Repositories

XML


7

Figure 3: Rochade EAE Components

4.1. Rochade Repository Rochade is one of the longest established, and is the most technologically competent repository currently available. The Rochade repository explicitly supports EA management. It is constructed specifically for the storage and high performance manipulation of network/object structures. This approach provides for: Concise modeling of complex information/repository structures Interdependent storage of data composed of items and links between the items in a network

structure. Superior performance of queries focused on text attributes, value attributes, and direct and

indirect relationships. The use of both forward (usage) and backward (referenced by) links makes it possible to traverse a network query in both directions with the same performance.

Great flexibility for reconciliation and versioning. Data store consistency: managed and maintained in two ways – Logically and Physically.

Logically: Rochade allows objects, from models to attributes to be stored once and shared across the repository. Thus primitive artifacts can be captured, versioned, configured and used in multiple complex components representing multiple processes and frameworks. Rules about the use and quality of artifacts can also be captured and stored in the repository. Using those rules, users can determine whether newly captured artifacts are consistent with current content and rules. Given a metamodel that defines alignment, and model/artifact elements that have been linked, Rochade can produce textual and graphical reports that show alignment to any depth.


Tools

GeneralConsumer

Stakeholder

Executive

Manager

Architect

Librarian

Engineer

Metadata Server

Artifact Staging


EA ModelingTools

Other MetadataSources


External EARepositories

RepositoryRepository

Interface Interface

PortalPortal

ManagerManager

XML


Tools

GeneralConsumer

Stakeholder

Executive

Manager

Architect

Librarian

Engineer

Metadata Server

Metadata Server

Artifact Staging


EA ModelingTools

Other MetadataSources


External EARepositories

RepositoryRepository

Interface Interface

PortalPortal

ManagerManager

XML


8

Physically: The Rochade MDBMS write algorithm exploits a low-level transaction mechanism to enforce database consistency. Each modification of an object will be completed or rolled back. All writing Rochade commands are carried out as transactions in the server. These transactions maintain consistency in the database even if a write operation is aborted. Any server aborts that may occur will not lead to a loss of data or to data corruption. When the server is started up again after an abort, connected databases are checked for consistency, and where necessary are automatically reconstructed. In this way, interrupted write actions are either completed or reset. The server is able to recognize and react immediately to consistency errors in the data supplied to it.

The Rochade network/object MDBMS has many object-oriented characteristics including the reusability of items within the repository. The object-oriented behavior of Rochade extends to the implementation of rules and behaviors governing the contents of a repository.

4.1.1. Rochade Server The Rochade server is the engine that manages the Rochade Repository and provides for metadata storage, retrieval and integrity. The Rochade server can be sited on any of the platforms below:

IBM OS/390, z/OS (MVS) Hewlett Packard HP-UX IBM AIX LINUX (Intel platforms) MS Windows 95, 98, Me, NT 4.0, 2000, & XP Siemens BS2000 Siemens Sinix Reliant Sun Solaris

4.1.2. Rochade APIs Many organizations utilize the Rochade Application Programming Interfaces (APIs) enable custom applications to use the Rochade repository. The Rochade APIs can be used from within any language or architecture, which enables calls to external routines. These include, but are not limited to:

• C/C++ • Visual Basic • Java • Delphi • PowerBuilder • COBOL • Rexx • SAX/XML

The C/C++, Java, and SAX/XML API’s are provided “out of the box,” with any other suitable language facilitated by defining the appropriate language specific calls.

4.1.3. Rochade RIMs The Rochade repository metamodel is highly generalized and provides for the representation and implementation of any repository data model. The content, structure, and syntax of the information stored by the repository are defined through the creation/modification of one or more Repository Information Models (RIMs).


9

Rochade RIMs (metadata models) are stored in the repository along with artifacts to facilitate artifact management, linking, and aggregation. These include RIMs for complex artifacts so that they can be built upon demand and published as necessary. Conceptually Rochade embodies the layered metamodel articulated by the Object Management Group (OMG). Customer metadata (M0) is modeled in the RIM (M1). The RIM is an instance of the Rochade Metamodel (M2) which is an instance of it’s own meta-metamodel (M3). A Rochade RIM is basically a schema for the potential contents of the repository database. RIMs (and the higher-level metamodels) are constructed using the following 4 basic building blocks:

Item Type (to describe a type of item/object) Attribute Type (to describe a property/characteristic of an item/object) Relationship Type (to describe links between items/objects) Rule/Method (to describe special processing associated with an

item/attribute/relationship or another rule) Using these building blocks it is very easy to modify and/or extend information models within Rochade. The diagram below identifies the meta-objects of a typical Enterprise Architecture RIM.

Figure 4: Conceptual Rochade EA RIM

The most important part of implementing a Rochade EAE is correctly defining RIMs for the environment. In order to establish the Rochade EAE, the EA engineering teams will need to develop a “mega-RIM” as a unifying metamodel with quality assurance rules. Typically this is done during one or more ASG-led RIM modeling workshops in which architects modify and extend ASG’s starter RIMs (see below) with enterprise unique meta-objects. During these workshops, links are also established between all of the conceptual and logical RIMs as well as physical RIMs that describe the various meta-structures of the enterprise environment to facilitate EA artifact interoperability. The result is an integrated enterprise model that is tailored to the specific tools, methods, and techniques employed within the enterprise. ASG has several template RIMs (metamodel “starter sets”). • Zachman EA Framework RIM • Department of Defense Architecture Framework (DoDAF) RIM

Framework

Cell

Artifact (Component)Perspective(Row)

Category(Column)

Object (Element)

Primitive

Tool or Technology

Model

Methodology

Work Product (Deliverable)

Steward (Owner)

Complex

DeterminesDetermines

Contains

Focuses

Composedof

Contains

Sourceof

Becomes

Used toProduce

Defines

MandatesResponsiblefor


10

• Federal EA Framework (FEAF) RIMs (those reference models for which XML is available) • Business Rules Group (BRG) RIM • CWM (Common Warehouse Metamodel) from the OMG

Rochade allows multiple RIMs to co-exist in the same repository. It also allows them to be linked at the meta-level -- point-to-point, networked, hierarchically, concentrically, etc. This capability allows models and artifacts from multiple EA frameworks and methodologies to be managed in a single, central repository. RIMs can also be used to integrate and manage multiple hierarchies of models and repositories. This means that the models for an enterprise and all its subordinate elements can be managed independently and still be interoperable with other repositories [e.g., Rochade can power a federated Enterprise Architecture Environment for the Department of Defense and its subordinate Agencies and Services – allowing each to be independent and yet collaborative.]

4.2. Rochade Manager The Rochade Manager is based upon ASG’s tightly-coupled and feature-rich client-server tool, Rochade AutoPilot. Repository Librarians and Administrators use it to communicate directly to the Rochade server. It can also be used for bulk metadata import/export. Rochade Manager is the standard Rochade administration interface, enabling, but not limited to, the following facilities: • Metamodel manipulation • User creation and access rights administration • Repository views administration • Versioning and configuration management administration Provided standard with the Rochade Manager are Foundation Level Services, or Core Classes. This provides an object-oriented method of accessing the Rochade environment. Rochade Manager is platform, mode and access mechanism independent. This results in the same facilities and security model being available irrespective of the actual mechanism a user employs to access the Rochade server. The facilities provided by the Foundation Level Services include, but are not limited to: • Item management searching and listings • Item manipulation – creation, retrieval, editing and deletion • Impact analysis • Version and configuration management

4.3. Rochade Interfaces Rochade Interfaces enable bulk metadata loading and generation. Rochade Interfaces are also called Busses and Scanners. Rochade Interfaces provide a mechanism for loading and/or exporting metadata to/from the Rochade repository for a number of languages, databases, modeling tools and environments. Rochade offers many ready-to-use interfaces to metadata sources such as source code, database catalogues, design tools, and data-warehouse tools. The majority of these interfaces are bi-directional. It is possible to analyze or scan existing data to populate Rochade, and it is also possible to export metadata through these interfaces. The exported metadata can then be consumed by the tools or as “include” files in programs. Additional interfaces can be developed by clients, or on a consultative basis by ASG or partner firms. Development of metadata interfaces is based on the Rochade API structures, using the Rochade Procedure Language (RPL) or (more typically) Java. Input is via APIs, or XML format,


11

or using RPL stream procedures. Export creates XML data, RPL streams, or data files, which can be directly used in the target tools.

Figure 5: Rochade Busses and Scanners

4.4. Rochade Portal The Rochade Portal is designed for disseminating information over the Internet. It is based upon ASG’s Rochade WebAccess tool, which utilizes industry-standard technologies – Java™ and JavaServer Pages™ (JSP) – that enable it to be used with a large number of Web servers and Web development tools. The Rochade Portal can serve as the single access point for stakeholders to all repository components in both the Development and Production Repositories. Repository content “Managers” have total control of access and availability. Consumers who have appropriate security and permissions can both read and write to the repository using both textual and graphical views. The Rochade Portal can also be customized to allow access to modeling tools and external components wherever they are available. The GUI for the Rochade Portal can be tailored to any environment. Most clients customize and implement a Rochade Portal that represents the Methodology and EA Framework they have adopted. To illustrate this capability, ASG has developed a demonstration environment that uses the Zachman framework as the visual paradigm (see Figure 6) for access to a Rochade EA Repository to assist in understanding and navigating enterprise architecture artifacts.


12

Figure 6: Zachman Framework as a front end to the Rochade EA Repository

Because the Zachman Framework is not a solution in itself, merely a framework, or classification scheme to work within, the Rochade Repository is designed to allow one or more metamodels to be defined for a particular cell, utilizing supplied industry standard models and tool/language specific models where appropriate. A Rochade repository also has the flexibility to allow for artifacts to be established for as much of the Zachman framework as required. In the demonstration environment, the initial screen is the complete Zachman framework allowing access to those cells a user is interested in, as defined by their security profile. A user may, for example, require information relating to the Conceptual Data Models within an organization – Row 2, Column 1and by selecting this cell would see a list of options available within that cell. These options, which are fully customizable, could be such things as a simple list of objects within the cell, a search facility, a diagram (such as an Entity Relationship model), an impact analysis query, etc. This enables architects and managers to implement the metamodels and processes of their Methodology and the EA Framework. There are no limitations to the number of cells that can be traversed, the volume of data that is stored, or the complexity of the connections between objects within the Framework. The actual mechanism for mapping objects between cells, layers and columns is highly dependent upon many factors, such as, but not limited to: • Source tool/environment characteristics • Frequency of changes/updates • Naming standards


13

• Organizational standards Because there is no "standard" way of working in an Enterprise Architecture Environment, Rochade provides the tools to enable each exact situation to be modeled and managed as necessary in each individual environment.

4.5. Modeling Tools In the Rochade-Powered Enterprise Architecture Environment, modeling tools are used for building and maintaining the artifacts for which they are best suited. Because no single tool excels at developing every artifact, that means that “best of breed” tools can be used by architects. This improves the quality of the architecting process as well as the quality of the artifacts. In addition, because versioning and configuration management is only done once an artifact version is approved for loading into the repository, there is no need to implement multiple artifact management processes.

4.6. Other Repositories In a typical Enterprise Architecture Environment, there may be several internal or external repositories or data stores that are not specifically supporting one of the modeling tools, yet contain artifacts or information of interest/value that should be captured, stored, integrated, managed and distributed via the Rochade Repository.

4.7. SW Component Engineering Tools The ultimate value of an Enterprise Architecture Environment is realized when EA artifacts, particularly service component models and data models, are used to drive both COTS implementation and custom application development. In the Rochade-Powered Enterprise Architecture Environment, the EA component “design models” managed in the repository are exported to various SW engineering tools that are used to develop and/or implement applications. For simplicity, we also include legacy application modernization tools in this category.

5. Rochade EAE Scenario The following is a typical scenario for a Rochade-Powered Enterprise Architecture Environment. It assumes that the Enterprise Architecture Environment is already established and some “as is” and “to be” artifacts are already in the Rochade repository.

5.1. Roles: Architect Stakeholder Executive/Manager General Consumer Librarian

5.2. Overview: The scenario has 4 major steps: 1. Check-in Model 2. Integrate Model 3. Publish/View Model 4. Check-out/Update Model

Figure 7 illustrates typical interaction with the Rochade-Powered Enterprise Architecture Environment.


14

Figure 7. Rochade EAE Scenario

5.3. Tasks: 1. Check-in Model

a. Architect completes a model. b. Stakeholders validate and verify the model. c. Managers approve adding the model to the Repository d. Architect exports the model to a Repository staging area. e. EA Librarian loads the staged model into the repository

2. Integrate Model

a. Architect and Librarian run model analysis routines b. Architect reviews inconsistencies among models and suggests alterations c. Architect submits changes to Repository staging area d. Architect and Librarian implement versioning and configuration control. e. Architect adds relationships between new model and existing models.

3. Publish/View Model

a. Librarian sets permissions and security for model and model elements. b. Architects, Executives, Managers, and Stakeholders view new model. c. Librarian publishes model in the Production Repository d. Consumers access and view content in the repository.

Color Indicates Rochade Component

Engineer ArchitectLibrarian Stakeholder Executive Manager Consumer

Completes Model

Validates Model

Approves Version

Exports Model Loads Model

Integrates Model

Check Out& Update

Integrate

Sets Security & Permissions Accesses Repository Artifacts

Request Change to Repository Artifacts & ModelsPerforms Impact

Analysis

Identifies Model(s) to be Updated

Exports Model(s)

Loads & Updates Model(s)

Validates Changes

Publish& View

Check In

Loads & Updates and/or

Develops Components

Interface Manager Portal Modeling Tool SW Engineering Tool

Views Models

Views Models

Publishes to Warehouse

Color Indicates Rochade Component


Completes Model

Validates Model

Approves Version


Integrates Model

Check Out& Update

Integrate



Analysis


Exports Model(s)


Validates Changes

Publish& View

Check In


Develops Components


Views Models

Views Models



Completes Model

Validates Model

Approves Version


Integrates Model

Check Out& Update

Integrate



Analysis


Exports Model(s)


Validates Changes

Publish& View

Check In


Develops Components


Views Models

Views Models



15

4. Check-out and Update Model(s)

a. Stakeholder recommends/requests change to artifact. b. Architect performs impact analysis and identifies model(s) needing updates. c. Librarian exports model(s) to staging area. d. Architect loads model(s) into appropriate modeling tools. e. Architect makes updates to model(s). f. Stakeholders validate and verify the changes. g. Architect exports the changes to a Repository staging area. h. EA Librarian loads the staged changes into the repository i. Perform steps 2 & 3 to integrate and publish the changes.

6. Rochade EAE Support Roles In common with many large applications, there are a number of roles to be fulfilled to support a Rochade Enterprise Architecture Environment:

Installation and administration are tasks requiring only a low level of resource, and no unusual technical skills. Model Development is a potentially complex task, but the complexity is inherent in the application, not the Rochade software. The user interface allows the definition of a model to be a simple task, once design is complete. Programming and configuration effort can range from light, to major. An enterprise repository can support a wide range of applications, and offer many opportunities for customization. It is characteristic of Rochade’s openness that it allows interfaces with almost any other technology. The more sophisticated the delivered application, the more effort involved – but Rochade provides a fully supportive environment. Consumer access to metadata can be essentially intuitive. Customization of the Rochade Portal technology allows all end user access to be in a question and answer / drill down style that eliminates the need to know about metamodels, the concept of metadata or any related technical complexities.

7. Rochade EAE – “An Industrial-Strength, High-Powered Solution” Rochade has been in existence for more than 20 years. The current generation was developed in 1992. Updates to the core product are made every 6-12 months. The most recent release (Rochade 6.2) was delivered to the market in June of 2003. Rochade EAE capabilities are summarized below.

Rochade is ideally suited for integrating diverse tools, repositories and data stores feeding an Enterprise Architecture Environment. All artifacts are managed in a cohesive repository that helps ensure the integrity and consistency.

Rochade is unique in its ability to support any data type and relate anything-to-anything. This is particularly important in an Enterprise Architecture Environment where there are a lot of relationships between objects that need to be understood from a variety of perspectives. Rochade’s network database design enables complex relationships to be defined, managed and reported with high efficiency and performance.

As the enterprise and architecture artifacts continuously go through change, clients are able to use Rochade to very quickly understand the impact of change as it potentially ripples through the Enterprise Architecture Environment. This allows for the Enterprise Architecture Environment to be easily maintained given the integrated, single point of understanding that spans the enterprise. For example,


16

when changes to EA objects are requested/recommended, architects can perform impact analysis of Repository contents to determine the scope of the change. Then they can send automatically generated messages to the “owners” or stewards of the potentially impacted objects.

Rochade is further unique in its ability to support business/technical user understanding across the enterprise by providing a customizable abstraction layer on top of the repository they can use to find information using the business/technical context they are familiar. Users never need to know they are interfacing with a repository, which not only empowers these users, but also removes some support burden from the IT staff. It’s not uncommon for Rochade customers to have thousands of business users interfacing with the product.

Rochade’s web-based interface supports full role/permission-based read and write access to the repository opening up many options for updates and other work to be easily accomplished from anywhere a web browser exists.

Business reports are a key element of an environment, and Rochade’s user interface has been built to support business as well as technical users. It supports the setting of a preference allowing business users to see business definitions and technical users to see technical definitions of the same item. This means that the understanding of definitions, relationships, audit trails, etc. can be exploited by the whole organization, rather than just IT.

Rochade also has all the capabilities to create and publish scorecards or metrics. As an example, our customers in the healthcare area use Rochade to provide standard quality metrics to address internal and external performance measures reporting as required by the National Committee of Quality Assurance (NCQA). The Health Plan Employers Data and Information Set, (HEDIS®), is designed to help employers evaluate and compare health plans and related offerings through a set of predefined performance measures addressing the quality of care; member access and satisfaction; membership and utilization; and related information for healthcare providers and/or insurers. The extensibility of the Rochade platform provides an excellent environment for managing these types of measures.

A Rochade EA Environment can support any management processes and can be integrated with any systems a client may implement to automate the processes. A Rochade-Powered Enterprise Architecture Environment is the single most critical technology that allows an enterprise to improve both their architecting process and their architecture content. A Rochade-Powered EA Environment allows an enterprise to develop, manage and get the most value from a “world class” EA that has the following characteristics:

Viable Meets mission goals, is actionable and adaptable. Also scaleable and extensible.

Integrated Links primitive architecture artifacts, vertically and horizontally, within a single framework.

Interoperable Allows multiple architectures, with different frameworks, to collaborate. Even geographically and hierarchically separated “federated” architectures

Consistent & Coherent

Artifacts and models reflect a single methodology. Complex models and work products produced from single set of primitive artifacts.

Engineered Artifacts built and managed using strategically-driven best practices and commercially available “best of breed” tools

Managed Uses metadata-powered repository for tool, artifact, model and work product management


17

Data-Centric Focuses on methodology-neutral architecture “design elements”

Evolutionary Enables and facilitates enterprise change and transformation Successfully accomplishing EA Engineering ultimately requires a coherent, “industrial strength” environment and management processes that make the best use of the environment. Rochade is a non-invasive technology that can be used to craft an environment of collaborative repositories that enable enterprise-wide EA artifact integration and management. The Rochade EAE is "tool agnostic'; i.e., any tools used to create and modify EA artifacts can be seamlessly integrated into the environment. The Rochade EAE facilitates capturing, storing, integrating, managing, and disseminating complex information, including EA artifacts, from multiple sources, internal and external. Consumers are able to see at a glance what artifacts are available, when they were captured/versioned, and how they are related.

ASG realizes that just having a world-class, industrial strength technology is not sufficient to ensure success. The most critical success factor is the EA Engineering processes. Fortunately, a Rochade EAE is capable of supporting and enabling all processes, including:

Program and project management Repository content management. Artifact integration management.

These functions enforce the alignment, traceability, integration and consistency of all content entered into the repository that, in turn, facilitates and enables EA actualization. How do you know when your enterprise is ready for a Rochade-Powered EA Environment? There will be several indicators: You are experiencing capacity/capability problems with EA modeling tools.

o Adding users degrades performance o Adding content degrades performance o Queries take too long o Updates take too long


18

o Difficult or impossible to establish linkages between artifacts o Cannot establish and manage complex artifact relationships o Difficult or impossible to create complex artifacts and deliverables from primitive models

You are using multiple tools to create EA artifacts and have difficulty with:

o Version control and configuration management o Artifact linking and integration o Stakeholder access o Reporting

You need to have a common access point and common “look and feel” for EA access and reporting.

You need to manage your EA across multiple organizations, locations, and/or infrastructures.

You need to manage a “federated” EA to support hierarchical enterprises.

It you are having performance problems with your EA modeling tools, if you are unable to effectively integrate and manage your complex EA, and if you need an EA environment that will meet your needs today and forever, then you are ready for Rochade.

12700 Sunrise Valley Drive, Reston, Virginia 20191, USA

Tel: 703.464.1305 | Fax: 703.464.4905 | Toll Free: 1.800.Rochade Allen Systems Group, Inc. | www.asgfederal.com/rochade | [email protected]

rochade-powered enterprise architecture environment · enables other enterprise metadata management...

Documents