Verification Plan & Levels of Verification

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Developed by Reneta Barneva, SUNY Fredonia
Standard Interfaces for FPGA Components Joshua Noseworthy Mercury Computer Systems Inc.
SOFTWARE TESTING. Software Testing Principles Types of software tests Test planning Test Development Test Execution and Reporting Test tools and Methods.
University Of Vaasa Telecommunications Engineering Automation Seminar Signal Generator By Tibebu Sime 13 th December 2011.
Alternate Software Development Methodologies
Verification Plan. This is the specification for the verification effort. It gives the what am I verifying and how am I going to do it!
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Prof. John Nestor ECE Department Lafayette College Easton, Pennsylvania ECE VLSI System Design Lecture 7 - Synchronizers.
Physical Implementation 1)Manufactured Integrated Circuit (IC) Technologies 2)Programmable IC Technology 3)Other Technologies Other Technologies 1. Off-The-Shelf.
1 HW/SW Partitioning Embedded Systems Design. 2 Hardware/Software Codesign “Exploration of the system design space formed by combinations of hardware.
System-Level Verification –a Comparison of Approach Ray Turner Rapid Systems Prototyping, IEEE International Workshop on.
EE694v-Verification-Lect5-1- Lecture 5 - Verification Tools Automation improves the efficiency and reliability of the verification process Some tools,
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
From Concept to Silicon How an idea becomes a part of a new chip at ATI Richard Huddy ATI Research.
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
Introduction to Software Testing
Digital Circuit Implementation. Wafers and Chips  Integrated circuit (IC) chips are manufactured on silicon wafers  Transistors are placed on the wafers.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Testing. Definition From the dictionary- the means by which the presence, quality, or genuineness of anything is determined; a means of trial. For software.
INFO 637Lecture #81 Software Engineering Process II Integration and System Testing INFO 637 Glenn Booker.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Software Testing.
Chap. 1 Overview of Digital Design with Verilog. 2 Overview of Digital Design with Verilog HDL Evolution of computer aided digital circuit design Emergence.
COE4OI5 Engineering Design. Copyright S. Shirani 2 Course Outline Design process, design of digital hardware Programmable logic technology Altera’s UP2.
ASIC/FPGA design flow. FPGA Design Flow Detailed (RTL) Design Detailed (RTL) Design Ideas (Specifications) Design Ideas (Specifications) Device Programming.
Putting together a complete system Chapter 10. Overview  Design a modest but complete system  A collection of objects work together to solve a problem.
FPGA-Based System Design: Chapter 6 Copyright  2004 Prentice Hall PTR Topics n Design methodologies.
PROCStar III Performance Charactarization Instructor : Ina Rivkin Performed by: Idan Steinberg Evgeni Riaboy Semestrial Project Winter 2010.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
The Macro Design Process The Issues 1. Overview of IP Design 2. Key Features 3. Planning and Specification 4. Macro Design and Verification 5. Soft Macro.
1 Ch. 1: Software Development (Read) 5 Phases of Software Life Cycle: Problem Analysis and Specification Design Implementation (Coding) Testing, Execution.
Verification Environment Architecture Sergey Nemanov December 21, 2005 Verification Leadership Seminar.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter.
2D/3D Integration Challenges: Dynamic Reconfiguration and Design for Reuse.
Verification – The importance
DEVICES AND DESIGN : ASIC. DEFINITION Any IC other than a general purpose IC which contains the functionality of thousands of gates is usually called.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
Macro Verification Guidelines Chapter 7.. Chap 7. Macro Verification Guidelines The goal of macro verification The macro is 100 percent correct in its.
MP3 Decoding Network 0xf1d0 Rod Green (rdg) Eric Haas (haas) Ming Luo (mluo) Jim Shuma (shuma)
Software Engineering and Object-Oriented Design Topics: Solutions Modules Key Programming Issues Development Methods Object-Oriented Principles.
Software Engineering Saeed Akhtar The University of Lahore.
Lecture 1 – Overview (rSp06) ©2008 Joanne DeGroat, ECE, OSU -1- Functional Verification of Hardware Designs EE764 – Functional Verification of Hardware.
EE694v-Verification-Lect7-1- Verification Plan & Levels of Verification The Verification Plan Yesterdays and today’s design environment Design specification.
CS223: Software Engineering Lecture 4: Software Development Models.
Digital Design Using VHDL and PLDs ECOM 4311 Digital System Design Chapter 1.
12005 MAPLDIssues in FPGA Verification Panel Discussion 2005 MAPLD International Conference Washington, D.C. September 6, 2005.
Chapter 11 System-Level Verification Issues. The Importance of Verification Verifying at the system level is the last opportunity to find errors before.
ECE 448 Lecture 6 Finite State Machines State Diagrams vs. Algorithmic State Machine (ASM) Charts.
ASIC/FPGA design flow. Design Flow Detailed Design Detailed Design Ideas Design Ideas Device Programming Device Programming Timing Simulation Timing Simulation.
Real-Time System-On-A-Chip Emulation.  Introduction  Describing SOC Designs  System-Level Design Flow  SOC Implemantation Paths-Emulation and.
Chapter 10 Software quality. This chapter discusses n Some important properties we want our system to have, specifically correctness and maintainability.
Lecture 1 – Overview (rSp06) ©2008 Joanne DeGroat, ECE, OSU -1- Functional Verification of Hardware Designs EE764 – Functional Verification of Hardware.
SOFTWARE TESTING SOFTWARE TESTING Presented By, C.Jackulin Sugirtha-10mx15 R.Jeyaramar-10mx17K.Kanagalakshmi-10mx20J.A.Linda-10mx25P.B.Vahedha-10mx53.
Software Engineering (CSI 321)
Digital System Verification
Verification and Testing
Object oriented system development life cycle
ECE 448 Lecture 6 Finite State Machines State Diagrams vs. Algorithmic State Machine (ASM) Charts.
Introduction to Software Testing
System-level verification and Board level verification
ChipScope Pro Software
Verification Plan & Levels of Verification
Baisc Of Software Testing
Test Case Test case Describes an input Description and an expected output Description. Test case ID Section 1: Before execution Section 2: After execution.
L9 - Verification Strategies
ChipScope Pro Software
Digital Engineering Laboratory
Physical Implementation
Presentation transcript:

