Changes

GC Enterprise Architecture/Framework (view source)

Revision as of 16:52, 28 August 2019

237 bytes added , 16:52, 28 August 2019

no edit summary

Line 32: Line 32:

| style="border-left: 10px solid #c5d5af; box-shadow: 0 4px 8px 0 rgba(0, 0, 0, 0.2), 0 6px 20px 0 rgba(0, 0, 0, 0.19); color: black; background-color: white; font-size:1.2em;" |

[[GC_Business_Enterprise_Architecture | 1. Business Architecture]]

+

Fulfillment to the needs of the stakeholders to the Government of Canada

+

* Ensure accountability for privacy is clear

+

* Ensure that gender diversity and inclusion is considered as part of an intersectional approach to designing for users. Consult the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices and best practices for gender inclusive language. (Would note here that there are likely other examples of best practices that could be included such as positive space exemplars, but nothing else is springing to mind at the moment!)

+

* Adopt a client-centric view of business delivery through customer journey maps and end-to-end service decomposition (internal (GC) and external (public))

+

Focus on the business outcome and Strategic Alignment to the Department and to the GC

+

* Establish the business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps

+

Horizontal Enablement

+

* Model business processes using departmental chosen standard for business process notation, such as Business Process Modeling Notation (BPMN), to identify common enterprise processes

+

* Encourage and adopt a process (for example: Test Driven Development (TDD)) to improve the trust between Business and IT

+

Align to the [https://gcconnex.gc.ca/file/view/50303099/gcbcm-gcmca-v2-visualmodel-20190617-en-pdf?language=en 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 departmental chosen standard for business process notation, such as Business Process Modeling Notation (BPMN), to identify common enterprise processes

−

* Establish the business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps

* Translate the business strategy into business capability implications using the GC Business Capability Model. Use these to guide investments.

+

Design for Users First and Deliver with Multidisciplinary Teams

Line 46: Line 61:

* Ensure quality and security is underpinning the Software Development Lifecycle

* Total Cost Of Ownership (TCO) should include the cost for design, construction, operation, and maintenance of a system. For example Training, Support, Disaster Recovery, and Retirement Cost

−

* Ensure accountability for privacy is clear

−

* Encourage and adopt a process (for example: Test Driven Development (TDD)) to improve the trust between Business and IT

−

* Ensure that gender diversity and inclusion is considered as part of an intersectional approach to designing for users. Consult the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices and best practices for gender inclusive language. (Would note here that there are likely other examples of best practices that could be included such as positive space exemplars, but nothing else is springing to mind at the moment!)

−

* Adopt a client-centric view of business delivery through customer journey maps and end-to-end service decomposition (internal (GC) and external (public))

Gita.nurlaila

514

edits