Difference between revisions of "Models/Work to Do - SSC EA Team"
Jump to navigation
Jump to search
m |
|||
| Line 2: | Line 2: | ||
{| class="wikitable" | {| class="wikitable" | ||
|+ | |+ | ||
| − | ! | + | !Item |
| − | ! | + | !Accountable |
| − | ! | + | !Responsible |
| − | ! | + | !Status |
|- | |- | ||
|Connectivity Segment Diagram | |Connectivity Segment Diagram | ||
| | | | ||
| − | | | + | |Melisssa |
| − | | | + | |Completed |
|- | |- | ||
|Hosting Segment Diagram | |Hosting Segment Diagram | ||
| | | | ||
| − | | | + | |Craig Bradley |
| | | | ||
|- | |- | ||
| Line 29: | Line 29: | ||
|Platform Segment Diagram | |Platform Segment Diagram | ||
| | | | ||
| − | | | + | |Craig Hill |
| | | | ||
|- | |- | ||
| Line 37: | Line 37: | ||
| | | | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==== Service Business Diagrams ==== | ==== Service Business Diagrams ==== | ||
Revision as of 13:20, 1 October 2019
Segment and SSC Service Diagrams
| Item | Accountable | Responsible | Status |
|---|---|---|---|
| Connectivity Segment Diagram | Melisssa | Completed | |
| Hosting Segment Diagram | Craig Bradley | ||
| Security Segment Diagram | |||
| Procurement Management Segment Diagram | |||
| Platform Segment Diagram | Craig Hill | ||
| Internal Support and Management Segment Diagram |
Service Business Diagrams
- Business Process Cooperation Diagrams for priority services in each segment. To be determined by segment architects and priorities.
Capability Planning Diagrams
Link SSC Services to capabilities.
- Specifics TBD as service diagrams are initiated.
Motivation Diagrams
Motivation analysis - many things that can be done....
- 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]
- SSC 3.0
Link Capabilities to Motivation
Tasks forthcoming....
SSC IT Standards
Replace the existing spreadsheet of IT Standards.
- 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]
- Choose an appropriate category to distinguish those objects, e.g.: "SSC IT Standard" [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]
- Manage the IT Standards henceforth in QW.
Applications
- Choose a category to associate with "high-level" applications that we want to report upon/track/list. [SKA]
- Add to conventions/metamodel. [SKA]
- Apply the category to existing applications in the system (Qualiware, GCDocs, BITS).
- Prepare a demonstrative Matrix to display them [SKA]
Internal Management Models
- BITS application architecture?
- EBIDM/Business Intake... many process documents available. It's not an SSC service, but it should be.
- Application management/reporting. CIO? What's in this report? What is that report called? What do we need to report on? Ask JOHN B.
- Review and refine the EA process models.
- PGoF model?
- Service management framework? Service approval processes?
