Line 24: |
Line 24: |
| | | |
| == Business architecture == | | == Business architecture == |
− | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b> | + | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/BusinessGuide click here for Business Architecture guide] </i></b></br></br> |
| | | |
| 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. |
Line 45: |
Line 45: |
| | | |
| == Information architecture == | | == Information architecture == |
− | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/DataGuide click here for Information/Data Architecture guide] </i></b> | + | <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 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. |
Line 81: |
Line 81: |
| | | |
| == Application architecture == | | == Application architecture == |
− | <b><i>[https://wiki.gccollab.ca/GC_Enterprise_Architecture/Framework/ApplicationGuide click here for Application Architecture guide] </i></b> | + | <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 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. |
Line 107: |
Line 107: |
| | | |
| == Technology architecture == | | == Technology architecture == |
| + | <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 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. |
| | | |