Project Calendar Overview

iv

First each group should select a topic from the following list: SIRS-Proj-Topics.pdf
A Doodle link will appear as an announcement on Fénix on Thursday, October 13th, 2016, 13:00, to allow each group to select and available topic.
Official group-to-topic assignments: SIRS-Proj-Topics-Selections.pdf

v

After the topics are officially attributed, the group has to prepare a proposal document.

vi

The proposal submission must be done on the week of October 24th until 20:00 of the weekday following the lab schedule .
Students with lab on Monday must submit before Tuesday, October 25th, 2016, 20:00.
Students with lab on Tuesday must submit before Wednesday, October 26th, 2016, 20:00.
Students with lab on Thursday must submit before Friday, October 28th, 2016, 20:00.

vii

The document is reviewed by faculty. A revised proposal taking the comments into account should be resubmitted before Friday, November 4th, 2016, 20:00.

viii, ix, x, xi

The group implements the project, using the lab sessions to receive feedback.
The solution should be built gradually, from basic solution, to intermediate, and to advanced.

xii

The group submits the project before Friday, December 9th, 2016, 17:00;
and enrolls in one of the presentation sessions chaired by their lab professor.

xiii

To complete the evaluation, the group will do a presentation of the work with slides, demo, and questions.
In some cases, a discussion may be necessary.

 

Project Calendar in detail

Week IV (2016-10-10_14): Topic selection

In this week, the lab guide is about Virtual Networking.

Topic selection:
Each student group must choose one of the proposed topics.
See the following document with the project topics list: SIRS-Proj-Topics.pdf

Topics will be assigned to groups using a Doodle pool. There will be a choice limit for each topic to ensure that student groups are evenly distributed by topic options. For this reason, each group should consider more than one topics, in case their first option is not available at the time of registration.

The Doodle poll link will appear on Fénix as an announcement on Thursday, October 13th, 2016 at 13:00.
The choice process closes on Friday, October 14th, 2016 at 20:00.

After the choice process closes, the official listing will be published here to confirm all information. After that, the groups can resume work on the project to detail their proposal.

See the following document with the official project topic selections for each group: SIRS-Proj-Topics-Selections.pdf.

 

Week V (2016-10-17_21): Proposal template

In this week, the lab guide is about Traffic Analysis.

During this week, each group should start preparing the project proposal according to the following guidelines.

Proposal

The project proposal should describe the problem and the proposed solution.
The use of UML diagrams is recommended for clear and concise communication.

Details:

  • PDF format
  • Mandatory file name "C XX W HHMM L proposal.pdf" (where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits, W is the weekday of the lab shift, HHMM is the time, L is the lab room number).
  • Limit 3 pages (excluding cover).
  • Pages should be numbered (preferably with a label like "Page X of Y").
  • Report cover: Project title. Headed by course name, group campus, group number. In the next row: group members sorted by ascending student number. For each student, include the number, name and professional photo.
  • Report body: The font should be no smaller than 11pt, with standard line and character spacing.

Mandatory body sections:

  • Problem (Given the chosen scenario, why is security necessary? What is the main problem being solved? Use around 200 words)
  • Requirements (Which security requirements were identified for the solution? Present as list)
  • Proposed solution (overview with diagram and explanation with around 200 words or less. Describe basic, intermediate, and advanced versions of the solution. Be explicit about keys and how they will be distributed.)
  • Tool references (libraries, etc. that will be used in the project. State if tool has been found/installed/tested/well-tested at the time of proposal)
  • Work plan (table containing one row per week until the submission date; and one column per group member with expected activities for the given week; some cells may be blank because of other courses. State clearly when basic, intermediate and advanced versions are expected to be achieved)

 

Week VI (2016-10-24_28): Proposal submission

In this week, the lab guide is about Firewalls. It is the last guide.

During this week students should present their proposal and receive instant feedback.

The proposal submission must be done until 20:00 of the weekday following the lab schedule.
Students with lab on Monday must submit before Tuesday, October 25th, 2016, 20:00.
Students with lab on Tuesday must submit before Wednesday, October 26th, 2016, 20:00.
Students with lab on Thursday must submit before Friday, October 28th, 2016, 20:00.
The submission is done on Fénix.

 

Week VII (2016-10-31_11-04): Proposal approval

There are no new lab guides from now on. From this point forward, the lab sessions are used for supporting the project development.

