[BINDING COVER]

COMPLETE TITLE OF THE PROJECT IN ALL

BSEE

CAPS, TIMES NEW ROMAN, FONT SIZE 20

COMPLETE TITLE OF THE PROJECT IN ALL CAPS, TIMES NEW ROMAN

Color of Binding = Navy Blue

Color of Text on Cover = Golden

by

<Student Name> in font size 16

<Reg. No. XX> in font size 15

A Project Report submitted to the

DEPARTMENT OF ELECTRICAL ENGINEERING
in partial fulfillment of the requirements for the degree of
BACHELORS OF SCIENCE IN ELECTRONIC ENGINEERING
[Font: Times New Roman, Size: 14]

Faculty of Engineering
Capital University of Science & Technology,
2014

Islamabad
<Month, Year>
[Font: Times New Roman, Size: 14]
COMPLETE TITLE OF THE PROJECT IN ALL
CAPS, TIMES NEW ROMAN, FONT SIZE 20

by

<Student Name> in font size 16

<Reg. No. XX> in font size 15

A Project Report submitted to the

DEPARTMENT OF ELECTRICAL ENGINEERING
in partial fulfillment of the requirements for the degree of
BACHELORS OF SCIENCE IN ELECTRONIC ENGINEERING
[Font: Times New Roman, Size: 14]

Faculty of Engineering
Capital University of Science & Technology,
Islamabad
<Month, Year>
[Font: Times New Roman, Size: 14]
 Copyright  2017 by CUST Student

All rights reserved. Reproduction in whole or in part in any form requires the prior
written permission of <student name> or designated representative. [Font: Times New
Roman, Size: 12]

ii
This page should contain the dedication of the Project/Thesis. Try to be
as brief as possible in this dedication. Do not include half of world in the
dedication. [Font: Times New Roman, Size: 14, Italic]

(This page is optional)

iii
 DECLARATION
It is declared that this is an original piece of my own work, except where
otherwise acknowledged in text and references. This work has not been submitted in
any form for another degree or diploma at any university or other institution for
tertiary education and shall not be submitted by me in future for obtaining any degree
from this or any other University or Institution.
[Font: Times New Roman, Size: 12]

<Name of Student 1>

<Reg. No. XYX>

<Name of Student 2 (if any)>

<Reg. No. XYZ>

Month Year (e.g. March, 2016)

iv
 CERTIFICATE OF APPROVAL

It is certified that the project titled “Performance Comparison of Adaptive

Beamforming Algorithms For Smart Antenna Systems” carried out by Muhammad
Salman Razzaq, Reg. No. EE073020, under the supervision of Dr. Noor Muhammad
Khan, Capital University of Science & Technology, Islamabad, is fully adequate, in
scope and in quality, as a final year project for the degree of BS of Electronic
Engineering.

Supervisor: -------------------------
Dr. Sajjad Hussain
Associate Professor
Department of Electrical Engineering
Faculty of Engineering
Capital University of Science & Technology, Islamabad

HOD: ----------------------------
Dr. Noor Mohammad Khan
Professor
Department of Electrical Engineering
Faculty of Engineering
Capital University of Science & Technology, Islamabad

v
 ACKNOWLEDGMENT

This page is intended to thank your supervisor, co-supervisor and all those (students,
teachers, TA/SA or any third party) who directly helped you out in the completion of
the project/thesis. [Font: Times New Roman, Size: 12]
 ABSTRACT

The abstract is the most important part of a Project report. Any abstract will be
read by ten or twenty times more than any other words in the report. So, to make a
positive impression, or just convey information, here's where to really pay attention to
writing.

The purpose of abstract in not just to tell the reader about what was done: it is
to tell him/her what was done in the simplest, most informative way possible. Making
an abstract understandable for a non-technical person should be the first priority.
Discussed below are the basic components of an abstract in any discipline and should
be handled in separate paragraphs.

First paragraph should be about Motivation/problem statement: Why do you

