ARTEMIS-2010-1 pSafeCer Grant Agreement number 269265 ARTEMIS-2011-1 nSafeCer Grant Agreement number 295373 Safety Certification of Software-intensive.

Slides:

Advertisements

Similar presentations

COBECOS SIXTH FRAMEWORK PROGRAMME PRIORITY 8.1 WP 4 – DATA HARMONISATION London, 5 – 7 September.

Advertisements

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.

Portable and Predictable Performance on Heterogeneous Embedded Manycores (ARTEMIS ) ARTEMIS Project Review October 2014 WP1 “Management and IPR”

© NCSR, Paris, December 5-6, 2002 WP1: Plan for the remainder (1) Ontology Ontology  Enrich the lexicons for the 1 st domain based on partners remarks.

April 19, 20003GPP2 report 3GPP2 Steering Committee TSG-A report DRAFT Seoul, Korea April 19, 2000.

ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Safety Certification of Software-intensive.

Rational Unified Process

27-29 September 2002CrossGrid Workshop LINZ1 USE CASES (Task 3.5 Test and Integration) Santiago González de la Hoz CrossGrid Workshop at Linz,

ESSnet on SDMX phase II Dario Camol

ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Safety Certification of Software-intensive.

LCG Milestones for Deployment, Fabric, & Grid Technology Ian Bird LCG Deployment Area Manager PEB 3-Dec-2002.

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

THE PROTOTYPING MODEL The prototyping model begins with requirements gathering. Developer and customer meet and define the overall objectives for the software.

Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.

S L H C – P P Management Tools Kick-off Meeting April 8 th, 2008 Mar CAPEANS CERN This project has received funding from the European.

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.

Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.

Software Engineering Management Lecture 1 The Software Process.

GDS Gaming Device Standards Event, Data, Location.

ECTL A Support to the Automated Safety Data Monitoring Indicator project.

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under.

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Sept 25-27, 2013 Riga Safety Certification of Software-intensive.

NOV-3733-SL-9347 Carbones KOM - May 10-11, 2010 – Toulouse, France 1 KICK-OFF MEETING May 10-11, 2010.

1/23 Prescriptive Process Models. 2/23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive.

Learning by Experience A Project in the Design Phase 2:15 – 3:00 Performed by: A Cast of Many.

Objectives: Develop a solution to either enhance or replace the FasTrak tool Scope/Why is this important?: Increase the transparency for issues that are.

The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.

NSHIELD Project Meeting Brussels - 15 Feb 2012 Luigi Trono.

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”

ARTEMIS JU Grant Agreement number ARTEMIS JU Grant Agreement number Safety Certification of Software-intensive Systems with.

ARTEMIS JU Grant Agreement number WP4 Instantiation WP4 Status 25 September, 2013.

Worldwide Protein Data Bank wwPDB Common D&A Project Full Project Team Meeting Rutgers March 16-19, 2010.

Requirements Management Overview NIGMS Software Development.

Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.

Certification and Adoption Workgroup HIT Policy Committee April 28, 2014 Discussion on Incremental Rulemakings.

T Iteration Demo Tempus I1 Iteration

Systems Architecture WG: Report of the Spring 2005 Meeting April 14, 2005 Takahiro Yamada, JAXA/ISAS.

Net-Centric Software and Systems I/UCRC A Framework for QoS and Power Management for Mobile Devices in Service Clouds Project Lead: I-Ling Yen, Farokh.

PDS4 Project Report PDS MC F2F UCLA Dan Crichton November 28,

Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.

Decisive Themes, July, JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011.

Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.

PDS 2010 System Design Report MC Face-to-Face Washington, DC March 25-26, 2010.

Testing and Release Procedures/Tools Cristina Aiftimiei (INFN-CNAF) Mario David (LIP)

© 2002 IBM Corporation Confidential | Date | Other Information, if necessary Java Workflow Toolbox (JWT) Release review: Workflow Editor v0.4 & Transformations.

