Suggestions for clear lab reports in computer sciencecourses A very short sample lab is in General advice: In general, your lab should be presented in a self-contained manner,and summarize what you accomplished, what conclusions you drew andwhy. The lab assignments have questions which were chronologicallyordered to indicate how we recommend you accomplish the tasks for thelab, but this is not the clearest way to present most reports.
Instead, you should break up your report into logical pieces, and tiethe pieces together with an introduction, conclusion, and otherhelpful comments What you would do differently next time. ○ How the exercise might be revised to make it clearer/more satisfying. ○ What the instructors and TAs might There should be no emphasis placed on “expressing yourself” or “keeping it interesting”; a programming lab report is not a narrative. ○ In a lab report, it is important to get .
Lab report sample - cal poly computer science
So they haven't read the book, nor have they readthe lab description. Your introduction should explain why they shouldread your report and give a roadmap explaining its structure.
Yourconclusion should summarize what the reader should have learned. Do notinclude in your report what you learned from doing it.
It is your responsibility to test your code thoroughly as you writeeach procedure and to convince the reader that you know allyour code works. If your code has a bug, report the bug and explainyour testing and what you know about where the bug is in your program.
If you fail to report a bug, the grader will assume you either (a)tested poorly or (b) were dishonest in your report.
Either way, yourgrade should be more severely reduced than if you just report yourbug The links on this page are to technical/research reports for each year listed up to 2000. They are listed by tr number in chronological order. The number of reports for each month/year varies. Reports with electronic versions have a link to the paper in .tex, .pdf and/or .ps format listed next to the report number in brackets..
Lab report DO's and DON'Ts: Do use complete sentences, with proper grammar and spelling. Don't blindly write up your lab in the same order and format as thelab assignment.
Do structure your lab in a logical way, with each section markedwith a helpful title.
Computer science lab report format
Don't use phrase like, ``In this lab we learned about help using one of these word processors. Please be aware that your lab report will not (in general) contain the same sections as this one. Structure your report logically with sections appropriate to your lab assignment. See this must read for detailed suggestions on how to write lab reports in computer science courses..
,'' nor,``We were asked to write a procedure which, .
Teaching students how to write a formal lab
'' Don't use the passive voice, ``A procedure was written to . (Your documentationshould make clear what the code does at a high level, not how it doesit at a low level.
Cs 1521 lab report format
Do summarize the results of procedure calls in a readable form. Whenappropriate, this could include Tables whose headings are carefully chosen and whose entries are rounded to an appropriate number of significant digits (2-4 depending on your judgment should be enough for most practical purposes.
In either case there should be enough of an explanation so I know whateach table entry means and/or what the graph represents.
Don't forgetto label axes in graphs, and make the units clearly visible in tablesand graphs. Usually, I would recommend sticking topresent tense.
Sample lab write-up for cs courses
Remember, the audienceyou are writing for has read neither the book nor the lab description,so your code should either be self-documenting or have enoughdocumentation so that it's clear what it does So they haven't read the book, nor have they read the lab description. Your introduction should explain why they should read your report and give a roadmap explaining its structure. Your conclusion should summarize what the reader should have learned. Do not include in your report what you learned from doing it..
You don't always need toprovide the individual test cases, but you should convince me how youhave tested every procedure and why you are confident that eachworks. If a procedure does not always work, you should report this,too.
Rather than copy huge pieces of code from the text, summarize theprocedures defined in the text.
You could, for instance, give asample procedure call for each procedure, and explain in a sentencewhat the procedure takes as input and what it returns Lab Java's List Interface. PURPOSE: Using the Java's List Do not describe less important variable such as subscripts. and loop control variables. 3. DATA MAIPULATION INSTRUCTIONS (15 points). An algorithm requires instructions; Therefore, list the steps you will take to solve the problem. 4. CONTROL STRUCTURES .
This way yourreport will remain self-contained without blindly copying from thebook.
Technical reports | computer science
Often the real point of a lab is to write some majorprocedure x, but to do so you need to write lots of smallprocedures, a, b, c, . If so, you should structure your report so that you get to x as soon as possible. One way to do this is to statethe behavior (with, for example, a sample procedure call) of onlythose procedures which x calls, then describe x, and then include the actual code for the littleprocedures a, b, c, .