Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

15 May 2019

Participants

Goals

  • Touchpoint some of the activities

Discussion topics

Item

Presenter

Notes

identified, the short list of four or five activities that were happening.

Where do we want to use on the confluence site to just start to store all this stuff?

Do we have a good landing spot for the platform architecture?

If that was originally created by the team, rename that it's a platform architecture

��,

Ken

· Did we decided to parallel track or assign specific owners? Yes

· Identified artifact surgery artifacts that are going on the enumerated list of capabilities, we can draw from the previous the architecture stuff, the scope, purpose and product of the platform, which was though map is functional capability, which has a hard dependency on number two.

.



NOTES

Products of architecture -

...

· Decide if we're going to pivot to working calls.

Action items

  •  HSPC Platform Architecture Activities:
    Nominal Timeline:
    30 May: Project Plan and Public Project Sketch (scope, etc.)
    15 July: Pre-Alpha Work on each artifact; Clarity around direction and approach, but detail incomplete.
    Face-to-Face: Late July (ish)?
    September 13: Alpha Draft Release Candidate
    1 October: Publish to HSPC the Alpha Document
    Workstream 1:
    - Artifact 1: Scope and purpose , and product of HSPC platform (inform interrelationship among projects and products) – (See intro material above) [ Bo ]
    - Artifact 1: Elaborate this into a short document: The products of the architecture?
    - Blueprint for ……
    - Enabler for the creation of a certification platform
    - Reference API specification
    - Visual depiction of the components and the interrelationships of those components – Platform
    5/15: Bo is working on an initial-cut draft document
    Workstream 2:
    - Artifact 2: Enumerated list of capabilities (relate to what is out there in the sandbox, or what is likely to be in short-window. Roadmap?) . Hierarchial [Ken]
    Activities to undertake:
    Workstream 3:
    - Artifact 3: Map between business function (concerns) and capabilities. Crosswalk. (Key use cases enabled?). Systems/services? [ Lorraine ]

Decisions