Develop Phase

During the Develop Phase detailed user stories or requirements are created, the solution is designed, built, deployed to a non-production environment, and tested for compliance with the requirements and CMS standards so that it is production ready. Requirements, user stories, design, development and testing must all be done in compliance with the CMS Technical Reference Architecture (TRA) and security, privacy and accessibility standards.  

The system development methodology is not prescribed, but must be established by the Business Owner and Developer. The TLC requires only a minimal set of artifacts, but components are expected to conform to their chosen system development methodology and to follow best practices in Program Management.

Examples of ways you can stay compliant with the TLC can be found in the TLC Resource Library.

Key Objectives

  1. Identify repository locations for system development artifacts.
  2. Satisfy information security, privacy, and Section 508 requirements prior to releasing to the production environment
  3. Update the TLC System Profile entry for the system

Exit Criteria

  1. Authorization to Operate (ATO)
  2. Final TLC System Profile Updates
  3. Software solution ready to be deployed to the Production environment

For inquires about the Target Life Cycle, please contact CMS IT Governance at

CMS TLC Guidance Document (PDF)
TLC Project Worksheet (DOCX)
Requirements Document Template (DOCX) – T (DOCX)
Design (DOCX)Interface Control Document Template (DOCX)
System Design Document Template (DOCX)
Test Case Specification Template (DOCX) – T (DOCX)
Test Plan Template (DOCX) – T (DOCX)
Test Summary Report Template (DOCX) –T (DOCX)
Service Level Agreement (SLA) Template (DOCX)
Operations & Maintenance Manual Template (DOCX)
Training Plan Template (DOCX) – T (DOCX)
User Manual Template (DOCX) – T (DOCX)
Implementation Plan Template (DOCX) – T (DOCX)
Page Last Modified:
11/15/2019 03:44 PM