Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Difference between revisions of "SSC Architecture Catalogs"
Jump to navigation
Jump to search
(Operating System catalog) |
|||
| Line 8: | Line 8: | ||
! Location | ! Location | ||
|- | |- | ||
| − | | Segment | + | |Segment |
|Existing | |Existing | ||
|Business Function type=segment | |Business Function type=segment | ||
|SSC architecture segments | |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 | + | |SSC Service |
|Existing | |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. | |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 | |Foundation Technology Services | ||
| Line 35: | Line 41: | ||
|System Software | |System Software | ||
|List of Operating System with types (specializations) | |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. | ||
| | | | ||
|} | |} | ||
Revision as of 08:48, 19 May 2020
Catalogs are lists of objects/items that are intended for reuse. One should always use an existing object from a catalog when it exists.
| 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. |
