Difference between revisions of "GC Enterprise Architecture/Standards/Business Architecture"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | <!-- NAV --> | ||
| + | {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center" | ||
| + | |- | ||
| + | |- | ||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="6%" | '''[[GC_Enterprise_Architecture|<span style="color: snow">'''Home'''</span>]]''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Government_of_Canada_Architectural_Standards|<span style="color: Snow">'''EA standards'''</span>]]''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="13%" | '''[[Past_Endorsed_Architectural_Decisions|<span style="color: Snow">'''EARB Endorsements'''</span>]] ''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Enterprise_Architecture_Artifacts|<span style="color: Snow">'''EA Artifacts'''</span>]] ''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="12%" | '''[[Architecture_Discussions|<span style="color: Snow">'''Working Groups'''</span>]] ''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[GC EARB|<span style="color: Snow">'''GC EARB'''</span>]] ''' | ||
| + | |||
| + | | style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="9%" | '''[[Monitoring_Architectural_Implementation|<span style="color: Snow">'''Other References'''</span>]] ''' | ||
| + | |||
| + | |} | ||
| + | |||
| + | <!-- NAV end --> | ||
| + | {{Translation to follow}} | ||
| + | |||
This is a definition for GC Business Enterprise Architecture | This is a definition for GC Business Enterprise Architecture | ||
| Line 20: | Line 43: | ||
* Establish business and IT metrics to enable business outcomes | * Establish business and IT metrics to enable business outcomes | ||
* Apply oversight and lifecycle management to digital investments through governance | * Apply oversight and lifecycle management to digital investments through governance | ||
| − | |||
Revision as of 11:37, 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. |
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
