Enterprise Business Objects are technology neutral descriptions of the information (data) needed to support a given business process or set of business processes. This document is to gather information about Enterprise Business Objects. Note: there is a new EBO Repository in the wiki here Enterprise Business Object Repository
Related Label: arch_ebo
Of Note: An Enterprise Business Object is not the same as the physical data model for the source system. The EBO definition should not be impacted by upgrades to systems. An EBO definition may point out gaps in the enterprise e.g. data where there is no enterprise source for the data element(s).
The data represented in the EBO is understandable and usable in its delivered form. In general, it does not require conversion from a "machine meaningful form" into a "human readable form".
An EBO should be a complete answer to a business data need regardless of source or gaps in the data.
EBOs and Architectural Realms
See EBOs and Architecture Realms for the full analysis.
Current EBOs and EBOs under development
Instructor EBO Charter (DoIT - Architecture) — The development of Instructor EBOs is important for both Course Guide as well as for the Digital Measures project. This charter is to define the EBOs needed from the Course Guide viewpoint specifically. They include both Instructor (information about the instructor him/herself) as well as Instruction (information about how the instructor teaches in general or specifically for a given course or set of courses.
The successful completion of this work will include a set of EBOs for both the Instructor and Instruction information, identification of gaps in the information and a listing of sample user scenarios for this information. Out of scope for this work though in scope for a parallel effort is the mapping to the Application Business Objects for the Course Guide and development of functional requirements from the Course Guide perspective.