Search Results

The technological and process developments within the semiconductor industry during the past two decades has led to significant advancements in the complexity, functionality and performance of standard devices, such as microprocessors, digital signal processors, memories and custom Application Specific Integrated Circuits (ASICs). Field Programmable Gate Array (FPGA) suppliers have taken advantage of these developments to offer device configurations that can include millions of programmable gates integrated with megabytes of internal memory and processor cores in package profiles and temperature ranges suitable for a variety of applications. The combination of reusable intellectual property, low unit costs and relative ease of implementation has led to increased FPGA usage in the automotive industry. Engineers are turning to FPGA solutions to enable the required features and functions not currently available with standard components.

Model-based systems development relies upon the concept of an executable specification. A survey of published literature shows a wide range of definitions for executable specifications [1, 2, 3, 4, 5, 6, 7, 8, 9 and 10]. In this paper, we attempt to codify the essential starting elements for a complete executable specification-based design flow. A complete executable specification that includes a functional model as well as test cases, in addition to a traditional prose document, is needed to transfer requirements from a customer to a supplier, or from a systems engineer to electrical hardware and software engineers. In the complete form demonstrated here, sub-components of a functionally-decomposed system manifest as modular reuse blocks suitable for publication in functional libraries. The overarching definition provided by product architecture and by software architecture must also be harmoniously integrated with design and implementation.