Technical Design
Version
Effective Date:
Project Manager:
Prepared By:
All information contained herein is proprietary and shall be kept confidential.
Technical Design
Table of Contents
REVISION HISTORY ................................................................................................................................................3
1.0 PROJECT DESCRIPTION ...........................................................................................................................3
1.1 ASSUMPTIONS ...............................................................................................................................................3
1.2 KNOWN ISSUES .............................................................................................................................................3
1.3 SYSTEMS / APPLICATIONS AFFECTED ...........................................................................................................4
2.0 SYSTEM INTERFACE FLOWS ..................................................................................................................4
2.1 CURRENT FLOW ............................................................................................................................................4
2.2 PROPOSED FLOW...........................................................................................................................................4
3.0 REQUIREMENT MATRIX - (OPTIONAL) .............................................................................................5
4.0 TECHNICAL DESIGN ..................................................................................................................................5
4.1 APPLICATION / SYSTEM TECHNICAL DESIGN ................................................................................................5
4.1.1 Batch Job Stream / Program Modifications .......................................................................... 6
4.1.2 Online / Screen Modifications .............................................................................................. 6
4.1.3 One Time Modifications ....................................................................................................... 7
4.1.4 CIM Modifications ................................................................................................................ 7
4.1.5 Reporting Modifications ....................................................................................................... 7
5.0 INTERFACE MODIFICATION IMPACTS ...............................................................................................7
6.0 NEW HARDWARE REQUIREMENTS ......................................................................................................8
7.0 SECURITY / LEGAL / COMPLIANCE CONSIDERATIONS.................................................................8
8.0 TESTING STRATEGY .................................................................................................................................8
ACRONYMS................................................................................................................................................................9
GLOSSARY .................................................................................................................................................................9
REFERENCES ............................................................................................................................................................9
APPENDIX A: ........................................................................................................................................................... 10
APPROVAL SIGNATURES .................................................................................................................................... 11
Page 2 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
Revision History
Version Version Author Comments
Date
1.0 Project Description
1.1 Assumptions
1.2 Known Issues
Issue ID Owner Issue Description
Figure 1: Issues Table
Page 3 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
1.3 Systems / Applications Affected
System / Application ID Description
Figure 2: Systems / Applications Affected Table
2.0 System Interface Flows
2.1 Current Flow
2.2 Proposed Flow
Page 4 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
3.0 Requirement Matrix - (Optional)
Technical Functional
Element ID Element ID Functional Element Description
Figure 3: Matrix Table
4.0 Technical Design
4.1 Application / System Technical Design
Page 5 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
Is this system/application distributed? Which pieces are: in the TZ? Wachovia Intranet? Located or
belong to a third party?
What kind of language will be used? (Cobol, ASM, Easytrieve, APS, C, SAS, REXX, etc)
Will the database be primarily transactional (add/change/delete records) or analytical (queries)?
Where is data sourced?
Are there any directories that are involved in mail routing or mail systems affected by this application? If
yes, specify.
Is the system hosted on a Citrix Server?
Is 128-bit encryption exportable to the country in which users will initiate a remote access
session?
What Citrix applications are required? (Example: Notes, Sametime, PICCT, etc)
Will there be multiple Citrix Applications?
Will applications be used by all users (provide spreadsheet of Citrix applications/user groups)?
Are there remote access points besides Citrix that are available?
Why was Citrix chosen?
Describe the licensing model/requirements for each application.
For each required Citrix Application provide the following: Expected total Citrix application
users given access to the system, Expected number of Citrix application users concurrently
accessing the system, Citrix storage requirements for the applications.
What fail over/load balancing systems are in place?
How many managed resource connections (database message queue, etc) should normally be used? How
big are the resource pools?
Will this project utilize any technologies not currently used within Wachovia? If yes, specify.
If Batch Processing is required:
What are the jobs that begin streams?
What are the jobs with Service Level Agreements?
What are the jobs that End Update Streams?
What are the jobs that End Report Streams?
What are the key milestone jobs? >
4.1.1 Batch Job Stream / Program Modifications
4.1.2 Online / Screen Modifications
Page 6 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
4.1.3 One Time Modifications
4.1.4 CIM Modifications
4.1.5 Reporting Modifications
5.0 Interface Modification Impacts
Page 7 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
Will this system/application reside in the Wachovia Transition Zone (TZ)?
What other system or application dependencies will this system/application have?
Will data be used by other applications? If yes, specify.
Document the system/application's upstream and downstream dependencies and add to the Configuration
Management Database (CMDB) (i.e. PICCT Inventory)?
Are upstream/downstream application Recovery Time Objectives (RTO) equal to or less than the process
RTO's?
Will a data transmission be needed for this process? Is the transmission external (to or from an outside
organization) or internal (application to application)? Will any dedicated network connectivity be needed
to perform the data transmissions? What is the largest and smallest file size that will need to be
transmitted?
What are the TCP port requirements? (Technical Requirement)>
6.0 New Hardware Requirements
7.0 Security / Legal / Compliance Considerations
8.0 Testing Strategy
Page 8 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
Acronyms
Acronym Description
Glossary
Word / Term Description
References
Document Title Document Source
Page 9 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
Technical Design
Appendix A:
Page 10 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011
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
_______________________________ _________________________________ _______________
Name Role Date
_______________________________ _________________________________ _______________
Name Role Date
_______________________________ _________________________________ _______________
Name Role Date
_______________________________ _________________________________ _______________
Name Role Date
Page 11 of 11 ddffae7e-87c2-47cc-8d82-b50e12b496db.doc
Confidential 11/16/2011