1. VA Internal Use Only 1 Product Architecture Recommendation Briefing Template

2. VA Internal Use Only 2 Presentation Overview The purpose of this briefing is to provide to management an overview of finding and recommendations on the architectural assessment of the product architecture The decision gates for completing this step include Business Governance, Data Governance, Technology Governance, Chief Architect Governance, and Capital Planning Governance. This briefing will describe the summary results of the target business products and services, Architecture decisions, ADS target decisions, and Product Architecture Overview.

3. VA Internal Use Only 3 Current-State Overview

4. Future-State Overview VA Internal Use Only 4 –Capture, integrate and share information from other sources –Identify needs (training, resources, etc.) –Measure performance of programs and their management –Meet reporting requirements –Analyze and prioritize LOB-mandated efforts –Justify requests and expenditures –Manage veterans-oriented service programs The conceptual architecture will give the VA an enhanced ability to:

5. VA Internal Use Only 5 Business Architecture

6. VA Internal Use Only 6 : –Conceptual Business Diagram –Business Process Diagram, showing lines of business covered Business Architecture – Models

7. VA Internal Use Only 7 Data Architecture

8. VA Internal Use Only 8 Functional Requirements

9. VA Internal Use Only 9 Application Architecture <Summarize the dynamic and hierarchical decomposition of the physical resources Summarize the description of the Interface Requirements Summarize security considerations, including authentication, au>thorization, confidentiality, integrity

10. Non-Functional Requirements VA Internal Use Only 10

11. VA Internal Use Only 11 : –Business Services Maturity Matrix points – near-term and long-term –Describe in 2-3 paragraphs how the conceptual architecture meets the service needs Service Oriented Architecture

12. VA Internal Use Only 12 Include Services model illustrations Service Oriented Architecture - Models

13. Technology Architecture VA Internal Use Only 13

14. Technology Architecture - Models VA Internal Use Only 14

15. Security Architecture <Summarize how security architecture interacts with all other constituent architecture domains of SA: Business, Data, Application, and Technology. Briefly describe how the Security Architecture will determine the appropriate user roles, security levels, and procedures. With regards to Data Architecture, briefly describe how the Security Architecture will determine various types of data security. > VA Internal Use Only 15

16. Security Architecture VA Internal Use Only 16

17. VA Internal Use Only 17 Re-use Highlights Highlight what systems (from what organizations) are key for re-use in target services highlighting rationale Highlight what enterprise services (from what organizations) are key for re-use in target services highlighting rationale Highlight what federal services (from what organizations) are key for re-use in target services highlighting rationale (Next slides will discuss Authoritative Data Source Re-use)

18. VA Internal Use Only 18 Major Gaps and Alternative Analysis: Highlight what key Gaps that need extra resolve and (from what organizations) are key for re-use in target services highlighting rationale. Highlight tactical wins in alternative analysis (near-term) along with long- term end-service solutions Architecture (long-term) Include architectural risks that should be considered

19. VA Internal Use Only 19 Major Gaps and Alternative Analysis: (cont.) Cover 1 or 2 from each Architecture domain areas

20. Gap Analysis – Architectural Decisions VA Internal Use Only 20 Capture 2-5 highlights summarizing and noting specific rationale for Architectural Decisions (From the Product Evaluation and Decision Analysis)

21. VA Internal Use Only 21 Governance Input Request In general, each governance team will have a separate focus. Target your conclusion based on who your audience is: –Business Governance (will focus on business services) –Data Governance (will review of data artifacts, ADS, and data services) –Technology Governance (will focus on Support services and enabling services. Feedback will likely focus on closing the gap on service rationale, gap/alternative analysis, and proposing enterprise license re- use opportunities. –Chief Architect Governance (will provide input on all services but likely focused on service re-use and identifying enterprise service opportunities –Capital Planning Governance (will key in on portfolio re-use and new investment needs)