Professional Documents
Culture Documents
High LVL Tech Design
High LVL Tech Design
Notes on accessibility: This template has been tested and is best accessible with JAWS 11.0 or higher.
For questions about using this template, please contact CMS IT Governance
(IT_Governance@cms.hhs.gov). To request changes to the template, please submit an XLC Process
Change Request (CR) (https://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-
Information-Technology/XLC/Downloads/XLCProcessChangeRequestCR.docx).
<Project Name/Acronym>
High-Level Technical Design
Version X.X
MM/DD/YYYY
Table of Contents
1. Introduction.................................................................................................................1
2. Current System...........................................................................................................2
2.1 Functional Description.........................................................................................2
2.2 User Community Description..............................................................................2
2.3 Technical Architecture.........................................................................................2
3. Goals, Objectives, and Rationale for New or Significantly Modified System......3
3.1 Project Purpose...................................................................................................3
3.2 System Goals and Objectives.............................................................................3
3.3 Proposed System................................................................................................3
3.3.1 System Scope...............................................................................................3
3.3.2 Business Processes Supported....................................................................3
3.3.3 High-Level Functional Requirements............................................................3
3.3.4 Summary of Changes...................................................................................3
4. Factors Influencing Technical Design......................................................................4
4.1 Relevant Standards.............................................................................................4
4.2 Assumptions and Dependencies.........................................................................4
4.3 Constraints..........................................................................................................4
4.4 Design Goals.......................................................................................................4
5. Proposed System.......................................................................................................5
5.1 High-Level Operational Requirements and Characteristics................................5
5.1.1 User Community Description........................................................................5
5.1.2 Non-Functional Requirements......................................................................7
5.2 High-Level Architecture.......................................................................................8
5.2.1 Application Architecture................................................................................8
5.2.2 Information Architecture..............................................................................10
5.2.3 Interface Architecture..................................................................................12
5.2.4 Technology Architecture..............................................................................14
5.2.5 Security and Privacy Architecture...............................................................14
6. Analysis of the Proposed System..........................................................................16
6.1 Impact Analysis.................................................................................................16
List of Figures
Figure 1 - High-Level Conceptual Information Model......................................................18
List of Tables
Table 1 - User Community Description..............................................................................6
Table 2 - Alternatives Considered for the Overall Architecture..........................................8
Table 3 - Description of Application Components..............................................................9
Table 4 - Description of Information Components............................................................11
Table 5 - Description of Required Interfaces...................................................................13
Table 6 - Record of Changes...........................................................................................20
Table 7 - Acronyms..........................................................................................................21
Table 8 - Glossary............................................................................................................22
Table 9 - Referenced Documents....................................................................................23
Table 10 - Approvals........................................................................................................24
Table 11 - XLC Template Revision History.......................................................................26
1. Introduction
Instructions: Provide identifying information for the existing and/or proposed automated
system or situation for which the High Level Technical Design applies (e.g., the full
names and acronyms for the development project, the existing system or situation, and
the proposed system or situation, as applicable). Summarize the purpose of the
document, the scope of activities that resulted in its development, its relationship to
other relevant documents, the intended audience for the document, and expected
evolution of the document. Emphasize that the High Level Technical Design is
completed during the Concept Phase of the Investment Lifecycle and is intended to
describe the conceptual design of the proposed system. This document provides a
framework for more detailed requirements and design activities in later phases of the
project.
2. Current System
Instructions: If applicable, this section describes the current system that is being
replaced, enhanced, or upgraded.
4.3 Constraints
Instructions: Describe any limitations or constraints that have a significant impact on the
design of the system. Such constraints may be imposed by any of the following (the list
is not exhaustive):
Hardware or software environment
End-user environment
Availability of resources
Interoperability requirements
Interface/protocol requirements
Data repository and distribution requirements
Other requirements described in the Requirements Document
5. Proposed System
Instructions: This section describes the operational requirements and technical design
of the proposed system.
5.2.4.1 Platform
Instructions: Identify the target platform expected for the system (e.g., mainframe, mid-
tier, or other).
5.2.5.1 Authentication
Instructions: Describe the basic user authentication approach to verify user identity
before allowing access to the system. For example, will the system use the IACS
single-sign-on solution?
5.2.5.2 Authorization
Instructions: Describe the anticipated approach for authorizing users to perform
functional activity once logged into the system.
5.2.5.3 Encryption
Instructions: Based on the business risks and the nature of the information, identify if
there are any anticipated needs to encrypt the data.
6.2 Risks
Instructions: Describe the risks that the preferred alternative presents and risks that will
remain after implementing the design.
Appendix E: Acronyms
Instructions: Provide a list of acronyms and associated literal translations used within
the document. List the acronyms in alphabetical order using a tabular format as
depicted below.
Table 7 - Acronyms
Acronym Literal Translation
<Acronym> <Literal Translation>
<Acronym> <Literal Translation>
<Acronym> <Literal Translation>
Appendix F: Glossary
Instructions: Provide clear and concise definitions for terms used in this document that
may be unfamiliar to readers of the document. Terms are to be listed in alphabetical
order.
Table 8 - Glossary
Term Acronym Definition
<Term> <Acronym> <Definition>
<Term> <Acronym> <Definition>
<Term> <Acronym> <Definition>
Appendix H: Approvals
The undersigned acknowledge that they have reviewed the High-Level Technical Design and
agree with the information presented within this document. Changes to this High-Level
Technical Design will be coordinated with, and approved by, the undersigned, or their
designated representatives.
Instructions: List the individuals whose signatures are desired. Examples of such
individuals are Business Owner, Project Manager (if identified), and any appropriate
stakeholders. Add additional lines for signature as necessary.
Table 10 - Approvals
Document Approved By Date Approved
6. Delete this “Notes to the Author / Template Instructions” page and all
instructions to the author before finalizing the initial draft of the document.