care about the problem? What practical, scientific, theoretical gap is your
research/project filling?

Methods/procedure/approach: What did you actually do to get your results?

(e.g. Designed something, developed your own algorithms/software/techniques, did
some survey, worked with some organization etc.)

Results/findings/product: As a result of completing the above procedure, what

did you learn/invent/create?

Conclusion/implications: What are the larger implications of your findings,

especially for the problem/gap identified in Motivation/problem statement paragraph?
 TABLE OF CONTENTS

DECLARATION.................................................................................iv
CERTIFICATE OF APPROVAL.........................................................v
ACKNOWLEDGMENT......................................................................vi
ABSTRACT........................................................................................vii
TABLE OF CONTENTS..................................................................viii
LIST OF FIGURES..............................................................................x
LIST OF TABLES...............................................................................xi
LIST OF ACRONYMS/ABBREVIATIONS....................................xiii
Chapter 1...............................................................................................1
INTRODUCTION................................................................................1
1.1 Overview......................................................................................................1
1.2 Project Idea...................................................................................................1
1.3 Purpose of the Project..................................................................................2
1.4 Project Specifications...................................................................................2
1.3.1 Non-Functional Specifications......................................................2
1.3.2 Functional Specifications..............................................................2
1.5 Applications of the Project...........................................................................2
1.6 Project Plan..................................................................................................2
1.7 Report Organization.....................................................................................4
Chapter 2...............................................................................................5
LITERATURE REVIEW.....................................................................5
2.1 Background..................................................................................................5
2.2 Related Technologies...................................................................................5
2.1.1 Related Technology 1....................................................................5
2.1.2 Related Technology 2....................................................................5
2.3 Related Projects............................................................................................5
2.4 Related Studies/Research.............................................................................5
2.5 Limitations and Bottlenecks of the Existing Work......................................5
2.6 Problem Statement.......................................................................................6
2.7 Summary......................................................................................................6
Chapter 3...............................................................................................7
PROJECT DESIGN AND IMPLEMENTATION................................7
3.1 Proposed Design Methodology....................................................................7
3.2 Design of the Project Hardware/ Software...................................................7
3.3 Analysis Procedure.......................................................................................7
3.4 Implementation Procedure...........................................................................7
3.5 Details about Hardware................................................................................7
3.6 Details about Software/Algorithm...............................................................8
3.7 Details of Simulations / Mathematical Modeling........................................9
3.8 Details of Final Working Prototype.............................................................9
3.9 Summary......................................................................................................9
Chapter 4.............................................................................................10
TOOLS AND TECHNIQUES............................................................10
4.1 Hardware Tools used..................................................................................10
4.2 Software(s), simulation tool(s) used..........................................................10
4.3 Summary....................................................................................................10
Chapter 5.............................................................................................11
PROJECT RESULTS AND EVALUATION.....................................11
5.1 Presentation of the findings........................................................................11
5.1.1 Hardware results..........................................................................11
5.1.2 Software results...........................................................................11
5.2 Verification of design functionalities.........................................................12
5.3 Discussion on the findings.........................................................................12
5.3.1 Comparison with initial Project Specifications...........................12
5.3.2 Reasoning for short comings.......................................................12
5.4 Limitations of the working prototype........................................................12
5.5 Recommendations and Future Work..........................................................12
5.6 Summary....................................................................................................12
Chapter 6.............................................................................................13
CONCLUSION...................................................................................13
REFERENCES....................................................................................14
APPENDICES....................................................................................15
Appendix – A.............................................................................................15
 Record of Births by Calendar Year............................................................15
Appendix – B.............................................................................................16

LIST OF FIGURES
Figure 1. Project Timeline.............................................................................................3
Figure 2. Block diagram of hardware design................................................................8
Figure 3. Block diagram of software algorithm.............................................................9
 LIST OF TABLES

Table 1 Proposed Project Plan......................................................................................3

Table 2: Software Testing Results...............................................................................11
 LIST OF ACRONYMS/ABBREVIATIONS

