Difference between revisions of "GC Enterprise Architecture/Standards/Business Architecture"
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
<!-- COLUMN 1 STARTS: --> | <!-- COLUMN 1 STARTS: --> | ||
| − | <span style="font-size: 1.5em;"><b><< | + | <span style="font-size: 1.5em;"><b><<Enterprise Architecture Standard main page</b></span> |
<!-- COLUMN 1 ENDS: --> | <!-- COLUMN 1 ENDS: --> | ||
| Line 37: | Line 37: | ||
<!-- COLUMN 2 STARTS: --> | <!-- COLUMN 2 STARTS: --> | ||
| − | <span style="font-size: 1.5em;"><b> | + | <span style="font-size: 1.5em;"><b>Information Architecture>></b></span> |
<!-- COLUMN 2 ENDS: --> | <!-- COLUMN 2 ENDS: --> | ||
Revision as of 17:09, 6 March 2019
| Home | EA standards | EARB Endorsements | EA Artifacts | Working Groups | GC EARB | Other References |
 |
This page is a work in progress. We welcome your feedback. Please use the discussion page for suggestions and comments. When the page is approved and finalized, we will send it for translation. |
|
<<Enterprise Architecture Standard main page |
Information Architecture>> |
1. Business Architecture
A Business Architecture is where an organization identifies the various services that it suppose to provide externally, as well as the various functions it needs to own to support the service to the external.
In terms of GC Business Enterprise Architecture, this is where the Government of Canada identifies the various departments and the services that it needs to provide to Canadians.
Align to the GC Business Capability model
- Define program services as business capabilities to establish a common vocabulary between business, development, and operation
- Identify capabilities that are common to the GC enterprise and can be shared and reused
- Model business processes using Business Process Management Notation (BPMN) to identify common enterprise processes
Design for Users First and Deliver with Multidisciplinary Teams
- Focus on the needs of users, using agile, iterative, and user-centred methods
- Conform to both accessibility and official languages requirements
- Include all skillsets required for delivery, including for requirements, design, development, and operations
- Work across the entire application lifecycle, from development and testing to deployment and operations
- Ensure quality is considered throughout the Software Development Lifecycle
- Ensure accountability for privacy is clear
- Encourage and adopt Test Driven Development (TDD) to improve the trust between Business and IT
Design Systems to be Measurable and Accountable
- Publish performance expectations for each IT service
- Make an audit trail available for all transactions to ensure accountability and non-repudiation
- Establish business and IT metrics to enable business outcomes
- Apply oversight and lifecycle management to digital investments through governance
