Ghiro Andrea – Burzio Gianfranco 20 Novembre, 2010 WP1 - Requirements DECISIVE.

Slides:



Advertisements
Similar presentations
PERFORMER KO MEETING NICE - 12 th & 13 th September 2013 WP1short presentation.
Advertisements

PERFORMER WP2 INTRODUCTION 13th of September 2013 CSTB Sophia Antipolis, France.
C2-SENSE WP2 Bojan Božić, Gerald Schimak, Refiz Duro C2-SENSE WP2 Meeting Paris
S Y S T E M S E N G I N E E R I N G.
Ensure Vendor/Engineer of Choice Product Quality
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
Lecture # 2 : Process Models
MethodAssess System Assessment. Methoda Computers Ltd 2 List of Subjects 1. Introduction 2. Actions and deliverables 3. Lessons and decisions.
Project Management November 2, Introduction Eric Lemmons Customer Project/Program Manager III Gary Obernuefemann Business Consulting IV.
S R S S ystem R equirements S pecification Specifying the Specifications.
R&R Consulting Approach
Development plan and quality plan for your Project
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
What is Business Analysis Planning & Monitoring?
S/W Project Management
© Siemens AG, CT SE 1, Dr. A. Ulrich C O R P O R A T E T E C H N O L O G Y Research at Siemens CT SE Software & Engineering Development Techniques.
1 Framework Programme 7 Guide for Applicants
Software Project Management
MyOcean2 First Annual Meeting – April 2013 WP2.3 Service Engineering MyOcean2 First Annual Meeting – Cork /16-17 April 2013.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software System Engineering: A tutorial
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
HL-LHC Quality management
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Benchmarking in WP 2.1. Sep 28th, 2004 © R. García-Castro, A. Gómez-Pérez Raúl García-Castro Asunción Gómez-Pérez September 28th, 2004 Benchmarking.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
Research Methods1 Introduction Introduction to Research Course Content Assessment.
EPOCA – 11. June EPOCAConsortiumOrganisation.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Scalable Semantic Product Data Stream Management for Collaboration and Decision Making in Engineering Project WP17: Demonstration and evaluation.
MODERN 1 st Year Review ENIAC MODERN Ref. Technical Annex MODERN_PartB Rev2 v2.4 WP1: Giuliana GangemiWP2: André Juge WP3: Wilmar HeuvelmanWP4:
1 Thank you for visiting our site and welcome to the “Introduction to ISO 22000” Presentation that you requested. For more information.
Development of Methodologies for Independent Verification and Validation of Neural Networks NAG OSMA-F001-UNCLASS Methods and Procedures.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Computerized Emotion Voice Detection and Project Management HCI 575 Enanga Fale.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Requirements Analysis
OUNL’s assessment model January the 10th 2006 Colin Tattersall & Henry Hermans.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Overview of Socio-cognitive Engineering General requirements Theory of Use Design Concept Contextual Studies Task model Design space System specification.
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.
1 WP7 Presentation WP7 -- Project Evaluation Computer Engineering and Networks Laboratory, ETH Zurich Prof. Dr. Bernhard Plattner.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Virtual Collaborative Social Living Community for Elderly Kick Off Event WP2 Overview Instituto Pedro Nunes Co-Living 12/3/ Paulo Freitas - Instituto.
Objective ICT : Internet of Services, Software & Virtualisation FLOSSEvo some preliminary ideas.
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
ARTEMIS Industry Association Title Presentation - 1 MORTIMUS+MACE+DECISIVE (ASP-5) Contact: Mikael Sjödin
Decisive Themes, July, JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011.
What’s New in SPEED APPS 2.3 ? Business Excellence Application Services.
Decisive – WP7 Decisive meeting at Stockholm, May 27th Susanna Teppola VTT Technical Research Centre of Finland.
WP2 Planning per Objectives of WP2 ●Definition of multi-faceted component-model with support for ●Expressiveness for non-functional attributes.
SQA project process standards IEEE software engineering standards
SQA project process standards IEEE software engineering standards
Funded by the Erasmus+ Programme EPP JO-EPPKA2-CBHE-JP Lina Tsakalou
Pre-Execution Process Review Presentation
Request for Proposal (RFP)
Informatics 121 Software Design I
Informatics 121 Software Design I
Informatics 121 Software Design I
Verification & Test Support for Safety Standards
PSS verification and validation
Informatics 121 Software Design I
Presentation transcript:

