Development of Integrated Hard- and Software Systems: Tasks and Processes
|
|
- Reginald Watts
- 6 years ago
- Views:
Transcription
1 TECHNISCHE UNIVERSITÄT ILMENAU Development of Integrated Hard- and Software Systems: Tasks and Processes Integrated Communication Systems
2 General Development Tasks Analysis of the requirements of the environment to the system Modeling the system to be designed and experimenting with algorithms involved Refining (or partitioning) the function to be implemented into smaller, interacting pieces HW/SW partitioning allocating elements in the refined model to either HW units or SW running on custom hardware or general microprocessors Scheduling the times at which the functions are executed (this is important when several modules in the partition share a single hardware unit) 2
3 System Development Process The Theory Analysis Waterfall model Design Implementation Development is not a pure top-down process use of subcomponents from the shelf => bottom-up lack of accurate estimation in early phases => feedback lack of confidence in feasibility => feasibility studies, prototyping Integration Maintenance => in practice the development process is a mixture of bottom-up and top-down design 3
4 Analysis Phase and Subphases Problem analysis Analysis Feasibility study Requirements analysis The goals of the analysis phase are to identify the purpose, merit and risks of developing the product, and to identify the purpose of the product and to understand its exact requirements 4
5 Problem Analysis Preliminary study to analyse important needs of the environment to be supported by the system discuss principal solution strategies Problem analysis Analysis Feasibility study => Problem definition (German: Lastenheft) project goals (business objectives) product goals, scope and major directions of the development specifies variables and constants of the product to be developed identifies resources necessary to conduct the development (capital investments, human resources) Requirements analysis 5
6 Feasibility Study (Machbarkeitsstudie) Check the feasibility of the product development and the product technical feasibility (availability of efficient algorithms,...) economic feasibility (time-to-market, market window, investment, pay-off) Focus of the feasibility study are critical issues of the system in order to improve confidence in the successful completion of the project Problem analysis Analysis Feasibility study Requirements analysis => Output (depends on exact focus of feasibility study) info on expected cost and benefits of the project info on technological and financial risks of project needed resources for development and/or marketing evaluation of possible technical alternatives 6
7 Requirements Analysis Detailed study of the requirements of the system as seen from its environment Identify, analyze and classify the specific requirements of the product to be developed The solution, i.e. the question of how the requirements are met is typically left open Problem analysis Analysis Feasibility study Requirements analysis => Requirements specification (German: Pflichtenheft) Complete and correct Defines output of the development process (deliverables) Definition of the interfaces to the environment Definition of overall functionality of the product Performance requirements Contraints on SW, operating system and HW Possibly guidelines for internal structure of the product 7
8 Requirements Definition: Contents Identification of the system (interfaces to the environment) Functional requirements (functionality provided at the interfaces) Temporal and performance requirements (throughput, response time, delay, jitter) Fault-tolerance and reliability Quality (absence of errors) Safety Operating platform (OS, general HW) Power consumption Heat disipation Operating environment (operating temperature, shock-, dust-resistance, etc.) Size Mechanical construction EMC (Tx/Rx) Maintainability Extendability Support Documentation Cost (development, deployment and operation) Date of completion... We will see methods to ensure that the requirements are met in the design section 8
9 Design and Subphases Design Architectural design Detailed design Implementation design Purpose: decide how the system meets the requirements -> inside view focus on the solution 9
10 Design and Subphases Architectural Design (Top-level Design) define the modules of the system and their interfaces goal: maximize internal coherence and minimize intermodule coordination modules are typically functional entities but may be structural entities as well (structural vs. behavioral modularization) Architectural design Design Detailed design Implementation design Detailed Design (Module Design) define the functional/behavioral details of each module independent of the implementation technique, e.g. its algorithms Implementation Design take into account the details of the used implementation technique, e.g. interfaces to operating systems and hardware When is the behavior of the system decided and when the structure? 10
11 The Design Space: A Complex Optimization Problem System architecture overall architecture (structural model, or mapping of functions on HW, etc.) Design methods (design tools and specification languages) HW selection (System-on-Chip, ASIC, FPGA, DSP, NP, uc, up) HW design methods (languages, HL-Synthesis, RTL-Synthesis, ) HW description (algorithms and implementation) HW mapping and scheduling SW description (programming languages, algorithms and implementation) SW mapping and scheduling HW/SW interfacing Interfacing with environment (embedding) Operating system (OS) support Make or buy (HW, SW, OS) Available human resources and know-how... 11
12 Design Models and Views An Overview Different modeling approaches focus on different aspects of the system & & & structural view msc data_transfer application transport network medium network transport application data-oriented view system functional view behavioral view 12
13 Structural Models Structural models focus on the structure of the system, i.e. its components, modules, etc., rather than its behavior Structural blocks may be abstract (ALUs, processors, memory, busses, chipsets, boards) or detailed (flip-flops, gatter) Examples: netlist, architectural block diagram & & & 13
14 Behavioral Models Behavioral models describe the behavior of the system or parts hereof Implementation of behaviroal models may be in SW or HW however some models are better suited for HW design others better for SW Examples: C program, Petri net, state diagram, data flow graph o(n) = c1 * i(n) + c2 * i(n-1) KEY_ON => START_TIMER WAIT OFF KEY_OFF or BELT _ON => END_TIMER_5 => ALARM_ON Send msg END_TIMER_10 or BELT_ON or KEY_OFF => ALARM_OFF ALARM Process 1 Process 2 Send Ack Receive Ack 14
15 Behavior and Structure Models of computation Requirements Structural model Validation Behavior Simulation System Behavior Mapping System Architecture HW/SW partitioning, scheduling Performance Simulation Synthesis Communication Refinement Flow To Implementation 15
16 Behavior meets Structure: The Optimization Problem Behavioral Space System Platform Structural Space 16
17 Behavior meets Structure: The Optimization Problem Behavioral Space System Platform There are numerous solutions to define the behavior consistent with the given requirements (algorithms, data structures) There are numerous ways to model the defined behavior of the system There are numerous solutions to define the structure of the system (Microcontroller, DSP, customized HW, configurable HW,...) There are multiple ways to model the defined structure of the system Design is about mapping the behavior (including data and functions) on the structure such that all requirements are fulfilled (cost, time constraints, capacity, reliability, maintainability, power consumption,...) Mapping is a very complex optimization problem Structural Space 17
18 Design: Behavior vs. Structure Behavioral specifications describe the functionality of the system using some modeling or programming language behavior specifications may be abstract models (state charts, UML, SDL) or concrete programs (C, VHDL, SystemC) behavioral specifications may be executed/implemented on real HW (C program, assembler) or simulated on virtual HW (VHDL, SystemC, SDL) Behavioral specifications ensure that the functional requirements are met however there is no confidence in non-functional aspects of the system, e.g. performance, real-time, fault tolerance, cost, power consumption,... Structural specifications are needed to implement the system in HW So, when is the best point in time to decide the structure? 18
19 Implementation Prerequisites: Functional details as algorithms, etc. are specified HW components are selected HW/SW partitioning may be decided... Tasks: coding of functions, algorithms, etc. in the selected implementation language test of the modules and components in isolation emulating the environment of the modules/components Notes: provided the design is complete and correct this is straight-forward the implementation phase represents a small part of the development process (appr. 20% for pure SW projects) 19
20 Validation Methods By construction Property is inherent. By verification Property is provable. By testing Check behavior of (all) inputs. By simulation Check behavior in the model world. By intuition Property is true. I just know it is. By assertion Property is true. Wanna make something of it? By intimidation Don t even try to doubt whether it is true. It is generally better to be higher in this list! :-) Validation is a continuous process applied in different phases of the development process and to different models of the system to ensure conformance with various properties/requirements of the system or its components (behavior, temporal requirements, shock resistance,...) 20
21 Integration Purpose: ensure compliance with system requirements complete the system for delivery Tasks: System integration: subsequent addition of HW components and SW modules to the system until the final system is established Integration testing: stepwise testing of system (requires knowledge of the system as a whole) System testing: test after all parts have been integrated Notes: Testing may be applied to almost all requirements or properties of systems, system components or modules (functionality, performance, reliability, termal resistance, shock resistance, ergonomics, man-machine interface, documentation,...) Testing is the most popular validation method in practice 21
22 Maintenance involved during the whole lifetime of a system, from delivery till removal from service deal with changes due to changing environments, changing functional or performance requirements removal of errors Note: often the maintenance cost are much greater than the development cost 22
23 Process Models Overview Waterfall model (top-down) engineering approach to building a house, bridge, etc. no feedback assumed Iterative waterfall model validation and feedback to earlier stages Evolutionary model system development process is considered an evolution of prototypes requirements are subsequently added to the system Spiral model generalisation of various process models (meta model) multiple development cycles including validation V model continuous validation with real world/environment Component-based (bottom-up) compose the system of a set of predefined components (object-based) 23
24 Classic Waterfall Model & Iterative Waterfall Model Classic waterfall model (top-down) Analysis Design Implementation engineering approach to building a house, bridge, etc. no feedback assumed Integration Maintenance Iterative waterfall model validation and feedback to earlier stages 24
25 Evolutionary Model Limits of the waterfall model often the requirements are incomplete in the beginning waterfall model is not appropriate where requirements are not well understood or not well defined with the waterfall model, there are no intermediate product releases Idea of the evolutionary model: provide intermediate product releases refine and extend requirements during the development process analysis design implementation test new prototype needed n y modification of product definition 25
26 Spiral Model Meta model supporting the flexible combination of the above approaches define objectives, alternatives and constraints evaluate alternatives, identify and resolve risks review results; plan next iteration develop and verify 26
27 V Model Extension of the waterfall model to integrate quality assurance (verification and validation) requirements definition application scenarios acceptance test validation top-level design High level test cases system test detailed design module implementation test cases test cases module test integration test verification Validation: ensure the system conforms with the needs of the environment (are we building the right system? product quality) Verification: ensures that the outcome of a development phase exactly conforms to the specification provided as input (is the system built right? process quality) 27
28 Traditional (Early Partitioning) vs. Codesign Approach Early Partitioning (Structure First) system architectur HW/SW Codesign (Behavior First) system description HW descr. SW descr. system architectur HW impl. SW impl. HW impl. SW impl. prototyp/product prototyp/product + optimized descriptions/models for HW and SW parts, respectively - lack of flexibility wrt HW/SW partitioning - problems with HW/SW integration + joint system description/model eases validation and integration - joint description is not optimized for both HW and SW + flexibility wrt. HW/SW partitioning 28
29 Traditional vs. Codesign Approach (Polis, Cadence VCC) Traditional System Design VCC Separation and Mapping System Behavior System Implementation System Architecture System Performance System Behavior System Architecture 1 2 Mapping Behavior on Architecture Refine 3 4 Implementation of System Data Sheets on paper Executable Data Sheets 29
30 References System Focus D. Gajski, F. Vahid, S. Narayan, J. Gong: Specification and Design of Embedded Systems. Prentice Hall, A. Mitschele-Thiel: Systems Engineering with SDL Developing Performance- Critical Communication Systems. Wiley, (section 2.1.2) J. Teich: Digitale Hardware/Software Systeme. Springer, Software Focus H. Balzert: Lehrbuch der Software-Technik Band 1: Softwareentwicklung. Spektrum-Verlag, R. S. Pressman: Software Engineering A Practicioner s Approach. Fourth Edition, McGraw Hill,
Development of Integrated Hard- and Software Systems: Tasks and Processes
TECHNISCHE UNIVERSITÄT ILMENAU Development of Integrated Hard- and Software Systems: Tasks and Processes Integrated Hard- and Software Systems http://www.tu-ilmenau.de/ihs System Development Poor Process
More informationIntegrated HW/SW Systems: Requirements
TECHNISCHE UNIVERSITÄT ILMENAU Integrated Hard- and Software Systems http://www.tu-ilmenau.de/ihs Integrated HW/SW Systems: Requirements Analysis process Functional requirements Performance requirements
More informationIntegrated HW/SW Systems: Requirements
TECHNISCHE UNIVERSITÄT ILMENAU Integrated HW/SW Systems: Requirements Integrated Communication Systems http://www.tu-ilmenau.de/iks Analysis process Functional requirements Performance requirements Real-time
More informationHardware Design Environments. Dr. Mahdi Abbasi Computer Engineering Department Bu-Ali Sina University
Hardware Design Environments Dr. Mahdi Abbasi Computer Engineering Department Bu-Ali Sina University Outline Welcome to COE 405 Digital System Design Design Domains and Levels of Abstractions Synthesis
More informationPart 2: Principles for a System-Level Design Methodology
Part 2: Principles for a System-Level Design Methodology Separation of Concerns: Function versus Architecture Platform-based Design 1 Design Effort vs. System Design Value Function Level of Abstraction
More informationHardware-Software Codesign. 1. Introduction
Hardware-Software Codesign 1. Introduction Lothar Thiele 1-1 Contents What is an Embedded System? Levels of Abstraction in Electronic System Design Typical Design Flow of Hardware-Software Systems 1-2
More informationCMSC 435: Software Engineering Section 0201
CMSC 435: Software Engineering Section 0201 Atif M. Memon (atif@cs.umd.edu) 4115 A.V.Williams building Phone: 301-405-3071 Office hours Tu.Th. (11:00am-1:00pm) Don t wait, don t hesitate, do communicate!!
More informationHardware Design and Simulation for Verification
Hardware Design and Simulation for Verification by N. Bombieri, F. Fummi, and G. Pravadelli Universit`a di Verona, Italy (in M. Bernardo and A. Cimatti Eds., Formal Methods for Hardware Verification, Lecture
More informationHardware-Software Codesign. 1. Introduction
Hardware-Software Codesign 1. Introduction Lothar Thiele 1-1 Contents What is an Embedded System? Levels of Abstraction in Electronic System Design Typical Design Flow of Hardware-Software Systems 1-2
More informationCodesign Framework. Parts of this lecture are borrowed from lectures of Johan Lilius of TUCS and ASV/LL of UC Berkeley available in their web.
Codesign Framework Parts of this lecture are borrowed from lectures of Johan Lilius of TUCS and ASV/LL of UC Berkeley available in their web. Embedded Processor Types General Purpose Expensive, requires
More informationVO Software Engineering
Administrative Issues Univ.Prof. Dr. Peter Auer Chair for Information Technology Email: auer@unileoben.ac.at Lecture Thursday 10:15 11:45 Project Lab Montag 16:00 19:00 Literature Helmut Balzert, Lehrbuch
More informationHardware/Software Co-design
Hardware/Software Co-design Zebo Peng, Department of Computer and Information Science (IDA) Linköping University Course page: http://www.ida.liu.se/~petel/codesign/ 1 of 52 Lecture 1/2: Outline : an Introduction
More informationHardware/Software Codesign
Hardware/Software Codesign SS 2016 Prof. Dr. Christian Plessl High-Performance IT Systems group University of Paderborn Version 2.2.0 2016-04-08 how to design a "digital TV set top box" Motivating Example
More informationEEM870 Embedded System and Experiment Lecture 4: SoC Design Flow and Tools
EEM870 Embedded System and Experiment Lecture 4: SoC Design Flow and Tools Wen-Yen Lin, Ph.D. Department of Electrical Engineering Chang Gung University Email: wylin@mail.cgu.edu.tw March 2013 Agenda Introduction
More informationIntroduction to Software Engineering
Introduction to Software Engineering Gérald Monard Ecole GDR CORREL - April 16, 2013 www.monard.info Bibliography Software Engineering, 9th ed. (I. Sommerville, 2010, Pearson) Conduite de projets informatiques,
More informationHardware-Software Codesign
Hardware-Software Codesign 8. Performance Estimation Lothar Thiele 8-1 System Design specification system synthesis estimation -compilation intellectual prop. code instruction set HW-synthesis intellectual
More informationSoftware Processes. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationHardware Software Codesign of Embedded System
Hardware Software Codesign of Embedded System CPSC489-501 Rabi Mahapatra Mahapatra - Texas A&M - Fall 00 1 Today s topics Course Organization Introduction to HS-CODES Codesign Motivation Some Issues on
More informationHW/SW Co-design. Design of Embedded Systems Jaap Hofstede Version 3, September 1999
HW/SW Co-design Design of Embedded Systems Jaap Hofstede Version 3, September 1999 Embedded system Embedded Systems is a computer system (combination of hardware and software) is part of a larger system
More informationSoftware Verification and Validation (VIMMD052) Introduction. Istvan Majzik Budapest University of Technology and Economics
Software Verification and Validation (VIMMD052) Introduction Istvan Majzik majzik@mit.bme.hu Budapest University of Technology and Economics Dept. of Measurement and Information s Budapest University of
More informationConcepts for Model Compilation in Hardware/Software Codesign
Concepts for Model Compilation in Hardware/Software Codesign S. Schulz, and J.W. Rozenblit Dept. of Electrical and Computer Engineering The University of Arizona Tucson, AZ 85721 USA sschulz@ece.arizona.edu
More informationRTL Coding General Concepts
RTL Coding General Concepts Typical Digital System 2 Components of a Digital System Printed circuit board (PCB) Embedded d software microprocessor microcontroller digital signal processor (DSP) ASIC Programmable
More informationEvaluation of Temporal and Performance Aspects
TECHNISCHE UNIVERSITÄT ILMENAU Evaluation of Temporal and Performance Aspects Integrated Hard- and Software Systems http://www.tu-ilmenau.de/ihs Problem Statement Performance Modeling Performance Evaluation
More informationHardware-Software Codesign
Hardware-Software Codesign 4. System Partitioning Lothar Thiele 4-1 System Design specification system synthesis estimation SW-compilation intellectual prop. code instruction set HW-synthesis intellectual
More informationEE382V: System-on-a-Chip (SoC) Design
EE382V: System-on-a-Chip (SoC) Design Lecture 8 HW/SW Co-Design Sources: Prof. Margarida Jacome, UT Austin Andreas Gerstlauer Electrical and Computer Engineering University of Texas at Austin gerstl@ece.utexas.edu
More informationDigital Hardware-/Softwaresystems Specification
Digital Hardware-/Softwaresystems Specification Seminar Architecture & Design Methods for Embedded Systems Summer Term 2006 University of Stuttgart Faculty of Computer Science, Electrical Engineering and
More informationIntroduction. Definition. What is an embedded system? What are embedded systems? Challenges in embedded computing system design. Design methodologies.
Introduction What are embedded systems? Challenges in embedded computing system design. Design methodologies. What is an embedded system? Communication Avionics Automobile Consumer Electronics Office Equipment
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationESE Back End 2.0. D. Gajski, S. Abdi. (with contributions from H. Cho, D. Shin, A. Gerstlauer)
ESE Back End 2.0 D. Gajski, S. Abdi (with contributions from H. Cho, D. Shin, A. Gerstlauer) Center for Embedded Computer Systems University of California, Irvine http://www.cecs.uci.edu 1 Technology advantages
More informationSystem Level Design with IBM PowerPC Models
September 2005 System Level Design with IBM PowerPC Models A view of system level design SLE-m3 The System-Level Challenges Verification escapes cost design success There is a 45% chance of committing
More informationChapter 4 Objectives
Chapter 4 Objectives Eliciting requirements from the customers Modeling requirements Reviewing requirements to ensure their quality Documenting requirements for use by the design and test teams 4.1 The
More informationThe requirements engineering process
3 rd Stage Lecture time: 8:30-12:30 AM Instructor: Ali Kadhum AL-Quraby Lecture No. : 5 Subject: Software Engineering Class room no.: Department of computer science Process activities The four basic process
More informationSOFTWARE ENGINEERING
SOFTWARE ENGINEERING INTRODUCTION TO SOFTWARE ENGINEERING. COURSE STRUCTURE AND REQUIREMENTS Saulius Ragaišis saulius.ragaisis@mif.vu.lt WHAT IS SOFTWARE ENGINEERING? First definition Software engineering
More informationChallenges. Shift to Reuse Strategy Higher Level of Abstractions Software!!!
Challenges Shift to Reuse Strategy Higher Level of Abstractions Software!!! 1 PERCENT OF TRANSISTORS WITHIN EMBEDDED IP (EXCLUDES MEMORY) 100 Random Logic Transistors Transistors (%) Transistors Within
More informationSoftware Engineering 2 A practical course in software engineering. Ekkart Kindler
Software Engineering 2 A practical course in software engineering IV. Working Together Working together Management Process Models Version Management Systems Collaborative Development Environments 3 Parts
More informationSOFTWARE ENGINEERING
SOFTWARE ENGINEERING INTRODUCTION TO SOFTWARE ENGINEERING. COURSE STRUCTURE AND REQUIREMENTS Saulius Ragaišis saulius.ragaisis@mif.vu.lt WHAT IS SOFTWARE ENGINEERING? First definition Software engineering
More informationA Consistent Design Methodology for Configurable HW/SW-Interfaces in Embedded Systems Embedded Systems Design
A Consistent Design Methodology for Configurable HW/SW-Interfaces in Embedded Systems Embedded Systems Design Stefan llimor, Markus Visarius, Wolfram Hardt {ihmor I visi I hardt}@upb.de University of Paderborn,
More informationTopics. Verilog. Verilog vs. VHDL (2) Verilog vs. VHDL (1)
Topics Verilog Hardware modeling and simulation Event-driven simulation Basics of register-transfer design: data paths and controllers; ASM charts. High-level synthesis Initially a proprietary language,
More informationHardware/Software Codesign
Hardware/Software Codesign 3. Partitioning Marco Platzner Lothar Thiele by the authors 1 Overview A Model for System Synthesis The Partitioning Problem General Partitioning Methods HW/SW-Partitioning Methods
More informationDesign Issues in Hardware/Software Co-Design
Volume-2, Issue-1, January-February, 2014, pp. 01-05, IASTER 2013 www.iaster.com, Online: 2347-6109, Print: 2348-0017 ABSTRACT Design Issues in Hardware/Software Co-Design R. Ganesh Sr. Asst. Professor,
More informationCS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS 6403 - SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS 1. Explain iterative waterfall and spiral model for software life cycle and various activities
More informationLecture 3: Design Methodologies
Lecture 3: Design Methodologies Embedded Computing Systems Mikko Lipasti, adapted from M. Schulte Based on slides and textbook from Wayne Wolf High Performance Embedded Computing 2007 Elsevier Topics Design
More informationHardware Modeling using Verilog Prof. Indranil Sengupta Department of Computer Science and Engineering Indian Institute of Technology, Kharagpur
Hardware Modeling using Verilog Prof. Indranil Sengupta Department of Computer Science and Engineering Indian Institute of Technology, Kharagpur Lecture 01 Introduction Welcome to the course on Hardware
More informationChapter 1 Overview of Digital Systems Design
Chapter 1 Overview of Digital Systems Design SKEE2263 Digital Systems Mun im/ismahani/izam {munim@utm.my,e-izam@utm.my,ismahani@fke.utm.my} February 8, 2017 Why Digital Design? Many times, microcontrollers
More informationProgrammable Logic Devices HDL-Based Design Flows CMPE 415
HDL-Based Design Flows: ASIC Toward the end of the 80s, it became difficult to use schematic-based ASIC flows to deal with the size and complexity of >5K or more gates. HDLs were introduced to deal with
More informationCOE 561 Digital System Design & Synthesis Introduction
1 COE 561 Digital System Design & Synthesis Introduction Dr. Aiman H. El-Maleh Computer Engineering Department King Fahd University of Petroleum & Minerals Outline Course Topics Microelectronics Design
More informationDesigning with VHDL and FPGA
Designing with VHDL and FPGA Instructor: Dr. Ahmad El-Banna lab# 1 1 Agenda Course Instructor Course Contents Course References Overview of Digital Design Intro. to VHDL language and FPGA technology IDE
More informationSemantics-Based Integration of Embedded Systems Models
Semantics-Based Integration of Embedded Systems Models Project András Balogh, OptixWare Research & Development Ltd. n 100021 Outline Embedded systems overview Overview of the GENESYS-INDEXYS approach Current
More informationSystem Level Design Technologies and System Level Design Languages
System Level Design Technologies and System Level Design Languages SLD Study Group EDA-TC, JEITA http://eda.ics.es.osaka-u.ac.jp/jeita/eda/english/project/sld/index.html Problems to Be Solved 1. Functional
More informationPerformance Verification for ESL Design Methodology from AADL Models
Performance Verification for ESL Design Methodology from AADL Models Hugues Jérome Institut Supérieur de l'aéronautique et de l'espace (ISAE-SUPAERO) Université de Toulouse 31055 TOULOUSE Cedex 4 Jerome.huges@isae.fr
More informationElectronic Design Automation Prof. Indranil Sengupta Department of Computer Science and Engineering Indian Institute of Technology, Kharagpur
Electronic Design Automation Prof. Indranil Sengupta Department of Computer Science and Engineering Indian Institute of Technology, Kharagpur Lecture No #1 Introduction So electronic design automation,
More informationSoftware architecture in ASPICE and Even-André Karlsson
Software architecture in ASPICE and 26262 Even-André Karlsson Agenda Overall comparison (3 min) Why is the architecture documentation difficult? (2 min) ASPICE requirements (8 min) 26262 requirements (12
More informationBibliography. Measuring Software Reuse, Jeffrey S. Poulin, Addison-Wesley, Practical Software Reuse, Donald J. Reifer, Wiley, 1997.
Bibliography Books on software reuse: 1. 2. Measuring Software Reuse, Jeffrey S. Poulin, Addison-Wesley, 1997. Practical Software Reuse, Donald J. Reifer, Wiley, 1997. Formal specification and verification:
More informationChapter 5: ASICs Vs. PLDs
Chapter 5: ASICs Vs. PLDs 5.1 Introduction A general definition of the term Application Specific Integrated Circuit (ASIC) is virtually every type of chip that is designed to perform a dedicated task.
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationProgrammable Logic Devices II
São José February 2015 Prof. Hoeller, Prof. Moecke (http://www.sj.ifsc.edu.br) 1 / 28 Lecture 01: Complexity Management and the Design of Complex Digital Systems Prof. Arliones Hoeller arliones.hoeller@ifsc.edu.br
More informationSystem Design and Methodology/ Embedded Systems Design (Modeling and Design of Embedded Systems)
Design&Methodologies Fö 1&2-1 Design&Methodologies Fö 1&2-2 Course Information Design and Methodology/ Embedded s Design (Modeling and Design of Embedded s) TDTS07/TDDI08 Web page: http://www.ida.liu.se/~tdts07
More informationMOJTABA MAHDAVI Mojtaba Mahdavi DSP Design Course, EIT Department, Lund University, Sweden
High Level Synthesis with Catapult MOJTABA MAHDAVI 1 Outline High Level Synthesis HLS Design Flow in Catapult Data Types Project Creation Design Setup Data Flow Analysis Resource Allocation Scheduling
More informationEE595. Part VIII Overall Concept on VHDL. EE 595 EDA / ASIC Design Lab
EE595 Part VIII Overall Concept on VHDL VHDL is a Standard Language Standard in the electronic design community. VHDL will virtually guarantee that you will not have to throw away and re-capture design
More informationSoftware Engineering Lifecycles. Controlling Complexity
Software Engineering Lifecycles Class url:http://laser.cs.umass.edu/courses/cs320.spring11/ Controlling Complexity Separation of Concerns Planning Ahead Do a little work now to make later work easier The
More informationFPGAs: High Assurance through Model Based Design
FPGAs: High Assurance through Based Design AADL Workshop 24 January 2007 9:30 10:00 Yves LaCerte Rockwell Collins Advanced Technology Center 400 Collins Road N.E. Cedar Rapids, IA 52498 ylacerte@rockwellcollins.cm
More informationLecture 1: Introduction Course arrangements Recap of basic digital design concepts EDA tool demonstration
TKT-1426 Digital design for FPGA, 6cp Fall 2011 http://www.tkt.cs.tut.fi/kurssit/1426/ Tampere University of Technology Department of Computer Systems Waqar Hussain Lecture Contents Lecture 1: Introduction
More informationFunctional verification on PIL mode with IAR Embedded Workbench
by Cristina Marconcini, STM CASE s.r.l. Functional verification on PIL mode with IAR Embedded Workbench The increase of complexity of embedded system components combined with time-to-market constraints
More informationSoftware Engineering 2 A practical course in software engineering. Ekkart Kindler
Software Engineering 2 A practical course in software engineering V. Working Together Working together Management Process Models Version Management Systems Collaborative Development Environments 3 Parts
More informationDesign Methodologies. Kai Huang
Design Methodologies Kai Huang News Is that real? In such a thermally constrained environment, going quad-core only makes sense if you can properly power gate/turbo up when some cores are idle. I have
More informationOverview. Design flow. Principles of logic synthesis. Logic Synthesis with the common tools. Conclusions
Logic Synthesis Overview Design flow Principles of logic synthesis Logic Synthesis with the common tools Conclusions 2 System Design Flow Electronic System Level (ESL) flow System C TLM, Verification,
More informationECE 587 Hardware/Software Co-Design Lecture 12 Verification II, System Modeling
ECE 587 Hardware/Software Co-Design Spring 2018 1/20 ECE 587 Hardware/Software Co-Design Lecture 12 Verification II, System Modeling Professor Jia Wang Department of Electrical and Computer Engineering
More informationHardware in the Loop Functional Verification Methodology
OMG's Third Software-Based Communications Workshop: Realizing the Vision Hardware in the Loop Functional Verification Methodology by Pascal Giard Jean-François Boland, Jean Belzile M.Ing. Student École
More informationECE 587 Hardware/Software Co-Design Lecture 11 Verification I
ECE 587 Hardware/Software Co-Design Spring 2018 1/23 ECE 587 Hardware/Software Co-Design Lecture 11 Verification I Professor Jia Wang Department of Electrical and Computer Engineering Illinois Institute
More informationLong Term Trends for Embedded System Design
Long Term Trends for Embedded System Design Ahmed Amine JERRAYA Laboratoire TIMA, 46 Avenue Félix Viallet, 38031 Grenoble CEDEX, France Email: Ahmed.Jerraya@imag.fr Abstract. An embedded system is an application
More informationIncremental development A.Y. 2018/2019
Incremental development A.Y. 2018/2019 Incremental development Interleaves the activities of specification, development, and validation. The system is developed as a series of versions (increments), with
More informationMentor Graphics Solutions Enable Fast, Efficient Designs for Altera s FPGAs. Fall 2004
Mentor Graphics Solutions Enable Fast, Efficient Designs for Altera s FPGAs Fall 2004 Agenda FPGA design challenges Mentor Graphics comprehensive FPGA design solutions Unique tools address the full range
More informationSOFTWARE ARCHITECTURE & DESIGN INTRODUCTION
SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION http://www.tutorialspoint.com/software_architecture_design/introduction.htm Copyright tutorialspoint.com The architecture of a system describes its major components,
More informationEmpAnADa Project. Christian Lange. June 4 th, Eindhoven University of Technology, The Netherlands.
EmpAnADa Project C.F.J.Lange@tue.nl June 4 th, 2004 Eindhoven University of Technology, The Netherlands Outline EmpAnADa introduction Part I Completeness and consistency in detail Part II Background UML
More informationIntroduction to Assurance
Introduction to Assurance Overview Why assurance? Trust and assurance Life cycle and assurance April 1, 2015 Slide #1 Overview Trust Problems from lack of assurance Types of assurance Life cycle and assurance
More information((MARKS)) (1/2/3...) ((QUESTIO N)) ((OPTION_ A)) What is Software?
SNJB s Late Sau. KBJ COE, Chandwad Department of Computer Engg PART I : Software development process, language and software development environments, language and software design methods, languages and
More informationHardware Modelling. Design Flow Overview. ECS Group, TU Wien
Hardware Modelling Design Flow Overview ECS Group, TU Wien 1 Outline Difference: Hardware vs. Software Design Flow Steps Specification Realisation Verification FPGA Design Flow 2 Hardware vs. Software:
More informationHardware Software Codesign of Embedded Systems
Hardware Software Codesign of Embedded Systems Rabi Mahapatra Texas A&M University Today s topics Course Organization Introduction to HS-CODES Codesign Motivation Some Issues on Codesign of Embedded System
More informationSpecifying and Prototyping
Contents Specifying and Prototyping M. EVREN KIYMAÇ 2008639030 What is Specifying? Gathering Specifications Specifying Approach & Waterfall Model What is Prototyping? Uses of Prototypes Prototyping Process
More informationHardware Software Codesign of SOC 晶片系統之軟硬體共同設計
Hardware Software Codesign of SOC 晶片系統之軟硬體共同設計 李宗演國立台北科技大學電子工程系 tylee@ntut.edu.tw http://www.ntut.edu.tw/~tylee/ 1 Contents Introduction SoC Models, Architectures, Languages SoC HW-SW Partitioning Function-Architecture
More informationBy Matthew Noonan, Project Manager, Resource Group s Embedded Systems & Solutions
Building Testability into FPGA and ASIC Designs By Matthew Noonan, Project Manager, Resource Group s Embedded Systems & Solutions Introduction This paper discusses how the architecture for FPGAs and ASICs
More informationSecond. Incremental development model
3 rd Stage Lecture time: 8:30 AM-2:30 PM Instructor: Ali Kadhum AL-Quraby Lecture No. : 4 Subject: Software Engineering Class room no.: Department of computer science Second. Incremental development model
More informationSystem Planning Overcoming Gap Between Design at Electronic System Level (ESL) and Implementation
System Planning Overcoming Gap Between Design at Electronic System Level (ESL) and Implementation Horst Salzwedel, TU Ilmenau Presented at EDACentrum Workshop: System Planning Hannover, 30 November 2006
More informationA Deterministic Flow Combining Virtual Platforms, Emulation, and Hardware Prototypes
A Deterministic Flow Combining Virtual Platforms, Emulation, and Hardware Prototypes Presented at Design Automation Conference (DAC) San Francisco, CA, June 4, 2012. Presented by Chuck Cruse FPGA Hardware
More informationRequirements and Design Overview
Requirements and Design Overview Robert B. France Colorado State University Robert B. France O-1 Why do we model? Enhance understanding and communication Provide structure for problem solving Furnish abstractions
More informationRecalling the definition of design as set of models let's consider the modeling of some real software.
Software Design and Architectures SE-2 / SE426 / CS446 / ECE426 Lecture 3 : Modeling Software Software uniquely combines abstract, purely mathematical stuff with physical representation. There are numerous
More informationTransformation of analysis model to design model
2010 International Conference on E-business, Management and Economics IPEDR vol.3 (2011) (2011) IACSIT Press, Hong Kong Transformation of analysis model to design model Lalji Prasad Truba College of Engineering
More informationRefinement and Formalization of Semi-Formal Use Case Descriptions
Refinement and Formalization of Semi-Formal Use Case Descriptions Matthias Riebisch, Michael Hübner Ilmenau Technical University Max-Planck-Ring 14; 98684 Ilmenau; Germany {matthias.riebisch michael.huebner}@tu-ilmenau.de
More informationIntroduction to Software Engineering
Chapter 1 Introduction to Software Engineering Content 1. Introduction 2. Components 3. Layered Technologies 4. Generic View of Software Engineering 4. Generic View of Software Engineering 5. Study of
More informationSE 2730 Final Review
SE 2730 Final Review 1. Introduction 1) What is software: programs, associated documentations and data 2) Three types of software products: generic, custom, semi-custom Why is semi-custom product more
More informationmywbut.com Software Life Cycle Model
Software Life Cycle Model 1 Basics of Software Life Cycle and Waterfall Model 2 Specific Instructional Objectives At the end of this lesson the student will be able to: Explain what is a life cycle model.
More informationRequirements Engineering: Specification & Validation. Software Requirements and Design CITS 4401 Lecture 18
Requirements Engineering: Specification & Validation Software Requirements and Design CITS 4401 Lecture 18 The Problems of Requirements What goal(s) are we trying to satisfy? How do we identify the scope
More informationSeminar report Software reuse
A Seminar report On Software reuse Submitted in partial fulfillment of the requirement for the award of degree of Bachelor of Technology in Computer Science SUBMITTED TO: www.studymafia.com SUBMITTED BY:
More informationWhat are Embedded Systems? Lecture 1 Introduction to Embedded Systems & Software
What are Embedded Systems? 1 Lecture 1 Introduction to Embedded Systems & Software Roopa Rangaswami October 9, 2002 Embedded systems are computer systems that monitor, respond to, or control an external
More informationRelease of Octopus/UML
Release of Octopus/UML 1 Release of Octopus/UML Domiczi Endre, Farfarakis Rallis, Ziegler Jürgen Nokia Research Center 1. INTRODUCTION...1 2. THE OCTOPUS MISSION...2 3. KEY CONCEPTS...2 3.1 Artifacts...2
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms
Standard Glossary of Terms used in Software Testing Version 3.2 Foundation Extension - Usability Terms International Software Testing Qualifications Board Copyright Notice This document may be copied in
More information1. i. What are the 3 major components of a information system and show their relationship input output
Higher National Diploma in Information Technology First Year, Second semesterexamination-2011 IT2005: System Analysis and Design Answer Script No. of pages: 11 1. i. What are the 3 major components of
More informationAbstraction Layers for Hardware Design
SYSTEMC Slide -1 - Abstraction Layers for Hardware Design TRANSACTION-LEVEL MODELS (TLM) TLMs have a common feature: they implement communication among processes via function calls! Slide -2 - Abstraction
More informationProduct Quality Engineering. RIT Software Engineering
Product Quality Engineering Q vs q Quality includes many more attributes than just absence of defects Features Performance Availability Safety Security Reusability Extensibility Modifiability Portability
More informationHardware Design Verification: Simulation and Formal Method-Based Approaches William K Lam Prentice Hall Modern Semiconductor Design Series
Design Verification An Introduction Main References Hardware Design Verification: Simulation and Formal Method-Based Approaches William K Lam Prentice Hall Modern Semiconductor Design Series A Roadmap
More information