<Project Name >

Technical Design

Version <>
Effective Date: < >

Prepared By: <Name>

Technical Design

Table of Contents
REVISION HISTORY................................................................................................................................................3
1.0 PROJECT DESCRIPTION...................................................................................................................................3
1.1 ASSUMPTIONS.........................................................................................................................................................3
1.2 KNOWN ISSUES.......................................................................................................................................................3
2.0 SYSTEM INTERFACE FLOWS..........................................................................................................................4
2.1 CURRENT FLOW......................................................................................................................................................4
2.2 PROPOSED FLOW.....................................................................................................................................................4
3.0 NAVIGATIONAL DIAGRAM..............................................................................................................................4
4.0 TECHNICAL DESIGN..........................................................................................................................................4
4.1 APPLICATION / SYSTEM TECHNICAL DESIGN...............................................................................................................4

4.1.1 Screen Templates........................................................................................................................5

5.0 SECURITY / LEGAL / COMPLIANCE CONSIDERATIONS.........................................................................5
6.0 TESTING STRATEGY..........................................................................................................................................5
ACRONYMS...............................................................................................................................................................6
GLOSSARY..................................................................................................................................................................6
REFERENCES.............................................................................................................................................................6
APPENDIX A:..............................................................................................................................................................7
APPROVAL SIGNATURES......................................................................................................................................8

<Project Name>
Confidential

Page 2 of 8

82033952.doc
1/21/2012

Technical Design

Revision History
Version

Version
Date

Author

Comments

1.0 Project Description

<Provide a short description of the purpose of the project. This can be copied from the Project Statement
of Work. >

1.1 Assumptions
<List known internal or external activities identified while defining the technical design that must remain
true. When activities do not remain true, impact to the design is possible. Assumptions can be listed as
bullet points. >

1.2 Known Issues

<Label and list the known issues that could impact the technical design. Use an Issues Table to log the
known issue by assigning an identifier (Issue ID) to the issue, a person (Owner) responsible for resolving
the issue and a brief description (Issue Description) of the issue. The issues can be obtained from open
issues found on the project issue log or while completing the design.
Are there any known single points of failure in the environment? If yes, specify or explain. >

Issue ID

Owner

Issue Description

Figure 1:

<Project Name>
Confidential

Issues Table

Page 3 of 8

82033952.doc
1/21/2012

Technical Design

Figure 2:

Systems / Applications Affected Table

2.0 System Interface Flows

<Provide a before and after conceptual view of the interfaces between the impacted systems or
applications. >

2.1 Current Flow

<Provide a conceptual view of the current interface flow between the impacted systems or applications.
>

2.2 Proposed Flow

< Provide a conceptual view of the interface flow after design changes are implemented to the impacted
systems or applications.

3.0 Navigational Diagram

4.0 Technical Design

<The functional design elements are expanded in this section to a technical design that technology must
implement to satisfy the needs expressed in the functional design document. This section is divided in
sub-sections, one for each system or application identified in section 1.4 Systems / Applications
Affected. >

4.1 Application / System Technical Design

<Project Name>
Confidential

Page 4 of 8

82033952.doc
1/21/2012

Technical Design

Class Name

AccountCreationProcessor

Class Package
Class Parent
Action(Add/Change)
Implementation Notes

List the actions which will be performed by the class performs

4.1.1 Screen Templates

<Provide the screen layouts. >

5.0 Security / Legal / Compliance Considerations

<Identify any security, legal or compliance requirements that must be taken into consideration when
implementing this technical design. The considerations can include data movement, copyrights or
regulatory compliances.
What type of encryption, if any, will be used? >

6.0 Testing Strategy

<Provide a high level description of the recommended approach for testing the design changes. >

<Project Name>
Confidential

Page 5 of 8

82033952.doc
1/21/2012

Technical Design

Acronyms
Acronym

Description

Glossary
Word / Term

Description

References
Document Title

<Project Name>
Confidential

Document Source

Page 6 of 8

82033952.doc
1/21/2012

Technical Design

Appendix A:

<Project Name>
Confidential

Page 7 of 8

82033952.doc
1/21/2012

Technical Design

Approval Signatures
My signature below indicates that I have reviewed this document and agree that it details the
requirements that I have for the initiative.

_______________________________
Name

_________________________________
Role

_______________
Date

_______________________________
Name

_________________________________
Role

_______________
Date

<Project Name>
Confidential

Page 8 of 8

82033952.doc
1/21/2012