Difference between revisions of "SCOTT:SCOTT Technical Board Meeting Paris2017"
From its-wiki.no
Josef.Noll (Talk | contribs) (→Topics) |
Josef.Noll (Talk | contribs) (→Topics) |
||
Line 13: | Line 13: | ||
= Topics = | = Topics = | ||
Overview over the project | Overview over the project | ||
+ | * what industry needs is an overview presentation: "From an Internet Company to an IoT Company: What are the security challenges and how you can handle them" | ||
* overall vision/visibility of the project (from 16 independent sub-projects to coordinated impact on the European scale) | * overall vision/visibility of the project (from 16 independent sub-projects to coordinated impact on the European scale) | ||
− | + | * "main vision for use cases" | |
* Implementation of building blocks in WPs - who takes responsibility? E.g. WP8 has 9 building blocks, and not even the lead partner is part of WP8 | * Implementation of building blocks in WPs - who takes responsibility? E.g. WP8 has 9 building blocks, and not even the lead partner is part of WP8 |
Revision as of 12:01, 13 September 2017
SCOTT Technical Board Meeting Paris2017 | ||||||
---|---|---|---|---|---|---|
|
SCOTT:SCOTT Technical Board Meeting Paris2017
Title | SCOTT:SCOTT Technical Board Meeting Paris2017 |
---|---|
Place | Paris, at CDG airport. see e-mail from 28 August. |
Date, Time | 2017/09/27, 1000-1700 |
Contact Person | Joachim Hillebrand |
Participants | Josef.Noll, Joachim Hillebrand, Werner Rom, Lukasz Szczygielski (GUT), Christian Johansen |
related to Project | SCOTT |
Keywords |
this page was created by Special:FormEdit/Meeting, and can be edited by Special:FormEdit/Meeting/SCOTT:SCOTT Technical Board Meeting Paris2017 |
Category:Meeting |
Venue
Hotel Ibis Paris CDG Airport Roissypôle BP 11122, 95701 (exit Terminal 3)
Topics
Overview over the project
- what industry needs is an overview presentation: "From an Internet Company to an IoT Company: What are the security challenges and how you can handle them"
- overall vision/visibility of the project (from 16 independent sub-projects to coordinated impact on the European scale)
- "main vision for use cases"
- Implementation of building blocks in WPs - who takes responsibility? E.g. WP8 has 9 building blocks, and not even the lead partner is part of WP8
- We should have a future oriented description, and perhaps architecture, showing the need of the envisaged building blocks. If not, kick them out
- 600 requirements, for what? - what is the message we are giving out?
- should be converted towards a hierarchical structure, e.g. high-level, detailed requirements
- then low-level requirements for implementation
- Building block requirements vs use case requirements (not consistently defined)
Solution(? - agreement needed)
- Use case own creates a drawing, identifying
- the core demonstrational outcome, with included Building Blocks
- the Building Blocks which are seen as additional value, but not implemented "yet"
- Building Blocks which are obsolete for the specific use case
Presentations
- Presentation: Privacy Labelling, Security Metrics, Roadmap towards a more secure and privacy-aware society (30 min)