[Last name, First name, Student number] [Lab number, Date] Introduction [Give a brief overall account of what was investigated/studied/designed, the aims of the exercise and the purpose or point of completing the exercise.] Methodology [Give a brief account of the strategy or plan of action used to complete the aims and tasks of the lab. Note that if the lab consists mainly of following the instructions given in the lab script then you don't have to copy/paste them here, but if the lab involves producing your own methodology or design development process then outline it in this section] Design [Include details of any design/debugging work, calculations, flow diagrams, programme code etc. used to complete the lab tasks. Results [Include any data, simulation results, screenshots/photos or other results as appropriate.] Discussion [Comment of the results and their interpretations. Some questions to consider might be: Are the results reasonable or as expected? Did the results show any noteworthy trends? What is the significance of the results? Were there any particular issues that came up along the way? This is an important section and it has a significant impact on your grade. It allows you to demonstrate that you are capable of independent thought and make sense of the lab activities and results. Do not assume that your results speak for themselves or leave it to the reader to work out their significance.] Conclusion A short section, possibly even just a single paragraph, to summarise what you have found and learned. Notes: i. Write in the 3rd person (for example, 'The wire was connected' rather than 'I connected the wire'). ii. Every figure (schematic, graph, photo etc.) and table should be numbered and labelled. It should also be referred to somewhere in the main body of the report. Don't assume figures are self-explanatory—make it clear why it is being included and what it is meant to show. [ELEE1064] Adv. Hardware Systems & Design Page 2 of 2 iii. Don't scatter bits and pieces of information all over the place. Keep information relevant to the section that it is in. iv. Full code listings can be included in an appendix to the report. v. Be concise.