Write a section that identifies the purpose/problem this will solve. (Problem Overview)
Write a section on how the spreadsheets, etc, will solve the problems. If you have additional advantages, such as how easy your methods will also support PowerBI and 2 web pages, then include those, as well. (Recommended Solution)
Write a more detail functional section that explains the working parts in more detail. (Functional Description)
Write a section that explains the costs and ROI. (Costs and ROI).
Then, go back to the beginning and write and 3 or 4 sentence "Executive Summary" section that summarizes it all.
If there are any terms that need explaining (and remember your target audience), include a short glossary.
Add a table of contents right after the "Executive Summary" (easiest done if you use Word Headers in the rest of your document, which should usually be limited to 3 levels at least in the TOC).
And a cover page followed by a "Revision History" page or include the revision history at the bottom of the cover page.
Get someone to review the document well prior to you submitting it to the people that you ultimately want to see it and make a decision.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)