Title of Project

Project Report

Submitted in Partial Fulfillment of the Requirements for the Degree of

BACHELOR OF TECHNOLOGY

in

COMPUTER SCIENCE & ENGINEERING

By

Name of Student

(University Roll no. _________________)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

MGM’s College of Engineering & Technology, Noida

 October, 2024

(Example)

TABLE OF CONTENTS Page

DECLARATION ................................................................................................... ii
CERTIFICATE ..................................................................................................... iii
ACKNOWLEDGEMENT .................................................................................... iv
ABSTRACT ........................................................................................................... v
LIST OF TABLES.................................................................................................. vii
LIST OF FIGURES................................................................................................ viii
LIST OF SYMBOLS .............................................................................................. ix
LIST OF ABBREVIATIONS ................................................................................ x
CHAPTER 1 (INTRODUCTION, BACKGROUND OF THE PROBLEM,
STATEMENT OF PROBLEM etc.)
1.1. Literature review…………………………………………………………. 1
1.2. Problem definition...................................................................................... 5
1.3. Brief introduction of the project.................................................................. 8
1.4. Proposed modules………………………………………………………. 9
1.5. Hardware & Software requirements………………………………………. 11
CHAPTER 2 (SYSTEMS ANALYSIS AND SPECIFICATION)
2.1. A functional model...................................................................................... 15
2.2. A data model............................................................................................... 17
2.2.1. .............................................................................................................. 19
2.2.2. .............................................................................................................. 20
2.2.2.1. ..................................................................................................... 21
2.2.2.2. ................................................................................................ 22
2.3. A process-flow model................................................................................. 23
2.4. A behavioral model……………………………………………………… 25
2.5. System Design
2.5.1 Technical feasibility
2.5.2 Operational feasibility
2.5.3 Economic feasibility
 CHAPTER 3 (MODULE IMPLEMENTATION & SYSTEM INTEGRATION)
3.1. ................................................................................................................ 36
3.2. ................................................................................................................ 39
CHAPTER 4 (TESTING AND EVALUATION)
4.1 Testing …………………………………………………………….….. 42
CHAPTER 5 (TASK ANALYSIS AND SCHEDULE OF ACTIVITIES)
5.1 Task decomposition …………………………………………..……….. 45
5.2 Project schedule ……………………………………………………….. 47
5.3 Task specification: for each task, identify goals, inputs, outputs, estimated effort and
duration, and task dependencies. ……………………………………… 50
CHAPTER 6 (PROJECT MANAGEMENT)
6.1 Major risks and contingency plans …………………………………… 52
6.2 Principle learning outcomes …………………………………………... 54

APPENDIX A ......................................................................................................... 58
APPENDIX B ......................................................................................................... 59
REFERENCES... .................................................................................................... 60
 List of Figures

Sr. No. Figure Number Figure name Page Number

 List of Tables

Sr. No. Table Number Table Name Page Number

 CERTIFICATE

This is to certify that Project Report entitled

“……………………..................................... ................................................................” which is
submitted by ………………………….... in partial fulfillment of the requirement for the award
of degree B. Tech. in Department of Computer Science and Engineering of MGM’s College of
Engineering and Technology which is affiliated by AKTU Lucknow, is a record of the candidate
own work carried out by him/her under my supervision. The matter embodied in this report is
original and has not been submitted for the award of any other degree.

Date: Supervisor Signature

Name of Supervisor

Designation
 DECLARATION

I hereby declare that this submission is my own work and that, to the best of my
knowledge and belief, it contains no material previously published or written by another
person nor material which to a substantial extent has been accepted for the award of any
other degree or diploma of the university or other institute of higher learning, except
where due acknowledgment has been made in the text.

Signature

Name of Student

Roll No.

Date
 ACKNOWLEDGEMENT

It gives us a great sense of pleasure to present the report of the B. Tech Project undertaken
during B. Tech. Final Year. We owe special debt of gratitude to ……………….., Department of
Computer Science & Engineering, MGM’s College of Engineering and Technology, Noida for
his/her constant support and guidance throughout the course of our work. His/her sincerity,
thoroughness and perseverance have been a constant source of inspiration for us. It is only
his/her cognizant efforts that our endeavors have seen light of the day.

We also take the opportunity to acknowledge the contribution of ………………. Head,