USB Universal Serial Bus

TTL Transistor Transistor Logic

UART Universal Asynchronous Receiver-Transmitter

SRAM Synchronous Random Access Memory

EPROM Erasable Programmable Read Only Memory

PCB Printed Circuit Board

RF Radio Frequency
 GENERAL INSTRUCTIONS

[All the information provided in this section is regarding the format of the
project report. Read it carefully and make sure that your report is according to
the required format. For your ease, the format is not only explained but also has
been demonstrated with proper font, font size, style and other formatting
requirements.]

Once the project/research work is complete, students are required to submit two hard
bound copies of project report. The report should be around 60 pages or according to
the limits set forth by your supervisor.

Contents/chapters of the Project Report should be in the format and order as given in
this document. Initially, we will discuss all the format requirements of the project
report. Then the contents to be included in the report will be briefly discussed

1.1 Formatting
The single-sided, normal character spaced manuscript is to be arranged as follows:

1.1.1 Submissions Required

Two hard-bound copies of the final project documentation must be submitted to your
supervisor before the Final Evaluation. Spine of binding must contain complete
Project/Thesis, level of work i.e. BS Project/MS Thesis/ PhD Dissertation and the
year of submission. Please keep in mind that the binding takes 3-4 days to complete

1.1.2 Binding

Color of binding should be Mahroon for PhD, Green for MS Thesis and Blue for BS
final year Projects with golden text. Use 80 grams paper; A4 (8.27 x 11.69) and make
sure that right paper is selected for both page setup and printer. All copies to be
submitted should be printed, photocopies will not be accepted.

1.1.3 Fonts and Spacing

The preferred font is Times New Roman; acceptable font size is 12; different
typefaces (e.g., italics) may be used only to show differences in captions and special
 Top
margin 1 inch

text. Starting from chapter 1, the line spacing must be 1.5 whereas the spacing both
before and after paragraph must be 6 points. For all the pages before “Chapter 1” e.g.
Table of Contents, Abstract, Declaration etc, Line spacing should be single i.e.1.

1.2 Chapter Heading

Chapters and section numbering should be same as given in Table of Contents.
Chapter should begin with ‘Chapter XX’ on the first line, in font size 18, Sentence
Case, left aligned and bold. Here XX refers to the chapter number. Spacing before
‘Chapter XX’ should be 6 points and after should be 24 points.

The following line should contain ‘CHAPTER HEADING TITLE’, all Upper case,
font size 18, center aligned and bold. Spacing before ‘CHAPTER HEADING TITLE’
should be 6 points and after should be 24 points.

1.3 Section Heading

Font size 16, Bold, Title case, left-aligned, spacing before and after 6 points.

1.3.1 Sub-Section Heading

Font size 14, Title case, left-aligned, spacing before and after 6 points.

1.3.1.1 Sub-Sub-Section Heading

Font size 12, Underlined, Sentence case, left-aligned, spacing before and after 6

Left points. Right

margin margin
If (Code has to be included)
1.5 inches { 1 inch
Use ‘Courier New’ with font size 10.
Use single line spacing and the spacing before and after the
paragraphs should be ‘0’ points.
}

1.4 Print Quality

Use laser printers or minimum 600 dpi inkjet printers.

1.4.1 Margins and Pagination

Left Margin 1.5 inches from the edge of paper.

Gutter 0 inches.

Top Margin 1 inch from edge of paper.

Bottom
margin 1.2 inches
Bottom Margin 1.2 inches from edge of paper.

Right Margin 1 inch from edge of paper.

Pages before Chapter 1 must have lower case Roman numerals, right aligned ½ inch
from bottom of page, starting with the ‘Copyright’ page that is numbered “ii”. Title
page is unnumbered, but is implied as number “i”.

First page of text uses the Arabic number “1” and pages thereafter carry consecutive
Arabic numbers, including the pages in the Appendices and the Bibliography. Arabic
numbers are positioned in the bottom right-hand corner, ½ inch from the bottom and
one inch in from the right edge of the paper.