Brussels, January 16th, Overview and status of the project.

Nicolas Granier / June 7th

Software Engineering Management

Software Verification and Validation

Session II: System authority for ERTMS 4RP Trackside approval

Software Requirements

UNIFIED PROCESS.

Digital Government Initiative Initiation Department of Information Technology Estevan Lujan, Acting Cabinet Secretary Susan Pentecost, Managing Director,

Department of Information Technology VINE3 UPGRADE Project Initiation Request David Dikitolia, Sr. Project Manager Bernadette Garcia, IT Business Analyst/Public.

CMAST Update March 25, 2014.

ESSnet on SDMX phase II Laura Vignola

Software Development Process

P25 Digital Statewide Public Safety Radio System Initiation Department of Information Technology Estevan Lujan, Acting Cabinet Secretary Michael Rohrbacher,

The Unified/Rational Unified Process (UP/RUP) Defined

Project Phases ‘98 ‘00 ‘02 ‘04 ‘06 Preparatory Phase

X-DIS/XBRL Phase 2 Kick-Off

SCOTT NO meeting Measurement

Point 6. Eurostat plans for Time Use Survey data processing and dissemination Working Group on Time Use Surveys 10 April 2013.

The ARTC Safety Management System Presentation 1/3

Aurora Hoxha & Drini Imami

Presentation transcript:

ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Safety Certification of Software-intensive Systems with Reusable Components Akhela nSC WP200 – Deliverables and CAs Massimiliano Turco (Akhela - ) SafeCer P7 September 25-27, 2013 Riga

27 th of September 2013, Riga Page 2 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number WP200 deliverables Del. no Deliverable name Lead beneficiary Delivery dateComments nSC D211.1/ nSC D212.1 Prototype analysis document Prototype enhancement specification document FBK M26 (May 2013)Released in April 2013 (M25) nSC D221.1/ nSC D222.1 Extended requirement document for tool framework Architecture document, design document for tool framework AKHELA M30 (September 2013) Preliminary draft version released at the end of April Deliverable released for internal review the 20 th of September 2013, as scheduled. nSC D223.1 Enhanced software prototypeAKHELA M42 (September 2014) Not yet started (M31) nSC D224.1 Test cases and test results for tool framework AKHELA M48 (march 2015) Not yet started (M43) nSCD231.1 SafeCer platform instantiation report ADACORE M42 (September 2014) On-going (started M25) nSC D232.1 Demonstrator feedback on the SafeCer framework ADACORE M42 (September 2014) Not yet started (starts M33) nSC D233.1 SafeCer platform validationADACORE M48 (march 2015) Not yet started (starts M43)

27 th of September 2013, Riga Page 3 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Work PackageAction\RequestResultDeadline WP210 (FBK)Merge the deliverable “nSC D211.1 Prototype analysis document” to the following one, “nSC D212.1 Prototype enhancement specification Document” Single deliverable document M25 (April 2013) WP220 (Akhela) Merge the deliverable “nSC D Requirements Document forTool Framework” to the following one, “D Architecture Document,Design Document for Tool Framework” Single delivarable named: “nSC D221.1_ D222.1 – Requirements, Architecture and Design Document for Tool Framework" M30 (September 2013) Same date scheduled for “D Architecture Document, Design Document for Tool Framework”. WP200 Corrective Actions

27 th of September 2013, Riga Page 4 ARTEMIS pSafeCer Grant Agreement number ARTEMIS nSafeCer Grant Agreement number Forthcoming activities and potential risks Software phase following the design of new addition and enhancement of the platform, as described above. Consequently, the D221.1_D222.1 should be labeled as a “living document” to be updated and aligned accordingly to the software developments. Release of a intermediate software prototype able to perform a possible simplified certification process (GPM/CTF/CAR), possibly covering one of the planned UC (or part of it). Risk: put in place a fully working integration with CTF/CAR & GPM.