Project Report (font size 16)

on (font size 14)

Title of Project (font size 18)

Submitted as partial fulfillment for the award of (Font Size 14)

BACHELOR OF TECHNOLOGY (font 22)

DEGREE (font size 20)
Session 2022-23 (Font Size 12)
in

Computer Science (font size 18)

By (font size 14)

Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)

Under the guidance of (font size 16)

NAME OF SUPERVISOR (font size 14)

ABES ENGINEERING COLLEGE, GHAZIABAD (font 16)

AFFILIATED TO
DR. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY, U.P., LUCKNOW
(Formerly UPTU)
(font size 14)
 Project Report (font size 16)
on (font size 14)

Title of Project (font size 18)

Submitted as partial fulfillment for the award of (Font Size 14)

BACHELOR OF TECHNOLOGY (font 22)

DEGREE (font size 20)
Session 2022-23 (Font Size 12)
in

Computer Science (font size 18)

By (font size 14)

Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)
Student Name (Roll No) (font size 13)

Under the guidance of (font size 16)

NAME OF SUPERVISOR (font size 14)

ABES ENGINEERING COLLEGE, GHAZIABAD (font 16)

AFFILIATED TO
DR. A.P.J. ABDUL KALAM TECHNICAL UNIVERSITY, U.P., LUCKNOW
(Formerly UPTU)
(font size 14)
 STUDENT’S DECLARATION

We hereby declare that the work being presented in this report entitled “ TITLE OF THE

PROJECT” (font size 14) is an authentic record of our own work carried out under the
supervision of Dr. /Mr. /Ms. “SUPERVISOR NAME” (font size 14)
The matter embodied in this report has not been submitted by us for the award of any other
degree. (font size 12Arial 1.5 Line Spacing)

Dated: Signature of students(s)

(Name(s).......................)
Department:

This is to certify that the above statement made by the candidates is correct to the best of my
knowledge.

Signature of HOD Signature of Supervisor

(Prof. (Dr.) Pankaj Kumar Sharma) (Name )
(Computer Science Department) (Designation)
Date............................ (Computer Science Department)

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 ...................................................... of Dr. A.P.J.
Abdul Kalam Technical University, formerly Uttar Pradesh Technical University is a record of
the candidate own work carried out by him/them under my supervision. The matter embodied
in this thesis is original and has not been submitted for the award of any other degree.

Signature of Supervisor
(Name )
(Designation)
(Computer Science Department)
 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 (Dr./Mr./Ms.) _______________, Department of
_________________, ABESEC Ghaziabad 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 cognizant efforts that our endeavors have seen light of the day.

We also take the opportunity to acknowledge the contribution of Professor (Dr.) ………., Head,
Department of Computer Science, ABESEC Ghaziabad for his 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: Signature:

Name : Name :

Roll No.: Roll No.:

Date : Date :

Signature:

Name :

Roll No.:

Date :
 ABSTRACT
The abstract is to be in fully-justified italicized text of size 12 points.
An Abstract is required for every project; 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.

Guidelines for writing abstract

An abstract is an abbreviated version of the project report. It should be limited to a maximum

of 250 words. An abstract should have the following in paragraph form (without headings) -
Introduction, Problem Statement, Procedure, Results and Conclusion. In Introduction, one
describes the purpose for doing such a project. It should address the need for such type of
work. It should explain something that should cause people to change the way they go about
their daily business. If the project leads to an invention or development of a new procedure, it
should mention its advantages. In the next stage, one should write down the Problem
Statement. It is needed to identify the problem that has been considered in the project. In
Procedures, the approach used to investigate the problem should be mentioned in the
abstract. In the fourth stage, abstract must clearly state the Results/ achievements obtained
through the execution of the project. Finally Conclusions are given an the last stage. One
should state clearly whether the objectives have been met or not. If not, the reasons behind it
should be stated in few words.

Keywords: Convolutional Neural Network, Machine Learning, CNN, etc.

 TABLE OF CONTENTS Page

