TechnicalDesignTemplatev20

8/4/2019 TechnicalDesignTemplatev20

1/11

Technical Design

Version

Effective Date:

Project Manager:

Prepared By:

All information contained herein is proprietary and shall be kept confidential.


2/11

Table of Contents

REVISION HISTORY................................................................................................................................................3

1.0 PROJECT DESCRIPTION ............. .............. .............. .............. .............. ............... .............. .............. ..... ..... ..... ....3

1.1 ASSUMPTIONS......................................................................................................................................................... 31.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 .....................................................................................................64.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 68415375.doc Confidential 9/18/2011

Technical Design


3/11

Revision History

Version Version

Date

Author Comments

1.0 Project Description

1.1 Assumptions

1.2 Known Issues

Issue ID Owner Issue Description

Figure 1: Issues Table


Technical Design


4/11

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

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

What protocols will be used? (Example: HTTP, FTP, NDM)What type of transactions will be transmitted? (Example: Wires, ACH)

How do the distributed pieces communicate? (Example: NDM over leased lines, FTP, etc). Provide(attach) data flows detailing communication.With which, if any, other systems or applications will this system or application interface?Does the physical model conform to enterprise standards for data element naming, and model meta data?

>


Technical Design


5/11

3.0 Requirement Matrix - (Optional)

Technical

Element ID

Functional

Element ID Functional Element Description

Figure 3: Matrix Table

4.0 Technical Design

4.1 Application / System Technical Design


6/11

Explain and diagram the logical layout of the application system.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? Ifyes, 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 concurrentlyaccessing 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? Howbig 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


7/11

changes or a description of the design change required. The screen change (layout) can be presented inan appendix to this document. >

4.1.3 One Time Modifications

4.1.4 CIM Modifications

< Identify required design changes for CIMs (Common Interface Messages). The design should identifychanges to the CIM and corresponding changes to the input and output of the CIM. Identify impacted file

layouts or database changes in addition to the CIM changes. The CIM design changes can berepresented by pseudo code, actual code changes, file and database layouts or a description of the designchange.

What technologies are used by the application? (Database, Messaging/MQ, Notes, MS Exchange, MSSQL Server, NDM/Connect Direct, J2EE/EJB, Thick Client, Optical Image, .NET/ASP, File Transfer orData Transmission, Information Broker, Web Service, Transaction Services, etc.) What is the version?

For any Customer Information Control System (CICS) transactions, will a user ID and password besupplied or will a generic ID be utilized? Specify.

For any Customer Information Control System (CICS) transactions, what quantity of data will be

retrieved?

How should error or return codes be handled? >

4.1.5 Reporting Modifications

5.0 Interface Modification Impacts


8/11

Are there any third party vendor dependencies providing business services? (Example: Beta, etc) If yes,specify.

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 neededto 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


Technical Design


9/11

Acronyms

Acronym Description

Glossary

Word / Term Description

References

Document Title Document Source


Technical Design


10/11

Appendix A:


Technical Design


11/11

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


Technical Design

TechnicalDesignTemplatev20

Documents

Transcript of TechnicalDesignTemplatev20