Patrick Murta
Jason Walonoski
Rick Geimer
Dan Chaput
Alex Kontur
Proposed Solutions Template
Background:
- Infrastructure use cases have been in development for the last year. Use Case Tiger Team completed first draft 6-8 weeks ago
- Chief Architects reviewed the use cases and identified core capabilities; also reviewed the regulatory and technical barriers documents
Solution frameworks:
- Each Tiger Team has been assigned at least one core capability
- Trying to ensure uniformity across artifacts created by the Tiger Teams
- Too much of a burden for each Tiger Team to worry about graphics; Dana, Diana, et al will focus on graphics and presentation, Tiger Team should focus on content/narrative
- Diana/Dana prepopulated the template using existing content; any content may be changed by the Tiger Team
- Each proposed solution document should stand on its own (i.e. addresses a specific capability, is cohesive, and can be digested by public audiences)
- Different capabilities/solutions will probably be separate documents, unless a proposed solution encompasses multiple capabilities
- Includes:
- Table of contents
- Intro/background – doesn’t need to change, explains the purpose of the FAST initiative, reference documentation list will be hyperlinked to existing documentation to help orient readers unfamiliar with FAST
- Current state overview – where the Tiger Team describes current state of the ecosystem (including what is working well and barriers)
- Problems to be solved – what the solution attempts to address (from use cases and/or barriers document) at the level of the capability
- Proposed solution overview – includes preferred approach, alternatives (in appendix), and other solutions that were considered but rejected
- Swim lane (sequence diagram) and/or wiring diagrams (framework includes files w/appropriate images)
Draft deliverable by July 15 (first draft of one solution for at least one capability)
- At least one diagram of preferred solution, don’t need to include draft narrative