Note: If required, footer can be used to provide any additional information in font size 10.

1.5 Equations
Equations and formulas should preferably be type-written in good quality word-
processing or graphics package.

All equations should be numbered in the format ‘(XX.YY)’ where ‘XX’ is chapter
number and ‘YY’ is the sequence number within that chapter; e.g. equation appearing
seventh in chapter two will be numbered as ‘(Eq 2.7)’.

(Eq 1.1)
1.6 References and Citation
The guidelines for citing electronic information as offered below are a modified
illustration of the adaptation by the IEEE documentation system and the style.

In all references, the given name of the author or editor is abbreviated to the initial
only and precedes the last name. Use them all; use et al. only if names are not given.
Use commas around Jr., Sr., and III in names. Abbreviate conference titles. When
citing IEEE transactions, provide the issue number, page range, volume number, year,
and/or month if available. When referencing a patent, provide the day and the month
of issue, or application. References may not include all information; please obtain and
include relevant information. Do not combine references. There must be only one
reference with each number. If there is a URL included with the print reference, it can
be included at the end of the reference.

Other than books, capitalize only the first word in a paper title, except for proper
nouns and element symbols. For papers published in translation journals, please give
the English citation first, followed by the original foreign-language citation See the
end of this document for formats and examples of common references. For a complete
discussion of references and their formats, see “The IEEE Style Manual,” available
as a PDF link off the Author Digital Toolbox main page.

Basic format for books:

[1] J. K. Author, “Title of chapter in the book,” in Title of His Published Book,
xth ed. City of Publisher, Country if not
[2]USA: Abbrev. of Publisher, year, ch. x, sec. x, pp. xxx–xxx.

Examples:
[3] G. O. Young, “Synthetic structure of industrial plastics,” in Plastics, 2nd ed.,
vol. 3, J. Peters, Ed. New York: McGraw-Hill, 1964, pp. 15–64.
[4] W.-K. Chen, Linear Networks and Systems. Belmont, CA: Wadsworth, 1993,
pp. 123–135.
Basic format for reports:
[5] J. K. Author, “Title of report,” Abbrev. Name of Co., City of Co., Abbrev. State,
Rep. xxx, year.

Examples:
[6] E. E. Reber, R. L. Michell, and C. J. Carter, “Oxygen absorption in the earth’s
atmosphere,” Aerospace Corp., Los Angeles, CA, Tech. Rep. TR-0200 (4230-46)-
3, Nov. 1988.
[7] J. H. Davis and J. R. Cogdell, “Calibration program for the 16-foot antenna,”
Elect. Eng. Res. Lab., Univ. Texas, Austin, Tech. Memo. NGL-006-69-3, Nov.
15, 1987.

Basic format for handbooks:

[8]Name of Manual/Handbook, x ed., Abbrev. Name of Co., City of Co.,
Abbrev. State, year, pp. xxx-xxx.

Examples:
[9] Transmission Systems for Communications, 3rd ed., Western Electric
Co., Winston-Salem, NC, 1985, pp. 44–60.
[10] Motorola Semiconductor Data Manual, Motorola Semiconductor
Products Inc., Phoenix, AZ, 1989.

Basic format for journals (when available online):

[11] Author. (year, month). Title. Journal. [Type of medium]. volume (issue),
pages. Available: site/path/file
Example:
[12] R. J. Vidmar. (1992, Aug.). On the use of atmospheric plasmas as
electromagnetic reflectors. IEEE Trans. Plasma Sci. [Online]. 21(3), pp. 876–
880. Available: http://www.halcyon.com/pub/journals/21ps03-vidmar

Basic format for papers presented at conferences (when available online):

