Telecom Seminar Presentation

7/28/2019 Telecom Seminar Presentation

1/26

1

Seminar: Writing

Technical Papers

Dr. Nizar Zarka

Telecom Department, HIAST

2013


2/26


3/26

3

Structure of a Technical Paper

About 20 pages Title Authors

Table of Contents

List of Figures

List of tables

List of abbreviation

Abstract

[Keywords] Optional

1. Introduction

2. State-of-the-Art

3. Implementation Description 4. Results & Analysis

5. Conclusions

Acknowledgements

References

[Appendix] Optional


4/26

4

Structural Components

Title

Title of the seminar

Authors

Student Name, Supervisor Name

CoordinatorsDr. Nizar Zarka & Mrs. Nada Muhana

Date and Semester


5/26

5


Table of Contents

List of Figures

List of tables

List of abbreviations

No Page Number(or use small roman number i,ii,iii,)


6/26

6


Add Page Header (page number, Title)

Abstract Basic Problem

Hint on solution approach Most important results

Limited to about (5%)

No references or figures

[Keywords] Selected to facilitate computer search


7/26

7

Structural Components1. Introduction

Problem background and importance

Brief description of proposed solution

How is it different and superior to other solutions

Main results, no detail Summary of report organization

Limit to more or less 10% of document length

2.State-of-the-Art (related works) Discuss ALL related work

Highlight the relevance to YOUR work

show gaps between current research and yours

Limit to more or less 15% of document length


8/26

8

Structural Components 3.

Can have one or several sections and subsections

Describe proposed model or approach

Assumptions, conditions

Provide theoretical foundations and analytical derivations

Exploit the power of graphics, Figures, tables

About 30% of the document length


9/26

9

Structural Components4.

Describe your experimental design

Validation

Present the results

Perform analysis and discussion of results Focus achievements and limitations

About 30% of the document


10/26

10


5. Conclusions (and Future Work)

Summarized problem statement

Summarized solution approach

Highlight main results and contributions Why is it worthwhile

What is to be done next Solution improvement

Applications to other scenarios

Expansions of methodology

About 10% of the document


11/26

11


AcknowledgementsAcknowledge those who helped you

Bibliography

Provide complete list of references cited in the report

[Appendix]

Essential materials for completeness: detailed proofs Special graphs or plots


12/26

References Students should read literature and afterwards

write in his own words.

It is forbidden to copy all textfrom other sources.

The supervisor has the right to reject any

seminar that contains several copied text, morethan 20% of the seminar.

It is necessary to cite every copied sentence,

e.g. [SWT06] 12


13/26

References

Only the mentioned references in the report are included in

the list

Reference list should contain mostlyjournal and conference

papers, books, standards, white paper.

Wikipedia: No guarantee about correctness ofinformation.

13


14/26

References [GM05] Goossens, M.; Mittelbach, F.: LaTeX-Begleiter. 2nd Edition,

Pearson Studium, 2005.

[JRM04] Jaeger, M.; Rojec-Goldmann, G.; Mhl, G.: QoS Aggregation

for Web Service Composition using Workflow Patterns.Proceedings of the 8th International Enterprise Distributed Object

Computing Conference (EDOC 2004),Vol. 4, pp.126-130,

Monterey, California, USA, 2004.

[SWT06] Seipold, T.; Wienzek, R.; Thien, D.: DOs and DONTs forseminars. http://www-i4.informatik.rwth-

aachen.de/content/teaching/seminars/dodont_e.html, 2006

14
http://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.html


15/26

ReferencesFor a book give:

the author,

the title, and the edition numberif there is one,

the name of the publisher,

the year of publication

[GM05] Goossens, M.; Mittelbach, F.: LaTeX-Begleiter. 2nd Edition, Pearson

Studium, 2005.

15


16/26

ReferencesFor a journal paper or conference give:

the names of the authors,

the title of the paper,

the title of the journal, the volume number of the journal,

the first and last page numbers of the paper.

the place of the conference

the year of publication,

[JRM04] Jaeger, M.; Rojec-Goldmann, G.; Mhl, G.: QoS Aggregation for

Web Service Composition using Workflow Patterns. Proceedings of the

8th International Enterprise Distributed Object Computing Conference,Vol. 4, pp.126-130, Monterey, California, USA, 2004.16


17/26

References

For an internet reference give:

the author of the web page,

the title of the web page, the complete URL.

the date of the web page

[SWT06] Seipold, T.; Wienzek, R.; Thien, D.: DOs and DONTs for

seminars. http://www-i4.informatik.rwth-

aachen.de/content/teaching/seminars/dodont_e.html, 2006

17
http://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.htmlhttp://www-i4.informatik.rwth-aachen.de/content/teaching/seminars/dodont_e.html


18/26

18

General Guidelines for Documents

Use A4 paper format

Usual borders like 2,54cm

Text should be in Times New Roman12pt, or Arial fonttype font size of 11pt.

Use blocked text alignment (alignment to left and right)

Insert blank line between the paragraphs.

Use punctuation


19/26

19

Figures and Tables You should use figures and tables for explanation

Figures & tables should be numbered independentlyas Figure x: Title

(aligned as centered)

Do not include a figure/table without explanation in the text

Reference all tables/figures like , see fig1., as shown in table2.


20/26

Figures and Tables Figure should be ofgood quality

Sometimes it is necessary to copy figures

(simulation results)

If you copy figures you have to make clear fromwhich source

20


21/26

Readability Core statements should be emphasized by using an

italicorbold style

Each paragraph should have emphasized word

Give the seminar to the English teacher forgrammar

correction.

It is not acceptable to deliver a work full of mistake. In

such a case, the supervisor is allowed to reject your

seminar

21


22/26

General rules on writing If it is necessary to bring in your own opinion,

you can use: In the autho r opin ion

Avoid some formulations like: I will try, Imnot sure,

Use only formulations which make the papersound well-stated.

22


23/26

Dos and DONTs It is Not possible to do the seminar work in a few days!

Do not vanish into space for month and come back only a few days

before the deadline

Plan a schedule for working at the beginning:

discussion with the supervisor

literature survey Read the basic material and understand it

designing a document template,

writing chapters in own word (Do not copy text from other sources!)

discussion with the supervisor Give written feedback to the supervisor/English teacherand

Do not ignore their suggestions

Do not run to the supervisor for each small problem23


24/26

24

Writing GuidelinesBrainstorm your ideas

Writing Order 1. Sate-of-the-Art

2. Implementation Description

3. Results and Analysis 4. Conclusions

5. Introduction

6. Abstract

7. Title 8. The rest of the document


25/26


26/26

26

Writing Guidelines

Read, read, and then read again Nothing better than the human touch

Have someone else read your paper and criticize it

The hardest the better

When reporting, stick to past tense

When writing in future tense, first person, future formed with

shallrather than will