diff --git a/main.typ b/main.typ index 4a7efa8..76edf3b 100644 --- a/main.typ +++ b/main.typ @@ -45,15 +45,15 @@ todo todo = Methodology -This publication was created following the process described in @process_fig. The protocol for the review is divided up into the object of the research see @research_questions_s, the search strategy see @sas_s, the selection criteria see @selection_criteria_s and the data extraction strategy see @data_extraction_s. +This publication is created following the process described in @process_fig. The protocol for the review is divided up into the object of the research see @research_questions_s, the search strategy see @sas_s, the selection criteria see @selection_criteria_s and the data extraction strategy see @data_extraction_s. #place( bottom + center, scope: "parent", float: true, [ #figure( - caption: [Overview of the review process], - image("review_process.svg") + caption: [Overview of the review process. Adapted from @ciccozzi_execution_2019 and @gotz_claimed_2021.], + image("review_process.png") ) ] ) @@ -65,28 +65,33 @@ This goal has been defined in two research questions: This questions aims to identify which advantages DFA has over other optimization techniques and which disadvantages it has when used. - RQ2 --- How is dataflow analysis used in current compilers? \ - This questions aims to identify how DFA is already used in current compilers and if it is used during normal compilation or if it has to be explicitly enabled. + This questions aims to identify how DFA is already used in current compilers, what optimizations are done with it and if it is used during normal compilation or if it has to be explicitly enabled. == Search and selection strategy -My search strategy consisted of 4 steps as seen in @sas_fig. \ +Our search strategy consisted of 4 steps as seen in @sas_fig. \ #figure( caption: [Search string used in electronic databases], kind: "raw", align(left)[ + // ("dataflow analysis" OR "data flow analysis") AND (compiler OR compilers OR compilation) AND (optimization OR optimizations) AND (advantages OR disadvantages OR strengths OR limitations OR trade-offs) AND (implementation OR usage OR used OR applied) + // ("Full Text .AND. Metadata":"dataflow analysis" OR "Full Text .AND. Metadata":"data flow analysis") AND ("Full Text .AND. Metadata":compiler OR "Full Text .AND. Metadata":compilers OR "Full Text .AND. Metadata":compilation) AND ("Full Text .AND. Metadata":optimization OR "Full Text .AND. Metadata":optimizations) AND ("Full Text .AND. Metadata":advantages OR "Full Text .AND. Metadata":disadvantages OR "Full Text .AND. Metadata":strengths OR "Full Text .AND. Metadata":limitations OR "Full Text .AND. Metadata":trade-offs) AND ("Full Text .AND. Metadata":implementation OR "Full Text .AND. Metadata":usage OR "Full Text .AND. Metadata":used OR "Full Text .AND. Metadata":applied) #set raw(syntaxes: "search-string.sublime-syntax", theme: "search-string.tmTheme") + // AND ("compiler optimization" OR "compilation optimization" OR "compiler optimizations" OR "compilation optimizations" OR "optimizing compiler" OR "optimizing compilers") ```SearchString - dfa OR (dataflow AND analysis) - AND (compiler* OR compilation) - AND (optimiz*) + ("dataflow analysis" OR "data flow analysis") + AND (compiler OR compilers OR compilation) + AND (optimization OR optimizations) + AND (advantages OR disadvantages OR strengths OR limitations OR trade-offs) + AND (implementation OR usage OR used OR applied) ``` ] ) -The papers from the first steps are collected from the electronic databases ACM Digital Library, IEEE Xplore, Springer Link, Web of Science with the search string seen in @sas_search_string. +The papers from the first steps are collected from the electronic databases ACM Digital Library, IEEE Xplore, Springer Link with the search string seen in @sas_search_string. The search string in @sas_search_string was created using the research questions in @research_questions_s and was always applied to the full text of the papers. \ In the second step all duplicates which where returned from multiple databases where removed from the results. \ In the third step the selection was filtered by applying all selection criteria from @selection_criteria_s. \ -In the forth step I snowballed the previously acquired results. This was to find relevant papers which where not included because of either the search string or the search criteria. \ -Afterwards all papers where evaluated based on the data extraction items mentioned in @data_extraction_s. +In the fourth step I snowballed the previously acquired results. This was to find relevant papers which where not included because of either the search string or the search criteria. \ +Afterwards all papers of the snowballing where evaluated based on the data extraction items mentioned in @data_extraction_s. #place( auto, scope: "parent", @@ -105,16 +110,14 @@ Afterwards all papers where evaluated based on the data extraction items mention rect((0, 0), (rel: bs), name: "acm") rect((0, -(bs.at(1)+0.3)*1), (rel: bs), name: "ieee") rect((0, -(bs.at(1)+0.3)*2), (rel: bs), name: "springer") - rect((0, -(bs.at(1)+0.3)*3), (rel: bs), name: "websci") - rect((bs.at(0)+1.5, -(bs.at(1)*1.5+0.45)), (rel: bs), name: "dup") - rect((bs.at(0)*2+2.25, -(bs.at(1)*1.5+0.45)), (rel: bs), name: "sel") - rect((bs.at(0)*3+3, -(bs.at(1)*1.5+0.45)), (rel: bs), name: "snow") - rect((bs.at(0)*4+3.75, -(bs.at(1)*1.5+0.45)), (rel: bs), name: "inc") + rect((bs.at(0)+1.5, -(bs.at(1)+0.3)), (rel: bs), name: "dup") + rect((bs.at(0)*2+2.25, -(bs.at(1)+0.3)), (rel: bs), name: "sel") + rect((bs.at(0)*3+3, -(bs.at(1)+0.3)), (rel: bs), name: "snow") + rect((bs.at(0)*4+3.75, -(bs.at(1)+0.3)), (rel: bs), name: "inc") line("acm.east", (rel: (0.75, 0)), name: "dlu") line("ieee.east", (rel: (0.75, 0))) - line("springer.east", (rel: (0.75, 0))) - line("websci.east", (rel: (0.75, 0)), name: "dld") + line("springer.east", (rel: (0.75, 0)), name: "dld") line("dlu.end", "dld.end", name: "dl") set-style(mark: (end: "straight")) @@ -124,9 +127,8 @@ Afterwards all papers where evaluated based on the data extraction items mention line("snow.east", "inc.west") content("acm", align(center)[ACM Digital Library \ n = ]) - content("ieee", align(center)[IEEExplore \ n = ]) + content("ieee", align(center)[IEEE Xplore \ n = ]) content("springer", align(center)[Springer Link \ n = ]) - content("websci", align(center)[Web of Science \ n = ]) content("dup", align(center)[Duplicate removal \ n = ]) content("sel", align(center)[Application of \ selection criteria \ n = ]) content("snow", align(center)[Snowballing \ n = ]) @@ -141,29 +143,31 @@ For a publication to be relevant it has to satisfy at least one inclusion criter #[ #v(10pt) #set enum(numbering: (.., i) => "IC" + str(i)) - + Publications comparing DFA to other optimization techniques - + Publications focusing on a specific compiler (e.g., LLVM, Java JIT, C\# JIT) - + Publications providing an implementation for a DFA optimization + + Publications discussing advantages and disadvantages of DFA compared to other optimization techniques. + + Publications focusing on one or more compilers (e.g., LLVM, Java JIT, C\# JIT). + + Publications providing an implementation for a DFA optimization. #v(10pt) ] -_IC1_ was chosen to help answer _RQ1_. \ +We chose _IC1_ to help answer _RQ1_. \ _IC2_ is to include publications which talk about a compiler and how DFA is implemented in it. \ -_IC3_ is to further include publications which directly provide an implementation +_IC3_ is to further include publications which directly provide an implementation. #[ #v(10pt) #set enum(numbering: (.., i) => "EC" + str(i)) - + Publications which discuss DFA in a non-compiler context - + Publications written in a language other than english - + Secondary and tertiary publications (e.g., systematic literaturer reviews, surveys) - + Publications in the form of tutorial papers, short papers, poster papers, editorials - + Publications for which the full text is not available + + Publications which discuss DFA in a non-compiler context. + + Publications written in a language other than english. + + Secondary and tertiary publications (e.g., systematic literaturer reviews, surveys). + + Publications in the form of tutorial papers, short papers, poster papers, editorials. + + Publications for which the full text is not available. + + Publications published before 2010. #v(10pt) ] _EC1_ is to exclude publications which talk about DFA in other contexts which are not relevant to compiler optimization. \ -_EC2-EC5_ are to exclude publications which don't provide enough information to include them in this publication. +_EC2-EC5_ are to exclude publications which do not provide enough information to include them in this publication. \ +_EC6_ is to make sure the publications are still relevant. == Data extraction -Based on the research questions I wrote 9 data items to exrtract from all included publications. @data_extraction_table lists all data items. \ +Based on the research questions I collected 9 data items to exrtract from all included publications. @data_extraction_table lists all data items. \ Data items _D1-D3_ are to document the source of the publication. \ _D4_ and _D5_ are to explicitly list the advantages and disadvantages for answering _RQ1_. \ _D6_ and _D7_ show in which compiler DFA was implemented and if it is running directly on a programming language like C++ or if it runs on a intermediate language like LLVM IR. \ @@ -203,8 +207,7 @@ All data items were extracted from the full text of all included publications. #colbreak() #set heading(numbering: none) -= References -#bibliography("refs.bib", title: none, style: "association-for-computing-machinery") +#bibliography("refs.bib", title: "References", style: "association-for-computing-machinery") /* #colbreak(weak: true) diff --git a/refs.bib b/refs.bib index c862e98..5bb4e29 100644 --- a/refs.bib +++ b/refs.bib @@ -1,19 +1,36 @@ -@article{netwok2020, - title={At-scale impact of the {Net Wok}: A culinarically holistic investigation of distributed dumplings}, - author={Astley, Rick and Morris, Linda}, - journal={Armenian Journal of Proceedings}, - volume={61}, - pages={192--219}, - year=2020, - publisher={Automatic Publishing Inc.} + +@article{ciccozzi_execution_2019, + title = {Execution of {UML} models: a systematic review of research and practice}, + volume = {18}, + issn = {1619-1366, 1619-1374}, + shorttitle = {Execution of {UML} models}, + url = {http://link.springer.com/10.1007/s10270-018-0675-4}, + doi = {10.1007/s10270-018-0675-4}, + abstract = {Several research efforts from different areas have focused on the execution of UML models, resulting in a diverse and complex scientific body of knowledge. With this work, we aim at identifying, classifying, and evaluating existing solutions for the execution of UML models. We conducted a systematic review in which we selected 63 research studies and 19 tools among over 5400 entries by applying a systematic search and selection process. We defined a classification framework for characterizing solutions for UML model execution, and we applied it to the 82 selected entries. Finally, we analyzed and discussed the obtained data. From the analyzed data, we drew the following conclusions: (i) There is a growing scientific interest on UML model execution; (ii) solutions providing translational execution clearly outnumber interpretive solutions; (iii) model-level debugging is supported in very few cases; (iv) only a few research studies provide evidence of industrial use, with very limited empirical evaluations; (v) the most common limitation deals with coverage of the UML language. Based on these observations, we discuss potential research challenges and implications for the future of UML model execution. Our results provide a concise overview of states of the art and practice for UML model execution intended for use by both researchers and practitioners.}, + language = {en}, + number = {3}, + urldate = {2025-05-22}, + journal = {Software \& Systems Modeling}, + author = {Ciccozzi, Federico and Malavolta, Ivano and Selic, Bran}, + month = jun, + year = {2019}, + pages = {2313--2360}, } -@article{netwok2022, - title={{Net Wok}++: Taking distributed dumplings to the cloud}, - author={Morris, Linda and Astley, Rick}, - journal={Armenian Journal of Proceedings}, - volume={65}, - pages={101--118}, - year=2022, - publisher={Automatic Publishing Inc.} +@article{gotz_claimed_2021, + title = {Claimed advantages and disadvantages of (dedicated) model transformation languages: a systematic literature review}, + volume = {20}, + issn = {1619-1366, 1619-1374}, + shorttitle = {Claimed advantages and disadvantages of (dedicated) model transformation languages}, + url = {https://link.springer.com/10.1007/s10270-020-00815-4}, + doi = {10.1007/s10270-020-00815-4}, + abstract = {There exists a plethora of claims about the advantages and disadvantages of model transformation languages compared to general-purpose programming languages. With this work, we aim to create an overview over these claims in the literature and systematize evidence thereof. For this purpose, we conducted a systematic literature review by following a systematic process for searching and selecting relevant publications and extracting data. We selected a total of 58 publications, categorized claims about model transformation languages into 14 separate groups and conceived a representation to track claims and evidence through the literature. From our results, we conclude that: (i) the current literature claims many advantages of model transformation languages but also points towards certain deficits and (ii) there is insufficient evidence for claimed advantages and disadvantages and (iii) there is a lack of research interest into the verification of claims.}, + language = {en}, + number = {2}, + urldate = {2025-05-22}, + journal = {Software and Systems Modeling}, + author = {Götz, Stefan and Tichy, Matthias and Groner, Raffaela}, + month = apr, + year = {2021}, + pages = {469--503}, } diff --git a/review_process.png b/review_process.png new file mode 100644 index 0000000..c9ae091 Binary files /dev/null and b/review_process.png differ diff --git a/review_process.svg b/review_process.svg deleted file mode 100644 index 5d21abe..0000000 --- a/review_process.svg +++ /dev/null @@ -1,3 +0,0 @@ - - -
Planning
Planning
Research
questions
Research...
Protocol
Protocol
Review need
identification
Review need...
Research questions
definition
Research questions...
Protocol
definition
Protocol...
Protocol
evaluation
Protocol...
Conducting
Conducting
Database
search
Database...
Selection
review
Selection...
Snowballing
Snowballing
Data extraction
Data extraction
Data
synthesis
Data...
Set of
publications
Set of...
Relevant publications
Relevant pub...
Data
items
Data...
Reporting
Reporting
Final report
Final report
Threats analysis
Threats analysis
Report writing
Report writing
Report evaluation
Report evaluation
Activity
Activity
Artifact
Artifact
Activity Flow
Activity Flow
Artifact Flow
Artifact Flow \ No newline at end of file