The iLab Experience a blended learning hands-on course concept you - - PowerPoint PPT Presentation

you set the focus

The iLab Experience

a blended learning hands-on course concept

Do It Yourself - Hardware YE - Topic Outline

May 29, 2018

YE 1st Lecture IoT DIY HW YE Topic Outline Kick Off, IPv6 IoT Smart Space SW & measr Advanced Wireless Playground Minilab 2 YE Didactics, Tools & iAdvise YE Review Presentation YE Final Presentation, Wrap-Up

BGP Minilab 1 WWW Security Your Exercise Topic Pitch summer term 2018

Giving good Feedback Prepare Your Exercise Prepare Your Exercise

Collaborative Memory

what are the most important things to remember from the last lab?

Oral Attestations

• Overall went well.
• Congratulations to you all for passing!
• Tipp for next time: meet with your team partner some days before

the exam and ask each other for some time about the topics. Do actually fully answer them to each other.

you set the focus

The iLab Experience

a blended learning hands-on course concept

Your Exercise - Topic Ouline

Your Exercise Sequence

Voting Outline 1st Lecture Review Final Lecture

Didactics Giving Feedback

Security

Available Topics

• 1. DNS delegations to other zones & querying DNS with GO. —> 205
• 2. MassDNS. —> 208
• 3. DNSSec with Linux Tools and GO. —> 206
• 4. Scanning DNS and DNSSec and mapping results to ASN/ Geolocations. —> 203
• 5. RPKI Validation. —> 201
• 6. DANE-TLSA. —> 209
• 7. CAA. —> 204
• 8. Certificate Transparency and OCSP revocation. —> 202
• 9. go-tlsscanner, BGPStream, and AS dynamics. —> 207

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

create your own exercise

Scanning DNS + DNSSEC and mapping to ASN/Geolocation

Victoria Simon, Kostiantyn Redko, Group 203

Outline Lecture

• DNS/DNSSEC

– DNS introduction – DNS file example – DNS operators – DNSSEC overview

• Practical applications of IP address mapping

– What is it used for

Outline PreLab

• Plan:

– Give some more background on DNS/DNSSEC – Give a short introduction to command line tools and Go – Give an example program that uses geoip2 database

• Requirements:

– Basic understanding of DNS and DNSSEC – Introduction to Go programming language

• Тооls:

– Dig, whois – geoip2-golang tool and database

Outline Lab

• Create a DNS server on the local setup
• Scan the sample DNS file
• Identify common errors when scanning
• Perform a large-scale scan for:

– Alexa 10k – Random 10k

• Parse the output and map IP addresses to locations/ASNs
• Create several charts from that data

Learning Goals

The Following Learning Goals are Covered in the Lecture PreLab Lab

Better understanding of DNS and DNSSEC

X X X

Identify common errors when scanning

X

large-scale Scan DNS and DNSSEC

X

Better understanding of Go

X X

Use Go to perform IP address mapping and to do statistics

X

Teaser Practical Part

DNS Server Client

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

DNSSEC - reach the website you asked for

Alvin, J.Erasmus - group 206

Outline - Lecture

• quickly revisit DNS
• Why is DNS bad? (show shortcomings)
• Motivation for DNSSEC
• How does DNSSEC work

Outline PreLab

• Teach how DNSSEC is deployed and used
• Required Background:

○ DNS (small revision) ○ GO programming (small tutorial?)

• Tools: everything needed to check

DNS/DNSSEC records

Outline Lab

• Setup DNSSEC for own domain
• manually verify DNSSEC
• automatic verification (GO programming)

What Will Your Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab DNSSEC security and the concept of delegation X X DNSSEC zone walking X x The use of DS, DNSKEY, RRSIG, NSEC and NSEC3 x X X Use Go to query DNSSEC records, verify signature of RRSIG, and complete DNSSEC chain X x

Teaser Practical Part

webserver serv.sub.top DNS-Server (for sub.top) DNS-server (for top) sub domain .sub.top top domain .top client

1 2 5 4

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

create your own exercise

Securing Internet Routing using RPKI

Team 201: Eidenmüller, Thomas; Schwarzenberg, Christoph

Outline Lecture

• Motivation: Securing BGP
• Introduction: RPKI & ROA
• Current deployment state

Outline PreLab

• Recap: BGP
• Security issues in BGP
• RPKI & ROA
• Prefixes and their maximum length
• Tools:
• Dragon Research Labs RPKI Toolkit
• Quagga/Cisco 800 series

Outline Lab

