A Project Report On

PROJECT TITLE
(Capitalize each word)

By

1. Student Name
2. Student Name

Submitted to

DEPARTMENT OF (COMPUTER / EEE / Civil) ENGINEERING

LUMBINI ENGINEERING, MANAGEMENT AND SCIENCE COLLEGE

Bhalwari

[Completion year in AD]

 A Project Report On

PROJECT TITLE
(Capitalize each word)

In partial fulfilment of requirements for the degree of

Bachelor of Engineering in

Computer Engineering

BY:
1. Student Name
2. Student Name

Under the Guidance of

Prof. Name

DEPARTMENT OF (COMPUTER / EEE/CIVIL) ENGINEERING

LUMBINI ENGINEERING, MANAGEMENT AND SCIENCE COLLEGE

Bhalwari

[Completion year in AD]

Spine/Side view of the Report –

Project
TITLE

year
 CERTIFICATE (For individual student)

This is to certify that the project entitled “PROJECT TITLE” has been carried
out by a team of …. members under my/our supervision in partial fulfillment
of the requirements for the degree of Bachelor in Computer Engineering,
Electrical and Electronics Engineering, or Civil Engineering at Pokhara
University, Kaski, Nepal.
Student Name: (individual)

Date:
Place: Lumbini Engineering Management and Science College, Bhalwari

External Examiner
…………………..

Supervisor Head of Department

…………………….. ……………………..

Name: …………………………….. Name: ……………………………..

Designation: ……………………………..

Principal
………………

Er. ………
Lumbini Engineering Management and Science College

i
 CERTIFICATE (For university and college)

This is to certify that the project entitled “PROJECT TITLE” has been carried
out by a team of …. members under my/our supervision in partial fulfillment
of the requirements for the degree of Bachelor in Computer Engineering,
Electronics and Communication Engineering, or Civil Engineering at Pokhara
University, Kaski, Nepal.
Team
Student Name:
Student Name:
Student Name:
Student Name:

Date:
Place: Lumbini Engineering, Management and Science College, Bhalwari

External Examiner Supervisor

……………………… ………………………..
Name: ………………………….
Designation: ………………………….

Head of Department Principal

…………………………….. ………………………….
Name: ………………….. Name: ………….
Designation: ………………….. LEMSC

ii
 PROJECT APPROVAL CERTIFICATE

This is to certify that the project entitled “Project Title” submitted by the
following students:
• Student Name (PU Registration No.: ________)

• Student Name (PU Registration No.: ________)

• Student Name (PU Registration No.: ________)

• Student Name (PU Registration No.: ________)

This project has been carried out under my / our supervision, in partial
fulfillment of the requirements for the degree of Bachelor in Computer /
Electrical and Electronics / Civil Engineering at Pokhara University, Nepal.
The project embodies the original work of the students and has not been
submitted earlier for the award of any degree to this institution.
We hereby approve the project work as part of the academic curriculum.

Supervisor HOD (Head of Department)

…………………….. ……………………..

Name: …………………………….. Name: ……………………………..

Designation: ……………………………..

Principal
………………

Er. ………
Lumbini Engineering Management and Science College

iii
 ACKNOWLEDGEMENT

Acknowledgement should be prepared by their wording showing

their gratitude towards the department.

Student Name:
Student Name:
Student Name:
Student Name:

iv
 ABSTRACT

Abstract should include introduction in two sentences, methods/ simulation/ sample/ data
in the following two sentences, together with analysis and interpretation. It should
conclude with findings in brief, with the significance of the project.

The abstract should not exceed 250 words.

Keywords: introduction, methods, analysis, significance (3-7 words which represent the
project)

v
 FORMAT OF PROJECT REPORT
1. Paper Size: A4 size, 80 Gsm paper
2. Margins: Top: 1" Bottom: 1" Left: 1.25" Right: 1"
3. Line Spacing: 1.5 line
4. Title of Chapter
Font: Times New Roman (Bold face)
Size: 16 point
Alignment: Right Alignment
Note: One thick line (2¼ point weight) after the name of the chapter (Specimen-I)
5. Heading
First Order Heading: (for example -- 1. INTRODUCTION)
Font: Times New Roman (Bold Face)
Size: 16 point
Note: One blank line before the heading (12 points)
Second Order Heading: (for example -- 1.1. Evolution)
Font: Times New Roman (Bold Face)
Size: 14 point
Note: One blank line before the heading (12 points)
Third Order Heading: (for example -- 1.1.1. Image Processing)
Font: Times New Roman (Bold Face)
Size: 12 point
Note: One blank line before the heading (12 points)
6. Text
Font: Times New Roman
Size: 12 point
Alignment: Justified (full text)
7. Abstract (Up to 250 words)
Heading (i.e. ABSTRACT)
Font: Times New Roman (Bold Face)
Size: 14 point
Note: Double blank lines after the heading. (12 points)
 Remaining Text
