High-Level System Design Using Foresight Giovanna Di Marzo Serugendo IT / CE.

Slides:

Advertisements

Similar presentations

Embedded System, A Brief Introduction

Advertisements

Construction process lasts until coding and testing is completed consists of design and implementation reasons for this phase –analysis model is not sufficiently.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.

ECOE 560 Design Methodologies and Tools for Software/Hardware Systems Spring 2004 Serdar Taşıran.

STATEMATE A Working Environment for the Development of Complex Reactive Systems.

PradeepKumar S K Asst. Professor Dept. of ECE, KIT, TIPTUR. PradeepKumar S K, Asst.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

Unit 2. Software Lifecycle

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

Project management Project manager must;

MotoHawk Training Model-Based Design of Embedded Systems.

Software Engineering COMP 201

Presenter : Yeh Chi-Tsai System-on-chip validation using UML and CWL Qiang Zhu 1, Ryosuke Oish 1, Takashi Hasegawa 2, Tsuneo Nakata 1 1 Fujitsu Laboratories.

1 HW/SW Partitioning Embedded Systems Design. 2 Hardware/Software Codesign “Exploration of the system design space formed by combinations of hardware.

Behavioral Design Outline –Design Specification –Behavioral Design –Behavioral Specification –Hardware Description Languages –Behavioral Simulation –Behavioral.

Software Engineering General Project Management Software Requirements

Copyright © 2006 Addison-Wesley. All rights reserved.1-1 ICS 410: Programming Languages Chapter 3 : Describing Syntax and Semantics Operational Semantics.

Define Embedded Systems Small (?) Application Specific Computer Systems.

COMP205 Comparative Programming Languages Part 1: Introduction to programming languages Lecture 3: Managing and reducing complexity, program processing.

Specification and Simulation of ALICE DAQ System Giovanna Di Marzo Serugendo.

Ritu Varma Roshanak Roshandel Manu Prasanna

1 SWE Introduction to Software Engineering Lecture 5.

1 Simulation Modeling and Analysis Verification and Validation.

L ECTURE 2 S OFTWARE P ROCESSES 1. O BJECTIVES To describe outline process models for requirements engineering, software development, testing and evolution.

Tool Integration of Ptolemy II EE290N Class Project Haiyang Zheng May

1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.

Real-Time Synchronised Petri Nets Giovanna Di Marzo Serugendo Dino Mandrioli, Didier Buchs, Nicolas Guelfi University of Geneva, Switzerland PN’02 / 24th.

20 February Detailed Design Implementation. Software Engineering Elaborated Steps Concept Requirements Architecture Design Implementation Unit test Integration.

Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.

Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.

S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.

CMSC 345 Fall 2000 Unit Testing. The testing process.

Models of Computation: FSM Model Reading: L. Lavagno, A.S. Vincentelli and E. Sentovich, “Models of computation for Embedded System Design”

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

Chapter 2: Software Process Omar Meqdadi SE 2730 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.

Software Requirements Engineering CSE 305 Lecture-2.

COP 3530 PROGRAM, FILE & DATA STRUCTURES Syllabus Syllabus Lab Information Lab Information Overrides Overrides Questions? Questions?

High Performance Embedded Computing © 2007 Elsevier Lecture 3: Design Methodologies Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based.

High Performance Embedded Computing © 2007 Elsevier Chapter 1, part 2: Embedded Computing High Performance Embedded Computing Wayne Wolf.

Project Life Cycles.

Modeling and simulation of systems Model building Slovak University of Technology Faculty of Material Science and Technology in Trnava.

Configurable, reconfigurable, and run-time reconfigurable computing.

Hardware/Software Co-design Design of Hardware/Software Systems A Class Presentation for VLSI Course by : Akbar Sharifi Based on the work presented in.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

- 1 - EE898_HW/SW Partitioning Hardware/software partitioning  Functionality to be implemented in software or in hardware? No need to consider special.

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

