CEG 4440 (or 6440) L#: Lab Title

  1. This article describes the expectations of typical lab reports of CEG4440/6440: Android Internals and Security
  2. There are 20 points (out of 100) assigned for the lab Report-Ln.pdf) [and the tarball, if any] for meeting the expectations below of editorial quality and report compliance.
  3. All lab reports are expected to be written as technical reports (TRs).
  4. Every paragraph that you include in the lab report must be in your own words. Do not copy-paste from other sources, including my descriptions of the lab. If you did, for seriously compelling reasons, you must cite the source(s).
  5. Be driven primarily by the following motive. Suppose you come across the lab report of yours, say, two years from now, and re-read it. Can you make sense of it? Can you recall the important thoughts you had and observations you made two years ago? Include all such details.

Cover Page/ Paragraph

The report must include lab title, your full name, your preferred email address, your WSU UID, your WSU/Pilot Login ID, date(s) of the lab, etc.


Purpose of the Experiment

Experiment Setup

Identify the (i) equipment and (ii) software you used. Some of this will repeat for every lab. Even so, include in every lab report. Android device and OS details. Linux has commands named lshw, and uname -a. Use it and select the important entries. Do not just dump it. Most software has a flag -v that gives its version number. Record any other details that you think are relevant for the particular lab.

Experimental Procedures

  1. The Lab descriptions given are not detailed recipes. You are expected to fill in all the missing details. Post requests for help, if needed, on Pilot.
  2. Describe the details of your procedures. If you literally followed the steps in our lab articles, with no changes whatsoever, just say so, instead of copy- and- paste. If you did do verbatim copy-and-paste, either from my articles or those written by others, you *must* *cite* your source explicitly; otherwise, it may be considered plagiarism.
  3. Labs typically have 4 or 5 tasks. Include subsections here for each task.

Recorded Observations

  1. Collect all your observations here. Much of this should be verbatim cut-and-pasted from stdout, or from a redirected stdout file. But grouped, and labeled. Be judicious about how voluminous this is. Cut out portions that are repetitive, or not illuminative. Include relevant screenshots or cut-and-pasted text. Avoid screenshots of pure text windows.
  2. Include time stamp/ duration of major steps. Learn to use the command named date.
  3. Labs typically have 4 or 5 tasks. Include subsections here for each task.

Interpretation of Recorded Observations

  1. Interpret your recorded observations. This is the most judged part of your report.
  2. Labs typically have 4 or 5 tasks. Include subsections here for each task.

Journal/ Remarks

  1. Include in the PDF a journal. Include entries related to this course only ;-) Make it a section. Critique this lab overall. This section should include your commentary on all aspects of this lab. Record how long each task took. Record/ describe glitches, if any. Are there any suggestions for improving the lab?
  2. Feel free to include a "personal experience" story in your description. What did you learn? Was something surprising? Was something [unexpectedly] difficult?


In technical reports, the conclusion section includes both summary as well as derived statements as ending remarks.


Include a numbered list of references you used. See the course articles for example usage of this section.


  1. Submit a PDF file named *exactly* Report-Ln.pdf, where n should be replaced with the number of the lab. (Scripts are used to check various things -- so file names, and section numbers, etc. should obey "rules".)
    1. In this course, we prefer open source tools, but you use what ever editor you like, turnin your report as a single PDF file.
    2. enscript can convert plain text files and source code into colorized PostScript files,
    3. ps2pdf converts PS files to PDFs, and
    4. pdfunite can combine several PDFs into one.
    5. It is recommended that you initially produce one dot-txt file for each section, and convert each to a PDF, then consolidate them into one PDF file, but name them as separate sections.
  2. Source code submission is expected in some labs. Submit all source code as one tar ball named Ln.tbz, with sub directories as needed.
  3. A lab report is a technical report. If you are unclear about the writing and formatting expectations, please look it up. Sections, and page numbers are a must. Make sure the report never exceeds 20 pages. Literally capturing the output can do that. Not counting the Recorded Observations, the entire report is probably about 10 pages.
  4. Because there are several to be submitted in this semester course, our standards of how well written the reports are fairly low. But, really careless reports will lose points from otherwise well-earned points.
  5. Report-Ln.pdf [and the tarball, if any] are assigned 20 points for meeting the above expectations of editorial quality and compliance.

last edited: Jan 2019