Contents


Metropolis Home
Overview
  Metamodel
  Tools
  Design Methodologies
  Platform-Based Design
  Wiki
Publications
 
  4/07 IEEE Article
  4/03 IEEE Article
  6/02 GSRC Presentations
  People
  Polis
  Search
Members
  src
  Private Forum

Metropolis: Design Environment for Heterogeneous Systems



Platform-based Design

The ideas of Metropolis are based in part on the concept of platform-based design. Platform-based design is defined as design that moves from the application space to the architectural space by using a common semantic articulation point refered to as the system platform. This view is consistent with top-down, bottom-up, and the meet-in-the-middle methodologies that we advocate.

Examples of platform based design include:
  1. Software running on a CPU
    • Application Space: C-code
    • System Platform: Instruction Set Architecture / Compiled Object Code
    • Architectural Space: Microarchitectural Implementation of ISA
  2. Hardware represented as gates
    • Application Space: RTL-code
    • System Platform: Boolean Netlist
    • Architectural Space:  Technology Dependant synthesized hardware
platform


Click here for papers on platform based design

Functionality

The behavior of the system is expressed as the composition of functional processes communicating through media. These only represent the system's behavior, and don't express any of the implementation decisions.

Architecture

The architecture is made up of elements that will physically realize the functionality. These elements can be thought of as containers that support a variety of behaviors for given costs (e.g. time, power, area). The architectural elements support different types of functionality, but do not specify which ones will be used or when. Examples of architectural elements include: hardware, microprocessors, dsp's, memories, buses, and reconfigurable logic.

Mapping

Mapping consists of associating the functional behaviors with the appropriate architectural containers. This is realized by a mapping netlist that contains the functional netlist, the architectural netlist, and corresponding synchronization and scheduling between the two.

Specific Platform Instances in Metropolis

YAPI/TTL
FTDF
Moore/Mealy Machines
Synchronous Data Flow
Analog Platforms

 
You are not logged in 
Contact 
©2002-2017 U.C. Regents