• Setup small Internet (similar to BGP lab)
• Deploy own RPKI Validation server
• Set up validated router
• Set up “bad“ router
• 1. Announce “forbidden” prefixes
• 2. Exploit maximum length quirk

➢ Discover effects of secured routing

What Will Your Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab Learn about RPKI and RPKI ROA X X Deploy a partially RPKI validated Internet X X Understand and exploit the max. prefix length problem X X Understand and verify the chain of trust X X X Discover the effects of secured routing X X X

Teaser Practical Part

RPKI Validator AS 1 “Good AS“ AS 2 “Good AS“ AS 3 “Bad AS“ User (Ping) Monitor3

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

iLab2 —Your own exercise BGP Anomaly Analysis

207 Inkeri Sepp¨ al¨ a & Philipp Trucks¨ aß

Outline Lecture

TLS encryption & authentication Routing, BGP artifacts, prefixes, anomalies & hijacks Recognizing attacks and differentiate from accidents

Outline PreLab

Basic understanding of certificates & BGP routing Differentiate anomalies & attacks through continuous TLS scanning Tools: BGPStream, go-tlsscanner, golang scripting

Outline Lab

Run TLS scan on Alexa Top 1M & hash certificates Use BGPStream for historical and live data & evaluate output Write go-script to detect (sub)MOAS events from the stream Detect affected domains Extend script to identify legitimate anomalies via TLS key consistency

What will your students learn?

Teaser practical part

WWW 1x PC pp. Access to WWW golang development setup

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

create your own exercise

Who has the DNS?

Shen Hu and Andreas Wehe (208)

Outline Lecture

• DNS mechanism at scale
• Who is the DNS authority, slight trust issues
• DNS outsourcing & censorship
• Teaser: measurement to plot to paper

Outline PreLab

• DNS components in detail
• DNS basics: authority, cache, resolver
• “Manual crawl” with dig
• Man massDNS
• Ipynb simple plot

Outline Lab

• Warm up: Dig, probe one website
• Analyse the DNS response: What do we get?
• Setup Massdns & explore Alexa top 1M
• Ipynb: graphical impression of DNS sources
• Focus on outsourcing DNS

What Will Your Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab Understand DNS participants: authority, cache, resolver X X X Understand challenge of probing the internet at scale X X Learn to use tools: dig, massDNS/Zmap X X Employ IpyNB for number crunching for visualization X X Reflect roles of DNS providers in the infrastructure X X X

Teaser Practical Part

This is your playground:

The Internet

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

Trust me, I am a DANE-TLSA

Sebastian Borchers, Mihailo Rajacic, Team 209

Outline Lecture

➢ Problems with CA we are facing currently ➢ If CA is hacked/breached, attackers can issue certificates and fake for example to be your bank's website. Knowing that lots of CA’s exist, it can bring a lot of potential attacks ➢ Solution: DANE-TLSA ➢ We explain what it is and how it can solve the problem ➢ Why is it not yet mass deployed? ➢ What is so interesting? ➢ DNS is one of the key components of the Internet, but it is also vulnerable -> you enhance this and make it more secure ➢ Imagine you want to do your online banking, but somebody fakes the certificate of your bank's website and scams you. With Dane-TLS it would not have happened

Outline PreLab

In prelab we are planning to show: ➢ Brief reminder of how basic DNS works Introduce NSLookUp/Dig/... ➢ Why DANE-TLSA is necessary (Security, independence of CAs) ➢ TLSA-Record: Usage and Structure ➢ How DNS is more secure with DANE ➢ Highlighting the necessity of DNSSEC, in order for DANE to be trustworthy

Outline Lab

In Lab part our goal is to: ➢ Setup Lab system script ➢ Write Go code template to retrieve certificates with TLS ➢ Write Go code template to retrieve DANE-TLSA records and parse them according to the 2x3 different storage options defined by the IETF ➢ Write Go code template to determine whether a certificate retrieved via TLS is correctly specified in DANE-TLSA ➢ Perform Man In the Middle attack ➢ Make efficient hints for students to complete Go code templates and make them work

What Will Your Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab Understand theoretical aspect of DANE-TLSA X X Learn why DANE-TLSA is important, but not yet in mass use X X Understand and use TLS certificates X X X Learn importance of DNS security X X X Complete Go code exercises on DANE-TLSA X

Teaser Practical Part

LiteratureYour Students Learn?

[1.] https://tools.ietf.org/html/rfc6698 [2.]https://docs.google.com/document/d/1UFdNEBR65OPrLNlvfWIyyolSF0U2WrnateKl7o s5yaE/edit?usp=sharing [3.] https://datatracker.ietf.org/meeting/87/materials/slides-87-dane-2

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

