Welcome to the Home Page of the Enterprise Business Architecture web site. The information provided in this web site defines the Enterprise Business Architecture (EBA), explains its purpose and provides an example of the approach using a case study Just click on the menu options above and the three icons below for additional sources of information about the EBA.

Definition: The Enterprise Business Architecture defines the enterprise value streams, their relationships to all external entities and other enterprise value streams, and the events that trigger instantiation. It is a definition of what the enterprise must produce to satisfy its customers, compete in a market, deal with its suppliers, sustain operations and care for its employees. It is composed of architectures, workflows and events.

Purpose: The Enterprise Business Architecture defines the formal link between the enterprise business strategy and the results predicted from supporting strategic initiatives. The EBA provides a single source and comprehensive repository of knowledge from which corporate initiatives will evolve and link. The evolution occurs from a fully integrated enterprise model of the business to all IT, organizational, and security architectures. The EBA also provides integration capabilities for software development, packaged software configuration, and process improvement initiatives.

By using the EBA, enterprises can formally engineer solutions that directly link to the desired results defined by the enterprise strategy. These are not “seat of the pants” type business projects, but rather “business by design.”

Executive profiles – A company is only as strong as its executive leadership. This is a good place to show off who’s occupying the corner offices. Write a nice bio about each executive that includes what they do, how long they’ve been at it, and what got them to where they are.