Line 112: |
Line 112: |
| In the following layer, key aspects of the top level of the GC Business Capability Model are depicted. This takes into consideration the IT plan investment framework and provides a mechanism to identify potentially redundant investments across, opportunities for rationalization, and identification of opportunities for enterprise solutions. | | In the following layer, key aspects of the top level of the GC Business Capability Model are depicted. This takes into consideration the IT plan investment framework and provides a mechanism to identify potentially redundant investments across, opportunities for rationalization, and identification of opportunities for enterprise solutions. |
| | | |
− | Add File:Business Architecture.png | + | == Add image File:Business Architecture.png == |
| [[File:Business Architecture.png|thumb]] | | [[File:Business Architecture.png|thumb]] |
| . | | . |
Line 138: |
Line 138: |
| The next layer projects the idea of a service‑oriented government, with a user‑centred approach to the business of government that puts citizens and their needs as the primary focus of our work, using “tell‑us‑once” service approaches, integrated services across the GC program and service landscape in a way that provides real‑time information to Canadians about their service applications. It is a perspective centred on users and service delivery when considering new IT solutions or modernizing older solutions. It builds on business architecture guidance to design for users first, focusing on the needs of users, using agile, iterative, and user‑centred methods in a whole-of-government context. | | The next layer projects the idea of a service‑oriented government, with a user‑centred approach to the business of government that puts citizens and their needs as the primary focus of our work, using “tell‑us‑once” service approaches, integrated services across the GC program and service landscape in a way that provides real‑time information to Canadians about their service applications. It is a perspective centred on users and service delivery when considering new IT solutions or modernizing older solutions. It builds on business architecture guidance to design for users first, focusing on the needs of users, using agile, iterative, and user‑centred methods in a whole-of-government context. |
| | | |
− | ADD '''[[:File:External_Stakeholders.png]]''' | + | == ADD image '''[[:File:External_Stakeholders.png]]''' == |
| + | Leveraging the concept of harmonization described for external users through Sign‑in Canada, GCPass will enable authentication and authorization to GC Systems for Internal stakeholders. The digital workplace will uniformly enable the work of public servants, building on a standard design. |
| + | |
| + | == ADD image Internal Stakeholders == |
| + | Information architecture is depicted in the following layer. Information architecture 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. |
| + | |
| + | == ADD image Information architecture == |