Verification Plan & Levels of Verification The Verification Plan Yesterdays and today’s design environment Design specification document Verification success Levels of verification EE694v-Verification-Lect7

EE694v-Verification-Lect7 The Verification Plan Just as a design meets a specification, the verification plan is the specification for the verification effort. Defines What is success How a design is to be verified Functional correctness Which testbenches to write Schedule for verification effort EE694v-Verification-Lect7

EE694v-Verification-Lect7 In The Past Verification was left to each designer to do as they wished Verification was done as time allowed Emphasis was “does chip work?” Have progressed from “does chip work?” to Does chip work in the system? Does chip work in the system as specified? Does the system work as specified? EE694v-Verification-Lect7

EE694v-Verification-Lect7 Today’s Environment Wish to have system integration go smoothly Simulate chip(s) in system environment to identify problems early, preferably during design and prior to fabrication Tools, if effectively used, can help Simulation Linting Other tools EE694v-Verification-Lect7

Specifying the Verification When will verification of design be completed to the required degree of confidence Must determine How much work verification will require How many people are needed for the verification effort How long will the verification effort take EE694v-Verification-Lect7

Design Specification Document Verification effort relies on a complete specification document Must be a written document Is the common source for both the design’s implementation and its verification When design’s output is not as expected this document helps determine whether the design is correct (verification in error) or not (verification correct) EE694v-Verification-Lect7

The Plan & 1st Time Success The verification plan defines what success is Insures all essential features of design are appropriately verified Documents which features are essential and which are optional Not all features of the final design need be included in defining 1st time success Final success requires that all features in the final design are working and verified so. EE694v-Verification-Lect7

Levels of Verification As the level of focus changes, what is being verified changes also The level of granularity is also included in the plan Best partitions to verify are those where controlability and observability are best Partitions being verified must have relatively stable functionality and interfaces EE694v-Verification-Lect7

Unit-Level Verification Design units are logical partitions and vary from small to large, simple to complex Small/Simple - FIFO, small state machine Large/Complex - PCI slave interface, DSP datapath Often have interfaces that are not fixed and firm Often functionality is not yet fixed and firm Any reasonable size project will have a large number of design units Verification of the entire design at this level would probably be too time consuming EE694v-Verification-Lect7

Reusable Component Verification Component is designed to its own specification Component intended to be used as-is in many different designs Typically the component implements a common function or allows connection to a standardized interface Component is used in many designs - focus is on its functionality Potential users must have confidence that design is indeed correct EE694v-Verification-Lect7

ASIC & FPGA Verification These units form a physical and possibly a logical partition Often have their own specification Often contain a collection of independently designed and verified components Todays ASICs and FPGAs are too complex to verify and debug during integration. Need verification for them prior to synthesis or downloading the programming. EE694v-Verification-Lect7

System-Level Verification There are many definitions for a system!!! In the book - “a system is a logical partition composed of independently verified components.” System could be composed of a few reusable components a subset of an SoC ASIC ASICs (or part of ASICs) on different boards Focuses on interaction between components Relies on individual components being functionally correct EE694v-Verification-Lect7

Board-Level Verification Confirm that component connectivity is correct Some components on boards, such as capacitors, do not translate easily to digital domain Depending on the complexity level, could be used to verify functionality (as with any other level) Must make sure what is verified is what is manufactured (as with all levels) EE694v-Verification-Lect7