It is common knowledge that one of the most highly sought after skills for technical experts is the ability to write coherently. The ability to communicate to administration and management is tantamount if you are interested in career progression (there is something to be said for being the best programmer in the basement and some people enjoy it there forever). This component of the course involves you utilizing your technical writing skills acquired in the technical writing course. Whitepapers at companies have many different styles, lengths, and requirements. I (and it's just me, the BEST way is the way your boss likes it) prefer short concise reports that are all formatted the same by everyone. This is my methodology for writing these things myself:
1) Try to write the problem down in a single sentence:
e.g. What hardware and software is required to run Windows Vista?
2) Conduct research on the matter and list sources at the end as you go. Number the sources. They may be alphabetical or chronological as the situation demands. In the below example, they are in the order they are used in the paper since neither appears to apply. (see note 1 about research)
[1]http://vistarequirements.com
[2]http://microsoft.com/vistareq.html
[3]http://microsoft.com/vistaconfigurator/vistaconfigurator.msi
3) Write an answer to the question and try to keep it to one page. Sometimes it is not possible and page limits or requirements are just plain stupid for the most part. Answer the question. If you can do it one sentence then writing 10 pages about it because you are required to is ridiculous. Likewise, if it takes 500 pages to answer the question, then use 500 pages. Don't try to condense all this into one page. You should, if the paper exceeds two pages, write an executive summary of a about a paragraph to describe what you did and include a Table of Contents.
4) READ YOUR PAPER!!!!!
First, be sure you answered the question. Did you actually answer it or did you just try and fake your way through it. Usually when I get these papers at companies, I will ask people to prepare a tutorial training session from them on powerpoint. Typically they can't. A long time ago, I had a very good boss who had this stamp that said B.S. and if you got the stamp, you had to do an presentation on the matter to the department explaining the problem and solution and then resubmit the paper until he didn't stamp it.
Second, proof your work. We are all lazier than in days gone by due to spell checkers, grammar checkers, and texting but this is no excuse and in fact is pathetic since you have all these tools to do it for you. Read it and make sure it makes sense. Also, make sure you can use English (use a dictionary if you don't know) Through, threw, and thorough are all different words. Nothing will cut you down with upper management than a report that looks like they hired you from some shack in the mountains (do you know the difference in except and accept, insured and ensured, affect and effect?)
Thirdly, now rewrite your answer. I will tell you a secret. Prepare a lecture on it and see if you can give it. You don't need an audience, if you can explain something in that format, you most likely understand it.
NOTE 1: Research requires more than just typing something in google and using the first thing you see. Always cross reference websites unless they are known to be reliable (to all) and likely to continue to exist for a long period (e.g. microsoft.com is good, rontheubergeek.com is not).