Академический Документы
Профессиональный Документы
Культура Документы
FACULTY OF ENGINEERING
Department Of Electrical And Electronic Engineering
I. JAHMEERBACUS
MAY 2004
It is essential that you produce a clear and concise report that reflects the literature
survey, problem identification, project aims and objectives, the engineering design work
carried out, tests performed and discussion of results. The emphasis should not be on
the length of the report, but rather on the way by which the above aspects are presented.
In this context, you should avoid downloading bulk text and images from books or the
Internet or use unconventional fonts or graphics with a view to impressing the reader.
You should rather show the reader that you have understood the problem at hand and
used an engineering approach to produce a working solution by working as a team with
your group members. You should also be able to explain the working principle and
design of each stage of the developed system.
REPORT FORMAT
With the format given below, the mini-project report should normally not exceed 30 pages
(excluding the appendix), and should not be shorter than 20 pages.
Margins:
Top, Bottom, Right: 25mm; Right: 30mm.
Equations:
Should be edited with Microsoft Equation, and should be numbered in ascending order in
each chapter: E.g:
di (t )
v s (t ) = i (t ) R + L (2.1)
dt
is the first Equation in Chapter 2.
Page Numbers:
Start with Page 1 at the beginning of Chapter 1. Page numbers should be centered at the
bottom of the page.
TITLE PAGE
The title page should include the following information:
• Mini-Project Title
• Student Names and ID Nos.
• A statement that the report is submitted in partial fulfillment of the requirements
for Practical Training (ELEC 1200) of the B.Eng. (Hons) in Electrical and
Electronic Engineering
• Date of submission
Page
Acknowledgement (iii)
Abstract (iv)
Chapter 1 Introduction 1
1.1 …
1.2 …
.
.
.
Chapter X Conclusion and Recommendations 20
References 22
Appendix 24
ACKNOWLEDGEMENT
Any person, institution, organization, department or lab, whose help or support you want
to acknowledge for the project.
ABSTRACT
A summary of 300 to 400 words of the practical application, the problem to be solved, the
approach used and the main results obtained.
LIST OF FIGURES
A list of all Figure Numbers presented in the report, and their title (E.g. Figure 2.1 Circuit
diagram of the Traffic Light Controller) along with the page numbers.
CHAPTER 1 INTRODUCTION
For this mini-project report the introduction should describe at least the following in
different sections:
1.1 Background
A preamble to the practical aspects and applications: E.g. For the design of a traffic light
controller example: How and why is traffic light control is important and/ or useful, what
are the main system requirements (like how to give priority to traffic and pedestrians, and
under what circumstances, etc.).
You should also survey the different works that have already been done in this area and
highlight their main features and shortcomings. Proper references should be included so
that the reader can refer to these articles.
NOTE:
• To enhance the report structure, the above sections may be broken down into
further sub-sections.
CHAPTER 2
This chapter should describe the design and implementation of the proposed system. For
this mini-project, the problem was formulated so that the system design can be described
in one chapter. For larger projects involving, for example, hardware and software design,
the system may be broken down into several parts, and more than one chapter would
normally be required to report the design.
The proposed system should be broken down into several functional blocks, as was done
in Chapter 1, and the design of each stage should be described in terms of:
If it is not possible to simulate the whole system in one step, the simulation results for at
least the individual stages must be shown. You should describe the tests performed on
the design in different sections of this chapter. As far as possible, the conditions for
simulation must be similar to the experimental test conditions. (e.g. component values,
supply voltages, etc.)
The equipment used to test the finished prototype (or each stage of it) should also be
listed, and the results can be expressed either graphically, in tabular form, in terms of
oscilloscope waveforms, or any other user-friendly means. It is most useful to express
the experimental results in a similar form to the simulation results so as to make the
comparison and discussion easier.
Conference Proceedings:
[1] Boost, M., Ziogas, P.S., “State-of-the-Art PWM Techniques: A Critical Evaluation”,
IEEE Power Electronics Specialists Conference, 1986, pp. 435-439.
Books:
[3] Mohan, N., Undeland, T.M., Robbins, W.P, “Power Electronics: Converters,
Applications and Design”, Second Edition, John Wiley and Sons, Inc., 1995.
Manuals:
[4] “Microsim PSpice & Basics: Circuit Analysis Software User’s Guide”, Microsim
Corporation, Irvine, California, 1996.
Research journals:
[9] Key, T.S., “Diagnosing Power Quality-Related Computer Problems”, IEEE
Transactions on Industry Applications, Vol. IA-15, No. 4, Jul./Aug. 1979, pp. 381-393
Magazines:
Dunker, K.F., Rabbat, B.G. "Why America’s bridges are crumbling”, Scientific
American, Vol. 268 No. 3, pp. 18-24, March 1993
Data Sheets:
[10] “ LM111/ LM211/ LM311 Voltage Comparator” Data Sheet, National
Semiconductor.
The Appendix must also contain the activities of the group over the project period. This
should be presented in tabular form as follows:
Week No. Activity Group Member Results
July 2004