Douglas Michael Densmore and Trevor Conrad Meyerowitz and Abhijit Davare and Qi Zhu and Guang Yang

EECS Department, University of California, Berkeley

Technical Report No. UCB/EECS-2008-16

February 18, 2008

http://www2.eecs.berkeley.edu/Pubs/TechRpts/2008/EECS-2008-16.pdf

This document presents three proposals for the execution semantics of mapping in Metro II. Mapping is the relationship between what a system does (functionality) and how it does it (architecture). The main concern is whether the functionality and architecture models should execute concurrently or sequentially during simulation. Proposal #1 presents sequential execution with the functionality being executed before the architecture. Proposal #2 also presents sequential execution, but with the architecture executing before the functionality. Finally, Proposal #3 presents concurrent execution. Processes are present in the architecture to execute simultaneously with the events mapped to them in the functionality.

Each of these three proposals is demonstrated on a set of design scenarios with hand traces illustrating their execution. Additionally general assumptions, glossary terms, and proposal-specific assumptions made regarding the execution semantics are discussed. Finally, the proposals are compared and contrasted, especially regarding how they can properly implement the examples and the general semantic assumptions.

---

BibTeX citation:

@techreport{Densmore:EECS-2008-16,
    Author= {Densmore, Douglas Michael and Meyerowitz, Trevor Conrad and Davare, Abhijit and Zhu, Qi and Yang, Guang},
    Title= {Metro II Execution Semantics for Mapping},
    Year= {2008},
    Month= {Feb},
    Url= {http://www2.eecs.berkeley.edu/Pubs/TechRpts/2008/EECS-2008-16.html},
    Number= {UCB/EECS-2008-16},
    Abstract= {This document presents three proposals for the execution semantics of mapping in Metro II. Mapping is the relationship between what a system does (functionality) and how it does it (architecture). The main concern is whether the functionality and architecture models should execute concurrently or sequentially during simulation. Proposal #1 presents sequential execution with the functionality being executed before the architecture. Proposal #2 also presents sequential execution, but with the architecture executing before the functionality. Finally, Proposal #3 presents concurrent execution. Processes are present in the architecture to execute simultaneously with the events mapped to them in the functionality.

Each of these three proposals is demonstrated on a set of design scenarios with hand traces illustrating their execution. Additionally general assumptions, glossary terms, and proposal-specific assumptions made regarding the execution semantics are discussed. Finally, the proposals are compared and contrasted, especially regarding how they can properly implement the examples and the general semantic assumptions.},
}

EndNote citation:

%0 Report
%A Densmore, Douglas Michael 
%A Meyerowitz, Trevor Conrad 
%A Davare, Abhijit 
%A Zhu, Qi 
%A Yang, Guang 
%T Metro II Execution Semantics for Mapping
%I EECS Department, University of California, Berkeley
%D 2008
%8 February 18
%@ UCB/EECS-2008-16
%U http://www2.eecs.berkeley.edu/Pubs/TechRpts/2008/EECS-2008-16.html
%F Densmore:EECS-2008-16