.
  • Context: a well-written technical report gives the reader the context they need to understand it.  For example, a software design in the Unified Modeling Language (UML) is meaningless without some textual description of the problem it solves.
  • Visualization: a well-written technical report is not just text.  It also incorporates visual elements such as graphs and tables to display data, UML diagrams to describe a software design, or network graphs to illustrate a network architecture.
  • Proper grammar, punctuation, and spelling: are not optional.  At the least, pay attention to your word processor’s spelling and grammar suggestions.  A better solution is to make use of the English Department’s Writing Center for suggestions on how to improve your report.
  • Originality: your report should be your original work.  Copying another person’s work and passing it off as your own is called plagiarism.  Any time you incorporate material from another source, whether as a quotation or summarized, you must cite your source.  This act of attribution shields you from charges of academic misconduct.  Examples of proper citation style can be found at .
  •  

    Back to the top