0% found this document useful (0 votes)
17 views5 pages

BTech 400 Report Writing Format

This document outlines the thesis structure and formatting requirements for BTech students in Software Engineering, Information Technology Security, and Game Development. It specifies the layout, preliminary pages, chapter organization, referencing style, and project guidelines. The thesis should be between 50 to 70 pages, formatted in Times New Roman, with specific citation and bibliographical referencing rules.
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
0% found this document useful (0 votes)
17 views5 pages

BTech 400 Report Writing Format

This document outlines the thesis structure and formatting requirements for BTech students in Software Engineering, Information Technology Security, and Game Development. It specifies the layout, preliminary pages, chapter organization, referencing style, and project guidelines. The thesis should be between 50 to 70 pages, formatted in Times New Roman, with specific citation and bibliographical referencing rules.
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
You are on page 1/ 5

THESIS OUTLINE FOR BTECH (SWE, ITS & GWD)

1. GENERAL LAYOUT
a. Cover Page should be PURE WHITE containing Landmark letterhead, topic,
department, student’s name, supervisor’s name, year and registration number.
b. The volume should be at least 50 pages (from chapter one) and not more than 70 pages.
c. Margins: normal (2.5cm on both sides)
d. Font type should be Times New Romans
e. Font size should be 12
f. Spacing 1.5 spacing.
g. Headings should be in upper case and in bold and centered.
h. Sub headings should be in bold and justified. Only initials of content words should be in
upper case. All function words (e.g. a, an, the, and etc) should be in lower case.

STRUCTURING THE WORK

2. PRELIMINARY PAGES (Numbered in Roman numerals. i, ii, iii, iv etc)


i. Table of Contents
ii. Dedication
iii. Acknowledgments
iv. List of Abbreviations and Acronyms
v. List of Tables (if any)
vi. List of figures (if any)
vii. Abstract (should include at least four key words)
3. CHAPTER ONE : GENERAL INTRODUCTION (Numbered in Arabic numerals.
1.1., 1.2, 1.3, etc)
1.1. Introduction
1.2. Background to Study
1.3. Statement of the Problem
1.4. Objectives of the Study (General and Specific Objectives)
1.5. Significance of the Study
1.6. Scope of the Study
1.7. Definition of Terms
1.8. Organization of the Study
3. CHAPTER TWO: LITERATURE REVIEW

2.1. Introduction
2.2. Review of Related Concepts or Conceptual Framework
2.2.1. ……
2.2.2. …….
2.2.3. …….
2.3. Review of Related Works (Review at least 5 works and at most 10 works. In each review;
document the project’s Name, Author(s), Technology Used, Strength(s),
Limitations/Recommendations for future works)
2.3.1. ….
2.3.2. ….
2.4. Propose Solution (Include the Architecture of the proposed System)

4. CHAPTER THREE: MATERIALS AND METHODS USED (follow this chapter


following your project topic and/or your specialties and their uniqueness. You will find below
a guide for various projects aligned to specialties and their uniqueness)

3.1 Introduction
3.2 Development (s) Methodology Used
3.2.1. . . .
3.2.1. . . .
3.3 Tools and Material Used
3.3.1 Hardware Requirements
3.3.2 Software Requirements
3.4 System Modules
3.5 System Analysis
3.5.1 Functional Requirements
3.5.2 Non-functional Requirements
3.5.3 Cost Evaluation
3.5.4 Project Schedule
3.5.5 Use Case Analysis
3.5.6 Sequence Diagram (s)
3.5.7 Activity Diagram
3.6 System Design or Network/Architecture Design (SWE and GWD related projects use System
design while ITS uses Network/Security Architecture Design)
3.6.1 System/Network/Security Architecture (use where applicable)
3.6.2 System Network/Security Design Strategy (use where applicable)
3.6.3 Class Diagrams (use where applicable)
3.6.4 Entity-Relationship-Diagram (use where applicable)
3.6.5 Data Dictionary (use where applicable)