[13] Author. (year, month). Title. Presented at Conference title. [Type of
Medium]. Available: site/path/file
Example:
[14] PROCESS Corp., MA. Intranets: Internet technologies deployed behind
the firewall for corporate productivity. Presented at
INET96 Annual Meeting. [Online]. Available:
http://home.process.com/Intranets/wp2.htp
Basic format for reports and handbooks (when available online):
[15] Author. (year, month). Title. Comp an y . C ity, State or Country.
[Type of Medium]. Available: site/path/file

Example:
[16] S . L . T a l l e e n . ( 1 9 9 6 , A p r . ) . T h e I n t r a n e t A r ch i -tec ture :
M a nag i ng i n f o r m a t i o n i n t h e n e w paradigm. Amdahl Corp., CA.
[Online]. Available: http://www.amdahl.com/doc/products/bsg/intra/infra/html
Basic format for computer programs and electronic documents (when available
online):
ISO recommends that capitalization follow the accepted practice for the language
or script in which the information is given.

Example:
[17] A. Harriman. (1993, June). Compendium of genealogical software.
Humanist. [Online]. Available e-mail: [email protected] Message: get
GENEALOGY REPORT

Basic format for patents (when available online):

[18] Name of the invention, by inventor’s name. (year, month day). Patent
Number [Type of medium]. Available: site/path/file

Example:
[19] Musical toothbrush with adjustable neck and mirror, by L.M.R. Brooks. (1992,
May 19). Patent D 326 189
[Online]. Available: NEXIS Library: LEXPAT File: DESIGN

Basic format for conference proceedings (published):

[20] J. K. Author, “Title of paper,” in Abbreviated Name of Conf., City of
Conf., Abbrev. State (if given), year, pp. xxxxxx.
Example:
[21] D. B. Payne and J. R. Stern, “Wavelength-switched pas- sively coupled single-
mode optical network,” in Proc. IOOC-ECOC, 1985,
pp. 585–590.
Example for papers presented at conferences (unpublished):
[22] D. Ebehard and E. Voges, “Digital single sideband detection for
interferometric sensors,” presented at the 2nd Int. Conf. Optical Fiber Sensors,
Stuttgart, Germany, Jan. 2-5, 1984.
Basic format for patents:
[23] J. K. Author, “Title of patent,” U.S. Patent x xxx xxx, Abbrev. Month, day,
year.

Example:
[24] G. Brandli and M. Dick, “Alternating current fed power supply,”
U.S. Patent 4 084 217, Nov. 4, 1978.

Basic format for theses (M.S.) and dissertations (Ph.D.):

[25] J. K. Author, “Title of thesis,” M.S. thesis, Abbrev. Dept., Abbrev. Univ., City
of Univ., Abbrev. State, year.
[26] J. K. Author, “Title of dissertation,” Ph.D. dissertation, Abbrev. Dept.,
Abbrev. Univ., City of Univ., Abbrev. State, year.

Examples:
[27] J. O. Williams, “Narrow-band analyzer,” Ph.D. dissertation, Dept. Elect. Eng.,
Harvard Univ., Cambridge, MA, 1993.
[28] N. Kawasaki, “Parametric study of thermal and chemical nonequilibrium
nozzle flow,” M.S. thesis, Dept. Electron. Eng., Osaka Univ., Osaka, Japan, 1993.

Basic format for the most common types of unpublished

references:
[29] J. K. Author, private communication, Abbrev. Month, year.
[30] J. K. Author, “Title of paper,” unpublished.
[31] J. K. Author, “Title of paper,” to be published.

Examples:
[32] A. Harrison, private communication, May 1995.
[33] B. Smith, “An approach to graphs of linear forms,” unpublished.
[34] A. Brahms, “Representation error for real numbers in binary computer
arithmetic,” IEEE Computer Group Repository, Paper R-67-85.

Basic format for standards:

[35] Title of Standard, Standard number, date.

Examples:
[36] IEEE Criteria for Class IE Electric Systems, IEEE Standard 308, 1969.
[37] Letter Symbols for Quantities, ANSI Standard Y10.5-1968.