Ghiro Andrea – Burzio Gianfranco 20 Novembre, 2010 WP1 - Requirements DECISIVE

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF AGENDA Topic & goals Tasks decomposition Relationships to other WPs Timing of tasks Proposed deliverables & delivery time Partners in the WP1 & tasks Proposed task leaders

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF WP1 covers the work on the specification of the business requirements and needs that the project is looking to answer. Commercial existing tools and European Patents will be analyzed in order to evaluate the needs about: learning from previous versions of the product hand-over of models to new engineering teams supporting product-management in steering the product requirements. Precise and testable requirements will be identified in order to cover these main areas: DECISIVE application monitoring, interfaces between DECISIVE models, DECISIVE human-centric tools interfaces, and decision-support to product management during the decision phase. An appropriated test methodology will be defined in order to verify the requirements fulfilling during the verification and validation phases. Topic & goals

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF WP1 will accomplish the following activities: Evaluate the current state-of-the-art approaches related to evolutionary development in the model- based engineering of embedded systems. Define requirements for tools and methodologies in order to provide: non-intrusive analysis and monitoring techniques to systematically collect information during the evolutions decision support for the synthesis of system architectures model management and visualization, to automate the management of models and improve comprehension during the system evolution Identify safety and certification requirements Define test methodologies to apply during validation phase Preliminary definition of candidate validation cases and scenarios Topic & goals

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF The tasks to be accomplished in Work Package 1 are summarized in the table below. Tasks decomposition TaskDescription T1.1State of the art. Collecting relevant and significant industry control use cases T1.2Identification of the monitoring requirements T1.3Identification of the interfaces requirements T1.4Identification of the human interface requirements T1.5Identification of the decision-support requirements T1.6Identification of safety and certification requirements T1.7Preliminary validation cases and test methodology definition

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Relationships to other WPs WP1 is the starting point for all the other WPs: Requirements defined in this WP are input for WP2, WP3, WP4, WP5. Preliminary validation cases and scenarios defined in this WP will be used in WP6 for the industrial validation phase Main risks related to this WP are: not well defined requirements not well defined test methodologies not correct or not enough candidate validation case definition

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Timing of tasks

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Proposed deliverables & delivery time Two Deliverable are planned for WP1: D1.1 – Business requirements and needs D1.2 – Preliminary validation case

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Partners in the WP1 & tasks TaskPartners T1.1Atego, IKER, NXP-A, NXP-D, UEF, UoO T1.2CEA, FHG-HHI, ISYS, UEF, UoO T1.3CEA, CISC, UoO T1.4BHL, CAU, CRF, LDZ, RTU, UES T1.5CRF, ISYS, LDZ, NXP-D, RTU T1.6Atego, AVL, IKER T1.7Atego, CRF, IKER, MU, NXP-A, NXP-D, PHILIPS, UES WPPartners WP1Atego, AVL, BHL, CAU, CEA, CISC, CRF, FHG- HHI, IKER, ISYS, LDZ, MU, NXP-A, NXP-D, PHILIPS, RTU, UES, UEF, UoO

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Partners in the WP1 & tasks PartnerT1.1T1.2T1.3T1.4T1.5T1.6T1.7Total PHILIPS12 AVL16 CISC44 NXP-A235 UEF6612 UoO77620 Atego44412 CEA12216 BHL44 CAU33 FHG66 NXP ‐ D 2125 CRF LDZ112 RTU235 IKER55414 ISYS325 MU55 UES

Inserire Titolo Evento This document contains information which are proprietary of CRF. Neither this document nor the information contained herein shall be used, duplicated nor communicated by any means to any third party, in whole or in part, except with the prior written consent of CRF Proposed WP1 task leaders TaskPartner T1.1IKER T1.2FHG-HHI T1.3UoO T1.4BHL T1.5RTU T1.6AVL T1.7PHILIPS