Design Specification Document A living document Specified the detail, at a high level, of what the design must satisfy. The Inputs and Outputs Specified as to number, format of each, input control signals, etc. Same for the outputs The internals High level specification of what transformation is done to the inputs to generate the outputs. Should include algorithms to use, and information on architecture of the execution unit(s). 1/8/2007 - Extra Credit Copyright 2006 - Joanne DeGroat, ECE, OSU

Copyright 2006 - Joanne DeGroat, ECE, OSU The Design Document Follows directly from the specification document. Gives specific details on how the design accomplishes what was specified. Need to the specification document to fully grasp what is presented. Should include the timeline for the effort. 1/8/2007 - Extra Credit Copyright 2006 - Joanne DeGroat, ECE, OSU

Copyright 2006 - Joanne DeGroat, ECE, OSU Verification Plan Goes hand in hand with the previous documents. Given how the design is implemented, it is the plan on how it will be verified that the implementation meets the specification through functional verification. Functional verification is supported by ModelSim and Questa, the tools we have access to. The Plan specifies the specific tasks to be done, the personal, the timeline, the methodology and tools to be used. 1/8/2007 - Extra Credit Copyright 2006 - Joanne DeGroat, ECE, OSU

The Verification Report The verification report covers the results of the verification effort, summarizing the results of each verification task presented in the Verification Plan. 1/8/2007 - Extra Credit Copyright 2006 - Joanne DeGroat, ECE, OSU

Copyright 2006 - Joanne DeGroat, ECE, OSU The Oral Report This report is an oral and slide presentation of what is contained in the 4 documents. It should cover the Specifications The design The verification plan The results of the verification effort And have a summary that the unit is good to market as IP. 1/8/2007 - Extra Credit Copyright 2006 - Joanne DeGroat, ECE, OSU