DECLARATION ................................................................................................... ii
CERTIFICATE……....................................................................................................iii
ACKNOWLEDGEMENTS .................................................................................. iv
ABSTRACT ........................................................................................................... v
LIST OF TABLES.................................................................................................. vii
LIST OF FIGURES................................................................................................ viii
LIST OF SYMBOLS .............................................................................................. ix
LIST OF ABBREVIATIONS ............................................................................... x
CHAPTER 1 1
1.1. ................................................................................................................. 5
1.2. ................................................................................................................. 8
CHAPTER 2 ……………………………. ......................................................... 13
2.1. ............................................................................................................... 15
2.2. ............................................................................................................... 17
2.2.1. ....................................................................................................... 19
2.2.2. ....................................................................................................... 20
2.2.2.1. ..............................................................................................21
2.2.2.2. ..........................................................................................
22
2.3. ...............................................................................................................23
CHAPTER 3 …………………………….......................................................... 30
3.1. ................................................................................................................36
3.2. ................................................................................................................39
CHAPTER 4 (CONCLUSIONS) ......................................................................40
APPENDIX A .........................................................................................................45
APPENDIX B .........................................................................................................47

REFERENCES... .................................................................................................... 49

10
 LIST OF TABLES
Table Description
Comparison Of Various Data Structures.
Table 2.1.4.1

11
 LIST OF FIGURES

Figure Description
A typical neural network
Fig 2.1

12
 LIST OF SYMBOLS

[x] Integer value of x.

≠ Not Equal

 Belongs to

€ Euro- A Currency

_ Optical distance

_o Optical thickness or optical half thickness

13
 LIST OF ABBREVIATIONS

AAM Active Appearance Model

ICA Independent Component Analysis

ISC Increment Sign Correlation

PCA Principal Component Analysis

ROC Receiver Operating Characteristics

14
 CHAPTER 1
INTRODUCTION

It is the first chapter of the Report. The purpose of an introduction in the B. Tech
Project Report is to justify the reasons for writing about the report. The goal in this
section is to introduce the topic to the reader, provide an overview of previous
research on the topic, and identify the own hypothesis. The goals just mentioned
could, if abused, lead to write an introduction that is pages and pages long. It can be
noted here that the introduction should not contain every bit of detail in the report, and
it should not include support for the report. An introduction might, however, include
the reasons for supporting the report.

In order for readers to trust the writer, the introduction must be well written with few
errors. In order to keep readers reading, the writer needs to catch the attention of the
reader and write in an interesting way. The unique language enhancement feature
may suggest words to strengthen the writing. Strong writing may hold readers'
attention.

In addition to well-written English with strong vocabulary, there are a few other
strategies to hold readers' attention. It should be noted that to excite the readers'
interest, one may also want to sound as though the readers know the topic that are
considered in the report. Some of the following strategies in the bullet-list above may
help.

• To pose a specific question that can invite the readers to keep reading for
the answer-- A provocative question works well to engage readers, so long
as it doesn't put them off

• To choose statistics to surprise readers or to go against the common belief

about a topic

• To mention a short, interesting anecdote (or story) related to the topic

• To provide an interesting (and relevant) quote

• To develop an unusual or unexpected comparison

It has been observed that the difficulty level to write the Introduction is average and it
takes the variable amount of time. Following sub headings are to be included in this
chapter depending on the project-

15
1.1. Problem Introduction

1.1.1. Motivation

1.1.2. Project Objective

1.1.3. Scope of the Project

1.2. Related Previous Work

It briefly includes previous work carried out in this field, researching the
problem studied, summarization of the results obtained etc

1.3. Organization of the Report.

It provides the short description of the work reported in each chapter.

16
 CHAPTER 2
(For non-web based projects)
LITERATURE SURVEY
(LITERATURE SURVEY FORMAT FOR NON-WEB BASED PROJECTS)

 A brief description of what is studied in the survey should be given in a paragraph of

6-10 lines (approx.) this paragraph should not contain any title.
 Then you can elaborate on each technique/algorithm/ technology depending on your
project section wise. For example if literature survey is for face recognition then all
existing approaches should be mentioned in a separate section.
 Each section should contain a heading and should be numbered. It can also contain
images, formulae, flow chart and tabular data that are needed for explanation. Each
section size should not exceed 1 to 1.5 pages.
 Use citations from the References section where ever required-
Example- A pun, or paronomasia, is a form of word play that deliberately exploits

[1]
ambiguity between similar-sounding words for humorous or rhetorical effect. (If the
contents are taken from reference 1 of References section).

All citations must be referred.

 Any included image, formula, flow chart or tabular data should be numbered and
should be referred in the respective section. Tables numbering should appear on the
top of table and figure numbering should be below the figure.
 At the end of the literature survey chapter, include a summary section with the
