Changes

GC Enterprise Architecture/Framework (view source)

Revision as of 10:44, 12 August 2019

233 bytes added , 10:44, 12 August 2019

* Add OSS Items

Line 36: Line 36:

* 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

−

* Establish the business architecture early, focusing on business services and capabilities to eliminate technological constraints from transformation designs and roadmaps</u~~></I~~>

+

* 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.</u~~></I~~>

+

* 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 45: Line 45:

* Work across the entire application lifecycle, from development and testing to deployment and operations

* 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</I~~></u~~>

+

* 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)) </u~~></I~~>

+

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

Design Systems to be Measurable and Accountable

−

* Publish performance expectations for each ~~~~business service and supporting application and technology service(s)~~~~

+

* Publish performance expectations for each business service and supporting application and technology service(s)

* Make an audit trail available for all transactions to ensure accountability and non-repudiation

* Establish business and IT metrics to enable business outcomes

Line 68: Line 68:

* Ensure data is collected in a manner that maximizes use and availability of data

* Ensure data collected aligns to existing enterprise and international standards

−

* Ensure that gender diversity and inclusion is considered according to the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices. The government is moving toward defaulting to gender, sex by exception, and adding a third gender option in a respectful and inclusive manner. This involves making changes in the front end (collection) and the back end (coding, display). For collecting information, the recommended approach is to offer the options “male”, “female” or the third option of “another gender”. If there is a need for more specificity and the capacity for analysis, add a write in option labelled “Please Specify”. </I~~></u~~>

+

* Ensure that gender diversity and inclusion is considered according to the Policy Direction to Modernize the Government of Canada’s Sex and Gender Information Practices. The government is moving toward defaulting to gender, sex by exception, and adding a third gender option in a respectful and inclusive manner. This involves making changes in the front end (collection) and the back end (coding, display). For collecting information, the recommended approach is to offer the options “male”, “female” or the third option of “another gender”. If there is a need for more specificity and the capacity for analysis, add a write in option labelled “Please Specify”.

* Where enterprise or international standards don't exist, develop Standards in the open with key subject matter experts

* Ensure collection of data yields high quality data as per data quality guidelines

Line 77: Line 77:

Data Management

−

* Demonstrate alignment with enterprise and departmental data governance, strategies, and reference models</I~~></u~~>

+

* Demonstrate alignment with enterprise and departmental data governance, strategies, and reference models

* Ensure accountability for data roles and responsibilities

* Design to maximize data use and availability

Line 105: Line 105:

Use Open Standards and Solutions by Default

* Where possible, use open source standards, and open source software first

+

* ''When using Open Source remain at the latest and greatest version''

+

* ''Ensure any extension or change to the Open Source item is contributed back to the community''

* If an open source option is not available or does not meet user needs, favour platform-agnostic COTS over proprietary COTS, avoiding technology dependency, allowing for substitutability and interoperability

* If a custom-built application is the appropriate option, by default any source code written by the government must be released in an open format via Government of Canada website and services designated by the Treasury Board of Canada Secretariat

* All open source code must be released under an appropriate open source software license

+

* ''Ensure valid license and legal requirements are met for use of Open Source items''

* Expose public data to implement Open Data and Open Information initiatives

Maximize Reuse

−

* Reduce integration Complexity - design systems to be highly modular and loosely coupled to be able to reuse components. </I~~></u~~>

+

* Reduce integration Complexity - design systems to be highly modular and loosely coupled to be able to reuse components.

* Leverage and reuse existing solutions, components, and processes

* Select enterprise and cluster solutions over department-specific solutions

Vivian.nobrega

101

edits