create your own exercise

Certification Authority Authorization (CAA)

Caroline Gergen | Juan Jaramillo | 204

Outline Lecture

• Theoretical background of CAA
• Importance of CAA
• Structure and how to obtain CAA records
• Pros and contras of CAA

Outline PreLab

• Introduction to the CAA format and records
• Vulnerabilities and alternatives to CAA
• Error potential of CAA

Outline Lab

• Usage of the „dnscaa“ tool
• Retrieve, parse and evaluate CAA records
• Handle revoked CAA Records

What Will The Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab Theoretical background of CAA X Pros and contras of CAA X Understand the CAA format X X Retrieve and parse CAA Records X X Usage of the „dnscaa“ tool X Handle revoked CAA Records X

Teaser Practical Part

This is your playground:

Order of Presentations

Team Topic 203 Scanning DNS and DNSSec and mapping results to ASN/Geolocations 205 DNS delegations to other zones & querying DNS with GO 206 DNSSec with Linux Tools and GO 201 RPKI Validation 207 go-tlsscanner, BGPStream, and AS dynamics 208 MassDNS 209 DANE-TLSA 204 CAA 202 Certificate Transparency and OCSP revocation

create your own exercise

Guess the correct log – CT insights

Berkay Kozan, Jan Krol Group 202

Outline Lecture

• What do you plan to teach in the lecture?
• The vulnerabilites of SSL.
• How CT operation works.
• How log proofs work.
• Why is your topic interesting?
• It shows modern and future technology in web security.
• Every secure website has to use CT nowadays.
• What cool stuff do you want to communicate to those doing

your planned lab?

• This lab will be in the style of a TV game-show for IT experts(nerds)

Outline PreLab

• What do you plan to do in the PreLab?
• Deepen the SSL handshake and vulnerabilities
• Show the technology behind CT like Auditors, Monitors and Log Proofs
• What is the required Background for the lab?
• The students should know SSL handshake
• Understand how log proofs work
• What are relevant tools you present?
• Chrome Developer Tools & openSSL

Outline Lab

• What do you plan to do in the Lab?
• In the theme of a nerdy TV game show, the participants have to fetch data from CT log and

establish a TLS connection to the game show safe

• What is the general setup?
• There will be 2 computers needed: a web server and a client.
• In which parts do you structure the lab?
• Setting up and establishing SSL connection
• Fetch data from CT log
• Compare SCT in TLS connection with logged SCT
• Students write a small auditor which fetches SCTs regularly in order to win the big prize in the

game

What Will Your Students Learn?

The Following Learning Goals are Covered in the Lecture PreLab Lab Students understand CT operation X X X Students understand the vulnerabilities of SSL. X X Students understand how log proof works X X Students write code to fetch data from CT log X X Students write code to compare SCT in TLS connection with logged SCT X X Students write a small Auditor for CT that fetches SCTs regularly and compares with what it sees in the TLS connection X

Teaser Practical Part

ds2os.org/

Orchestration Distributed Smart 2pace System

DIY - Hardware Creation

Orchestration Distributed Smart 2pace System

Smart Space Orchestration

Physical World Physical World Computer Virtual World Computer

}

Three parts

• DIY HW
• Build an actual hardware device
• Work with a microcontroller
• DIY SW
• Learn about semantic modeling, middleware, blackboard coupling,

autonomous management, …

• P2P Measurements
• Learn about doing and evaluating measurements in a distributed

system.

ds2os.org/

Orchestration Distributed Smart 2pace System

ID card-based Reconfiguration of a Smart Room

Profile mop Profile b Profile Standby

The ID cards can be used to configure Smart Environments

Profile mop Profile b Profile Standby

The ID cards can be used to configure Smart Environments

“So what?”

DIY Hardware

13€ 60€ 10€ 40€

<200€

Dave Mellis Tom Igoe Gianluca Martino David Cuartielles Massimo Banzi time 2005 Creating your own hardware is difficult. Creating your own hardware is easy. *HW Maker Culture

Orchestration Distributed Smart 2pace System

TWO DIY Maker Cultures

DIY Hardware

DIY Software

Arduino DS2OS Smart Device Smart Space App time ?

2005

Creating your own IoT Software Apps is difficult. Creating your own IoT Software Apps is easy.

Orchestration Distributed Smart 2pace System

DIY Hardware

DIY Hardware

DIY Software Arduino DS2OS Smart Device Smart Space App time 2016