heading SUMMARY. In this section sum up the above studied techniques/algorithms/
technologies paragraph wise.

17
Input Layer Hìdden Layer Output Layer

1 1
2

2 2

. .
. 3
.
. . .
.
n n0 n '

Figure 2.1. A typical neural network

18
 CHAPTER 2
(Web Based Projects)
SOFTWARE REQUIREMENT SPECIFICATION

Describe the general factors that affect the product and its requirements. This section does
not state specific requirements. Instead, it provides a background for those requirements,
which are defined in section 3, and makes them easier to understand. In a sense, this section
tells the requirements in plain English for the consumption of the customer. Section3 will
contain a specification written for the developers.

2.1 Product Perspective

Put the product into perspective with other related products. If the product is independent
and totally self-contained, it should be so stated here. If the SRS defines a product that is a
component of a larger system, as frequently occurs, then this subsection relates the
requirements of the larger system to functionality of the software and identifies interfaces
between that system and the software. If you are building a real system, compare its
similarity and differences to other systems in the marketplace. If you are doing a research-
oriented project, what related research compares to the system you are planning to build.

A block diagram showing the major components of the larger system, interconnections, and
external interfaces can be helpful. This is not a design or architecture picture. It is more to
provide context, especially if your system will interact with external actors. The system you
are building should be shown as a black box. Let the design document present the internals.

The following subsections describe how the software operates inside various constraints.

2.1.1 System Interfaces

List each system interface and identify the functionality of the software to accomplish the
system requirement and the interface description to match the system. These are external
19
systems that you have to interact with. For instance, if you are building a business
application that interfaces with the existing employee payroll system, what is the API to that
system that designer’s will need to use?

2.1.2 Interfaces

Specify:

(1) The logical characteristics of each interface between the software product and
its users.
(2) All the aspects of optimizing the interface with the person who must use the
system

This is a description of how the system will interact with its users. Is there a GUI, a command
line or some other type of interface? Are there special interface requirements? If you are
designing for the general student population for instance, what is the impact of ADA
(American with Disabilities Act) on your interface?

2.1.3 Hardware Interfaces

Specify the logical characteristics of each interface between the software product and the
hardware components of the system. This includes configuration characteristics. It also
covers such matters as what devices are to be supported, how they are to be supported and
protocols. This is not a description of hardware requirements in the sense that “This program
must run on a Mac with 64M of RAM”. This section is for detailing the actual hardware
devices your application will interact with and control. For instance, if you are controlling X10
type home devices, what is the interface to those devices? Designers should be able to look
at this and know what hardware they need to worry about in the design. Many business type
applications will have no hardware interfaces. If none, just state “The system has no
hardware interface requirements” If you just delete sections that are not applicable, then
readers do not know if: a. this does not apply or b. you forgot to include the section in the
first place.

2.1.4 Software Interfaces

Specify the use of other required software products and interfaces with other application
systems. For each required software product, include:

20
 (1) Name
(2) Mnemonic
(3) Specification number
(4) Version number
(5) Source

For each interface, provide:

(1) Discussion of the purpose of the interfacing software as related to this software
product
(2) Definition of the interface in terms of message content and format

Here we document the APIs, versions of software that we do not have to write, but that our
system has to use. For instance if your customer uses SQL Server 7 and you are required
to use that, then you need to specify i.e.

2.1.4.1 Microsoft SQL Server 7. The system must use SQL Server as its database
component. Communication with the DB is through ODBC connections. The system must
provide SQL data table definintions to be provided to the company DBA for setup.

A key point to remember is that you do NOT want to specify software here that you think
would be good to use. This is only for customer-specified systems that you have to
interact with. Choosing SQL Server 7 as a DB without a customer requirement is a Design
choice, not a requirement. This is a subtle but important point to writing good requirements
and not over-constraining the design.

TABLE 2.1.4.1. Comparison Of Various Data Structures.

Operatio Sequential Linked List AVL-Tree

n List

Search O(log n) O(n) O(log n)

Delete O(n) O(1) O(log n)

Insert O(n) O(1) O(log n)

21
2.1.5 Communications Interfaces
Specify the various interfaces to communications such as local network protocols, etc. These
are protocols you will need to directly interact with. If you happen to use web services
transparently to your application then do not list it here. If you are using a custom protocol to
communicate between systems, then document that protocol here so designers know what to
design. If it is a standard protocol, you can reference an existing document or RFC.

2.1.6 Memory Constraints

