Centers for Medicare & Medicaid ServiceseXpedited Life Cycle (XLC)

[Insert Project Name]

Preliminary Design Review (PDR)[Insert Date of PDR]

[Insert Clarity ID]

1

In preparation for your project’s Design Reviews, model diagrams with examples of System Architecture, Technology Stack, Security Design, Performance Design, Physical Design, and Multi Data Center Integration can be accessed from the following SharePoint site pages. Since these example diagrams are located on an internal SharePoint site, if you would like to see the example diagrams but don’t have access to the site, please request them from your CMS project manager/project lead. PDF: https://share.cms.gov/office/ois/Services/TRB/TRB%20Samples/TRB%20Sample%20Architectural%20Diagrams.pdfVisio: https://share.cms.gov/office/ois/Services/TRB/TRB%20Samples/TRB%20Sample%20Architectural%20Diagrams.vsd

Template Instructions

This document is a template for the Preliminary Design Review (PDR).

Sections should not be removed from the presentation. If a section is not applicable, please indicate as such and provide an explanation.

Additional slides may be added to convey information that you feel is important to share that is not addressed by this template.

Please ensure that your presentation is Section 508 compliant by following the URL:

http://www.hhs.gov/web/policies/checklistppt.html

DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

2

Template Revision History

DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

Version Date Author Description of Changes

1.0 09/16/2009 K. Maenner, OIS/DITPPA Baseline Version

1.1 01/15/2010 K. Maenner, OIS/DITPPA

1. Removed planned tests from the Test Plan page.

2. Added slides to discuss Project Management.

1.3 06/11/2010 C. Shaunessy, OIS/DITGCorrected Slide 8 (Design Considerations) to correspond to Section 5 of SDD.

1.4 07/14/2011 C. Shaunessy, OIS/DITG Added cost/schedule slide

2.0 04/23/2012 C. Shaunessy, OIS/DITG Reformatted for XLC.

3.0 05/01/2014 C. Shaunessy, OIS/DITGReplaced CMS logo; deleted slide background image. Incorporated changes per CR 13-005 and 14-004.

3.1 08/2014 C. Shaunessy, OIS/DITG

Added/updated Performance Measures slide per CR 14-010. Added Clarity ID to title slide. Added note about new model system architecture diagrams.

3.2 02/2015 S.Potu, OEI/DPPIG Updated CMS logo.

3

Presenters

Presenter’s Name Role

4

See this slide’s notes pages for slide instructions.

High Level Business Concept

[Insert graphic providing a high-level overview of the business process from Section 5 of the Business Case.]

5

Project Information

Business Need[Insert condensed business need and drivers from the Business Case or from the AR presentation]

Goals/Scope/Purpose[Insert condensed goals/scope from the Business Case and the business and functional purpose from the Requirements Document or from the AR presentation]

Stakeholders[Insert stakeholder information from the Business Case or from the AR presentation]

Cloud Services[Are you planning to use cloud services now or in the future?]

6

Proposed System

System Scope[Insert condensed system scope from the High-Level Technical Design.]

High Level Functional Requirements[Insert high level functional requirements from the High Level Technical Design.]

Summary of Changes[Insert condensed summary of changes of the current system from the High-Level Technical Design (if applicable).]

7

AR Findings

[Identify any recommendations and/or findings from the AR and their resolution.]

8

Records Management

[Describe where the system’s data will reside and identify any data exchanges that may occur. Alternatively, you may attach Section 5.1.7 of the project’s Requirements document.]• Inputs: Identify all data (as well as the format of the data—paper, manual input,

electronic data) supplied to the system as well as who/what is supplying the data.• Provide instructions on what happens to the manual/electronic inputs after they

are entered into the master file/database and are verified.• Master Files – Provide a detailed description of the data maintained in the

system/database.• Provide detailed instructions for the retention and disposition of this data (where

will the data be maintained, when will the data be deleted or destroyed).• Outputs: List all reports, data sharing with other Agencies/CMS systems, etc.• Provide instructions for how long the reports are needed for Agency business and

when they should be destroyed/deleted.• Is this system replacing a paper-based records system or an existing electronic

system?  If electronic, has the migration of the legacy data been addressed?

9

Design Considerations

[Summarize the design goals and guidelines, development methods and contingencies, and architectural strategies as described in the System Design Document.]

10

Design Considerations

