GC Enterprise Architecture/Standards/Business Architecture
< GC Enterprise Architecture | Standards
Revision as of 11:37, 6 March 2019 by Gita.nurlaila (talk | contribs)
| 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. |
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