Business Architecture Provides a Disciplined Approached to Business Change
Today more than ever businesses are asked to embrace change. Transforming your business requires looking at things differently than you do now.

There is an approach being used at all levels of government, a standard in the province of Ontario, at the municipal level and a developing standard in the GoC and nationally, that helps to bridge the gaps between the business areas and Information Technology Management, optimize programs, services and processes and maximize your IT investment management and infrastructure. This approach is an industry standard known as business architecture.

What is Business Architecture?
 Business architecture is a knowledge base that catalogs and describes the work performed to realize an Enterprise or Business’ strategic objectives!

A Business Architecture will provide a common contextual and conceptual view of

•
 A business Architecture is developed by bringing business subject matter expertise and existing documentation together through Business Architecture practitioners

•

Business Architecture is represented using government-standard set of methods and models

Business Architecture Value

•

 Assure a clear, comprehensive and accurate record of how the business works through government-standard methodology and models
•
 Establish a common language to describe the business that will facilitate communication between business and IT stakeholders
•

Provide, through an "As-Is" Business Architecture, a baseline framework of current business that will support and facilitate:
  • Alignment of the program and its services with government priorities
  • Alignment of I&IT solutions with the program’s business goals and objectives
  • Clarification of organization roles, responsibilities and relationships
  • Identification of business operation change opportunities (e.g., more effective application of business policy rules)
  • Identification of I&IT gaps and / or opportunities for enhancement
  • Creation of specifications for business information and process automation requirements
  • A fuller, more inclusive response to program change due to a greater understanding of linkages and impacts across the business (e.g., policy change impacts)
  • Business transformation design (i.e., to simplify and streamline the program) and the development of a “To-Be” Business Architecture