Etienne Venter is the Enterprise Architect for Woolworths and has over 22 years experience in business & systems analysis and creating and maintaining a practical enterprise architecture.

Etienne has developed a practical system development life cycle methodology based on the Zachman framework for use with the ARIS family of products.

His passion for enterprise architecture lies in the ability to make it practical and workable at enterprise and project levels, and to equip business and system analysts to work in an integrated way to achieve the different project objectives and ultimately the enterprise architecture.

Presentation
A practical system development life cycle methodology (iBAS) based on the Zachman Framework for Enterprise Architecture & ARIS
iBAS [integrated business architecture solution] is a practical utility assisted methodology based on the Zachman Enterprise Architecture Framework that facilitates a integrated project approach on how to get from enterprise strategy to process development to system design by directing, assisting and coordinating the effort of various roles within the enterprise including the strategy team, business analysts, risk managers, system analysts, developers and trainers.

iBAS governs how the ARIS Repository is populated in order to produce always up to date documentation based on pre-defined specification scripts at any step of the life cycle.

The iBAS system development life cycle methodology consists of:
· SIA – Strategy Impact Assessment
· PDR – Project Definition report
· BRS – Business Requirement Specification
· SRS – System Requirement Specification
· AIS – Application Integration Specification.

Row 1: Scope [contextual]
Row 1 primarily addresses the Business Strategy, the supporting initiatives and identifies which L2 processes are impacted by the initiatives. It also sets the context of each L2 process by identifying the key inputs, outputs, supporting mechanisms and aspects that control the execution of L2 processes.

Row 2: Business Model [conceptual]
Row 2 addresses the Project Definition as well as the detail Business Process Requirements per initiative. This ensures that all resources have a common project definition which defines the business processes to be designed. The iBAS scripts are used to generate respectively the PDR [Project Definition Report] as well as the detail BRS [Business Requirement Specifications]. The approach also ensures that although a project approach is followed the enterprise architecture is created and maintained in the process. The
focus is on those key processes that support the strategic objectives
directly as well as on all the related inputs, outputs, supporting mechanisms and controls.

Row 3: System Model [logical]
Row 3 addresses the System Requirements as well as the System to System Integration Requirements required to support the key business processes. This ensures that there is a close fit between the Business Model [Row2] and the System Model [Row3]. The iBAS scripts are used respectively to generate the SRS [System Requirement Specifications] as well as the AIS [Application Integration Specifications].

Summary
iBAS demystifies the complexities of Enterprise Architecture and is a practical approach to creating and maintaining an Enterprise Architecture for use in Business Process management.

return to program