Department of Computer Science & Engineering, MGM’s College of Engineering and
Technology, Noida for his/her full support and assistance during the development of the project.

We also do not like to miss the opportunity to acknowledge the contribution of all faculty
members of the department for their kind assistance and cooperation during the development of
our project. Last but not the least, we acknowledge our friends for their contribution in the
completion of the project.

Signature:

Name:

Roll No.:

Date:

Signature:

Name:

Roll No.:

Date:
 ABSTRACT
The abstract is to be in fully-justified italicized text, at the top of the left-hand column as it is
here, below the author information. Use the word “Abstract” as the title, in 12-point Times,
boldface type, centered relative to the column, initially capitalized. The abstract is to be in 10-
point, single-spaced type, and may be up to 3 in. (7.62 cm) long. Leave two blank lines after the
abstract, then begin the main text. All manuscripts must be in English.

An Abstract is required for every paper; it should succinctly summarize the reason for the work,
the main findings, and the conclusions of the study. The abstract should be no longer than 250
words. Do not include artwork, tables, elaborate equations or references to other parts of the
paper or to the reference listing at the end. The reason is that the Abstract should be
understandable in itself to be suitable for storage in textual information retrieval systems.
 CHAPTER 1

INTRODUCTION
Systems Analysis and Specification

In writing the specification, we should begin with the requirements document and then you
should identify the following.

The system functionality

The operational parameters (conditions under which your system will operate, including required
software and hardware systems)

Failure modes and actions on failure

Limitations & restrictions

User interface or system interface

It should also include

1. A functional model

This will usually take the form of a functional decomposition: a hierarchical breakdown of the
major functional blocks involved in the processing/analysis/transformation. Typically, this will
be a modular decomposition of the computational model. Each leaf node in the functional
decomposition tree should have a short description of the functionality provided, the information
(data) input, and the information (data) output.

2. A data model

The identification of the major data-structures to be used to represent input, output, and
temporary information. This is sometimes known as a data dictionary. Note that we are not
interested here in the implementation of the data-structures (e.g. linked list, trees, arrays) but
with the identification of the data itself. Very often, it is useful to use entity relationship
diagrams to capture the data model.

3. A process-flow model

This model specifies what data flows into and out of each functional block (i.e. into and out of
the leaf nodes in the functional decomposition tree). Normally, data-flow diagrams are used to
convey this information, and are organized in several levels (i.e. DFD level 0, DFD level 1, etc.)
The level zero DFD is equivalent to the system architecture diagram and shows the sources and
sinks of information outside your system.
4. A behavioral model

This will typically use a state-transition diagram to show the behaviour of the system over time,
i.e. the different states it can be in, the event and triggers that cause a change in state, and the
functional blocks associated with each state. It is also often useful to create a control-flow
diagram: a version of the data-flow diagram with events and triggers superimposed on each
process.

5. A clear and detailed definition of all the user and system interfaces; one of the best ways of
encapsulating this information is to create a user-manual.

System Design

You are now in a position to design your system using whatever design methodology is
appropriate for the area (and these will inevitably be specific to the particular area, be it filter
design, amplifier design, software design, and so on). That said, there are a few general
guidelines that apply to all areas:

Identify several design options – algorithm, data-structures, files, interface protocols – and
compare them.

Analyze your design to ensure it is technically feasible (i.e. validate its realizability).
Remember, you can’t always build everything you design, either for theoretical reasons (ideal
filters, for example) or for pragmatic reasons (a 1- Farad capacitor would make for some
interesting implementation problems)

Analyze your design to ensure it meets the specifications (i.e. validate its operational viability)
‰ Cost your system (i.e. validate its economic viability)

Choose the best design. You will have to define what ‘best’ means for your particular project. It
might mean the cheapest to manufacture, it might mean the fastest, and it might mean the
smallest – it all depends. It’s up to you to identify the test for optimality.
 LIST OF SYMBOLS

[x] Integer value of x.

≠ Not Equal

 Belongs to

€ Euro- A Currency

_ Optical distance

_o Optical thickness or optical half thickness

 LIST OF ABBREVIATIONS

AAM Active Appearance Model

ICA Independent Component Analysis

ISC Increment Sign Correlation

PCA Principal Component Analysis

ROC Receiver Operating Characteristics

 REFERENCES
Examples of Journal Article referencing:

1. Drucker, D. C., "Photoelastic Separation of Principal Stresses by Oblique Incidence", Journal

