Difference between revisions of "TEK5530/Group work"

From its-wiki.no
Jump to: navigation, search
(Report requirements)
(Report requirements)
Line 1: Line 1:
== Report requirements ==
+
<small>[[TEK5530|back to TEK5530]]</small>
The report is the replacement for the group work in the previous years. It will count 20% in your exam grade and you will get questions related to it on the exam, so the total will be closer to 50%.  
+
= Report requirements =
 +
The student will assess an IoT system, applying a security or privacy analysis. The assessment can be done alone or in a group. The advantage of group work is that you can challenge each other, and have discussions about your analysis. The presentation of the report forms the first 8 min of the exam, and is the basis for questions of the content of the exam.  
  
 
The students are free to come with ideas on the report's topic.
 
The students are free to come with ideas on the report's topic.
  
 
Formal requirements:
 
Formal requirements:
- at least 6 pages of content (without Table of contents, cover page etc.)
+
* at least 6 pages of content (without Table of contents, cover page etc.). ''The report is "for your eyes only, and serves as the basis of your presentation''. ''Reason is that we want you to learn to structure a report, and present the report''.
- student is free to choose to write in english or norwegian
+
* student is free to choose to write in english or norwegian
- should contain (but not limited to): introduction, background, description of tasks to be done, presentation of results and conclusion.
+
* should contain (but not limited to): introduction, background, description of tasks to be done, presentation of results and conclusion. (see suggestions)
  
Possible fields:
+
==Possible field of work ==
 
* Multi-metrics approach in practice, this is the normal group work which was given previously, example: A good (A) delivery from 2016: [[Media:good_example_group_work.pdf]], you are allowed to choose a simpler example.
 
* Multi-metrics approach in practice, this is the normal group work which was given previously, example: A good (A) delivery from 2016: [[Media:good_example_group_work.pdf]], you are allowed to choose a simpler example.
 +
* Microsoft Threat analysis
 
* Security possibilities in Raspberry Pi wireless sensor networks
 
* Security possibilities in Raspberry Pi wireless sensor networks
* Zigbee: analysis of security capabilities, use case home automation
+
 
 +
Examples:
 +
* Zigbee or Connected Home over IP<ref>https://www.connectedhomeip.com</ref> : analysis of security capabilities, use case home automation
 
* A security evaluation of wifi-mains smart plugs
 
* A security evaluation of wifi-mains smart plugs
 +
 +
= Suggestions for Group Work =
 +
The main goal for your project work is to analyse an application scenario with respect to a complete system design. Thus,
 +
:1. establish the application goals with respect to coverage, capacity, or maintainability
 +
:2. have a system in mind that delivers the expected applications
 +
:3. Select your evaluation criteria, e.g. price, performance, capacity for the system evaluation
 +
:4. Divide the system into components, and perform an analysis of the components. Establish the required models for an appropriate calculation of the system performance.
 +
:5. Present the results, using the evaluation criteria defined earlier
 +
:6. Compare the outcome of the system analysis with your application goals
 +
:7. evaluate your results, e.g. by identifying components/functionalities which influence your system
 +
:8. suggest further work,  and provide reasons for those suggestions 
 +
 +
</references>
 +
= Evaluation criteria for Group Work=
 +
The results of your work should be presented during the last lecture, and a short report (max 12 pages) has to be established. The report can be separate, or can just be a description of what is on you slides.
 +
 +
Your presentation is expected to last for 25-35 min.  Your presentation will be evaluated with respect to the following criteria:
 +
 +
Application scenario/Use case
 +
* ''To what extend does the application scenario address the topics envisaged in TEK5110''
 +
 +
Identification of functionalities of the system components
 +
* ''Which are the functionalities that have to be modelled?''
 +
* ''Are the models suitable for the analysis?''
 +
 +
Perform the analysis
 +
* ''What are the results of my calculations/measurements/monitoring?''
 +
* ''To what extends satisfy the models the expected functionality?''
 +
* ''What is the sensitivity of my results?''
 +
 +
Critical review and future work
 +
* ''are the critics well reasoned?''
 +
* ''do what degree is the future work addressing shortcomings?''

Revision as of 08:59, 4 March 2021

back to TEK5530

Report requirements

The student will assess an IoT system, applying a security or privacy analysis. The assessment can be done alone or in a group. The advantage of group work is that you can challenge each other, and have discussions about your analysis. The presentation of the report forms the first 8 min of the exam, and is the basis for questions of the content of the exam.

The students are free to come with ideas on the report's topic.

Formal requirements:

  • at least 6 pages of content (without Table of contents, cover page etc.). The report is "for your eyes only, and serves as the basis of your presentation. Reason is that we want you to learn to structure a report, and present the report.
  • student is free to choose to write in english or norwegian
  • should contain (but not limited to): introduction, background, description of tasks to be done, presentation of results and conclusion. (see suggestions)

Possible field of work

  • Multi-metrics approach in practice, this is the normal group work which was given previously, example: A good (A) delivery from 2016: Media:good_example_group_work.pdf, you are allowed to choose a simpler example.
  • Microsoft Threat analysis
  • Security possibilities in Raspberry Pi wireless sensor networks

Examples:

  • Zigbee or Connected Home over IP[1] : analysis of security capabilities, use case home automation
  • A security evaluation of wifi-mains smart plugs

Suggestions for Group Work

The main goal for your project work is to analyse an application scenario with respect to a complete system design. Thus,

1. establish the application goals with respect to coverage, capacity, or maintainability
2. have a system in mind that delivers the expected applications
3. Select your evaluation criteria, e.g. price, performance, capacity for the system evaluation
4. Divide the system into components, and perform an analysis of the components. Establish the required models for an appropriate calculation of the system performance.
5. Present the results, using the evaluation criteria defined earlier
6. Compare the outcome of the system analysis with your application goals
7. evaluate your results, e.g. by identifying components/functionalities which influence your system
8. suggest further work, and provide reasons for those suggestions

</references>

Evaluation criteria for Group Work

The results of your work should be presented during the last lecture, and a short report (max 12 pages) has to be established. The report can be separate, or can just be a description of what is on you slides.

Your presentation is expected to last for 25-35 min. Your presentation will be evaluated with respect to the following criteria:

Application scenario/Use case

  • To what extend does the application scenario address the topics envisaged in TEK5110

Identification of functionalities of the system components

  • Which are the functionalities that have to be modelled?
  • Are the models suitable for the analysis?

Perform the analysis

  • What are the results of my calculations/measurements/monitoring?
  • To what extends satisfy the models the expected functionality?
  • What is the sensitivity of my results?

Critical review and future work

  • are the critics well reasoned?
  • do what degree is the future work addressing shortcomings?


Cite error: <ref> tags exist, but no <references/> tag was found