PROJECT TITLE
Project/Internship Proposal
FOR PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE
OF
BACHELOR IN INFORMATION TECHNOLOGY AWARDED BY
PURBANCHAL UNIVERSITY
SUBMITTED BY
Name – roll no
COLLEGE LOGO
COLLEGE OF INFORMATION TECHNOLOGY AND ENGINEERING
(CITE)
DEPARTMENT OF COMPUTER SCIENCE
SUBIDHANAGAR, TINKUNE, KATHMANDU
March, 2018
GUIDELINES FOR Project/Internship Proposal
CITE students submitting their project proposal should strictly follow the given
general guidelines.
1 Format guidelines for proposal
1.1 Size and Margins
1.1.1 A4 is the recommended report size.
1.1.2 The top, right and bottom size margins should be 1 inch, whereas the left
side margin should be 1.25 inch for both textual and non-textual (e.g.,
figures, tables) pages.
1.2 Line Spacing
The general text of long tables, quotations, footnotes, multi-line captions and
bibliographic entries (references) should be in single spacing (6 lines per inch),
with text size in 12 points.
1.3 Text Format
1.3.1 Font should be Times New Roman of size 12 points (for normal text).
1.3.2 1. Heading1/Title (14 points, Bold).
1.1 Heading2/Sub heading (12 points, Bold).
1.4 Latex
APA Format.
2 Organization
2.1 The Title (or Cover) Page
An effective title clearly describes the purpose of the paper in a single statement or
question.
Title should be catchy and specific to domain not broad.
It should not so long, minimize use of many words.
Try to give your application/product a good name.
2.2 Abstract (Optional)
An abstract is a summary of the information in a document.
It should not exceed 250 words.
It should be written in one paragraph.
It should be written in the past tense as it refers to work done.
Long words should be followed by its abbreviation which would be used throughout the
abstract and proposal.
It should never give any information or conclusion that is not stated in the proposal.
2.3 Table of Contents
2.4 Introduction
Introduction discusses the meaningfulness of the study along while it presents the
problem or issue.
Introduction is short and right to the point of information.
Write what exactly your project does.
2.5 Problem Statement (Why have you chosen this topic?)
Make it critical.
The problem should be stated in such a way that if there is no project there would be a
great loss/impact.
2.6 Objective
Mention the main aim of your project, think about the outcome.
Always start from To.
Objectives should be: specific, measurable, achievable, realistic, time bound.
2.7 Scope and Limitation
In scope:
Write about what consequences your project outcome can bring.
Mention what extra feature you would like to add, or write about the scalabity and
extendability of your product.
You can write about what impacts it can create when it goes on large scale.
In limitation:
Write about some of the things you couldn’t include but always wanted to.
Mention the performance limitations, real time working dependence.
Writing about the accuracy of the data you take and processed result will make your
proposal more precised.
2.8 Methodology
While talking about the software development model in our case, in methodology you
write about the methods you are going to use to achieve your objectives. Its main
content should be:
2.8.1 Software Development Model (with justification)
You mention which software development life cycle model you will be
using, and the reason for choosing this model despite of other models.
2.8.2 Study of existing system (Literature Review)
Literature review is the study and research of similar systems/applications
that are already developed or are already in market which are in some way similar to
yours.
You can include at most 5 websites, apps , books etc. that are someway
related to your project or give you inspiration to do.
2.8.3 Data Collection (Requirement Collection)
In data collection, you mention how you are going to collect various data
that are needed for your project development.
Mention about the primary and secondary sources of your data.
Some of the data sources might be review, questionnaire, web surfing, site
visiting etc.
2.8.4 Requirement Analysis
Change user requirement into system requirement.
Group to functional and nonfunctional requirement.
2.8.5 Feasibility Analysis (Possible or not)
Write about the feasibility of your product after development.
Mention about various feasible areas like operational, economical,
technical etc.
2.8.6 Testing
When you develop an application/ software testing is inevitable to
minimize various errors and make your product more accurate and
optimized.
In this section, briefly write about the different testing approaches you will
be using like: Unit testing, Integrated testing, System testing, Acceptance
testing.
2.8.7 Tools used
We make use of different available tools and technologies to develop our
product.
In tools used section we mention the various such tools we will be using or
are planning to use.
Just write their purpose and recommended is their versions for use
don’t write definition of tools.
2.9 Overview of system
Pictorial representation of your system comes under overview of the system.
Diagram should explain how the overall system works.
You can include any of the following:
Use Case Diagram or Flowchart or DFD (best to use this), Decision Table, ER Diagram
etc.
2.10 Time schedule (GANTT chart)
In time schedule, you give the brief summary of how much time the project will
take including all steps.
Represent them in GANTT chart.
To show the projected time planning.
2.11 Expected outcome
Write about what your product should do.
Must be meet the objective.
2.12 Bibliography
Mention books, publications and their authors that you may reference to somewhere
during the project.