ds2os.org/

Orchestration Distributed Smart 2pace System

s2o - hardware

Marc-Oliver Pahl

Orchestration Distributed Smart 2pace System

What is this about?

Smart Devices

A hardware device that can sense and interact with its environment via sensors and actuators, and that can be managed remotely using software is called Smart Device.

Smart Spaces

A physical space that contains smart devices is called Smart Space.

Smart Space Orchestration

Monitoring and controlling (managing) Smart Devices within a Smart Space with software is called Smart Space Orchestration.

Orchestration Distributed Smart 2pace System

Creating Hardware

time 2005 Creating your own hardware is difficult. Creating your own hardware is easy.

Orchestration Distributed Smart 2pace System

Massimo Banzi - one of the creators of Arduino 2012 TED talk

Orchestration Distributed Smart 2pace System

Arduino Video

• Arduino
• Created 2005 at IVREA for simplifying interaction design class
• Industrie 3.0 (create objects on your own)
• Open Source Hardware => Makers Movement
• “you have unlocked” … “I just feel overwhelmed” … “going into

every field you could imagine”

Orchestration Distributed Smart 2pace System

Do It Yourself (DIY) Hardware

You will experience it in this lab…

Orchestration Distributed Smart 2pace System

Introduction to Electronics

The electrical engineering details will not be part of the exam. Slides by Alexander Güssow

Orchestration Distributed Smart 2pace System

How is a Breadboard cabled?

Agenda

• Introduction to Electronics

– Voltage and current – Units and parameters – Resistance: Ohms Law and Kirchhoff's Laws – (Light Emitting) Diodes

• Common Sensor types

Voltage in practice

• Voltage 𝒗 𝒖 : ℝ → ℝ
• Always measured between two points
• 𝑣 𝑢 = 𝑑 where 𝑑 ∈ ℝ

DC Voltage

• 𝑣 𝑢 = û sin 2𝜌𝑔𝑢

AC Voltage

• Touching >50V AC or >120V DC can harm you

Voltmeters measure static and fluctuating voltages

Oscilloscopes display time-variant voltage curves

Current

• Voltage sources: Pump analogy
• Closing the circuit

– Charge Flow?

Current is the charge flow rate in a circuit in Coulomb/s.

Current in practice

• Current 𝒋 𝒖 : ℝ → ℝ
• Different charged particles
• Actual direction unknown
• Closed electric circuit
• Stopping large currents quickly is dangerous

Ammeters measure static and fluctuating currents

Voltage and Current

Measurements

Common units and parameters

Name Symbol SI-Unit Formula Voltage U or u(t) or V V Current I or i(t) A Electric Power P W 𝑄 = 𝑉 ⋅ 𝐽 Electric Energy W Ws, J 𝑋 = 𝑄 ⋅ 𝑢 Electrical resistance R Ohm (Ω) 𝑆 = 𝑉/𝐽

Ohms Law

• R is constant
• One free variable remains
• Intrinsic property
• Physical device: Resistor
• Color of the rings encodes

their value

Resistance

𝑆 = 𝑉 𝐽 Resistor (circuit symbol) Resistor (picture)

𝐽(𝑉) = 𝑉 ⋅ 1 𝑆

Resistor Current-Voltage characteristic

Resistor color codes

Kirchhoffs 1st Law

„The sum of currents into and out of any single node of a network is always zero.“ Pay attention to the direction of the current-arrows:

• Arrows into a node are positive
• Arrows out of a node are negative

Kirchhoffs 1st law holds for all nodes in a circuit.

𝑗𝑙

𝑜 𝑙=1

= 0

𝐽 − 𝐽1 − 𝐽2 − 𝐽3 = 0

Kirchhoffs 2nd Law

„The sum of Voltages in any closed loop through a cirquit is always zero.“ Source: http://www.elektronik-kompendium.de/sites/grd/0608011.htm, as of 19.11.2015

𝑉2 + 𝑉1 − 𝑉𝑟1 − 𝑉𝑟2 = 0

𝜁1 − 𝑆1 ⋅ 𝑗1

𝑃ℎ𝑛𝑡 𝑀𝑏𝑥

− 𝑆2 ⋅ 𝑗2 = 0 𝜁2 − 𝜁1 − 𝑆2 ⋅ 𝑗2 − 𝑆3 ⋅ 𝑗3 = 0

Resistor superposition

Source: http://www.iris.uni-stuttgart.de/lehre/eggenberger/eti/, Chapter 8, as of 19.11.2015

Voltage divider circuit

