Difference between revisions of "SSC Architecture Catalogs"

From wiki
Jump to navigation Jump to search
(Replaced content with "{{Delete|reason=Expired content.}}")
Tag: Replaced
 
(12 intermediate revisions by one other user not shown)
Line 1: Line 1:
Catalogs are lists of objects/items that are intended for reuse.  One should always use an existing object from a catalog when it exists.
+
{{Delete|reason=Expired content.}}
{| class="wikitable"
 
|-
 
!Catalog
 
!Status
 
!Element
 
! Description
 
! Location
 
|-
 
|Segment
 
|Existing
 
|Business Function type=segment
 
|SSC architecture segments
 
|BusinessProcessCoopViewpoint: APPROVED Strategic: Segments
 
|-
 
|Business Capability
 
|Existing
 
|Capability
 
|A list of business capabilities - which are to be realized/supported by various architectures.
 
|CapabilityMapViewpoint
 
|-
 
|SSC Service
 
|Existing
 
|Business Function type=SSC Service|| SSC Services - as described in the official SSC Service Inventory.  Represented in QualiWare as functions with a special attribute.
 
|BusinessProcessCoopViewpoint: APPROVED Service Inventory
 
|-
 
|Foundation Technology Services
 
|Existing
 
|Technology Service
 
|List of level 1 and 2 technologies as determined by convention by EA
 
|
 
|-
 
|Actors
 
|Proposed
 
|Business Actor
 
|List of official actors - named persons or groups
 
|
 
|-
 
|Operating Systems
 
|Proposed
 
|System Software
 
|List of Operating System with types (specializations)
 
|
 
|-
 
|Projects
 
|Proposed
 
|Work Package
 
|List of SSC Projects and initiatives.  Work package = project or initiative.
 
|
 
|-
 
|Gaps
 
|Proposed
 
|Gap
 
|List of identified strategic architectural gaps - intended to be filled by projects
 
|
 
|-
 
|Goals/Outcomes
 
|Proposed
 
|Goal/Outcome
 
|List of identified strategic goals and outcomes - every project must connect to at least one.
 
|
 
|}
 

Latest revision as of 09:40, 28 October 2024