Changes

Jump to navigation Jump to search
m
no edit summary
Line 47: Line 47:  
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b></br></br>
 
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b></br></br>
   −
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 is defined as the management and organization of data for a business. 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 both structured and unstructured 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. How personal information is treated such as its collection, use, sharing (disclosure), and management must respect the requirements of the ''[https://laws-lois.justice.gc.ca/eng/ACTS/P-21/index.html Privacy Act]'' and its related policies.
    
=== Collect data to address the needs of the users and other stakeholders ===
 
=== Collect data to address the needs of the users and other stakeholders ===
Line 83: Line 83:  
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide click here for Application Architecture guide] </i></b></br></br>
 
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide click here for Application Architecture guide] </i></b></br></br>
   −
Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that oriented around business services and based on re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases.
+
Application architecture is defined as the management of software used by a business to solve problems. Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that are oriented towards business services and re‑useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases.
    
=== Use open source solutions hosted in public cloud ===
 
=== Use open source solutions hosted in public cloud ===
Line 108: Line 108:  
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/TechnologyGuide click here for Technology Architecture guide] </i></b></br></br>
 
<b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/TechnologyGuide click here for Technology Architecture guide] </i></b></br></br>
   −
Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages.
+
Technology architecture is defined as the management and organization of technical equipment and devices of a business. Technology architecture is an important enabler of highly available and adaptable solutions that must be aligned with the chosen application architecture. Cloud adoption provides many potential advantages by mitigating the logistical constraints that often negatively impacted legacy solutions hosted “on premises.” However, the application architecture must be able to enable these advantages. Therefore, objectives for cloud solutions must be implemented in a way that supports the application architecture.
    
=== Use cloud first ===
 
=== Use cloud first ===
Line 133: Line 133:     
The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed.
 
The GC Enterprise Security Architecture program is a government‑wide initiative to provide a standardized approach to developing IT security architecture, ensuring that basic security blocks are implemented across the enterprise as the infrastructure is being renewed.
 +
 +
More information regarding GC Enterprise Security Architecture can be found on the [https://www.gcpedia.gc.ca/wiki/GC_ESA_Artifact_Repository GC ESA Artifact Repository]
    
=== Build security into the system life cycle across all architectural layers ===
 
=== Build security into the system life cycle across all architectural layers ===
16

edits

Navigation menu

GCwiki