Specify any applicable characteristics and limits on primary and secondary memory. Don’t
just make up something here. If all the customer’s machines have only 128K of RAM, then
your target design has got to come in under 128K so there is an actual requirement. You
could also cite market research here for shrink-wrap type applications “Focus groups have
determined that our target market has between 256-512M of RAM, therefore the design
footprint should not exceed 256M.” If there are no memory constraints, so state.

2.1.7 Operations
Specify the normal and special operations required by the user such as:

(1) The various modes of operations in the user organization

(2) Periods of interactive operations and periods of unattended operations
(3) Data processing support functions
(4) Backup and recovery operations

(Note: This is sometimes specified as part of the User Interfaces section.) If you separate
this from the UI stuff earlier, then cover business process type stuff that would impact the
design. For instance, if the company brings all their systems down at midnight for data
backup that might impact the design. These are all the work tasks that impact the design of
an application, but which might not be located in software.

2.1.8 Site Adaptation Requirements

In this section:

(1) Define the requirements for any data or initialization sequences that are
specific to a given site, mission, or operational mode
(2) Specify the site or mission-related features that should be modified to adapt
the software to a particular installation

22
If any modifications to the customer’s work area would be required by your system, then
document that here. For instance, “A 100Kw backup generator and 10000 BTU air
conditioning system must be installed at the user site prior to software installation”.

This could also be software-specific like, “New data tables created for this system must be
installed on the company’s existing DB server and populated prior to system activation.” Any
equipment the customer would need to buy or any software setup that needs to be done so
that your system will install and operate correctly should be documented here.

2.2 Product Functions

Provide a summary of the major functions that the software will perform. Sometimes the
function summary that is necessary for this part can be taken directly from the section of the
higher-level specification (if one exists) that allocates particular functions to the software
product.

For clarity:

(1) The functions should be organized in a way that makes the list of functions
understandable to the customer or to anyone else reading the document for the
first time.
(2) Textual or graphic methods can be used to show the different functions and their
relationships. Such a diagram is not intended to show a design of a product but
simply shows the logical relationships among variables.

AH, Finally the real meat of section 2. This describes the functionality of the system in the
language of the customer. What specifically does the system that will be designed have to
do? Drawings are good, but remember this is a description of what the system needs to do,
not how you are going to build it. (That comes in the design document).

2.3 User Characteristics

Describe those general characteristics of the intended users of the product including
educational level, experience, and technical expertise. Do not state specific requirements but
rather provide the reasons why certain specific requirements are later specified in section 3.

23
What is it about your potential user base that will impact the design? Their experience and
comfort with technology will drive UI design. Other characteristics might actually influence
internal design of the system.

2.4 Constraints

Provide a general description of any other items that will limit the developer's options. These
can include:

(1) Regulatory policies

(2) Hardware limitations (for example, signal timing requirements)
(3) Interface to other applications
(4) Parallel operation
(5) Audit functions
(6) Control functions
(7) Higher-order language requirements
(8) Signal handshake protocols (for example, XON-XOFF, ACK-NACK)
(9) Reliability requirements
(10) Criticality of the application
(11) Safety and security considerations

This section captures non-functional requirements in the customers language. A more formal
presentation of these will occur in section 3.

2.5 Assumptions and Dependencies

List each of the factors that affect the requirements stated in the SRS. These factors are not
design constraints on the software but are, rather, any changes to them that can affect the
requirements in the SRS. For example, an assumption might be that a specific operating
system would be available on the hardware designated for the software product. If, in fact,
the operating system were not available, the SRS would then have to change accordingly.

This section is catch-all for everything else that might influence the design of the system and
that did not fit in any of the categories above.

2.6 Apportioning of Requirements.

24
Identify requirements that may be delayed until future versions of the system. After you look
at the project plan and hours available, you may realize that you just cannot get everything
done. This section divides the requirements into different sections for development and
delivery. Remember to check with the customer – they should prioritize the requirements and
decide what does and does not get done. This can also be useful if you are using an iterative
life cycle model to specify which requirements will map to which interation.

2.7. Use case

2.7.1. Use case Model

 Some Guide Lines for use cases

 Place Your Primary Actor(S) In The Top-Left Corner Of The Diagram

 Draw Actors To The Outside Of A Use Case Diagram
 Name Actors With Singular, Business-Relevant Nouns
 Associate Each Actor With One Or More Use Cases
 Actors Model Roles, Not Positions
 Use <<system>> to Indicate System Actors
 Actors Don’t Interact With One Another
 Introduce an Actor Called “Time” to Initiate Scheduled Events
 Associations are depicted as lines connecting two modeling elements