During this week the faculty reads the proposals and makes comments on them. In particular, the stated goals - basic, intermediate, advanced - are approved with or without changes.

At the end of the week, before Friday, November 4th, 2016, 20:00, a corrected proposal, taking the comments into account, should be submitted to Fénix for commitment.
The mandatory file name is "C XX W HHMM L proposal revised.pdf" (where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits, W is the weekday of the lab shift, HHMM is the time, L is the lab room number).

 

Week VIII (2016-11-07_11): Report template

During this week, each group should start implementing the project and the report according to the following guidelines.

Report

The project final report should describe the problem and the implemented solution, along with an evaluation of results.

Document:

  • PDF format.
  • Mandatory file name "C XX W HHMM L report.pdf" (where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits, W is the weekday of the lab shift, HHMM is the time, L is the lab room number).
  • Limit 4 pages (excluding cover)
  • Pages should be numbered (preferably with a label like "Page X of Y").
  • Report cover: Headed by course name, campus, group number. Followed by group members sorted by ascending student number. For each student, include the number, name, IST email and a professional photo. Project title.
  • Report body: The font should be no smaller than 11pt, with standard line and character spacing.

Mandatory body sections:

  • Problem (Given the chosen scenario, why is security necessary? What is the main problem solved? Use around 200 words)
  • Requirements (Which security requirements were identified for the solution? Present as list)
  • Solution (overview with diagram and explanation with around 200 words or less. Describe basic, intermediate, and advanced versions of the solution. Be explicit about keys and how they will be distributed.)
  • Results (What was actually implemented?)
  • Evaluation (How do you evaluate your solution? Mention strengths and weaknesses. Justify implementation choices.)
  • Conclusion (Ending statements in 1 or 2 paragraphs)
  • References (short list of essential tools and publications with a brief description of how it was used for the project)

 

Week IX (2016-11-14_18): basic solution

The project support continues during this week. Students are encouraged to present the basic solution working.

 

Week X (2016-11-21_25): intermediate solution

The project support continues during this week. Students are encouraged to present the intermediate solution working.

 

Week XI (2016-11-28_12-02): final solution

The project support continues during this week. Students should present their complete solution working, as well as a complete draft of the report.

 

Week XII (2016-12-05_09): final submission

The project support in the labs ends during this week.

The project must be submitted before Friday, December 9th, 2016 at 17:00.
Students should use this final week to prepare the final presentation, making only corrections and small improvements to the solution.

The submission should contain a ZIP file with:

  • ReadMe file, describing the required platform (e.g. Linux 64 bit, Ubuntu 16.04.1 LTS, Java 8u101) and setup instructions;
  • All configuration files and scripts required to configure the solution on the specified platform;
  • All developed source code;
  • Existing tests and example files.

The mandatory file name is "C XX W HHMM L solution.zip"
(where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits, W is the weekday of the lab shift, HHMM is the time, L is the lab room number)

The report should be submitted separately, also in Fénix, in PDF format. There is a one day tolerance for the submission of the report.

The mandatory file name is "C XX W HHMM L report.pdf"
(where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits, W is the weekday of the lab shift, HHMM is the time, L is the lab room number)

After the submission, each group should enroll with the group code C XX in one session where they will present and it must be a session chaired by their lab professor. (where C is A for Alameda, T for Tagus, and XX is the Fenix group number in two digits)

The enrollmentl links will be announced ten minutes after the project submission deadline.

 

Week XIII (2016-11-12_16): presentations

During this week (and probably during some days of next week), the projects are presented and evaluated in public sessions. The slot reservation process will be announced later.

Each group presents its solution (5 minutes for slides), show how it works (5 minutes for live/recorded demonstration) and answer individual question (5 minutes for questions and answers).
If necessary, a discussion will be scheduled with the group.

It is highly recommended that the presentation includes a slide with the architecture figure, a slide with the key distribution, and a slide with the protocol, step-by-step.

Each group member must participate and talk in the presentation, and be prepared to answer questions.

Presentation session participation

Moreover, each student must attend at least one more of the project presentation sessions that will be announced, to learn from the projects of other groups. There will be a record of presence to keep track of this participation requirement.

Slides and recorded demo submission

After the presentation, and to complete the evaluation process, each group should also submit the presentation PDF.

The final slide of the presentation should contain a clickable link (URL) pointing to the demo video, uploaded to a public video service such as YouTube or Vimeo. These videos will be compiled in a playlist that will be made available on the course page, after all the project evaluations are completed.