Solution design is a solution binder that brings together all of the aspects of the solution. The following are suggested coverage areas that a solution design should comprises:

• There should be an end-to-end pictorial flow of the entire business process by function, for example, one end-to-end flow diagram for the supply chain, one end-to-end flow diagram for financials, and likewise for the other business functions.
• The end-to-end flow must have starting/entry points, ending/closure points, and handover to other process diagrams.
• All of the decision points that can bring in additional business scenarios should be included.
• There should be steps that are manual or automated.
• The roles expected to perform the function in Microsoft Dynamics in a swim lane view should be present.
• Fundamental security and integration solution components should be included.
• All of the artifacts and configurations that will be needed to deploy the solution in production should be included.
• The critical takeaway from the SDD is that the core implementation team (especially customer members) is on board with the overall solution flow and design.
• The SDD must be able to convey the entire set of business processes in the scope of the project. These may include, but are not limited to, the following:
  • Record to report
  • Order to cash
  • Procure to pay
  • Plan to inventory
  • Others

Also, it must contain the core processes that enable the previously mentioned processes, as follows:

• • Legal entities
  • Number sequences
  • Languages
  • Users
  • Countries involved
  • Systems involved

The SDD is a highly important artifact in implementing Dynamics 365; it is your single point of reference to know anything about the solution. In simple words, an SDD connects all of the dots together.

In a medium and complex project, along with the overall solution design document, you would need a detailed functional and technical document to outline how a customized feature is supposed to work. In the next sections, let's understand the critical aspects of writing functional and TDDs.