of Applied Mechanics, Vol. 65, pp. 156-160, 1943.

2. Maiers, J., and Sherif, Y. S. , "Application of Fuzzy Set Theory," IEEE Transactions on
Systems, Man, and Cybernetics, Vol. SMC-15, No.1, pp. 41-48, 1985.

Example of Book referencing:

3. Doe, N., Control System Principles, New York: John Wiley, 1999.

Example of Referencing of an Article in a Book:

4. Hwang, C. J., "Rule-based Process Control," in E. Kumarmangalam and L. A. Zadeh

(Eds.), Approximate Reasoning in Intelligent Systems, Decision and Control, pp.
145-158, Oxford: Pergamon Press, 1987.

Example of referencing of a B. Tech. Report:

5. Nayak, T., "Application of Neural Networks to Nuclear Reactors," M.Sc. Report, U.P.
Technical University, 2005.

Example of referencing of a Ph. D. Dissertation:

6. Muskìn, H. L., "Development of A Knowledge-Based System for a Nuclear Power Plant,"

Ph.D. Dissertation, U. P. Technical University, 2003.

Example of referencing of a Conference Paper :

7. Lokhande, R., Arya, K. V., and Gupta, P., "Identification of Parameters and Restoration of
Motion Blurred Images", Proceedings of the 2006 ACM Symposium on Applied
Computing (SAC 2006), pp. 89-95, Dijon, France, April 2- 7, 2006.

Example of referencing of a Paper presented at Conference but not Published :

8. Lokhande, R., and Gupta, P., "Identification of Parameters of Motion Images", presented at
5th International Conference on Cyber Systems, New Delhi, India, April 12- 17, 2004

Example of referencing of a Report [Technical, Internal, or Memoranda]: :

9. Das, A. R., Murthy D., and Badrinath J., A Comparison of Different Biometrics Traits,
RSRE Memorandum No. 4157, RSRE Malvern, 2001.
Example of referencing of a Manual

10. Bell Telephone Laboratories Technical Staff, Transmission System for Communications,
Bell Telephone Laboratories, 1995.

Example of referencing of a Class Note

11. "Signal integrity and interconnects for high-speed applications," class notes for ECE 497-
JS, Department of Electrical and Computer Engineering, University of Illinois at Urbana-
Champaign, Winter 1997.

Example of referencing of a Private Communication

12. Banerjee, T., (Private Communication), 1998

Example of referencing of an Article from Internet

13. Biometrics Group, Indian Institute of Technology Kanpur, "Multimodal Biometrics

System," December 2006, http://www.cse.iitk.ac.in/users/biometrics.html

14. Gupta, P. ([email protected]), "Biometrics System," Usenet post to sci.electronics.design, July 4,

2007.

Example of referencing of an Article from Catalog

15. Catalog No. MWM-1, Microwave Components, M. W. Microwave Corp., Brooklyn, NY

Example of referencing of an Article from Application Note

16. Hewlett-Packard, Appl. Note 935, pp. 25-29.

Example of referencing of an Article from Application Note

17. Kar, K. and Majumder, D., "Fuzzy Controller Component," U. S. Patent 23,160,040,
December 21, 2006.
Project report formatting guidelines

1. Report should have at least 50 and at most 80 pages (or depends on your project)

2. The entire pages of the report should be in A4 size strictly, with 1” top and
bottom margin and 1.25” left and right margin.
3. The entire report should be typed in Times New Roman with 12 pt.
4. The title and main headings of the paragraphs are to be in bold.

5. Report may be divided into the number of chapters as required, with chapter
number assigned on the top and chapter name immediately below it (with single line
spacing) using Times New Roman 16 pt bold.
6. Each main paragraph or heading should be numbered with a whole number. (e.g 1)

7. Every sub heading should be given decimal of whole number of the heading.
(e.g1.1)
8. Subsidiary paragraphs to the sub heads may have decimal points of the sub heads if
required. (e.g 1.1.1)
9. One paragraph should only deal with a single issue and sub issues should be dealt
in sub paragraphs numbered accordingly.

10. Each line should be separated by a line spacing of 1.5, and each paragraph by line
spacing of 2.
11. The complete text should be justified in the report (no left or right aligning).
12. No short forms are to be used in the report besides the specified areas.

13. Numbering of each page should be done in the footer section at the middle bottom
corner.