with an optional open-headed arrowhead on one end of the line
indicating the direction of the initial invocation of the relationship.
Generalizations are depicted as a close-headed arrow with the arrow
pointing towards the more general modeling element.
2.7.2 Use Case Diagram (you can use either use case diagram or scenario)
2.7.3 Use Case Scenario (Following details can be provided for a use case scenario)

Use Case
Description
Element
Use Case
ID to represent your use case
Number
Application What system or application does this pertain to
Use Case Name The name of your use case, keep it short and sweet
Use Case
Elaborate more on the name, in paragraph form.
Description
Primary Actor Who is the main actor that this use case represents
Precondition What preconditions must be met before this use case can start
Trigger What event triggers this use case
The basic flow should be the events of the use case when everything is perfect; there are no
Basic Flow errors, no exceptions. This is the "happy day scenario". The exceptions will be handled in the
"Alternate Flows" section.
Alternate Flows The most significant alternatives and exceptions

25
2.8 Sequence diagrams ( Example for Registration Process)

26
 CHAPTER 3
(For non-web based projects)
SYSTEM DESIGN AND METHODOLOGY
3.1. System Design

3.1.1. System Architecture /DiagrammaticalView

3.1.2. DFD, Class Diagram, flow charts, ER Diagrams (which ever applicable
depending on the project)

3.2. Algorithm(s)

(if required, add any other section applicable for the methods and
approaches you have followed)

27
 CHAPTER3
(For Web-Based Projects)
SYSTEM DESIGN

System Design should include the following sections (Refer each figure or table in some text).
Figure number should be provided below the figure and the table numbering should be
provided above the table.

3.1. Architecture diagrams

Figure 3.1 3-Tier Architecture Diagram example

3.2. Class diagrams

3.3. Data Flow Diagram

3.4. Activity Diagram (Example for Registration and Login)

3.5. ER Diagrams

3.6. Database schema diagrams

28
 CHAPTER 4
IMPLEMENTATION AND RESULTS (If Implemented)

4.1. Software and Hardware Requirements

In this section provide the details of any software or hardware requires for the
implementation of the project.

4.2. Assumptions and dependencies

4.3. Constraints (If Applicable)

4.4. Implementation Details

4.4.1. Snapshots Of Interfaces

4.4.2. Test Cases

List the test cases used to test your work.

4.4.3. Results

Include the output of your work here. The result can be in tabular and/or
graphical format depending on the project. Comparison with earlier or other
work may also be presented.

29
 CHAPTER 5
CONCLUSION

5.1. Performance Evaluation

5.2. Comparison with existing State-of-the-Art Technologies

5.3. Future Directions
It must indicate whether the work carried out suggests any interesting further
avenues. It should discuss the possibility of improving the work by future workers. A
paragraph should be written on the practical implications of the work.

This chapter should usually be reasonably short---a few pages perhaps. As with the
introduction, it is a good idea to ask someone who is not a specialist to read this
section and to comment

30
 Appendix
If there is material that should be in the project report but which would break up the
flow or bore the reader unbearably, include it as an appendix. Some things which are
typically included in appendices are: important and original computer programs, data
files that are too large to be represented simply in the results chapters, pictures or
diagrams of results which are not important enough to keep in the main text. Thus in
the appendix, one may include

1. All data used in the report

2. Reference data/materials not easily available

3. Tables (where more than 1-2 pages)

4. Calculations (where more than 1-2 pages)

5. All key articles

6. List of all additional resource materials

7. List of equipment used for an experiment or details of complicated procedures.

8. In case of more than one appendix , they should be numbered as Appendix A,
Appendix B etc

Listings of the developed computer software should be given in an appendix.

However, if the code is longer than 300 lines the listing should be given in a
separate CD following proper indentation and comments.

31
 References
Thumb rules followed to refer some one’s work are given below.

1. Cite all ideas, concepts, text, data that are not own by the project group

2. If author makes a statement, he must back it up with his own data or a

reference

3. All references cited in the text must be listed

4. List all references cited in the text in alphabetical

5. Follow the format or citation style as discussed in chapter 4.

(Example of References using the Numeric System)

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. TechnicalUniversity, 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.

32
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

33
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.

34
35