Voicu Groza, 2008 SITE, HARDWARE/SOFTWARE CODESIGN OF EMBEDDED SYSTEMS 1 Hardware/Software Codesign of Embedded Systems CONCURRENT ENGINEERING Voicu.

An Introduction to Software Engineering

Electrical and Computer Engineering University of Cyprus LAB 1: VHDL.

Workshop - November Toulouse Astrium Use Case.

Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.

Verification of FT System Using Simulation Petr Grillinger.

1 Copyright  2001 Pao-Ann Hsiung SW HW Module Outline l Introduction l Unified HW/SW Representations l HW/SW Partitioning Techniques l Integrated HW/SW.

© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.

Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.

Abstraction :Managing Design Complexity through High-Level C-Model Verification Mike Andrews Mentor Graphics Yuan-Shiu Chen present.

Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?

Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 5:Architectural Design l Establishing the overall structure of a software.

Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVII. Verification and Validation.

System-on-Chip Design

Chapter3:Software Processes

Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.

LHC experiments Requirements and Concepts ALICE

Controlling a large CPU farm using industrial tools

High-level System Design Using Foresight

Matlab as a Development Environment for FPGA Design

ECE-C662 Introduction to Behavioral Synthesis Knapp Text Ch

Software Development Chapter 1.

Presentation transcript:

High-Level System Design Using Foresight Giovanna Di Marzo Serugendo IT / CE

IT Seminar/November Outline w Development Process w HW/SW Co-Design w Foresight: a Modelling and Simulation tool w ALICE DAQ System

IT Seminar/November Development Process (1) w Separate Functionality from Architecture Design system functionality before thinking at hardware/software implementation details w Formal Specification and Verification Mathematical definition of system (unambiguous) Semantics of specification provides a model Behaviour of model = behaviour of system Verification: model behaves correctly (simulation, model checking)

IT Seminar/November Development Process (2) w First Phase: Functional Requirements Abstract specification: interfaces, functionality Verification: incomplete/inconsistent functional requirements, performance problems, design errors Analysis: critical parameters, maximum (minimum) performances, particular conditions w Second Phase: Architectural Concerns Detailed specifications: algorithms, hardware choices, alternative architectures Verification, analysis: check requirements and performances

IT Seminar/November HW/SW Co-design w Foresight Systems, Inc. w System Design Foresight tool Specification Execution w System Co-design Foresight co-design tool Foresight specification with hw/sw components Specification Execution w HW/SW Components HDL simulation environment Seamless CVE

IT Seminar/November Foresight (1) w Foresight Tool System Level Modeling and Simulation Tool w Specification Hierarchical Specifications Data Flow Diagrams (event-driven processes, events, control) State Transitions Mini-specs Real-time parameters

IT Seminar/November Foresight (2) w Analysis Type checking, input/output checking, syntax errors w Execution of Specification (Simulation) Real-time execution of specification Stand-alone executable specification Animation of Diagrams Real-time constraint validation Debugging functions (breakpoints, monitors windows) Simulation is NOT formal verification ! Works on Sun workstation

IT Seminar/November ALICE DAQ w Model of whole ALICE DAQ System Trigger System (L0, L1, L2) Trigger and Tracking Detectors DAQ (with sub-event building, event building, storage) Parameters (buffer sizes, etc.) w Evaluation of Performances Whole system: maximal bandwidth / real bandwidth For each detector: buffer occupancy, bandwidth usage w Alternative Algorithms Event building computing L2 trigger decision

IT Seminar/November ALICE: Overall System

IT Seminar/November ALICE: Tracking Detectors

IT Seminar/November ALICE: FSM, Mini-Spec

IT Seminar/November Results Maximal Bandwidth After 1 sec (6038 ev) Expected at L2:

IT Seminar/November Conclusion w Separate Functionality from Architecture w Foresight Systems provides integrated tools Formal Specification and Execution Seamless replacement of formal components by hardware/software components w Advantage Correct errors before implementation Think about the functional level (correct interfaces)