1.8 Appendices
Title = ‘APPENDIX AA’ where ‘AA’ corresponds to A, B, C.... in sequential order,
font size 18, left-aligned, starting from line 1 of page.
Numbering will continue from references in a sequential order; e.g. if last page of
references is page 182, Appendix A will start from page 183 and so forth.
The text in appendices should be with single line spacing, and with 12 font size.
Solutions to some equations or Author’s publications or a list of publications arising
from MS work can be included in an appendix.
Chapter 1

INTRODUCTION

The introduction chapter of your project report is the one in which you provide all of
the basic information that the reader will need to understand the report which is to
follow. Such things as the background of your research, how you came to research
your topic, what your topic is and how it relates to the world around it, and what kind
of general principles and methodology you will be using to research your topic and
evaluate your hypothesis, are all aspects of what you will cover in the introduction
chapter.

1.1 Overview
To start writing your introduction chapter, first come up with a simple one sentence
summary of the goal of your research. The reader will come to the first chapter of
your project report expecting a statement of purpose. This statement should tell the
reader what the topic of the thesis/project is and what you hope to achieve. Then
elaborate the statement a little and explain it briefly [1].

1.2 Project Idea

Now tell the reader what your hypothesis is, as well as your basic reasons for
believing in the hypothesis. How does your knowledge of the reality of the field make
you lean towards one hypothesis or another? Explain to the reader how you will be
able to prove or disprove the hypothesis that you set out with through the course of
your research/work. Talk about any particular relevant issues that could affect the
course of the research, or any basic questions or problems that people might have
regarding the topic and how you will go about your research process. Try to anticipate
how people will react to your hypothesis and make sure that you are able to start your
project on a strong heading. It may be best to have the opening paragraph of your
report reviewed before you embark on the research process, to make sure that you are
on the right track (or at least that the track makes sense to others) before you set off
and put a lot of effort into collecting data.
1.3 Purpose of the Project
Next, you can talk about the background of the project. How did you choose the
project? What kind of greater historical context does the research that you are
engaged in exist within? You may want to talk about any related experiments or
research that specific people have done in the past, including landmark research cases
which are related to the topic at hand. This gives the reader a sense of how your
research fits into the greater scheme of things, and lets the reader compare what you
are about to present to the research which they may or may not already be familiar
with from leading figures in the history of the field.

1.4 Project Specifications

Section will describe detailed specifications of your design. Add project specifications
in tabular form and briefly explain them.

1.5 Applications of the Project

The subheading is self-explanatory. Tell the reader what difference your work
can/will make in real life.

Project Applications should be entered with bullets.

1.6 Project Plan

Give details of project plan. Project plan will contain details of how work is divided
into part I & II and how resource persons have been allocated. Use tables to give
details of project plan.

1.6.1 Project Milestones

Give distribution of tasks, task duration and resource person details for part I and II
separately

Table 1 Proposed Project Plan

Tasks Duration Source Person
Literature Review 02 Weeks Samina Khan
Signal Acquisition 02 Weeks Usama, Shiraz
Signal amplification and Filtration 04 Weeks Usama, Shiraz, Samina

Rectification 01 Week Usama, Shiraz, Samina

Envelope Detection and 02 Weeks Usama, Shiraz, Samina
Amplification
Processing over Arduino 1 week Usama,Shiraz,Samina
And Servo Control

1.6.2 Project Timeline

Give timeline for project part I and II separately. You should use Microsoft project to
show project timeline graphs.

Figure 1. Project Timeline

1.7 Report Organization
Finally, give the reader a sense of how the project report is organized. Provide some
kind of chapter by chapter breakdown to tell the reader what can be expected so that
the reader will be able to scan the report at first and have a good sense of what ended
up happening. Use solid principles of organization throughout your report, in addition
to hitting all the above topics in your introductory paragraph, to make your report as
readable as possible.
Chapter 2

LITERATURE REVIEW

This chapter will include all of you work before starting the core of your report. What
you studied and why you studied that particular article/paper or book.

1.1 Background Theory

