Network Security Essentials

R&D projects

 
 

[List of R&D projects]

Students are required to produce a mini-project, building upon and complementing the material covered in class. You may be working with other class members as part of a team or decide to make an individual study. Teams will be formed during the third class, in plenty of time for you to meet, plan, and work with other members of your team. Projects must culminate with a short presentation for the class and the submission of a final report. The report will contribute to the final grading of the course.

A set of former, ongoing and suggested projects is to be found by following this link. You may select one of the suggested projects, or you may propose your own comparable project. All projects must be approved by the instructor. Teams/individuals must submit a well-organized proposal of roughly one page in length. The proposal should clearly describe the project to be undertaken, including the topic to be covered, any investigation, development, or experimentation to be conducted, and the expected results. Proposals will be reviewed and must be approved by the instructor.

IMPORTANT DATES

Budget your time wisely. Make a time-table for your project and take notice of the deadlines.

  • INITIAL TEAM MEETINGS: Class #3
  • PROPOSALS DUE: Class #4
  • PROPOSALS RETURNED: Class #5
  • PROJECT PRESENTATIONS/REPORTS DUE: Class #12

PRESENTATION GUIDELINES

Plan to give a 15-20 minute presentation, with time for questions and discussion. Presentations should be self-contained, and should be clear and precise. Briefly introduce the topic including any background information, describe the investigation, development, or experimentation that was conducted, and provide any demonstrations developed as part of the project, or describe the results of the investigation or experimentation.

The following format is suggested:

  1. Title. Name the project and all the team members.
  2. Outline. Summarize the full presentation.
  3. Introduction. Introduce the purpose and goals of the project. Provide any background material necessary to understand the presentation.
  4. Investigation, development, or experimentation conducted. Describe the actual work performed during the project.
  5. Results. Show any demonstrations developed or results achieved during the project.
  6. Conclusion.

REPORT GUIDELINES

Each term project will result in a detailed 8-26 page written technical report. The project report should be neat, readable, self-contained, and preferable written in English. Any class member should be able to understand your report, and benefit from the results you present. You should include adequate references and/or background materials and you should use tables, diagrams, graphs, figures, and portions of printouts to enhance readers' comprehension of your project.

The following format is suggested. You don't have to follow it exactly. Some sections may not be needed, or additional sections may be necessary.

  1. Title. Make it consise and catchy!
  2. Introduction. Include background material and discuss the scope and limitations of your project.
  3. Body. The body of your report. This includes the methodology used. Be sure to fully describe any figures, tables or diagrams you include. Present and discuss your Results.
  4. Conclusions. Summarize you key findings. Include recommendations, especially for future work and unsolved problems.
  5. Nomenclature (where applicable)
  6. References (must always be included), annotated if possible.
  7. Appendices, including supporting material as needed.

Do not submit complete computer outputs. Relevant excerpts from program listings or output should be included, but reduced to the size of the rest of the report and containing either as figures or tables in the text or as an appendix.

GENERAL GUIDELINES

Preferable the written reports should use 17x24 cm paper format with 9pt, Arial/Helvetica and Times Roman/Book Antiqua font. Top margin is set to 2,5 cm and bottom margin is set to 3,0 cm Left and right margins are set to 2,0 cm. You are encouraged to use the following templates for MSWord or LaTeX, respectively. Moreover, you should consider to follow this Guideline to have your report appear more professional.

Submit an electronic copy of the report in pdf format with an accompanying archive file (e.g., zip) containing the source files. The best reports will be collected into an edited ASE Technical Report with an assigned ISBN. The report will be published through the university web.

Grading of written reports will be based upon substantive content, appropriate organization and use of allotted report size, and effectiveness of the report. Multiple errors in grammar and spelling are unprofessional and detract from the clarity of your report and will be graded accordingly.

NOTE: Take the time to properly cite material written by someone else. Include references where applicable and put verbatim quotes in quotation marks. Do not paraphrase excessively. If you have questions about this, ask me.

 

[Home] [Plan] [Exercises] [Projects]

Copyright 2012, Aarhus University School of Engineering.
Course responsible: Associate Professor Rune Hylsberg Jacobsen