263
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: − − <!-- Table start --> − {| − {|class="wikitable sortable" style="width:100%;" − |+ class="nowrap" | <div style="font-size: 1.2em; text-align: left;">Business Capability Model</div> − |- − |width=100%| The [[GC Enterprise Architecture/Business Capability Model| <b>GC BCM v2.1</b>]] is laid out with associated descriptions. Please note that proposed updates are flagged and considered under construction. A request to GC EARB will be made to endorse the formal adoption of updates to the model. − |- − |} − <!-- Table end --> Line 54:
Line 44: + + + + + + + + + +
GC Enterprise Architecture/Framework (view source)
Revision as of 13:26, 15 February 2021
, 13:26, 15 February 2021no edit summary
== Business architecture ==
== Business architecture ==
Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus.
Business architecture is a critical aspect for the successful implementation of the GC Enterprise Ecosystem Target Architecture. The architectural strategy advocates whole‑of‑government approach where IT is aligned to business services and solutions are based on re‑useable components implementing business capabilities in order to deliver a cohesive user experience. As such, it is essential that business services, stakeholder needs, opportunities to improve cohesion and opportunities for reuse across government be clearly understood. In the past these elements have not been a priority. It is expected that the IT culture and practices will have to change to make business architecture, in general, and these elements a primary focus.
=== Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs ===
=== Design services digitally from end‑to‑end to meet the Government of Canada users and other stakeholders’ needs ===
== Information architecture ==
== Information architecture ==
Information architecture includes both structured and unstructured data. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data and information as the collection, use, sharing (disclosure), and management of personal information must respect the requirements of the ''Privacy Act'' and its related policies.
Information architecture includes both structured and unstructured data. The best practices and principles aim to support the needs of a business service and business capability orientation. To facilitate effective sharing of data and information across government, information architectures should be designed to reflect a consistent approach to data, such as the adoption of federal and international standards. Information architecture should also reflect responsible data management, information management and governance practices, including the source, quality, interoperability, and associated legal and policy obligations related to the data assets. Information architectures should also distinguish between personal and non‑personal data and information as the collection, use, sharing (disclosure), and management of personal information must respect the requirements of the ''Privacy Act'' and its related policies.
<!-- Table start -->
{|
{|class="wikitable sortable" style="width:100%;"
|+ class="nowrap" | <div style="font-size: 1.2em; text-align: left;">Business Capability Model</div>
|-
|width=100%| The [[GC Enterprise Architecture/Business Capability Model| <b>GC BCM v2.1</b>]] is laid out with associated descriptions. Please note that proposed updates are flagged and considered under construction. A request to GC EARB will be made to endorse the formal adoption of updates to the model.
|-
|}
<!-- Table end -->
=== Collect data to address the needs of the users and other stakeholders ===
=== Collect data to address the needs of the users and other stakeholders ===
