Guidelines for Project Proposal

Requirements for Report Writing:

Report should meet following standards:

Font Name: Times New Roman

Left Margin: 1.5 inch

Right Margin: 1.25 inch

Top Margin: 1.25 inch

Bottom Margin: 1.25 inch

Header and Footer: 0.5 inch

Line Spacing: 1.5

Paragraph Spacing: 18 pt

Font Size: 12 pt (for normal text)

Follow following standard for headings

1. Heading1 (16 pt, Bold)

1.1 Heading2 (14 pt, Bold)

1.1.1 Heading3 (12 pt, Bold)

 Affiliated to Pokhara University

UNITED TECHNICAL COLLEGE

UNIVERITY LOGO

A Minor Project Proposal

on
PROJECT TITLE
[Code No:…….]

(For partial fulfillment of _______ Year/Semester in Computer Engineering)

Submitted by

Name(Roll No.)
………
Name(Roll No.)

Submitted to
Department of Computer Engineering

May 23, 2023 (Submission Date)

 ABSTRACT
The abstract should provide a concise summary of the project. It must address the following:
 What: Brief description of what the project is about.
 Why: The purpose and significance of the project.
 How: Tools, methods, or processes used to implement the project.
 Expected Outcome: Anticipated results or deliverables.

Word Limit: 150-200 words

Structure:
 Background: 1-2 sentences
 Objective/Purpose: 1-2 sentences
 Methodology/Tools: 1-2 sentences
 Expected Outcome: 1-2 sentences
 Conclusion: 1 sentence

Keywords: (keywords of your project that describe your project) For eg.
Procedural programming, file, information.

Keywords: Up to 5 keywords related to the project

 TABLE OF CONTENT
The page number from abstract to Acronyms should be in Roman number. Actual page
numbering of document starts from first chapter of the document which in introduction section.

TABLE OF CONTENTS

TITLE PAGE NO.

Acknowledgement i
List of figures iii
List of tables iv
List of symbols v
Abbreviation vi
Chapter 1: Introduction 1

1.1 ………….. 1

1.2 …………. 2

1.2.1 ………. 5

1.2.2 ........... 6

1.2.2.1 ………. 10

Chapter 2: Related Works 12

2.1.
.
.
Chapter 3: Design and Implementation 18
Chapter 4: Conclusion 20
Reference 22
Appendices 23
 LIST OF FIGURE
It gives information about all the figures used in the documentation. All figures used in the report
should be listed, used during explanation of the works.

For e.g.

Figure Page no.

1.1 Computer Architecture 5

4.2 Figure xyz 15

….

…..

Here 1.1 specifies, it is a first figure of chapter 1, and 3.2 specify it is second figure of chapter 3.
 LIST OF TABLE (IF ANY)

It should give information about all the tables used in the documentation. Figures and table
should be given appropriate title.

(Similar to that of List of Figures)

 ACRONYMS/ABBREVIATIONS (IF ANY)
The list all abbreviations used in the documentation is included in this section (alphabetical order).

For.e.g

DMA Dynamic Memory Allocation

RAM Random Access Memory

VR Virtual Reality
 CHAPTER 1
INTRODUCTION

Introduction heading includes following subheading. The font size for title should be 16 bold,
heading 14 bold and subheadings 12 bold. Paragraph should content line spacing of 1.5 with
font size of 12. Preferable font type is Times New Roman.

1.1. Background
It should include basic information in the field of project work. What are the recent trends
and development on area of the project should be briefly discussed in this topic.

It should contain at least 2-3 paragraphs, having 200-400 words.

It should include:

Recent development in the field

Drawbacks and significance of existing works

1.2. Problem Statement

Clearly state the problem that the project aims to address.

1.3. Objectives
What is basic purpose of your project. List the objectives of your project work in bullets (not
exceeding 4).

1.4. Motivation and Significance

Motivation to choose the topic, importance and contribution of your project work is included
in this section.

Why did you choose this particular topic as your project ?

How does the work address drawback of existing system?

How is it different from the existing works?

It consists of short paragraph about features of your project work. A brief introduction of features
that project is going to address, helps to make the project proposal more robust.

1.4. Scope of the Work

Define the boundaries and limitations of the project.

 CHAPTER 2
RELATED WORKS

It focuses on discussion of similar types of other task/projects, that has been performed earlier.

It should include recent projects, works, website, etc. as reference.

Referencing should be in APA format.

According to (John, 2012), Management System should include components of…

Thapa and Shrestha (2010) have done similar project where they have implemented…