Known: U Wanted: R1 and R2 such that U1 and U2 are what we want

• Choose two of: I, R1, R2
• Then solve:

𝑉1 = 𝑉 𝑆1 𝑆𝑘

𝑜 𝑘=0

• Loading the output also

changes U1 and U2

Current divider circuit

Given I, R1 and R2, what are I1 and I2? 𝐽1 = 𝐽 1/ 1/𝑆𝑘

𝑜 𝑘=0

𝑆1

(Light Emitting) Diodes – I-V Diagram

Source: http://electronics.stackexchange.com/questions/76367/accounting-for- led-resistance, as of 19.11.15

LEDs I-V Diagram, Case specs

Source: http://www.electronics.dit.ie/staff/tscarff/DT089_Physical_Computing_1 /LEDS/Leds.htm, as of 19.11.15

How to actually use LEDs

• 𝐽𝐸𝑗𝑝𝑒𝑓 𝑊

𝐸 = 𝐽𝑇 𝑓

𝑊𝐸 𝑜⋅𝑊𝑈 − 1

• Current rises exponentially with voltage
• Diodes will break if the 𝐽𝐺 current is exceeded
• Linearize & shift this using a Resistor in Series
• Kirchhoff‘s 1st gives: 𝐽𝑀𝐹𝐸 = 𝐽𝑆 so let 𝐽 = 𝐽𝐺

𝑛𝑏𝑦

• Choose suitable R such that the LED is only at about

80% 𝐽𝐺

𝑛𝑏𝑦 when the circuit is operating

Resistor-Diode and Diode I-V Diagram

Source: Own work using LTSpice simulation program, IN4148 Diode

Common Sensors

Resistive type

• Used like a resistor
• Resistance will change

with measure

• Correlation can be non-

linear Digital type

• Analog – Digital

conversion on-chip

• Digital signal

– PWM (Automotive) – Manufacturer specific protocol – Bus (I2C, CAN, ...)

Microcontroller interfaces

I2C / TWI GND, TCL, SDA Master-Slave-Bus GPIOs PxN, i.e. PB1

UART / Serial TIA-232-F GND, Rx, Tx Point-to-Point SPI SCLK, MOSI, MISO, nSS / nCS Master-Slave-Bus Selected Star or Daisy-Chaining

Using Manufacturer Specific Interfaces

• Read Datasheet

– Voltage levels – Timing requirements – Sample comm diagrams

• Debugging tools (multimeter, oscilloscope

protocol analyzer)

• Real time requirements

(Embedded) Computer Architecture

Bare metal

• Avoid non-determination
• Get maximum run time
• Similar to OS-like solutions

– Preemption – Priorities – Cyclic approach – Event driven approach

Operating system

• Desktop OS are non-

deterministic

• Real time OS (RTOS)

– Priority Scheduling – Preemptive Scheduling

• System libraries run time is

known / bounded

Arduino Mega 2560

• 16 MHz ATmega2560
• 8 kB RAM
• GPIO, max. 1 MHz
• UART, I2C, SPI
• ADC, (PWMDAC)
• Bare Bones

Arduino Hardware Architecture

ATmegaX: 8-Bit Harvard RISC

USB/Programmer (ATmega16U2)

you set the focus

The iLab Experience

a blended learning hands-on course concept

Your Exercise - Topic Ouline

• Week -4: Concept & T
• pic Pitch
• Prepare your outline talk
• Week -1:Outline Presentation
• Present a first structure for your lab, prelab, and lecture.
• Week 1: Didactics & T

echniques & Preparation

• Lecture Preparation (most relevant concepts?)
• Prelab Preparation (detailing the lecture content + tools + more)
• Practical Part Lab Preparation (no cooking recipe)
• Week 2: Your lecture
• Finalise and improve your content.
• Week 3: Review and Get Reviewed
• Review other team
• Get reviewed by other team
• Week 4+5: Present the lab and the feedback received & next steps
• Improve by materialising the feedback
• Week 6: Final presentation (Lecture with lab outlook, highlights)

peer grading

• 1 slide deck for topic outline

presentation (both talk!)

• Slide deck lecture (both talk!)
• Ready PreLab, Lab
• Review report
• Slide on review feedback &

planned improvements

• Final lecture slides
• Final PreLab, Lab, Peer Grade

Expected Artefacts

your exercise

iAdvise

ralph.holz@sydney.edu.au Mon Tue Wed Thu Fri

Exchanging about the Plan Progress Report and remaining Steps Each team ~1h Each team ~1h

Enjoy =)