Modularity vs. Reusability: Code Generation from Synchronous Block Diagrams

DMCA

Modularity vs. Reusability: Code Generation from Synchronous Block Diagrams (2008)

Cached

Download Links

Other Repositories/Bibliography

DBLP

by Roberto Lublinerman

Venue:	In Design, Automation, and Test in Europe (DATE’08). ACM
Citations:	21 - 8 self

BibTeX

@INPROCEEDINGS{Lublinerman08modularityvs.,
    author = {Roberto Lublinerman},
    title = {Modularity vs. Reusability: Code Generation from Synchronous Block Diagrams},
    booktitle = {In Design, Automation, and Test in Europe (DATE’08). ACM},
    year = {2008}
}

OpenURL

Abstract

We present several methods to generate modular code from synchronous hierarchical block diagrams. Modularity means code is generated for a given macro (i.e., composite) block independently from context, that is, without knowing where this block is to be used, and also with minimal knowledge about its sub-blocks. We achieve this by generating a set of interface functions for each block and a set of dependencies between these functions that is exported along with the interface. The main trade-off is the degree of modularity (number of interface functions) vs. reusability (the set of diagrams that the block can be used in without creating dependency cycles). 1

Keyphrases

modularity v synchronous block diagram code generation interface function present several method minimal knowledge modular code dependency cycle main trade-off synchronous hierarchical block diagram

DMCA