508 Compliance[If applicable, briefly describe what 508 testing will be done, from Sections

5.4 & 5.5 of the System Design Document?]Performance[If applicable, briefly describe what hardware and software performance

strategies will be implemented, from Sections 3, 4.2.2, & 4.3.2 of the System Design Document?]

Security[If applicable, briefly describe what security features are being

implemented, from Sections 3, 4.2.1 & 4.3.1 of the Systems Design Document?]

[If applicable, briefly describe how are any outstanding High or Moderate findings and/or SEV1 or SEV 2 issues being addressed?]

11

Design Considerations

Technical Reference Architecture (TRA)[If applicable, briefly describe from Section 3 & 4 of the System Design

Document, how the system is TRA compliant and address any non-compliance issues, specifically:– What application code is being reengineered to comply with the

TRA?– What business logic code is being separated from the data access

logic code?– What business logic is being moved from the data tier to the

application tier?– How will the system provide indirect access from the application to

the data tier since direct access is not allowed?]

12

Design Considerations

Shared Services[If applicable, briefly describe from Section 3 & 4 of the System Design

Document…What new shared services will be created?How will any new shared services being developed be consumable by other

projects?What existing shared services will be consumed?]

Non-shared Service Reusable Components[If applicable, briefly describe from Section 3 & 4 of the System Design

Document…What new reusable components will be developed?How can any new reusable components being developed be reused by other

projects?What existing reusable components will be implemented?]

13

Design Considerations

Software Architecture[If applicable, briefly describe from Sections 3, & 4.3 of the System Design

Document…What are the key software design decisions based on the mapping of the

requirements to the prioritized Quality Attributes (aka non-functional requirements)? E.g. If Modifiability is more important than Performance, then it is highly probable that a different solution will be designed.

What is being designed to enhance automation and to ensure that parameters, URIs, URLs, port numbers, and other variables can be changed without recompiling the code and/or restarting the application?

What industry standard software patterns are being implemented in the software architecture to create a repeatable development processes?]

14

Design Considerations

Data Architecture[If applicable, briefly describe from Section 3 & 4.4 of the System Design

Document…What is being done to align with the Enterprise Data Models?What is being done to reduce the amount of data being stored for non-

system of record data?What is being done to use existing system of record data, e.g. Integrated

Data Repository (IDR) data, in a non-persistent or temporary manner?What conformed data entities are being created to support new/existing

functionality?What existing data entities are being conformed to support new/existing

functionality?]

15

Design Considerations

Business Intelligence[If applicable, briefly describe from Section 3 & 4.4 of the System Design

Document…What enterprise data models will be used to support both reports and

dashboards?What methodology will be implemented to ensure no duplication of data or

logic is required to support both reports and dashboards?]

Portal Architecture[If applicable, briefly describe from Section 3 & 4.3 of the System Design

Document…What existing portlets will be consumed?What new portlets will be reusable by other projects?]

16

System Architecture

[Insert the system architecture diagram depicting the overall, integrated structure of the system in terms of presentation, application and data regions including data storage and manipulation, user and external interfaces from the System Design Document.]

17

18

Performance Measurement Area Technology

Technology Component

Measurement Category/ Grouping

Measurement Indicator Target

Benchmark (if applicable)

(See Notes) (See Notes) (See Notes) (See Notes) (See Notes)

Response Data

• Operational / System Environment• System Interconnection / Information Sharing• System Security Level• E-Authentication Level:

See this slide’s notes pages for slide instructions.

19

Test Plan

[Insert the testing approach / strategy from Section 4 of the Test Plan.]

20

Release Plan

[Insert the release content and schedule from Sections 3.3 and 3.4 of the Release Plan.]

21

Data Conversion

[Insert the data conversion scope from Section 5.1 of the Data Conversion Plan.]

22

Project Management Update:Status

[Provide an update on the status of the project.]

23

Project Management Update:Risks & Issues

[Provide an update on the project risks and issues, including the probability of occurrence and the mitigation for each risk.]

24

Project Management Update:Cost & Schedule

• Cost• Schedule

25

See this slide’s notes pages for slide instructions.

Project Management Update:Deliverables Status

[Provide an update on the status of the deliverables required for the project as documented in the Project Process Agreement. Also provide an update on the status of your Information Security Certification & Authorization process.]

26

Centers for Medicare & Medicaid ServiceseXpedited Life Cycle (XLC)

Conclusion of Preliminary Design Reviewfor [insert project name]

27