Scribd
Upload
10 views3 pages

Full-Stack Development Report Guidelines

The document outlines the structure and guidelines for preparing a final report for the COCS 32133 Full-Stack Software Development course. It includes sections such as the title page, abstract, introduction, background, design, implementation, and discussions/conclusions, along with formatting requirements. Emphasis is placed on avoiding plagiarism and adhering to Harvard/IEEE referencing style.

Uploaded by

chathun18333alwis
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
10 views3 pages

Full-Stack Development Report Guidelines

The document outlines the structure and guidelines for preparing a final report for the COCS 32133 Full-Stack Software Development course. It includes sections such as the title page, abstract, introduction, background, design, implementation, and discussions/conclusions, along with formatting requirements. Emphasis is placed on avoiding plagiarism and adhering to Harvard/IEEE referencing style.

Uploaded by

chathun18333alwis
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

COCS 32133- Full-Stack Software Development

Guideline for the preparation of the final report

Structure of the final report:

Title Page
Abstract
Acknowledgements
Table of Contents
Table of Figures (if available)
1. Introduction
1.1 Motivation
….
2. Background
2.1 …
….
3. Design
3.1 …
….
4. ….
5 ...
…
…
References

Font type: Times New Roman References


Font size: 12 points

Line spacing: 1.5


Recommended contents:

Title page

 Project title
 Submitted by whom (group number and student details)
 Faculty/University
 Month/Year

Abstract – Maximum one page

1. Introduction

 Motivation for carrying out the project


 Project objectives
 Scope of the project
 Limitations

2. Background

 Description of the wider context of the problem


 A literature review on any theories associated with the problem, existing solutions, their
limitations, and why they are not suitable in this case
 Methods or tools that could be used in your solution

3. Design

 Overall design proposed


 Include necessary diagrams and describe them in the text
 Selection of the section to be implemented (with justification)
 Detailed design of the section to be implemented (description and diagrams)

4. Implementation
 Technologies used
 User interface design
 Reports generated

5. Discussions and conclusions

 Overall discussion on the process followed in conducting the project and its outcomes
 Conclusions
 Proposed future work
Important:

 Avoid plagiarism – it is an offence

 Follow the Harvard/IEEE Referencing Style for references.

You might also like