Programming Lab Reports - Writing - LibGuides at Loyola Marymount University Get Help Skip to Main Content Library LibGuides Writing Programming Lab Reports Writing This Guide was created as a joint project of the Academic Resource Center and the William H. Hannon Library. Home General WritingToggle Dropdown Understanding the Assignment Need a Topic? Evaluating Sources Audience Brainstorming Strategies Critical Reading Outlining Drafting Strategies Thesis Formulation Introductions Conclusions Argument Show Don't Tell Expand Your Draft Flow & Lexical Coherence Revision Checklist Style and GrammarToggle Dropdown Introduction to Style and Grammar Apostrophes Article Usage for ESL Learners Capitalization Clarity: Get Rid of Nominalizations Cohesion: Does my Paragraph Flow? Commas and Colons Conciseness Confusing Words Fragments Parallel Structure Passive Voice Quotation Marks Run-on Sentences Subject-Verb Agreement Writing Mechanics Using and Citing SourcesToggle Dropdown Other Styles Writing in the Disciplines Art History History Literature Philosophy Psychology Programming Lab Reports Scientific Lab Reports Screenwriting Theology Meet with a Tutor ARC Info Academic Resource Center Hours: Monday-Thursday: 8:00 AM-6:00 PM Friday: 8:00 AM-4:00 PM Phone Number: 310-338-2847 Email: arc@lmu.edu www.lmu.edu/arc We are located in Daum Hall on the 2nd floor! Writing a Programming Lab Report Report Format Assignment/Problem Description: What were you required to implement? This is a word-for-word reiteration of the problem given to you. Discussion: ● Solution/Program Description: A brief description of what your program does, including how your program works. For example, you might state whether your solution is recursive or iterative, or if it uses memoization. If requested, include a flowchart that corresponds to the design of your program. ● Major Implementation Issues: What were the most difficult parts of your program to implement? Known Bugs and/or Errors: List all the known bugs and/or errors of your program. After extensively testing your program, you should be aware of (nearly) every issue it has. How does your program handle bad input? How does your program handle edge cases? This section is a space for full-disclosure; what’s wrong with your program? Lessons Learned: ● What went well ● 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 have done differently to promote learning General Tips ● It is expected that you use as much formal (bland) language as you can. 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 to the point. Be descriptive enough that your audience can understand the problem and your solution, but strive to be concise. ● Focus on the work accomplished rather than the process used to complete the work. Links to other resources Jeff Atwood's Programming Blog Web Design Game Development Practice Programming Online Enter Coding Competitions << Previous: Psychology Next: Scientific Lab Reports >> Last Updated: Sep 24, 2021 10:59 AM URL: https://libguides.lmu.edu/writing Print Page Login to LibApps Report a problem Subjects: Research Tools, Writing
