Another design document that is especially important for the technical team is the TDD. The TDD covers the technical details of the FDD. This document mainly answers the following question: How will the functionality be implemented in the new system?

A TDD provides solutions to technical issues, so it not only provides guidance on what needs to be developed but also on how it will be developed. This document is prepared for the technical team, who are responsible for customizing, extending, and integrating Dynamics 365 CE with other systems. These details are hidden from stakeholders and key users while using Dynamics 365 CE. A TDD also provides details on the architecture of a Dynamics 365 CE implementation.

The following are features of a good Dynamics 365 CE TDD:

• Provides details about the Dynamics 365 CE implementation infrastructure architecture
• Helps to understand the overall customer application architecture
• Lists all of the possible integration required
• Lists all of the custom logic required to write using scripting or server-side code
• Explains the workflow required to automate day-to-day business activities
• Provides details about the development environment and release management

Now that we understand what FDDs and TDDs are, let's look at how we can prepare them. We'll start with how to prepare an FDD.