|
|
| (4 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
| |
| − | |LayeredViewpoint: (WIP)Strategic: Foundation Technology Services
| |
| − | |-
| |
| − | |Actors
| |
| − | |Started
| |
| − | |Business Actor
| |
| − | |List of official actors - named persons or groups
| |
| − | |CatalogueDiagram:SSC
| |
| − | |-
| |
| − | |Operating Systems
| |
| − | |Existing
| |
| − | |System Software
| |
| − | |List of Operating System with types (specializations)
| |
| − | |CatalogueDiagram:SSC
| |
| − | |-
| |
| − | |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.
| |
| − | |
| |
| − | |-
| |
| − | |SSC Architecture Principles
| |
| − | |Proposed
| |
| − | |Principle
| |
| − | |List of architecture principles - used in EA assessments, and as requirements for every SSC project/initiative.
| |
| − | |
| |
| − | |-
| |
| − | |Standards
| |
| − | |Proposed
| |
| − | |Sub-type of Principle?
| |
| − | |List of SSC IT Standards. A subset/subtype of principles.
| |
| − | |
| |
| − | |-
| |
| − | |Driver
| |
| − | |Proposed
| |
| − | |Driver
| |
| − | |List of SSC Drivers, which may include legislation, policy, directives, strategies, standards, IT standards, and any other motivations for the organization.
| |
| − | |
| |
| − | |-
| |
| − | |Roles
| |
| − | |Proposed
| |
| − | |Role
| |
| − | |Standardized list of roles and types of roles in the enterprise.
| |
| − | |
| |
| − | |-
| |
| − | |Databases
| |
| − | |Started
| |
| − | |System Software
| |
| − | |List of databases, database software and types.
| |
| − | |
| |
| − | |-
| |
| − | |Storage
| |
| − | |Started
| |
| − | |TBD
| |
| − | |List of storage, storage types.
| |
| − | |
| |
| − | |}
| |