5. CHAPTER FOUR: IMPLEMENTATION, RESULTS AND TESTING


4.1. Introduction
4.2. Implementation
4.2. 1 .......
4.2. 2 .....
4.2. 3 ....
.
.
.
4.3. Results
4.3.1 . . . . . .
4.3.1 . . . .
4.3.1. . . .
.
.
.
4.4. System Testing Strategies
4.1 Unit Testing
4.3.1 Integration Testing
4.3.1 System Testing

Note that your figures be presented and discussed under different figures.

6. CHAPTER FIVE: SUMMARY OF FINDINGS, CONCLUSION AND


RECOMMENDATIONS

5.1. Discussions
5.2. Conclusions
5.3. Recommendations
5.4. Perspectives for Further Study
7. REFERENCING STYLE

7.1. IN-TEXT CITATIONS


7.1.1. For indirect quotations, write the name of the author, the year and the page number in
brackets. The author’s name should be separated from date with a comma. In case there are
two or more authors who have to be cited, each author should be separated from the other
with a semi column. E.g. (Van Djik, 2008, p. 3) or (Van Djik, 2008, p. 3; Fairclough, 1992,
p. 45; Wodak, 2001, p. 89).
7.1.2. For indirect quotations from web sites, put the web site as a footnote and indicate the day,
time of the day and year it was accessed.
7.1.3. For direct quotations that are less than four lines, put them in quotation marks (“……”)
followed by the name of the author, year and page number.
7.1.4. For direct quotations that are four lines or more than four lines, they should be withdrawn
from the main text by 1cm to the left followed by the name of the author, year and page
number. Eg.

CDS can be defined as fundamentally interested in analysing hidden, opaque, and visible
structures of dominance, discrimination, power and control as manifested in language. In
other words, CDS aims to investigate critically social inequality as it is expressed,
constituted, legitimized, and so on, by language use (or in discourse). Most critical
discourse analysts would thus endorse Habermas’s claim that ‘language is also a medium
of domination and social force. It serves to legitimize relations of organized power…
(Habermas, 1967, p. 63).

7.2. BIBLIOGRAPHICAL REFERENCES


7.2.1. They should be organized alphabetically without numbering
7.2.2. Scientific books should have the full name of the author, year of publication in brackets,
title of book in italics, publishing house and the place (city or town of publication). E.g.
Chilton Paul, (2004), Analysing Political Discourse, Routledge, London and New York
7.2.3. Scientific books with more than one author and less than four should have the full names
of the authors, year of publication in brackets, title of book in italics, publishing house and
the place (city or town of publication).
Jim Mckinley & Heath Rose, (2020), The Routledge Handbook of Research Methods in
Applied Linguistics, Routledge, Taylor & Francis Group, London and New
York, 1st edition
7.2.4. Scientific books with four or more than four authors should have the full name of the
first followed by et al (meaning and others) author, year of publication in brackets, title of
bookin italics, publishing house and the place (city or town of publication).
WODAK, Ruth et al (1999), The Discursive Construction National Identity’, Edinburgh
University Press, Edinburgh
7.2.5. All these conditions should apply to scientific articles. However, titles of articles should be
in quotations marks while the titles of journals in which they are published should be in italics,
and then followed by the volume, issue number and range of pages. E.g.
Abbas Deygan, D. & Hussein Dhahi M. (2016), ‘Representation of the Syrian Crisis in the
American Political Speeches: A Critical Discourse Analysis’, International Journal of
Language and Linguistics, Vol. 3, No. 1, pp. 40-48
7.2.6. For internet sources, see the example below.

AIJMER Karin, (2016), “Modality and Mood in Functional Linguistic Approaches”, Retrieved
from www.oxfordhandbooks.com on 13th October 2020 at 4: 32 am.

8. Project Guidelines for BTech Supervision (these guidelines are applicable for the nature of our
projects and not necessarily your various specialties. Use the guide where applicable and ensure
to discuss with your supervisor(s)).

You might also like