Scribd Logo
Upload

Welcome to Scribd!

  • 55 views

    Mobot Report Guidelines

    Uploaded by

    Conor Dillon-Leetch
    The document outlines guidelines for a final report on a mobot project, including that it should be individually written and submitted as a PDF with the code included in an appendix. It should follow a standard format with numbered sections and subsections, and include major sections on introduction, development, conclusions and recommendations, bibliography, software, and presentation. The development section should discuss problems encountered and solutions, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Mobot Report Guidelines

    Uploaded by

    Conor Dillon-Leetch
    55 views2 pages
    The document outlines guidelines for a final report on a mobot project, including that it should be individually written and submitted as a PDF with the code included in an appendix. It should follow a standard format with numbered sections and subsections, and include major sections on introduction, development, conclusions and recommendations, bibliography, software, and presentation. The development section should discuss problems encountered and solutions, and test results.

    Original Description:

    DCU Mobot report guidelines

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines guidelines for a final report on a mobot project, including that it should be individually written and submitted as a PDF with the code included in an appendix. It should follow a standard format with numbered sections and subsections, and include major sections on introduction, development, conclusions and recommendations, bibliography, software, and presentation. The development section should discuss problems encountered and solutions, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    55 views2 pages

    Mobot Report Guidelines

    Uploaded by

    Conor Dillon-Leetch
    The document outlines guidelines for a final report on a mobot project, including that it should be individually written and submitted as a PDF with the code included in an appendix. It should follow a standard format with numbered sections and subsections, and include major sections on introduction, development, conclusions and recommendations, bibliography, software, and presentation. The development section should discuss problems encountered and solutions, and test results.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 2

    Mobot report guidelines

    The final report is an individual report - independently written by each person. The report should
    be submitted as a single PDF file. Your InteractiveC program code must be included in an
    appendix.
    Each report must have an official school continuous assessment cover page.
    The recommended length for the report is approximately 10 typed A4 pages. This should include
    diagrams and photographs where appropriate. Your IC code for your robot should be included in
    an Appendix. The report must be divided into numbered sections and subsections, with suitable
    headings, for example:
    1. Introduction
    2. Development
    2.1 The HandyBoard
    2.2 Lego Chassis Design
    2.2.1 Gearing Ratios
    and so on.
    The overall format must include the following major sections (the approximate mark allocation,
    from the total 40% for the report, is shown in brackets):
    1. Introduction (3%)
    This should briefly outline the project as it was originally presented to you. This should
    encapsulate your understanding of the project and its objectives and not just a re-statement of
    these notes!
    2. Development (15%)
    This should record your team's experience in developing your robot and how you worked
    together. It might have subsections for the HandyBoard, the motor arrangement, the sensors, the
    software etc. It should clearly present the specific problems you encountered, and what
    measures you took to overcome them--and should clearly state whether problems were, in fact,
    solved. You discuss the final status of your robot. This should clearly explain the extent to which
    your robot finally met the requirements of the project. Avoid wild or sweeping statements (``it
    worked flawlessly''). Just confine yourself to specifying what tests of the overall functionality you
    carried out, and and what the results of such tests were. This is where you can reflect on your

    contribution to the team's efforts.


    3. Conclusions and Recommendations (5%)
    This should be a short section presenting 3-5 concluding remarks or recommendations--either
    directed at the organisers of the module, or future students. These may be positive or negative,
    but should be supported by the discussions presented earlier in the report.
    4. Bibliography (2%)
    This should provide references to any books, articles etc., which you found useful in carrying out
    the project. The information provided should be sufficient for any interested reader to locate a
    copy of the original document. References to online materials should include a URL. Each entry
    in the bibliography should be numbered. References to entries in the bibliography may appear in
    the body of your report using these numbers enclosed in square brackets (e.g., ``See [6,9] for
    more information on battery technologies and capacity.'').
    Note carefully that your report must not contain significant material directly copied, or
    paraphrased, from the HandyBoard manual, or the online notes, or any other publication. Where
    appropriate, simply refer to these publications (including them in your bibliography), without any
    need for extensive quotation.
    5. Software (10%)
    As already noted, software listings should be included as attachment(s) to the report. 10% of the
    overall marks will be awarded for these. Criteria here will include such things as whether the code
    is appropriate, intelligible, consistently indented, uses relevant variable and function names, etc.
    6. Presentation (5%)
    The final 5% of the marks will be awarded for the overall presentation of the report. The
    presentation must be professional--i.e., demonstrating a satisfactory standard of grammar,
    punctuation, spelling, etc. Avoid excessive informality, such as slang words etc. Ensure that any
    technical terms you use are appropriate to the context.

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy