EA4BI is an enterprise architecture framework focused on Business Intelligence (BI)
An integrated set of 8 BI architecture and 3 BI design viewpoints
Facilitates and empowers end-to-end BI modeling
Offers better alignment with enterprise architecture
Provides linkage with other enterprise architecture domains and modeling languages, such as ArchiMate, BPMN, UML, and data modeling
Business and Management also need to be made clear that information is not readily available as raw material, but rather the result of an often-complex production process tailored to the specific environment of the organization.
BI project members quickly face the complexity of gaining the required insights in, and actively managing the overview of, both the problem space and the solution space related to this core process of turning data into information and knowledge.The objective of EA4BI is to offer assistance by expanding the discipline of enterprise architecture modeling to BI. As an enterprise architecture framework and toolkit focused on BI, it facilitates and empowers end-to-end BI modeling, but also provides interfaces with other enterprise architecture domains and modeling languages.
Enterprise Architecture (EA) takes place at a high level in the organizational structure. Strategy and concepts are strongly focused in this discipline, with very limited attention for concrete technology choices and implementation details. In order to support this conceptual level, EA4BI provides the viewpoints of Ross & Weill Core Diagram and Analytical Master Data Management.
Solution Architecture (SA) is deliberately positioned at the center. This discipline translates the enterprise architecture into a time-based project portfolio and facilitates the selection of appropriate technology, thereby allowing for the implementation of the organizational strategy. In order to support this concrete level, EA4BI provides the viewpoints of Five-Layered BI Architecture, Data Vault 2.0 Architecture, Inmon Corporate Information Factory (CIF), and Kimball Data Warehouse Architecture.
Technical Architecture (TA) takes a deep dive into the technology for a given project scope, as such preparing it for detailed design and implementation. In order to support this practical level, EA4BI provides the viewpoints of Technical Reference Architecture (TRA) and Technical Solution Architecture (TSA).Technical Design (TD) enables the linkage of detailed technical design with the previous architectural layers. Where the latter offers guidance and black-box views (still hiding the implementation details), TD offers a white-box view (revealing the implementation details) and actually controls the implementation done by the development team. EA4BI offers the viewpoints of Dimensional Modeling and Data Vault 2.0 Modeling, in order to provide support for both mainstream methodologies. The Extract Transform Load (ETL) viewpoint allows to describe the complexities of data retrieval, data processing and data storage.
The following example overview diagram illustrates the usage of EA4BI across all the layers: the three major perspectives enterprise architecture offers (enterprise, solution, technical) and a fourth one providing linkage to technical design.
EA4BI provides an appropriate set of relationships that offer full traceability between all the elements present on all the viewpoints that are part of the four layers.
Traceability between the three architectural layers is achieved by means of the relationship types composition and realization. Traceability towards the technical design layer is realized by means of a dependency.
EA4BI offers two extensibility features:
The former would manifest itself by creating an EA4BI relationship between an EA4BI element and/or diagram and a non-EA4BI element and/or diagram. The latter would result in an EA4BI element having a non-EA4BI composite diagram depicting the substructure.
The following example diagram illustrates both extensibility features:
As such, both extensibility features can be used to provide linkage to mainstream enterprise modeling languages such as ArchiMate, BPMN, UML, and data modeling. A coordinated application of these features can also result in extending EA4BI with organization-specific and/or industry-specific modeling policies and practices.
I am a senior solution architect and enterprise architect, associated with inno.com (www.inno.com). Since 2006, I have been implementing, teaching, coaching, and realizing projects with Sparx Enterprise Architect for various organizations in Belgium, the Netherlands and Luxemburg. With a specialization and certification in the Microsoft business intelligence (BI) stack since 2008, I have also delivered various BI training courses and realized multiple BI projects. EA4BI combines all my favorite ICT topics –enterprise architecture, modeling, business intelligence and Sparx.https://www.linkedin.com/in/rudi-claes-39a696b
It would be valuable to integrate architecture with Business Intelligence (BI). As architectural diagrams (ArchiMate etc.) are difficult to business people, it would be useful to enable dashboards with easier visualizations within a tool such as one of those BI tools.. ..Or perhaps portals like Prolaborate can integrate architecture and BI..
I have created an architecture framework with Sparx EA that supports holistic, overall development (link below), but even though architecture diagrams are useful when developing new ideas to concepts and services & products, more easier visualizations for different stakeholders are needed..