The Minesweeper (Rai & Parajuli, 2012) has features like….

The similar kind of project work(mention authors along with their works) were performed
earlier which has properties…

In writing this section , your purpose is to convey to your reader what knowledge and ideas have
been established on a topic, and what their strengths and weaknesses are. (D Taylor, “The
Literature Review: A Few Tips on conducting it”). It also should include previous work,
comparison between works, drawbacks and current work.

As well as this chapter focuses on understanding the current systems, tools, or approaches similar
to the project. Structure this section as follows:

 Overview of Existing Systems

o Describe the currently available systems or projects related to the topic.
o Include examples of software, tools, applications, or solutions with relevant
details.

 Comparison of Features
o Compare the key features of the existing systems.
o Highlight strengths and weaknesses.
o Example:
System A: Brief description, features, drawbacks.
System B: Brief description, features, drawbacks.

 Gaps in Existing Systems: Identify shortcomings, limitations, or inefficiencies in the

existing systems.

 Significance of Proposed Work: Describe how your project improves upon existing systems
or addresses identified gaps.
 CHAPTER 3
METHODOLOGY

The Design and Implementation section of a project proposal outlines the approach, tools, and
methods employed to achieve the project's objectives. This section typically begins with an
explanation of the overall strategy, highlighting its effectiveness, relevance, and any innovative
aspects.

Provide a brief overview of the overall approach taken to design and implement the project.
Mention the key technologies and tools used.

3.1. Requirements Gathering

 Objective: Define how the key requirements and goals of the project were identified and
documented.
 Techniques Used: Methods such as literature reviews, stakeholder consultations, or data
analysis could be employed.
 Tools: Tools such as spreadsheets, collaboration platforms (e.g., Google Forms, Notion),
or research management software used for requirement documentation.

3.2. System or Model Design

 Overall Framework: Outline the conceptual or architectural framework used, whether

it's a system architecture (e.g., client-server, distributed systems) or an ML pipeline.
 Core Components: Describe elements such as feature engineering, algorithm selection,
or system modules.
 Prototyping and Visualization: Mention tools like Figma, Matplotlib, or PowerPoint
used for prototyping or conceptual visualization.
3.3. Technology Stack

 Primary Technologies: Highlight the tools and platforms central to the project, such as
programming languages (Python, R, JavaScript) or ML libraries (TensorFlow, PyTorch,
scikit-learn).
 Infrastructure: Include computing resources (e.g., cloud platforms like AWS, GCP, or
local servers).
 Data Management: Tools or databases (e.g., MySQL, MongoDB, or BigQuery) used for
data storage and retrieval.
 External Integrations: Mention APIs, datasets, or external services integrated into the
project.

3.4. Development Process

 Approach: Describe methodologies such as Agile for iterative development or CRISP-

DM for data-driven projects.
 Version Control: Specify tools like Git for managing code or research versions.
 Collaboration and Task Management: Tools like Trello, Asana, or GitHub Projects
used to organize and monitor tasks.
 CHAPTER 4
EXPECTED OUTCOME

The expected outcome section of a project proposal should clearly state the specific changes
or results that the project aims to achieve. It should be specific, measurable, achievable,
relevant, and time-bound (SMART).

The expected outcomes should be directly related to the problem or need that the project is
addressing. They should also be aligned with the project's goals and objectives.
 CHAPTER 5
CONCLUSION

Summarize your overall proposal. The conclusion should not contradict with the objectives
of the project.
 REFERENCE

It is list of books, resources, internet links, magazines, research papers etc.that help your work
as reference during your project duration. Reference should be included in APA format. APA
format for reference and citation can be generated in different word processing software,
including microsoft word.

For Reference format, Go through below mention site

https://www.citethisforme.com/citation-generator/apa

Example Reference:
Author, A. A. (Year). Title of work. Publisher. DOI/Link
 BIBLIOGRAPHY (OPTIONAL)
It includes listing of the books, Internet sources and other similar works that you take
use indirectly in designing, carrying out, and understanding your project.

Bibliography should be included in APA format.

 APPENDICES
Appendices are used to provide additional information that is relevant to the project proposal,
but may not be essential for the reader to understand the main body of the proposal.

Gantt chart:
The Gantt chart for the project is provided in Appendix A. The Gantt chart shows the start and
end dates of each task, as well as the dependencies between tasks.

Cost estimation (Optional):

The cost estimation for the project is provided in Appendix B. The cost estimation includes a
breakdown of the expected costs associated with the project, including labor costs, material
costs, and other expenses.