Power BI Business Intelligence Report | MS Access Split Database
PROJECT DOCUMENTS

Your way is our way. Why? Because every company has a culture, and every culture is unique. Because I have worked on both new and previously existing Power BI and Microsoft Access development projects method of analysis, requirements gathering, and documentation between companies is as varied as cultures are from company to company.

If you prefer a formal and comprehensive project document then you will get just that from me. I can also provide it in two translations, one for the technical reader and one for the not so technical reader.

In other more fluid cases, where there are many Power BI reports and Microsoft Access databases on site, a company may not even know how project files exist, and I may be asked to create a list of the databases, record the primary contact information, and quantify the app’s usage, it’s business value, and urgency. In these cases, or where rapid applications development and new needs comes into view, a more general pictorial storyboard may be requested.

In ether case, I will provide you with the type of documentation with respect to functional requirements (WHAT is needed) and Non-Functional Requirements (HOW the system will work) that you expect.