586
edits
Changes
Jump to navigation
Jump to search
Line 36:
Line 36: − + Line 54:
Line 54: − + Line 72:
Line 72: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
GC Enterprise Architecture/Enterprise Solutions (view source)
Revision as of 14:26, 24 September 2020
, 14:26, 24 September 2020→Decision Making Framework for Enterprise Solutions
!Illustration
!Illustration
|-
|-
|Centralization
|Centralizated
|Reusable assets are standardized to the entire GC in a consolidated manner, governed by a centralized authority and can also be provisioned by a single service provider , and is fully integrated across all instances. It maximizes utility of major investments which address common business needs, have Enterprise-wide scope, long durations, and require participation from all departments and agencies
|Reusable assets are standardized to the entire GC in a consolidated manner, governed by a centralized authority and can also be provisioned by a single service provider , and is fully integrated across all instances. It maximizes utility of major investments which address common business needs, have Enterprise-wide scope, long durations, and require participation from all departments and agencies
Example: SSC Secure Cloud Enablement and Defense (SCED), desktop standards, data standards
Example: SSC Secure Cloud Enablement and Defense (SCED), desktop standards, data standards
|
|
|-
|-
|Interoperability
|Interoperable
|Reusable assets are developed by departments using standards and published for provisioning by others. This stand alone, or decentralized option allows departments to implement their own unique assets but publish and consume APIs and Open Source software centrally led guidance and standards.
|Reusable assets are developed by departments using standards and published for provisioning by others. This stand alone, or decentralized option allows departments to implement their own unique assets but publish and consume APIs and Open Source software centrally led guidance and standards.
Examples: IBM Curam (BDM – Public Cloud-hosted Containterized microservices exposed as APIs)
Examples: IBM Curam (BDM – Public Cloud-hosted Containterized microservices exposed as APIs)
Cons: Does not easily allow for reuse. Encourages niche skills not portable across the GC
Cons: Does not easily allow for reuse. Encourages niche skills not portable across the GC
|
|}
== Registry of GC reusable assets ==
{| class="wikitable"
|+Proposed model for registry
!Classification
!
!Business capabilities addressed
!User Journeys addressed
!Source of assett
|-
|Centralizated
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Distributed
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Interoperable
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|-
|Departmental
|
|
|
|
|-
|
|asset name
|
|
|
|-
|
|asset name
|
|
|
|
|}
|}
