Technical Design Document

Hello powerbiexpert22  ,   good general list.   Getting closer.  This is a very important topic forall sorts of reasons.   I would have you circle back to the guidance I offered you June 8.   When it comes to designs and planning, the initial response is usually 'it depends' and 'what is the situation' - how can you decrease risk and increase value in your work for the client and organization?

When delving into the subject, my earlier response commenced with:

"Specific documents needed may vary based on the project scope, organization, industry, and granularity requrired.   The first question to fulfill, is to ask and answer what is the current governance model, what are the expectation, and guardrails.  Power BI governance refers to a set of processes, policies, and standards that organizations put in place to manage and control the use of Power BI."

In this reply, I would like to direct your attention to the author's inquiry and the solution  

that provides  further explanation on this subject.  specifically, which focus on

Test-Driven Development. Also, I really appreciate the checklists created by Data

Goblin. They are quite helpful.  https://data-goblins.com/checklists

As I am writing this Ritaf1983 added her reply, and I agree with her.  

When addressing this topic outside of an academic context, it's important to consider the organization's and my boss's goals and requirements for the project. If I had to recommend one book on the subject (and I just pulled it down from the bookshelf), it would be "Software Requirements," 3rd Edition by Karl E. Wiegers, a Microsoft Press publication, as well as any and all of the Developer Best Practices (23 books) on Amazon.