WP1 Requirements

From its-wiki.no

Jump to: navigation, search

WP1 - Requirements Management

WP Title: Requirements Management and Assessment of Project Objectives Management
Project: SCOTT
Lead partner: NXP AT
Leader: Joachim Hillebrand
Contributors: NXP AT, VIF, ACCIONA, ISEP, NOKIA, GUT, SMARTIO, TELENOR ASA, UiO

Objective

The objective of WP1 is to provide clear structure and guidance, to effectively manage the requirements definition and harmonization process in SCOTT. WP1 will also serve as alignment platform to lead and coordinate SP1, and to ensure an efficient and harmonized approach within WP2 – WP5, the content driven work packages providing harmonized requirements per Technology Line. Besides requirements coming from Use Cases and project level objectives, emphasis will also be put on requirements resulting from WP28, where a framework for building trusted systems will be developed and linked to SCOTT use cases. The principles of the requirements harmonization process are shown in the following figure (for the initial iteration): The iterative approach used in SCOTT means, that technological building blocks required by use cases can be (depending on their nature and requirements) developed within one up to max. three iteration loops. This optional flexibility will enable early availability of demonstrators, in-time feedback loops and in consequence an effective and agile development approach. A high-level description of the iterative approach used in SCOTT is shown in the following figure: Additionally, this work package will also manage the assessment of project objectives including related progress reporting, under special consideration of the “iterative” approach used in SCOTT.


Partners in WP01

Tasks in WP01

UiO

  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).
  • Contribution to the assessment of project objectives (Task 4).

SmartIO 


  • Contribution to the definition of guidelines and best practices (Task 1).

  • Contribution to the assessment of project objectives (Task 4).


Telenor(also WP3 lead; link to TL Roaming & Cloud Integration)

  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).

  • Contribution to the requirements tracking (Task 3).

Deliverables in SCOTT:WP01

Working area

Phone conf 21Sep2017

The minutes can be found under: https://projects.avl.com/16/0094/WP01/_layouts/15/WopiFrame.aspx?sourcedoc=/16/0094/WP01/Documents/02_Meetings%20and%20WebEx/Meetings%20and%20Calls%202017/SCOTT%20SP1%20Webex_20170921.pptx&action=default

Guideline for the requirements alignment phase (10Aug2017)

This is in first instance intended for WP2 – WP5 leaders for running the alignment process and providing related deliverables D2.1 – D5.1 in time. A pro-active dialog with involved partners and in-time planning of alignment meetings seems vital to keep the schedule. This information is complementary to D1.1.

In a second instance it is for SP2 (WP6) and SP3 (WP22), in order to stay well aligned and to avoid duplication. Please communicate as appropriate in your SPs.

Template for D2.1 – D5.1

We will provide a template suggestion by 18.8., incl. a proposal for sub-structure and content, to support you and to ensure D2.1 – D5.1 have the same look and feel.

Please also consider the required review work and organize in time!

Dashboard to track progress of requirements entry & alignment process

Last but not least we will provide a weekly update about the progress of the requirements entry process, later on about the alignment process to this selected group.

The focus is to identify gaps, mainly from a BB-perspective, but also from a UC perspective, to be able to trigger corrective actions ASAP.

  • The first report is available (status per 9.8.), we will further fine-tune and optimize it as we go. We hope it is of help for your work.
  • To my knowledge there has been some discussion about BBs 23E, 23M, 26C and 26C. Is this closed now? What is the outcome?

The guidance document (“SCOTT_Guidance_WP2-5_Alignment.ppt”) and the first progress report (“SCOTT_Requirements Entry_ Status 090817.ppt”) can be found under: https://projects.avl.com/16/0094/WP01/default.aspx?RootFolder=%2F16%2F0094%2FWP01%2FDocuments%2F04%5FDocuments&FolderCTID=0x012000C91DC1FD094FFC4287129CE98EC1C64B&View=%7BB4A03CDC%2D095F%2D4974%2D83E0%2D2DE09D11279F%7D

The template for D2.1-D5.1 is still work in progress, and will be made available in the same folder by end of next week.


Facts about "WP01"RDF feed
Lead partnerNXP AT +
LeaderJoachim Hillebrand +
ObjectiveThe objective of WP1 is to provide clear sThe objective of WP1 is to provide clear structure and guidance, to effectively manage the requirements definition and harmonization process in SCOTT. WP1 will also serve as alignment platform to lead and coordinate SP1, and to ensure an efficient and harmonized approach within WP2 – WP5, the content driven work packages providing harmonized requirements per Technology Line. Besides requirements coming from Use Cases and project level objectives, emphasis will also be put on requirements resulting from WP28, where a framework for building trusted systems will be developed and linked to SCOTT use cases. The principles of the requirements harmonization process are shown in the following figure (for the initial iteration): The iterative approach used in SCOTT means, that technological building blocks required by use cases can be (depending on their nature and requirements) developed within one up to max. three iteration loops. This optional flexibility will enable early availability of demonstrators, in-time feedback loops and in consequence an effective and agile development approach. A high-level description of the iterative approach used in SCOTT is shown in the following figure: Additionally, this work package will also manage the assessment of project objectives including related progress reporting, under special consideration of the “iterative” approach used in SCOTT.of the “iterative” approach used in SCOTT. +
Page Link[[SCOTT:WP01|]] +
Page TitleWP1 - Requirements Management +
PartnerNXP AT +, VIF +, ACCIONA +, ISEP +, NOKIA +, GUT +, SMARTIO +, TELENOR ASA + and UiO +
ProjectSCOTT +
SmartIO contribution
  • Contribution to the definition of guidelines and best practices (Task 1).

  • Contribution to the assessment of project objectives (Task 4). +
Telenor contribution(also WP3 lead; link to TL Roaming & Cloud(also WP3 lead; link to TL Roaming & Cloud Integration)
  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).

  • Contribution to the requirements tracking (Task 3).ion to the requirements tracking (Task 3). +
  • TitleRequirements Management and Assessment of Project Objectives Management +
    UiO contribution
  • Contribution to the definition of guidelines and best practices (Task 1).
  • Contribution to the overall harmonization of requirements (Task 2).
  • Contribution to the assessment of project objectives (Task 4). +