Changes

Jump to navigation Jump to search
Line 57: Line 57:  
<br><br>
 
<br><br>
   −
<h3><span style="font-size: 1.5em;"> 1. Business Architecture</span></h3> <br>
+
<h2><span style="font-size: 1.5em;">Business Architecture</span></h2> <br>
    
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
 
Business Architecture is where an organization identifies the various services that it needs to provide externally, as well as the various functions it owns or needs to own internally to support their services to the public. In the context of GC Enterprise Business Architecture, this is where the Government of Canada identifies the various departments, the services they provide to Canadians and the functions they owns. <br><br>
Line 205: Line 205:       −
<h3><span style="font-size: 1.5em;">2. Information Architecture</span></h3>
+
<h2><span style="font-size: 1.5em;">Information Architecture</span></h2>
    
<!-- COLUMN 1 ENDS: -->
 
<!-- COLUMN 1 ENDS: -->
Line 233: Line 233:  
<h4><b><u>Use and share data openly in an ethical and secure manner</u></b></h4>''Section under development'' (ESP/Bitar)
 
<h4><b><u>Use and share data openly in an ethical and secure manner</u></b></h4>''Section under development'' (ESP/Bitar)
   −
<h3><span style="font-size: 1.5em;">3. Application Architecture</span></h3> <br><br>
+
<h2><span style="font-size: 1.5em;">Application Architecture</span></h2> <br><br>
    
Application Architecture consists of understanding and designing the various applications within a department, how they tie in to the business service supporting the departmental mandate, where they are located in the architecture landscape of the department as well as the GC, how they interact with each other and with their users, the zoning requirements, etc. Application Architecture focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>
 
Application Architecture consists of understanding and designing the various applications within a department, how they tie in to the business service supporting the departmental mandate, where they are located in the architecture landscape of the department as well as the GC, how they interact with each other and with their users, the zoning requirements, etc. Application Architecture focuses less on internal mechanics and specific programming and more on overall design on how data is consumed and created by the system. It views the interactions between applications, databases, middleware to ensure scalability, reliability, availability and manageability. <br><br>
Line 322: Line 322:       −
<h3><span style="font-size: 1.5em;">4. Technology Architecture</span></h3> <br><br>
+
<h2><span style="font-size: 1.5em;">Technology Architecture</span></h2> <br><br>
    
<h4><b>Use Cloud first</b></h4>
 
<h4><b>Use Cloud first</b></h4>
Line 340: Line 340:       −
<h2><span style="font-size: 1.5em;">Security Architecture</span></h2>  
+
<h2><span style="font-size: 1.5em;">Security Architecture</span></h2>Input from Cyber, Sept 23, 2020
    
=== Overview of the GC Enterprise Security Architecture (ESA) Program ===
 
=== Overview of the GC Enterprise Security Architecture (ESA) Program ===

Navigation menu

GCwiki