A Solution Design Document (SDD) includes information about the working elements of the overall solution, including Dynamics AX standard features (Fits), Gaps, and integrations. It is important to get the entire solution depicted in a pictorial representation. The business process modeler in LCS is a great tool with which to put together the solution design document.
Solution design documents are primarily referred to by core team members of the implementation team. The following are the key objectives of solution design documentation:
- The details of the business flow in the future solution based on Microsoft Dynamics AX
- Solution validation
- The single point of reference for future value additions, issues, and troubleshooting
- Documenting the high level
- Business and solution flow diagrams
Solution design is a solution binder and puts together all the aspects of the solution. The following are the suggested coverage areas that the solution design should comprise:
- There should be an end-to-end pictorial flow for the entire business process by organization function. For example, one end-to-end flow diagram for the supply chain, one end-to-end flow diagram for financials, and likewise for other business functions.
- The end-to-end flow must have starting/entry points, ending/closure points, and handover to other process diagrams.
- There should be all the decision points that can bring in additional business scenarios.
- There should be steps that are manual or automated.
- Roles expected to perform the function in Microsoft Dynamics in a swimlane view should be there.
- Key security and integrations solution components should be included.
- All artifacts and configurations that would be needed to deploy the solution in production should be included.
The key takeaway from SDD is that the implementation core team (especially customer members) is on board with the overall solution flow and design.