Font: Times New Roman
Size: 12 point
Alignment: Justified (Full Text)
Keywords: Italic
*** (Note: Imported word from another language to be in italic) ***
8. Figures and Tables: Centered Placed
Caption:
Figure captions must be below the figure and centered.
Table captions must be above the table and centered.
Font: Times New Roman (Bold)
Size: 12 point
Alignment: Centered
9. Page Numbering (Centered)
The pages from the certificate page to the list of tables/figures/abbreviations/approvals
should be numbered in Roman starting from i. The pages from chapter 1 onwards
should be numbered in numeric starting from 1. The page number should be inserted at
the bottom, aligned center.
10. Citation and References / Bibliography
The listing of references should be in the references section. The references contain the list
of articles, books, URLs, etc., that are cited in the document. The books, articles, and other
that are studied during the study but are not cited in the document can be listed in the
bibliography section. The citation and referencing standard should be the IEEE referencing
standard. The text inside the document should be cited in IEEE style. The IEEE referencing
standard can be found on the web.
Note:
1. The Project Report must be Black colored Hard Bounded and golden-embossed lettering
and printed in Duplicate (i.e. Three Copies). A soft copy of the report, software and
supplementary documents in USB device must be submitted.
2. Three copies of the report should be submitted to the college (One for the University, one
for the college Library and one for the Research Management Cell). A copy of the relevant
supervisor is optional. Every student of the group may have their own additional copy.
3. For all the above three copies, the names of all the students in that group must be there on
the Cover page, First page, Certificate and in Acknowledgement. Personal copy of the
students must contain their names only on the Certificate.
4. The students have to write the report in their own words.
5. A draft copy of the report must be submitted 15 days before the time of presentation. The
line spacing of the main body must be 2.0.
6. A Final (specimen) copy of the report must be on time of presentation.
7. Four days after the final presentation, Black colored, hard-bounded and golden-embossed
lettering must be submitted for certification.
8. "Cover Page, First Page, Specimen Copy " words are only for students' instruction;
they should not be printed in the report.
9. The sequence of pages to be followed is as:
a. Cover & Title Page
b. Certificate Page
i. Supervisor Recommendation
ii. Head / Program Coordinator, Supervisor, Internal and External
Examiners’ Approval Letter
c. Acknowledgement
d. Abstract
e. Table of Contents
f. List of Abbreviations, List of Figures, List of Tables
g. Main Report
h. References / Bibliography (if any)
i. Appendices (Screenshots + Snippets of major source code components + Log of visits
to supervisor + datasets if any used)

11. Prescribed chapters in the main report

1. Chapter 1: Introduction
1.1. Background or Overview
1.2. Problem Statement
1.3. Objectives
1.4. Scope and Limitation
1.5. Development Methodology (Except civil)
1.6. Report Organization
2. Chapter 2: Literature Review
2.1.Description of fundamental theories, general concepts and terminologies
related to the project
2.2. Review of the similar/relevant projects, theories and results by other
researchers
3. Chapter 3: System Analysis (Methodology for civil dept.)
3.1. System Analysis
3.1.1. Requirement Analysis
i. Functional Requirements (Illustrated using use case
diagram/use case descriptions)
ii. Non Functional Requirements
 3.1.2. Feasibility Analysis
i. Technical
ii. Operational
iii. Economic
iv. Schedule
3.1.3. Analysis (May be Structured or Object Oriented)
If a structured approach:
• Data modelling using ER Diagrams
• Process modelling using DFD
If object-oriented approach:
• Object modelling using Class and Object Diagrams,
• Dynamic modelling using State and Sequence
Diagrams
• Process modelling using Activity Diagrams
4. Chapter 4: System Design (Optional for civil)
4.1. Design (May be structured or object-oriented as per the approach
followed in the analysis chapter)
If a structured approach:
• Database Design: Transformation of ER to relations and
normalizations
• Forms and Report Design
• Interface and Dialogue Design
If object-oriented approach:
• Refinement of Class, Object, State, Sequence and Activity
diagrams
• Component Diagrams
• Deployment Diagrams 4.2. Algorithm Details
5. Chapter 5: Implementation / Experiments and Testing
5.1. Implementation
5.1.1. Tools Used (CASE tools, Programming languages, Database
platforms)
5.1.2. Implementation Details of Modules (Description of
classes/procedures/functions/methods/algorithms)
5.2. Testing
5.2.1. Test Cases for Unit Testing
5.2.2. Test Cases for System Testing
 5.3. Result Analysis

6. Chapter 6: Conclusion
6.1. Conclusion
6.2. Future Enhancement / Recommendations (Optional)
While writing the above chapters, students should avoid basic definitions. They
should relate and contextualize the above-mentioned concepts with their project work.
 Specimen Copy

CHAPTER – 2
IMAGE PROCESSING

1. INTRODUCTION
Workflow management is a rapidly evolving technology that is increasingly being leveraged by
businesses across various industries.
Its primary characteristic is the automation of processes involving combinations of human
and machine-based activities, particularly those involving interaction with IT applications
and tools. Although its most prevalent use is within the office environment in staff intensive
operations such as insurance, banking, legal and general administration, etc., it is also
applicable to some classes of industrial and manufacturing.
1.1 The Evolution of Workflow

Many types of products in the IT market have supported aspects of workflow

functionality.
1.1.1. Image Processing
Workflow has been closely associated with image systems, and many image systems
have workflow capability either built-in or supplied in conjunction with a specific
workflow product.
1.1.2. Document Management
Document management technology is concerned with managing the lifecycle of
electronic documents.
1.1.3. Electronic Mail and Directories
Electronic mail provides a powerful facility for distributing information between
individuals within an organization or between organizations. Thus, electronic mail
systems have themselves been progressing towards workflow functionality through
the proper channel.
Prescribed content flow for the project proposal
1. Introduction
2. Problem Statement
3. Objectives
4. Methodology
a. Literature Review (Requirement Identification)
i. Study of Existing System /
ii. Requirement Analysis
b. High-Level Design of System (Methodology of the proposed system/ Flow
Charts/ Working Mechanism of Proposed System / Description of Algorithms)
c. Feasibility Study
i. Technical
ii. Operational
iii. Economic
iv. Schedule (Gantt chart showing the project timeline)
5. Expected Outcome
6. References