[insert project name] detailed design review (ddr) [insert date of ddr] centers for medicare &...

[Insert Project Name]

Detailed Design Review (DDR)[Insert Date of DDR]

Centers for Medicare & Medicaid ServiceseXpedited Life Cycle (XLC)

[Project Name] - DDR

Template Instructions

This document is a template for the Detailed Design Review (DDR).

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

[Project Name] - DDR

Template Revision History

DELETE THIS SLIDE BEFORE FINALIZING YOUR PRESENTATION

Version Date Author Description of Changes

1.0 02/2010 K. Maenner, OIS/DITPPA Baseline Version

1.1 07/2011 C. Shaunessy, OIS/EASG/DITG Added EVM slides

2.0 5/2012 C. Shaunessy, OIS/EASG/DITG Reformatted for XLC

[Project Name] - DDR

Presenter’s Name Role

Presenters

4

See this slide’s notes pages for slide instructions.

[Project Name] - DDR

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

5

PDR Findings

[Project Name] - DDR

Business Need[Insert condensed business need and drivers from Sections 4.1 & 4.3 of the

Business Case or from the PSR presentation]

Goals/Scope/Purpose[Insert condensed goals/scope from section 4.2 of the Business Case and the business and functional purpose from sections 3.1 & 3.2 of the Requirements Document or from the PSR presentation]

Stakeholders[Insert stakeholder information from Section 4.4 of the Business Case or from the PSR presentation]

Project Information

6

[Project Name] - DDR

7

System Scope[Insert condensed system scope from Section 4.3.1 of the High-Level

Technical Design.]

High Level Functional Requirements[Insert high level functional requirements from Section 4.3.3 of the High

Level Technical Design.]

Summary of Changes[Insert condensed summary of changes of the current system from Section

4.3.4 of the High-Level Technical Design (if applicable).]

Proposed System

[Project Name] - DDR

System Security Level: [insert the System Security Level from Section 2.9 of the Information Security Risk Assessment.]

E-Authentication Level: [insert the E-Authentication Level from Section 2.10 of the Information Security Risk Assessment.]

[Please note if either of these assessments have changed since the PDR or if they have remained the same.]

8

Response Data

[Project Name] - DDR

[Summarize the Logical and Physical Data Models for the application.]

9

Data Design

[Project Name] - DDR

[From the System Design Document, list the various user classes/roles associated with the system. For each user class/role, provide estimates of the total number of users anticipated, a maximum number of concurrent users, and the number of external users. Also include the inputs and outputs associated with each user class/role.]

User & Machine Readable Interface

10

[Project Name] - DDR

System Architecture

[Insert the system architecture diagram from the Preliminary Design Review presentation, which depicts the overall, integrated structure of the system in terms of presentation, application and data regions including data storage and manipulation, user and external interfaces. If not available from the PDR, this information can be obtained from Sections 6.4, 7.2, 8 and 12 of the System Design Document.]

[Project Name] - DDR

[From the information contained in the System Design Document, insert a diagram depicting the physical hardware design.]

12

Physical Design

[Project Name] - DDR

13

Software Design

[Project Name] - DDR

[From the information contained in the System Design Document, insert a diagram depicting the security design.]

14

Security Design

[Project Name] - DDR

[From the information contained in the System Design Document, insert a diagram depicting the performance/reliability design.]

15

Performance Design

[Project Name] - DDR

[From the information contained in the System Design Document, insert a diagram depicting the internal communications design.]

16

Internal Communications Design

[Project Name] - DDR

[From the System Design Document, provide design specifications for the following minimum levels of control and any additional controls as appropriate or necessary:

a)Internal security to restrict access of critical data items to only those access types required by users/operators

b)Audit procedures to meet control, reporting, and retention period requirements for operational and management reports

c)Application audit trails to dynamically audit retrieval access to designated critical data

d)Standard tables to be used or requested for validating data fields

e)Verification processes for additions, deletions, or updates of critical data

f)Ability to identify all audit information by user identification, network terminal identification, date, time, and data accessed or changed.]

17

System Integrity Controls

[Project Name] - DDR

[From the System Design Document and Section 6 of the Interface Control Document, if applicable, describe the interface(s) between the system being developed and other systems (e.g. batch transfers, queries, etc.), indicating the location of the interfacing system. Include the interface architecture(s) being implemented (e.g. wide area networks, gateways, etc.) and the interfacing mechanisms (e.g., MQ, Gentran, etc.). If remote connectivity is required, identify the method of access. Provide a diagram depicting the communications path(s) provided in Section 3, System Overview, of the System Design Document. The graphical representation should depict the connectivity between systems, showing the direction of data flow.]

18

External Interfaces

[Project Name] - DDR

[Insert information on the planned testing from the Test Plan. Describe the various types of testing (test functions) to be performed.]

19

Planned Tests

[Project Name] - DDR

[From the Test Plan, list and describe the system functions/features not planned to be tested and explain why.]

20

Features Not Being Tested

[Project Name] - DDR

[From the Test Plan, describe the defect resolution process to be implemented during testing, including the operational definition and assignment of appropriate impact/severity levels.]

21

Defect Management

[Project Name] - DDR

[From the Test Plan, provide details and a graphical representation of the environmental components required to test the system, including hardware, software, communications, and any other resources used to configure the test environment, as well as any security considerations.]

22

Test Environment

[Project Name] - DDR

[From the Test Plan, list the milestone events and dates for all testing activities.]

23

Test Schedule

[Project Name] - DDR

[From the Test Plan, list the milestone events and dates for all testing activities.]

24

Release Impacts

[Project Name] - DDR

[From the Release Plan, describe any release-specific communication that needs to occur.]

25

Release Notification

[Project Name] - DDR

[From the Data Conversion Plan, describe the approach that will be used to extract, transform/cleanse and load data from the source to target destinations during the conversion/migration process.]

26

Data Conversion Approach

[Project Name] - DDR

[From the Data Conversion Plan, provide a schedule of conversion activities to be accomplished.]

27

Data Conversion Schedule

[Project Name] - DDR

[From the Data Conversion Plan, describe the strategy to be used to ensure data quality before and after all data conversions.]

28

Data Conversion Quality Assurance

[Project Name] - DDR

[From the Implementation Plan, describe the planned deployment, installation, and implementation approach.]

29

Implementation

[Project Name] - DDR

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

30

Project Management Update:Status

[Project Name] - DDR

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

31

Project Management Update:Risks & Issues

[Project Name] - DDR

32

Project Management Update:Cost & Schedule

• Cost• Schedule

See this slide’s notes pages for slide instructions.

[Project Name] - DDR

[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.]

33

Project Management Update:Deliverables Status

Conclusion of Detailed Design Review

for [insert project name]