Difference between revisions of "GC Enterprise Architecture/Standards/Business Architecture"

From wiki
Jump to navigation Jump to search
(Created page with "This is a definition for GC Business Enterprise Architecture")
 
Line 1: Line 1:
 
This is a definition for GC Business Enterprise Architecture
 
This is a definition for GC Business Enterprise Architecture
 +
 +
<b>Align to the GC Business Capability model</b>
 +
* 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
 +
 +
<b>Design for Users First and Deliver with Multidisciplinary Teams</b>
 +
* 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
 +
 +
<b>Design Systems to be Measurable and Accountable</b>
 +
* 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
 +
|}

Revision as of 12:32, 6 March 2019

This is a definition for GC Business Enterprise Architecture

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

|}