WritingReports - Some Guidelines for Writing Technical...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Some Guidelines for Writing Technical Reports In this course you will be learning many tools for translating context-specific questions into queries made in computer code. A practicing statistician must then translate the results of these computationsbe they numbers, tables, or figuresback into a context-specific answer. In this class, each full-length assignment will ask you to turn in a short written technical report, representing the end result of this cycle. Format The technical report should be divided into appropriate sections. These may vary depend- ing on the analysis (for example, for one assignment we will be simulating data rather than obtaining it from an outside source), but in general your report should include most of the following. Title: Make it informative, not Homework 1. Author Abstract: This is a short (100-200 word) summary of the questions addressed, meth- ods/techniques used, and results obtained....
View Full Document

This note was uploaded on 12/20/2009 for the course STAT 133 taught by Professor Staff during the Fall '08 term at University of California, Berkeley.

Page1 / 2

WritingReports - Some Guidelines for Writing Technical...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online