Changes

Jump to navigation Jump to search
no edit summary
Line 368: Line 368:  
|}
 
|}
   −
==== Service Business Diagrams ====
+
==== Segment Diagrams ====
 +
For each main segment (6):
 +
* Segment (Business Process Cooperation) Diagram  (defines the functions/services in that segment)
 +
* Motivation Diagram (links capabilities to drivers/goals/outcomes)
 +
* Capability Planning Diagram (links services to capabilities)
 +
 
 +
==== Service Business Process Cooperation Diagrams ====
 
* Business Process Cooperation Diagrams for priority services in each segment.  To be determined by segment architects and priorities.
 
* Business Process Cooperation Diagrams for priority services in each segment.  To be determined by segment architects and priorities.
 +
* Technology Usage Diagram (FOR that SERVICE only).  Other diagrams will be needed in future for common infrastructure components.
 +
* As necessary, application and technology (detail) diagrams.
   −
==== Capability Planning Diagrams ====
+
==== Motivation Diagrams (strategic) ====
Link SSC Services to capabilities.
+
Motivation analysis - many things that should be done....
* Specifics TBD as service diagrams are initiated.
+
* Strategic drivers/goals/outcomes - analysis
 
+
* TBS Policy drivers/goals/outcomes
==== Motivation Diagrams ====
+
* g ITSG 22  [Jacques?]
Motivation analysis - many things that can be done....
+
* ITSG 33  [Jacques?]
* Create a motivation diagram detailing ITSG 22  [Jacques?]
  −
* Create a motivation diagram detailing ITSG 33  [Jacques?]
   
* ITSP 22.  There's a model (reference model) in the tool now.  How to link to motivation?  [SKA/Jacques]
 
* ITSP 22.  There's a model (reference model) in the tool now.  How to link to motivation?  [SKA/Jacques]
* SSC 3.0
+
* SSC 3.0 - Should be a current priority.
 
  −
==== Link Capabilities to Motivation ====
  −
Tasks forthcoming....
      
==== SSC IT Standards ====
 
==== SSC IT Standards ====
 
Replace the existing spreadsheet of IT Standards.
 
Replace the existing spreadsheet of IT Standards.
 +
* Represent IT Standards as drivers, with goals/outcomes/requirements/constraints.
 
* Determine proper object to use to represent standards in ArchiMate.  (Driver, Goal, Requirement, Constraint?)  [SKA]
 
* Determine proper object to use to represent standards in ArchiMate.  (Driver, Goal, Requirement, Constraint?)  [SKA]
** And determine how to link to motivation (Driver/Goals/Outcome....) [SKA]
+
** Need tool modifications to support (Attributes added to Driver template). [Denise, Steve L., Steve A.]
** Choose an appropriate category to distinguish those objects, e.g.:  "SSC IT Standard"  [SKA]
   
** Add to conventions and content metamodel.  [SKA]
 
** Add to conventions and content metamodel.  [SKA]
* Modify the chosen object to have the attributes needed to support IT Standards (as we did based on the DND standard template).  [Denise/SKA]
   
* Populate the known IT Standards as a catalogue within Qualiware.  [TBD]
 
* Populate the known IT Standards as a catalogue within Qualiware.  [TBD]
 
* Manage the IT Standards henceforth in QW.
 
* Manage the IT Standards henceforth in QW.
Line 408: Line 410:  
* PGoF model?
 
* PGoF model?
 
* Service management framework?  Service approval processes?
 
* Service management framework?  Service approval processes?
 +
* SISD (should be covered under SIS Service - but they need integration help from EA in particular - focus.  Identify inefficiencies/gaps.)
    
==== Bottom-Up - Foundation Technology Service Models ====
 
==== Bottom-Up - Foundation Technology Service Models ====
 
Services down may not always produce all the supporting architecture needed.  May wish to consider a parallel "bottom-up" approach, identifying key areas of infrastructure, drawing from recently prepared RAD functional decompositions to identify reusable and key parts/pieces, e.g.:  Data Center, Inter-building network, DNS, Active Directory, etc....
 
Services down may not always produce all the supporting architecture needed.  May wish to consider a parallel "bottom-up" approach, identifying key areas of infrastructure, drawing from recently prepared RAD functional decompositions to identify reusable and key parts/pieces, e.g.:  Data Center, Inter-building network, DNS, Active Directory, etc....
 +
* Email infrastructure
 +
* Data centers
 +
* Data Center Networks
 +
* Intra-building network/GC WAN
 +
* Networks - Conceptual
 +
* ...

Navigation menu

GCwiki