Skip Headers
Oracle® Fusion Middleware Quick Start Guide for Oracle Enterprise Repository
11g Release 1 (11.1.1.4.0)

Part Number E16581-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Identify Stakeholders

The fourth step in getting started with Governance is to identify initial Governance stakeholders.

This chapter contains the following sections:

4.1 Overview

Now that you've identified the assets that should be governed, it's time to work with the stakeholders to:

Figure 4-1 Closed Loop Governance Process

Description of Figure 4-1 follows
Description of "Figure 4-1 Closed Loop Governance Process"

Figure 4-1 provides an overview of some of the stakeholders that participate in the closed loop governance process. This process is supported by the governance infrastructure.

The following description of common stakeholders in the closed-loop governance process, and the typical Roles assigned to them in the Oracle Enterprise Repository.

4.2 Stakeholders

This section describes the various Oracle Enterprise Repository solution packs available:

4.2.1 Service Competency Center/ Software Factory/ Portfolio Management Team

Role in Governance

  • Identify common needs across the community.

  • Identify assets and levels of investment needed to fulfill those needs.

  • Determine the expected return on asset investments.

  • Manage the asset lifecycle, from initial inception, creation, distribution, usage all the way through to retirement.

  • Define common functionality in the Enterprise Repository.

    • Create an asset in Oracle Enterprise Repository

    • Populate definitional metadata

    • Attach relevant documentation

    • Identify a target availability date

  • Establish Governance workflows for their portfolio of assets

    For more information about workflows, see "Configuring Oracle Enterprise Repository Workflow" in Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository.

  • Participate in the Governance approval process for assets in their portfolio.

  • Evaluate the performance of their assets by reviewing usage history, developer feedback, runtime performance metrics, policy status, and compliance reports.

  • Use the Oracle Enterprise Repository Navigator to evaluate the impact should they change or modify their assets

  • Create new versions of existing assets, and retire old versions.

Typical Roles Assigned in Oracle Enterprise Repository

Registrar

4.2.2 Business Analysts

Role in Governance

  • Specify global business requirements

  • Reuse existing business processes

  • Structure new business processes using existing capabilities and services

  • Drive revenue by extending business processes to trading partners

Typical Roles Assigned in Oracle Enterprise Repository

Advanced Submitter

4.2.3 Project Architects

Role in Governance

  • Analyze and search software assets to design a project architecture that maximizes appropriate reuse (SLA for services, maturity of components, design document

  • Create and use applications, services and component versions

  • Notify stakeholders of changes to applications, services and components

Typical Roles Assigned in Oracle Enterprise Repository

Advanced Submitter

4.2.4 Developers (as Consumers)

Role in Governance

  • Analyze and search software assets for specific reuse (features, dependencies, how to guides, test harness)

  • Use applications, services and component versions

  • Notify stakeholders of changes to applications, services and components

  • Use reusable assets in the creation of other assets

  • Search repository for suitable reusable assets for projects

  • Integrate reusable assets, with additional responsibility for engineering or modifications made necessary by the integration

Typical Roles Assigned in Oracle Enterprise Repository

User

4.2.5 Developers (as Producers/Harvesters)

Role in Governance

  • Creates reusable assets from scratch and/or reengineers existing assets to be reusable

  • May be responsible for testing assets and ensuring quality standards are met

  • May be responsible for maintaining assets and helping users understand asset functionality, features, limitations, and applicability

Typical Roles Assigned in Oracle Enterprise Repository

Advanced Submitter

4.2.6 Registrars

Role in Governance

  • Assess, certify, classify, add, and delete assets from the repository

  • May be responsible for maintaining the operational aspects of the repository

  • Ensures that work products meet quality, documentation, and other established standards.

  • May communicate new work product additions or deletions to all constituents.

  • Match consumer engineer needs with producer engineer capabilities and availability.

Typical Roles Assigned in Oracle Enterprise Repository

Registrar

4.2.7 Enterprise Architects

Role in Governance

  • Track progress toward the target architecture

  • Communicate progress to the executives

  • Communicate architectural standards to delivery teams

  • Monitor compliance.

Typical Roles Assigned in Oracle Enterprise Repository

Registrar

4.2.8 Program Manager

Role in Governance

Coordinates planning, prioritization, monitoring, and support of the governance program, while aligning it with changing business needs.

  • Facilitates the definition of the program objectives

  • Oversee all aspects of the enterprise initiative.

  • Establish consensus and promote the program goals and objectives, including schedules, budget, key milestones, and deliverables.

  • Co-develop, review, and integrate the supporting project plans.

  • Development of communication plans, risk management plans, and skill gap analysis.

  • Provide regular updates to senior management, customer representatives and program participants.

  • Establish metrics and reporting requirements.

Typical Roles Assigned in Oracle Enterprise Repository

Registrar Administrator

4.2.9 CIO

Role in Governance

Analyze and search reuse and the contributions of applications, components, services by LOB, product, value chain

Typical Roles Assigned in Oracle Enterprise Repository

User

4.2.10 Executive Sponsor

Role in Governance

An individual or group representing management and its interests

  • Authorizes, encourages and supports the use of resources

  • Provides visibility that management supports the program

Typical Roles Assigned in Oracle Enterprise Repository

User

4.2.11 Governance Champion

Role in Governance

  • Program support and evangelism throughout every level of the organization

  • Educates others on the program concepts, its long-term benefits, its inhibitors, and the motivation behind its implementation

  • Sets direction for the effort and implementation

  • Communicates successful efforts throughout the organization

Typical Roles Assigned in Oracle Enterprise Repository

User