1 SAFEPROBE Plenary Meeting 2006-12-06, Torino T1.2.3 Requirements Andreas Ekfjorden Volvo (Sweden) SAFEPROBESAFEPROBE.

Slides:



Advertisements
Similar presentations
IT KEY SKILLS LEVEL 1 Evidence required for: A poster or Word document.
Advertisements

ITSF STORE BUSINESS SOLUTION PRESENTATION. STORE MODULE INCLUDES: Material Management Purchasing Components Handling Shipments Receiving of parts Store.
Requirements Specification and Management
Program Management Portal: Overview for the Client
COMP4710 Senior Design Process Documentation and Deliverables.
Introduction to Integrated Library Systems
TEK: write legibly and use appropriate capitalization and punctuation conventions ELPS: 5B- write using newly acquired basic vocabulary and content-based.
Human Computer Interaction G52HCI
1 CP2236 Information Systems Design Business & Technical System Options Required System Logical Data Flow Modelling Larger versions of slides 17,20,23,24.
ID-2050 Lecture #7. Assignment #9 1.Background Storylines 2.More Literature Review/Ann. Bibliography 3.Methodology Sections - Methods 4.Methodology Specifics.
Hazard and Incident Warning « Majority of events occurring on the road represent a danger for road users » By transmitting road events and road status.
1 Safespot applications for Infrastructure-Based Co-Operative Road-Safety World congress on ITS, Beijin /15SAFESPOT Fabien Bonnefoi, Francesco Bellotti,
Design Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Module Code CT1H01NI: Study Skills For Communication Technology Lecture for Week Autumn.
Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads”
1 Shawlands Academy Higher Computing Software Development Unit.
SAFESPOT Project SP1 Meeting 3 rd – 4 th April, Berlin 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads” Debra.
XML The Overview. Three Key Questions What is XML? What Problems does it solve? Where and how is it used?
K-12 Web Content Development Process
An Overview of MPEG-21 Cory McKay. Introduction Built on top of MPEG-4 and MPEG-7 standards Much more than just an audiovisual standard Meant to be a.
RoboTeam 9/1/2011 Preformed by:Costia Parfeniev, Boris Pinzur Supervised by: Kobi Kohai.
SAFESPOT Project SP1/SP4 Harmonization Meeting 9 th June, Lyon 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads”
© Janice Regan, CMPT 300, May CMPT 300 Introduction to Operating Systems Principles of I/0 hardware.
SP1 – Meeting March 1 st - 2nd 2007 – Pontedera (Pisa) Electronic Systems 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on.
Ms. Edelman Monday AIM: How do you use the thumbnail sketch to develop your concept? DO NOW: Develop 3 concept thumbnails in your sketchbooks.
SAFESPOT – Local Dynamic Maps for Cooperative Systems April, 12th 2007, CRF – SP2 Infrasens meeting 1 Local dynamic maps in cooperative systems IP - “Smart.
Adding the Executive Summary and …. Executive Summary (1-2 pages) briefly presents these items: 1.sustainability problem 2.rationale for your project.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
ISO/IEC CD and WD : Core Model and Model Mapping ISO/IEC JTC1/SC32/WG September 2005, Toronto SC32/WG2 Japan (Kanrikogaku Ltd) Masaharu.
Updating JUPITER framework using XML interface Kobe University Susumu Kishimoto.
Incident Object Description and Exchange Format
1 SAFESPOT Project SP1 SAFEPROBE , Torino Volvo Integration progress Andreas Ekfjorden Volvo (Sweden) SAFEPROBESAFEPROBE.
SAFESPOT Project Kick off Meeting February 16 th and 17 th 2006 Rome 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart.
SP2 Plenary Meeting – Data Fusion March 2008, Munich 1 Infrastructure Side Data Fusion Tobias Schendzielorz (TUM) Paul Mathias (Siemens) SAFESPOTSAFESPOT.
SAFESPOT Project Kick off Meeting February 16 th and 17 th 2006 Rome 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart.
SP2 Progress Meeting – Data Fusion September 2007, Paris 1 Infrastructure Side Data Fusion Tobias Schendzielorz Technische Universität München.
Request for Proposal (RFP)
Slide 1 CS 310 Ch 6: Software Requirements Requirements engineering: establishing the services that the customer requires from a system and the constraints.
The Software Development Process
The Refereeing Module of the SPMS FEL2005: August Heinz-Dieter Nuhn – Scientific Editor Beck Reitmeyer – Conference Editor Referee = Reviewer = Expert.
SF- SP1 – Plenary Meeting June 14 th and 15 th Santorini 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads”
SYSE 802 John D. McGregor Module 1 Session 2 Requirements Modeling in SysML.
Copyright © Curt Hill Tortoise SVN A Subversion Client.
IEEE SISWG P Sub-Committee Status Summary Walt Hubis 4/15/2009.
Volvo Technology Corporation
SAFESPOT Project SP2 WP3 1 Title S. Marco, S. Manfredi (CSST) SP1 Meeting PONTEDERA 1st March 2007 INFRASENS Functional Architecture.
Prof. Hany H. Ammar, CSEE, WVU, and
SP1 – Meeting April 23 rd Schieberdingen Electronic Systems Page 1 of 13 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles.
Project management and communication structure Nataša Urbančíková Faculty of Economics Technical University of Košice.
GOOGLE SITES HOW TO USE GOOGLE SITES TO CREATE A WEBSITE FOR CORNERS, STUDENT GROUPS, YOUTH CLUBS, YALI STEPHEN PERRY, IRO, GHANA OCTOBER 2014.
SF-SP1 Plenary Meeting March 01-02/03/2007 Pontedera - PIAGGIO 1 Integrated Project Co-operative Systems for Road Safety “Smart Vehicles on Smart Roads”
Darmstadt, October 9th 2007ECSS/CCSDS Coordination meeting 1 ECSS/CCSDS cooperation.
Auto-Park for Social Robots By Team Daedalus. Requirements for FVE Functional Receive commands from user via smartphone app Share data with other cars.
T Project Review ITSUPS Implementation
XML The Overview. Three Key Questions What is XML? What Problems does it solve? Where and how is it used?
T Project Review RoadMappers I2 Iteration
GSC Global Standards Collaboration GSC#10 28 August – 2 September 2005 Sophia Antipolis, France 1 eCALL In Vehicle System to provide information at car.
05 October 2010 HMA-FO Task 2: Feasibility Analysis Service HMA Follow On Activities Task 2: Feasibility Analysis Service (Sensor Planning Service) Monthly.
T Iteration Demo LicenseChecker I2 Iteration
T Project Review X-tremeIT PP Iteration
AECS Accident Emergency Call System
HMA Follow On Activities
SP2 Integration Workshop Short Introduction to the LDM
Software Documentation
WP1 INERTIA Framework Requirements, Specifications and Architecture
An Overview of MPEG-21 Cory McKay.
Informal document GRRF-86-36
Securing and Sharing a Presentation
Progress report of GRSG informal group
Presentation transcript:

