Welcome to BC3 Analytics.

There are many definitions of Enterprise Architecture, which often leads to confusion in applied applications. To build a common taxonomy, Lapalme categorizes Enterprise Architecture into three domains:  Enterprise IT Architecting, Enterprise Integrating, and Enterprise Ecological Adaptation (Lapalme, 2012, p. 38).

  1. Enterprise IT Architecting: alignment of IT assets to support business unit strategy.
  2. Enterprise Integrating: designing and executing a coherent enterprise strategy across all functional units.
  3. Enterprise Ecological Adaptation: enabling innovation and environmental system adaptation by fostering "bi-directional" operating relationships.

Enterprise Data Architecture (EDA) is a set of methodologies and technologies that govern how the enterprise collects, stores, arranges, and uses data. Successful data architecture initiatives support all of Lapalme's domains. A complete EDA solution integrates multiple data sources into a cohesive platform for analyzing and reporting operational effectiveness. Seemingly, there is no end to the amount of data an organization needs, and when more than one employee needs access to the same information, the errors often multiply.    Effective leadership in Enterprise Data Architecture applications addresses this issue by providing fundamental guidelines and policies governing how the enterprise manages and uses data and information.

There are no one-size-fits-all solutions to EDA problems. Each solution considers the needs of an organization by addressing stakeholders' concerns, including answering questions about strategic objectives, project priorities, and organizational directions.

For more information, please select one of the following practice categories:

Next Steps...

Please ask for more information, or book an appointment.

Source: Lapalme, J. (2012, October 30). Three Schools of Thought on Enterprise Architecture. IEEE Computer Society. Retrieved from http://www2.mitre.org/public/eabok/perspectives_on_ea/