Give detailed overview of the concepts and technologies used in proposed project.

1.2 Related Technologies

Describe what other technologies are related to your project work.

2.1.1 Related Technology 1

Go in detail of one technology very close to your work.

2.1.2 Related Technology 2

If required, select another appropriate technology related to your work and explain it.

1.3 Related Projects

Projects already done or currently being done related to your work [2].

Give details of two related projects.

1.4 Related Studies/Research

In what direction other researchers from your field are working. What is hot in
research these days and what is not? [3].

1.5 Limitations and Bottlenecks of the Existing Work

Whatever you discussed above, discuss their limitations and bottlenecks so that the
reader becomes aware of what needs to be done in this research area [4].
1.6 Problem Statement
Now tell the reader what your hypothesis is, as well as your basic reasons for
believing in the hypothesis. How does your knowledge of the reality of the field make
you lean towards one hypothesis or another? Explain to the reader how you will be
able to prove or disprove the hypothesis that you set out with through the course of
your research/work. Talk about any particular relevant issues that could affect the
course of the research, or any basic questions or problems that people might have
regarding the topic and how you will go about your research process

1.7 Summary
Summarize all what you have written in literature review.
Chapter 3

PROJECT DESIGN AND IMPLEMENTATION

This is the very core of your project/thesis/work. By now the reader is aware of your
goal, the relevant work going on and the tools you are going to use. Now explain from
beginning till very end all the methods you used to accomplish your results. Do not
hesitate in writing about all the techniques you applied but they were unable to give
you the required results. This is a part of learning process and should be included in
your report. The section headings in this chapter will be different for each report. Don
not hesitate in modifying/ adding/ removing any of these section headings as per your
requirement as you know best how you proceeded in your work and what were the
key steps features involved. Just make sure not to miss out on any of the steps. Some
sample section headings are given below. These won’t be explained as they are self-
explanatory and most probably will be amended by you according to your report
requirements [5].

1.8 Proposed Design Methodology

Describe the Design Methodology in detail. Add a detailed block diagram to shown
the main building blocks in the proposed design.
1.9 Analysis Procedure
Describe different options available for techniques/algorithms/hardware components
used in proposed design. Justify the use of techniques/algorithms/hardware that has
been selected.
1.10 Design of the Project Hardware/ Software

1.11 Implementation Procedure

Give Block diagram of the proposed implementation
1.12 Details about Hardware
In this design procedure we decided that how the posted messages from different
users on website will be displayed at any public place in the world by just using a
controller, displaying screen and a connection of internet.

The controller we selected for this purpose is Raspberry-Pi3 Model-B because it has
built in Wi-Fi and on board HDMI port which makes the interfacing very easy with
any screen. The Raspberry-Pi3 and display screen could be placed at the any public
place where we want to display or convey the messages to the public.

The Raspberry-Pi3 will access the website contents by connected to the internet
through its built-in Wi-Fi and display the Notices or Messages on the large display
screen using HDMI port and cable. The Ubuntu-Mate light operating system is
installed on Raspberry-Pi3 and then the kiosk mode is also implemented in the
operating system that will display the Message board screen in full screen view on
each boot-up without any external interrupt.

Figure 2. Block diagram of hardware design

1.13 Details about Software/Algorithm

In design procedure we decided that how should we design the user interface and the
outlook of main website and other pages. We also decided that what data we should
require from user for registration who want to post a message and the options we
should give to a user after a successful login to his/her account. We also design the
message panel screen where the posted messages will be displayed. After developing
and designing the Website we upload it to the owned online server domain of
“godaddy.com” for web hosting. We design the following pages using PHP and
HTML in a sequence[7].

Figure 3. Block diagram of software algorithm

1.14 Details of Simulations / Mathematical Modeling

1.15 Details of Final Working Prototype

1.16 Summary
Summary of all your methodologies.
Chapter 4
TOOLS AND TECHNIQUES

