Final Year Project Report Best Practices

Most reports have front matter (declaration, abstract, contents), an introduction, a literature review or review of existing products, requirements and design, implementation, testing and evaluation, results and discussion, conclusions and future work, references and appendices. Development and research projects often use different outlines, so follow your department's format.

It depends on your university and department. HEC Pakistan's Graduate Education Policy 2023 gives the benefit of doubt up to 19% for MS and PhD work, with no uncited single source at 5% or more, and India's UGC 2018 regulations treat up to 10% as minor for masters and research theses. Undergraduate projects usually follow a department rule, so ask your FYP coordinator.

Use whatever your department specifies. Computing and engineering departments commonly use IEEE, with numbered citations in order of first appearance. Some programmes use APA, with author and year in the text and an alphabetical reference list. Whichever you use, apply it consistently.

Only within your university's and supervisor's rules, which vary widely. Where it is allowed, use it to explain, check and brainstorm rather than to write sections, disclose your use in the required format, verify everything it produces and make sure you can explain every sentence and line of code yourself.

No. Turnitin says the similarity score only measures matching text and does not decide whether plagiarism happened. A low score can still hide uncited ideas or figures, and a higher score can come from properly quoted and cited material.

Generally not in the main chapters. Describe algorithms and key logic with pseudocode or short snippets, and put longer listings in an appendix or link to the repository. Check whether your department wants the code submitted separately.