Please report any problems to the Shared Tools Team at    Broken Links? Missing Macros? WIKI Retiring Plugins
Child pages
  • EBO Methods and Rationale
Skip to end of metadata
Go to start of metadata

The ethos of an EBO

As is true of any IT object, Enterprise Business Objects are comprised of specific pieces of information and rules that govern the maintenance and presentation of that information. They follow a known lifecycle from instantiation through retirement and may attain differing states through the course of their existence.

This section takes a look at how to describe the important characteristics of an EBO.  It considers the essential and optional data elements, the interfaces the object presents, the changes that it undergoes in its lifecycle, any security considerations, and the relationship to other EBOs.

In order to keep our focus on the truly important and business-meaningful aspects of an EBO, we should give primacy to the business processes with which it interacts -- the information that is shared, the operations that take place, and the security constraints governing those interactions. In addressing these, the rest will follow.

Another important consideration is the system that consumes the information and the channel through which it is made available.  This is addressed in the "realms" discussion above.

  • What is a business-meaningful and unambiguous definition of this EBO?  e.g., what does course mean?
  • In what ways does this EBO interact with, derive from or otherwise depend on  other EBOs?
Business Process scenarios
  • What processes do we need to support now that involve the EBO? 
  • If there were no silos, what processes would we want to support (or do we think we'll be asked to support) that involve the EBO?
  • Who are the authorized actors in each process? How will we authorize, i.e., what will we expect of the requesting entity in order to release the information? 
  • Does the process require a batch or real-time transfer of information?
Life Cycle
  • What business process occasions a new instance of one?
  • What is the authoritative source?
  • What determines its visibility/availability?
  • What are important states to consider?  
  • What systems and business processes may modify it?
  • How is it decommissioned?
  • What data elements are required for it to exist?
  • What data elements are optional but need to be made available to the interfaces?
  • What are the security constraints on any of the data elements?
Current State Analysis
Goal of this work

Identify the Enterprise Business Objects for a given area. Capture the elements (data elements) that make up each EBO along with the security requirements for the elements. Document the existing interfaces and schemas that are used to expose the EBO. Determine the timeliness (freshness) and availability requirements for the EBO. Capture state changes between EBOs.

Current State Analysis Flow Diagram

Note: that there are three different entry points into this flow. Only one is shown (Create a New EBO). The other entry points are from a system point of view and from a business process point of view.