2009
DOI: 10.1145/1455229.1455232
|View full text |Cite
|
Sign up to set email alerts
|

System-scenario-based design of dynamic embedded systems

Abstract: Document VersionPublisher's PDF, also known as Version of Record (includes final page, issue and volume numbers) Please check the document version of this publication:• A submitted manuscript is the author's version of the article upon submission and before peer-review. There can be important differences between the submitted version and the official published version of record. People interested in the research are advised to contact the author for the final version of the publication, or visit the DOI to the… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
117
0

Year Published

2010
2010
2019
2019

Publication Types

Select...
4
3
2

Relationship

1
8

Authors

Journals

citations
Cited by 131 publications
(117 citation statements)
references
References 68 publications
0
117
0
Order By: Relevance
“…Here, we use the concept of scenario [6,22] to capture the application dynamism on our target MPSoC system. There are two different kinds of scenarios: inter-application scenarios describe the simultaneously running applications in the system, while intra-application scenarios define the different execution modes for each application.…”
Section: Application and Architecture Modelmentioning
confidence: 99%
See 1 more Smart Citation
“…Here, we use the concept of scenario [6,22] to capture the application dynamism on our target MPSoC system. There are two different kinds of scenarios: inter-application scenarios describe the simultaneously running applications in the system, while intra-application scenarios define the different execution modes for each application.…”
Section: Application and Architecture Modelmentioning
confidence: 99%
“…However, these methods typically still suffer from scalability issues when the number of workload scenarios becomes very large as they need to find and store one or more optimal task mappings per scenario at design time (to be used at run time). One solution to address this problem is by reducing the number of workload scenarios by means of clustering [6,27]. However, these methods still suffer from an additional problem of searching for optimal mappings of (clustered) workload scenarios at design time: it should already been known at design time which applications can execute on the target platform.…”
Section: Scalable Run-time Task Mapping In Sharamentioning
confidence: 99%
“…This facilitates to identify all the allowed modes and the transitions between them, and to check the cost of mode switchings. In [5], for H.264 decoder, an average switching time overhead between two modes has been measured to be equal to 0.2% of the total system time. This slight value has been caused due to a low number of existing modes, obtained due to the clustering, and thus relatively lower switching.…”
Section: Related Workmentioning
confidence: 99%
“…The central concept for dealing with dynamic behavior is a scenario [19]. Dynamic behaviors within an application are divided in a limited number of so-called scenarios.…”
Section: Overview Of the Approachmentioning
confidence: 99%