Proceedings Twelfth International Conference on VLSI Design. (Cat. No.PR00013) 1999
DOI: 10.1109/icvd.1999.745170
|View full text |Cite
|
Sign up to set email alerts
|

Formal system design based on the synchrony hypothesis, functional models, and skeletons

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2001
2001
2020
2020

Publication Types

Select...
3
2
2

Relationship

2
5

Authors

Journals

citations
Cited by 11 publications
(3 citation statements)
references
References 15 publications
0
3
0
Order By: Relevance
“…Aiming the elevation of model abstraction level, and still based on formal design methods, formal systems design (ForSyDe) was first presented in 1999 [19] as a methodology based on a purely functional language, Haskell, and on the perfect synchrony hypothesis, thus supporting only synchronous MoC at first. Its main modeling and simulation tool is the ForSyDe-Shallow, implemented as a Haskell embedded domain specific language (EDSL).…”
Section: Formal System Design (Forsyde)mentioning
confidence: 99%
“…Aiming the elevation of model abstraction level, and still based on formal design methods, formal systems design (ForSyDe) was first presented in 1999 [19] as a methodology based on a purely functional language, Haskell, and on the perfect synchrony hypothesis, thus supporting only synchronous MoC at first. Its main modeling and simulation tool is the ForSyDe-Shallow, implemented as a Haskell embedded domain specific language (EDSL).…”
Section: Formal System Design (Forsyde)mentioning
confidence: 99%
“…Thus, the implementation of signals, process constructors, domain interfaces, and is straightforward and allows us to express ForSyDe models in a clean way with minimal effort. For examples of ForSyDe expressed in Haskell, see [44].…”
Section: Modeling Languagementioning
confidence: 99%
“…Starting with an unconstrained system model of an ATM Switch with operation and maintenance functionality [15,16] (Fig. 7), we illustrate the design exploration process, which includes data type exploration and architecture exploration.…”
Section: Design Space Explorationmentioning
confidence: 99%