TDD

Technical Design Document

Propose
The technical design Document describes technical details of the design. It builds upon the design described in the corresponding FDD. It should be viewed as a technical supplement to the FDD describing how the feature will technically be implemented. Information contained in the FDD should not be repeated in the TDD. The goal of producing a TDD is to help developers plan and layout the technical architecture for their feature and capture information that will be helpful to others during a technical review. The goal is not to document technical details after the fact on what was implemented. If written upfront, it encourages developers to think through the entire process before they start coding. It also provides an inventory of the objects that will be need to be built/changed, which should help in estimating the development effort.

Content
Assumptions
List any assumptions made in this technical design document. Include any other TDDs that this TDD is dependent on.

Technical Dependencies
List any People Tools features not yet completed that this technical design is dependent on. Also include any other TDDs or other technologies this TDD is dependent on.

Related Documents
Requirement Source Itemize any other reference document, including the name of the document and its location that were used. Name of FDD and the details of the reference documents. Other Documents List any other related documents that can help in the understanding of this feature, if yes, specify the folder name and path

General Info
Developer name Development Aproach Type Plataform Related Vendor Package Functional Spec Reference Database Platform <Developers Name> <Programming Approach> <Interface/Conversion/Report/Process/Customization/Enhancements> <People Tools Version> <In case of an interface only, List Vendor Package name> <Functional Specification Document> <Database>

Impact Analysis
Other PeopleSoft Products Impacted As a result of the technical design, describe how any other products will be impacted beyond what is already described in the FDD. Common Component Impact As a result of the technical design, describe any impact to utilities like the currency conversion utility, or other Common Components Data Model Impacts Describe any downstream impacts these data model changes will have on existing online pages, reports and integrations. Describe what objects will need to be changed as a result of the data model changes.

Technical Design
Design Overview Describe the design and include a Process Flow, Data Flow, and?or State Diagram as appropriate. ERD Diagram Include a high level ERD diagram of the tables involved in the design.

PeopleSoft Object
Projects List any projects that will need to be created/modified. Fields New List any new fields will need to be created Fields Rename List any fields will need to be renamed. Renamed fields will be needed for the upgrade conversion maps. Translate Values List any translate values will need to be added/modified.

Tables New/Modify List any tables that will need to be created and/or modified.