FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2611116631> ?p ?o ?g. }

• W2611116631 abstract "Abstract—The proliferation of multi- and manycores createsan important design problem: the design and verification formixed-criticality constraints in timing and safety, taking intoaccount the resource sharing and hardware faults. In our work,we aim to contribute towards the solution of these problems byusing a formal design language – the real time BIP, to modelboth hardware and software, functionality and scheduling. Inthis paper we present the initial experiments of modeling mixed-criticality systems in BIP. I. I NTRODUCTION The introduction of many-cores and multi-cores is leadingto an increasing trend in embedded systems towards imple-menting multiple subsystems upon a single shared platform.However, in most applications, not all the subsystems areequally critical. Especially this observation is important whenhuman lives depend on correct functionality, e.g. in avionicssystems. In mixed criticality systems different degrees offailures, from minor, hazardous to major, need to be distin-guished [1]. The previous work mostly assumes time or spaceisolation of subsystems having different levels of criticality.However, when integrating different subsystems on a singlemulti-core die there is a need to share hardware resources (pro-cessors, on-chip memory, and global interconnect) betweendifferent subsystems. Also, handling safely the hardware fail-ure is another design problem, that will only increase as multi-core will become more and more commonplace. This problemalready manifested itself in popular many-core systems – theGPUs – so it is relatively well studied how to manage theresource sharing and safety when all subsystems have thesame level of criticality. However, adding the mixed criticalityassumption may easily boost the complexity from tractable tointractable [2], and a general lack of design methodology canbe stated.A popular language for programming safety-critical sys-tems is Ada, and a great interest exists today to expressmulti-core and especially mixed-critical applications in thislanguage [3], [4]. However, for verification of safety properties(i.e., automatic check for absence of bugs), any program hasto be translated to a formal model, which is a non-trivial taskeven for Ada, which was designed to facilitate an easier staticanalysis of code [5]. Formalization is required not only foranalysis of safety properties, but also for timing [6]. Formalmodels play important role in the analysis of hardware faultsand fault correction [7] and of the shared resource conflictsin multicores [8]. Therefore in our mixed-criticality project" @default.
• W2611116631 created "2017-05-12" @default.
• W2611116631 creator A5007058417 @default.
• W2611116631 creator A5020750660 @default.
• W2611116631 creator A5039081580 @default.
• W2611116631 creator A5050964783 @default.
• W2611116631 creator A5069785845 @default.
• W2611116631 date "2013-08-21" @default.
• W2611116631 modified "2023-09-26" @default.
• W2611116631 title "Modeling Mixed-critical Systems in Real-time BIP" @default.
• W2611116631 cites W1483587293 @default.
• W2611116631 cites W1491546977 @default.
• W2611116631 cites W1544921803 @default.
• W2611116631 cites W1578262153 @default.
• W2611116631 cites W1972097705 @default.
• W2611116631 cites W1994680589 @default.
• W2611116631 cites W2005353733 @default.
• W2611116631 cites W2009253638 @default.
• W2611116631 cites W2018263494 @default.
• W2611116631 cites W2048903680 @default.
• W2611116631 cites W2069892106 @default.
• W2611116631 cites W2078000719 @default.
• W2611116631 cites W2087090692 @default.
• W2611116631 cites W2098436411 @default.
• W2611116631 cites W2116514438 @default.
• W2611116631 cites W2122316816 @default.
• W2611116631 cites W2125415493 @default.
• W2611116631 cites W2146412113 @default.
• W2611116631 cites W2170064878 @default.
• W2611116631 cites W2216355539 @default.
• W2611116631 cites W2255529110 @default.
• W2611116631 cites W2536456289 @default.
• W2611116631 cites W59365162 @default.
• W2611116631 hasPublicationYear "2013" @default.
• W2611116631 type Work @default.
• W2611116631 sameAs 2611116631 @default.
• W2611116631 citedByCount "2" @default.
• W2611116631 countsByYear W26111166312014 @default.
• W2611116631 countsByYear W26111166312015 @default.
• W2611116631 crossrefType "proceedings-article" @default.
• W2611116631 hasAuthorship W2611116631A5007058417 @default.
• W2611116631 hasAuthorship W2611116631A5020750660 @default.
• W2611116631 hasAuthorship W2611116631A5039081580 @default.
• W2611116631 hasAuthorship W2611116631A5050964783 @default.
• W2611116631 hasAuthorship W2611116631A5069785845 @default.
• W2611116631 hasBestOaLocation W26111166311 @default.
• W2611116631 hasConcept C41008148 @default.
• W2611116631 hasConceptScore W2611116631C41008148 @default.
• W2611116631 hasLocation W26111166311 @default.
• W2611116631 hasLocation W26111166312 @default.
• W2611116631 hasLocation W26111166313 @default.
• W2611116631 hasOpenAccess W2611116631 @default.
• W2611116631 hasPrimaryLocation W26111166311 @default.
• W2611116631 hasRelatedWork W2130043461 @default.
• W2611116631 hasRelatedWork W2350741829 @default.
• W2611116631 hasRelatedWork W2358668433 @default.
• W2611116631 hasRelatedWork W2376932109 @default.
• W2611116631 hasRelatedWork W2382290278 @default.
• W2611116631 hasRelatedWork W2390279801 @default.
• W2611116631 hasRelatedWork W2748952813 @default.
• W2611116631 hasRelatedWork W2899084033 @default.
• W2611116631 hasRelatedWork W3004735627 @default.
• W2611116631 hasRelatedWork W2530322880 @default.
• W2611116631 isParatext "false" @default.
• W2611116631 isRetracted "false" @default.
• W2611116631 magId "2611116631" @default.
• W2611116631 workType "article" @default.