Project Report Assignment | Buy assignments online
Please check the attachments
Interim Report Structure
Structuring your interim report
Like all academic writing, your interim report consists of three parts: an introduction, a body and the conclusion. While some general advice is provided below, the body of your interim report will be determined by your topic, the available literature and the broader requirements of the project
You are also required to write an abstract for your work that provides a summary of your research.
The abstract should include:
- Purpose/Motivation: research questions, relevance & context of the project (one or two sentences).
- Design/Methodology/Approach: Explain the methods used for the data collection in your project (this includes literature; and other analyses your project requires)
- Results/Findings: Briefly outline the results of your systematic search; the consistent themes, any gaps if appropriate (one or two sentences).
- Conclusion: final assessment of the overall evidence and how it will help you conduct the rest of your project (one or two sentences).
The introduction should include:
- the nature of the topic under discussion (the topic of your project)
- the reason for the project
- relevance
- the research questions addressed
- the parameters of the topic (what does it include and exclude)?
The body paragraphs should include:
Methodology/methodologies
Research project | Implementation projects | Maths projects |
· Searching the literature
o targeted search: identify names, dates databases, professional sources searched o Search strategy: keywords, phrases used · Literature/article selection o Why information was included and/ or excluded? o What specific topics of interest were targeted? · Evaluating the evidence o Study design classification? (in the articles selected, did you look at the types of methods used to report findings) |
· This should include information about how you found your peer reviewed/professional sources
· You also need to detail what our methods were using for researching your project (ie requirements analysis for software) |
· Requirements for this assessment need to be negotiated with your supervisor and the co-ordinator.
|
Results
Research project | Implementation projects | Maths projects |
· Literature collection and selection
o How many sources collected o How many reviewed o How did you classify organise the literature? (eg methodologies and methods in use; general conclusions that are being drawn) · Critical evaluation and synthesis o What are the key themes and ideas common in the literature o What contradictions/ inconsistencies did you find? o What relationships did you find between articles o What gaps did you find? |
· You should discuss the results of each of the tasks you undertook to gain data for your project
· You then need to synthesise this information to show how you will then use this in the next part of the project |
· Requirements for this assessment need to be negotiated with your supervisor and the co-ordinator.
|
Discussion
- Examining the evidence
- What does the evidence mean overall? Explain the information found. What answers did you find to your research questions?
- What gaps did you find?
- What else needs to be done?
- Implications
- From the information found, what will you do to implement your project?
- What processes/information/practices do you need to use/follow to successfully complete your project?
The conclusion should include:
- Summarise findings
- Restate the purpose of your review
- Describe the overall evidence: a summary of major findings (agreements and disagreements)
- A summary of general conclusions that are being drawn.
- A summary of where your project sits in the literature and how your research will help you conduct your project.
- What has been gained from the review
- What is your take home message?
Project Formatting Guidelines Checklist
Complete this checklist for your project documentation.
NOTE: This is assessable as part of your project plan and needs to be submitted with the plan
Format issue | Details | Checked |
Format | All assessment tasks (except the journal) should be submitted as a Word document | |
All documentation should be a single word processed document unless special circumstances are required. | ||
Project Title | A title of not more than 16 words should be provided. | |
Title Page | A Title Page should be submitted with each individual project submission. | |
Title page should have the following information:
· Author Details · Abstract (Lit Review and the final Report) · Keywords (Lit Review and the final Report) |
||
Author Details | Details should be supplied on the Title Page including:
· Full name of the author · E-mail address of the author |
|
Abstract | · A structured abstract should be included on the Title Page, | |
Abstract should address the following:
· Motivation or Problem Statement · Objective of the project · Methodology/Approach · Results/Findings · Implications · Limitation Please note -the list is suggestive and not mandatory |
||
· Maximum 250 words in total (including keywords). | ||
Keywords | · Provide no more than 5 keywords on the Title Page, | |
· Keywords should encapsulate the principal topics of your project | ||
Project Topic | · Include the original project topic outline that you chose for your project
· This should be the second page of your document. |
|
Headings | · Headings must be 7 words or less | |
· There should be a clear indication of the distinction between the hierarchies of headings. | ||
· Headings should have a numbering system that matches the heading levels. | ||
· First level headings to be presented in bold format 18 pt | ||
· Subsequent sub-headings to be presented in medium italics 14 pt. | ||
· Further headings (level 3) should be bold 12pt | ||
Presentation | · Writing should be presented in clear, concise English. | |
· Fonts should be Calibri or Helvetica, 11 point font | ||
· Spacing should be double or 1.5-line spacing throughout | ||
· Margins: use standard margins | ||
· Page numbers: All pages of your documents must be numbered consecutively, including appendices and references | ||
· Page numbers should appear in a footer on the right of each page. |
Notes/Endnotes | · No notes or endnotes | |||||||||||||||||||||||||||||
Table of Contents | · Table of Contents should be automatically generated based on your Word headings. | |||||||||||||||||||||||||||||
Figures | · All Figures (charts, diagrams, line drawings, web pages/screenshots, and photographic images) should be included in the body of your documents. | |||||||||||||||||||||||||||||
· Ensure that all images are of reasonable quality and easily understood | ||||||||||||||||||||||||||||||
· All figures should be labelled appropriately and referred to in the body of the document. | ||||||||||||||||||||||||||||||
Tables | · Tables should be included in the main body of the article. | |||||||||||||||||||||||||||||
· All Tables should be labelled appropriately and referred to in the body of the document. | ||||||||||||||||||||||||||||||
· Ensure that any superscripts or asterisks are shown next to the relevant items | ||||||||||||||||||||||||||||||
References | · References to all publications must be in Harvard style and carefully checked for completeness, accuracy and consistency. | |||||||||||||||||||||||||||||
· In-text citations :Cite publications in the text: | ||||||||||||||||||||||||||||||
· Citing one author- use the first named author’s name and date (Adams, 2006) Make sure you use the family name | ||||||||||||||||||||||||||||||
· Citing two authors, (Adams and Brown, 2006) | ||||||||||||||||||||||||||||||
· Citing three or more authors (Adams et al., 2006). | ||||||||||||||||||||||||||||||
· Reference list should be at the end of each project document before any appendices | ||||||||||||||||||||||||||||||
· Reference list should be in alphabetical order | ||||||||||||||||||||||||||||||
Books | Formatting for books should be as follows:
Norman, D 2002, The Design of Everyday Things, Basic Books. |
|||||||||||||||||||||||||||||
Formatting for journals should be as follows:
Patnaik, D & Becker, R 1999, ‘Needfinding: The Why and How of Uncovering People’s Needs’,Design Management Journal, Spring , pp. 37-43.
|