1 SAFEPROBE Plenary Meeting , Torino T1.2.3 Requirements Andreas Ekfjorden Volvo (Sweden) SAFEPROBESAFEPROBE

2 SAFEPROBE Plenary Meeting , Torino Current Status The actual requirements list has been checked (and refined) in several iterations. Some analysis has been done –covers all parts of the D122 UseCase diagram –Some Doubles have been removed but not all –Almost all requirements are directed to SP1, hand over some to SP3 seem to be needed? Discussion needed –Requirements from SP4 may need to be transferred to SP3, this has to be handled in Specifications process. The word document is in a first draft format but needs more descriptions. No formal Crosschecking has been done!

3 SAFEPROBE Plenary Meeting , Torino The SAFEPROBE Platform in the World SAFEPROBE Platform OEM HMI RSU

4 SAFEPROBE Plenary Meeting , Torino Common language for requirements Each requirement shall have a unique English name (it is not the case now) Slippery Road –Ice, gravel, snow, oil on the road etc GNSS –Satellite navigation systems: GPS, Galileo etc Change “Beacon” to “Transponder” in a vehicle?

5 SAFEPROBE Plenary Meeting , Torino Specific Requirements UTC as time standard for DF? Volvo have added a “minimum platform” requirement –“It shall be possible to install a limited platform on any vehicle only using a minimal adaptation.” –Rationale: “A vehicle shall not need to carry a full sensor setup to function as a SF vehicle. The minimum setup is the Platform, Short range communication and GNSS capabilities. A minimal set of vehicle data may be needed (TBD - Speed, Yawrate)” Slippery Road and Road Departure –Several proposals exist, can we use the term Slippery road and rewrite? (next slide)

6 SAFEPROBE Plenary Meeting , Torino Slippery Road Req. from UC SP1_UC_01_26 Possibility of road departure detected by ego vehicle The system shall detect areas of reduced friction (due to slippery road conditions) and put the information in the LDM SP1_UC_01_26 Possibility of road departure detected by infrastructure The system shall be able to receive information on the road condition from the infrastructure and put the information on the LDM SP1_UC_01_27 Possibility of road departure communicated If information on low friction on the road is in the LDM, this information shall be sent to other vehicles and the infrastucture SP1_UC_04_026 Low friction detected by ego vehicle The system shall detect areas of reduced friction and put the information in the LDM SP1_UC_04_027 Low friction detected by infrastructure The system shall be able to receive information on the road condition from the infrastructure and put the information on the LDM SP1_UC_04_028 Low friction communicated If information on low friction on the road is in the LDM, this information shall be sent to other vehicles and the infrastructure

7 SAFEPROBE Plenary Meeting , Torino Unclear requirement: SP1_UC_51_27 Road geometry calculation with sensors The system shall help road geometry calculation with information from sensors

8 SAFEPROBE Plenary Meeting , Torino Architecture dependent SP1_UC_06_007 Digital Map The system must have a (static) digital map and the should be cooperable with the local dynamic map. SP1_HW_51_35 Screen capabilities (HMI) The screen shall have graphic capabilities, with TBDxTBD pixels and TBD colors at least. SP1_SW_05_10 Data Structure and Format Documentation The structure and format of all in- vehicle platform data exchanged between major (tbd) modules shall be documented using XML This is an SP7 issue? This should be kept in mind for the architecture discussion?

9 SAFEPROBE Plenary Meeting , Torino To Do Next Finish the D1.2.3 –Add an introduction on the SAFEPROBE platform in the SAFESPOT system –Fuller description on the introduction to the requirements lists – The authors –“Cleaning up” unambiguous names and to extensive explanations – Volvo and requirements originators Crosschecking with SP2,3,4,5,7 –Should this a part of the specifications process and will not be included in the deliverable. Standard msg development – separate task

10 SAFEPROBE Plenary Meeting , Torino Finishing of D :st Draft (Word) for comments –out Friday afternoon –Comments and additions by –Second draft out –Comment by 19/12 –Peer review delivery 20/12 Final draft out for comments (Excel list) Monday afternoon

11 SAFEPROBE Plenary Meeting , Torino SP4 Requirements The list from SP4 with SP1 Requirements is 77 items long! Critical items SP4 requirements