VPs and gem5
This commit is contained in:
26
src/doc.bib
26
src/doc.bib
@@ -5,6 +5,20 @@
|
||||
file = {/home/derek/Nextcloud/Verschiedenes/Zotero/storage/N5Y7EZNT/2021 - Changing Exception level and Security state in an .pdf}
|
||||
}
|
||||
|
||||
@inproceedings{antonino2018,
|
||||
title = {Enabling {{Continuous Software Engineering}} for {{Embedded Systems Architectures}} with {{Virtual Prototypes}}},
|
||||
booktitle = {Software {{Architecture}}},
|
||||
author = {Antonino, Pablo Oliveira and Jung, Matthias and Morgenstern, Andreas and Faßnacht, Florian and Bauer, Thomas and Bachorek, Adam and Kuhn, Thomas and Nakagawa, Elisa Yumi},
|
||||
editor = {Cuesta, Carlos E. and Garlan, David and Pérez, Jennifer},
|
||||
date = {2018},
|
||||
pages = {115--130},
|
||||
publisher = {{Springer International Publishing}},
|
||||
location = {{Cham}},
|
||||
abstract = {Continuous software engineering aims at orchestrating engineering knowledge from various disciplines in order to deal with the rapid changes within the ecosystems of which software-based systems are part of. The literature claims that one means to ensure these prompt responses is to incorporate virtual prototypes of the system as early as possible in the development process, such that requirements and architecture decisions are verified early and continuously by means of simulations. Despite the maturity of practices for designing and assessing architectures, as well as for virtual prototyping, it is still not clear how to jointly consider the practices from these disciplines within development processes, in order to address the dynamics imposed by continuous software engineering. In this regard, we discuss in this paper how to orchestrate architecture drivers and design specification techniques with virtual prototypes, to address the demands of continuous software engineering in development processes. Our proposals are based on experiences from research and industry projects in various domains such as automotive, agriculture, construction, and medical devices.},
|
||||
isbn = {978-3-030-00761-4},
|
||||
file = {/home/derek/Nextcloud/Verschiedenes/Zotero/storage/KGD8N29E/Antonino et al. - 2018 - Enabling Continuous Software Engineering for Embed.pdf}
|
||||
}
|
||||
|
||||
@article{arm2015,
|
||||
title = {{{ARM Cortex-A Series Programmer}}’s {{Guide}} for {{ARMv8-A}}},
|
||||
author = {{ARM}},
|
||||
@@ -503,6 +517,18 @@
|
||||
file = {/home/derek/Nextcloud/Verschiedenes/Zotero/storage/SWBFKXLG/Sudarshan et al. - 2022 - A Weighted Current Summation Based Mixed Signal DR.pdf}
|
||||
}
|
||||
|
||||
@book{systemc2023,
|
||||
title = {1666-2023 - {{IEEE Standard}} for {{Standard SystemC Language Reference Manual}}},
|
||||
date = {2023},
|
||||
publisher = {{IEEE}},
|
||||
location = {{New York}},
|
||||
abstract = {SystemC® is defined in this standard. SystemC is an ISO standard C++ class library for system and hardware design for use by designers and architects who need to address complex systems that are a hybrid between hardware and software. This standard provides a precise and complete definition of the SystemC class library so that a SystemC implementation can be developed with reference to this standard alone. The primary audiences for this standard are the implementors of the SystemC class library, the implementors of tools supporting the class library, and the users of the class library},
|
||||
isbn = {978-1-5044-9867-8},
|
||||
langid = {english},
|
||||
annotation = {OCLC: 1397698694},
|
||||
file = {/home/derek/Nextcloud/Verschiedenes/Zotero/storage/46IIZIMH/2023 - 1666-2023 - IEEE Standard for Standard SystemC Lan.pdf}
|
||||
}
|
||||
|
||||
@online{touvron2023,
|
||||
title = {{{LLaMA}}: {{Open}} and {{Efficient Foundation Language Models}}},
|
||||
shorttitle = {{{LLaMA}}},
|
||||
|
||||
Reference in New Issue
Block a user