In this chapter, you will be discussing in detail all the tools used in your work. This
includes hardware, software and simulation tools or any other thing which aided in
your project. If multiple hardware/software tools are used, use subheadings and go in
detail of each one of them.

1.17 Hardware Tools used

Details about hardware used. Use subheadings to explain different types of hardware
used. [6]

1.18 Software(s), simulation tool(s) used

Details about software(s) used. Use subheadings to split different software, simulation
or mathematical tools used.

1.19 Summary
Summary of the chapter.
 Chapter 5

PROJECT RESULTS AND EVALUATION

In this chapter, you will explain all the results you achieved after completing all what
you explained in previous chapter. Try to find a balance while explaining your results.
Neither makes your project/work look worthless in case you were unable to achieve
the goals identified. Nor should you claim to have solved all the problems in the
world by the results you have achieved. Take a step by step approach as identified in
the section headings below.

1.20 Presentation of the findings

A general description of results of the project/thesis. Tables/Waveforms/Graphs
should be used to describe the results.

5.1.1 Hardware Results

Split the project in major parts and discuss the results for each part.

5.1.2 Software Results

Again split the project in different parts discuss the results for each part.

Table 2: Software Testing Results

Conditions Testing
Sensor 1 Before installing the sensors on project we have first attached the sensors on board
and connected them Arduino and with the help of Arduino IDE Software we have
seen the result on first sensors on screen

Sensor 2 Later Another sensor was integrated with previous one and both of the results we
displayed on screen by the help of Arduino IDE software

Pins Condition Now different conditions were implemented by programming in arduino IDE software
Test and results were observed over the screen

LCD Test We first tested the LCD by printing the “Hello Word” on it by programming at
ardunio software latter sensors were attached to see the proper results
1.21 Verification of design functionalities

1.22 Discussion on the findings

Elaborate your findings/results and provide a critical analysis. Comparisons with
some standards or other authentic work done.

5.3.1 Comparison with initial Project Specifications

What you initially claimed and what you achieved in the end.

5.3.2 Reasoning for short comings

Most probably there will be some results not in line with your goal, explain the
reasons for this e.g. Hardware/recourses unavailability, time constraints e.t.c.

1.23 Limitations of the working prototype

The goals/results you achieved if some constraints have or if they are for some
specific conditions, explain all these.

1.24 Recommendations and Future Work

What your recommendations would be to someone who wants to carry on with your
work where you left it or wants to improve it.

1.25 Summary
Summary of the results.
Chapter 6

CONCLUSION AND FUTURE WORK

What is the strongest and most important statement that you can make from your
observations? If you met the reader at a meeting six months from now, what do you
want them to remember about your paper? Refer back to problem posed, and describe
the conclusions that you reached from carrying out this investigation, summarize new
observations, new interpretations, and new insights that have resulted from the present
work. Include the broader implications of your results. Make sure you do not repeat
word for word of any part of project report above.
 REFERENCES

[1] P. Kocher, "Security as a new dimension in embedded system design," in

Proceedings of the 41st annual Design Automation Conference, 2004.
[2] S. Chattopadhyay, Embedded System Design, PHI Learning Pvt. Ltd, 2013.
[3] J. W. W. a. S. C. Henkel, "On-chip networks: A scalable, communication-
centric embedded system design paradigm," in Proceedings. 17th International
Conference on. IEEE, 2004.
[4] A. a. M. D. N. Sangiovanni-Vincentelli, "Embedded system design for
automotive applications," in IEEE Computer , 2007.
[5] P. Arató, "Hardware-software partitioning in embedded system design," in
IEEE International Symposium on. IEEE, 2003.
[6] "Atmel Studio," [Online]. Available:
http://www.atmel.com/products/microcontrollers/8051architecture/default.aspx
. [Accessed 21 October 2016].
[7] D. D. a. F. V. Gajski, "Specification and design of embedded hardware-
software systems," in IEEE Design & Test of Computers , 1995.
APPENDICES

Appendix – A

Record of Births by Calendar Year

Appendix – B