Difference between revisions of "Old Name of the new project"
| Line 1: | Line 1: | ||
{{StudentProjectTemplate | {{StudentProjectTemplate | ||
| − | |Summary= | + | |Summary=Mobile Acumen |
|Programme=EIS Masters 15hpc | |Programme=EIS Masters 15hpc | ||
|Keywords=Smart homes, pervasive computing, DiaSuite | |Keywords=Smart homes, pervasive computing, DiaSuite | ||
| Line 8: | Line 8: | ||
|Supervisor=Walid Taha | |Supervisor=Walid Taha | ||
|Examiner=Mohammad Reza Mousavi | |Examiner=Mohammad Reza Mousavi | ||
| − | |Level= | + | |Level=Master |
|Status=Open | |Status=Open | ||
}} | }} | ||
| − | The core research question is to whether | + | The core research question is to whether we can improve the performance of Acumen to serve as a programming language for Mobile device applications. |
| − | This project will be aligned with | + | This project will be aligned with efforts to explore the use of Acumen in primary school education. |
| − | The research question | + | The research question is primarily about the feasibility of using a compiler to attain performance sufficient for building useful Mobile device applications using Acumen. |
| − | The first component of the work is | + | The first component of the work is build a prototype compiler. This involves first selecting a series of more sophisticated examples that illustrate key features of Acumen. Next, corresponding "generated" C or Java code is written by hand and tested extensively. Then, a BNF for a sufficient subset of C or Java is defined in Scala. Next, an interpreter is written for this subset (to enable fast testing of the translator). Then, a translator that automates this translation is written. Then, property-based tests are built for this interpreter. Next, a pretty-printer that generates an ASCII file for compilation on the target domain is built, and all collected examples are used to generate this translation. Finally, a collection of performance benchmarks are developed and used to evaluate the performance of the results of the compiler. |
| − | The second component is to identify a | + | The second component is to identify related work about domain-specific languages and portable mobile app development and read it and write a coherent overview of this literature, and position the results in the context of this literature. |
| − | The | + | The thrid component is writing up the results of the work. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
References: | References: | ||
| − | * https:// | + | * https://pdfs.semanticscholar.org/17ca/d7d6aef48805c1ab0eced0e9d64895fa3f89.pdf |
| − | * | + | * http://nlytn.me/archives/2014/08/26/114 |
| − | + | * http://ieeexplore.ieee.org/abstract/document/7483269/ | |
| − | * http://ieeexplore.ieee.org/ | + | * http://gemoc.org/20130702-GlobalDSL13/xmob.pdf |
| − | * http:// | + | |
Revision as of 21:33, 8 November 2016
| Title | Old Name of the new project |
|---|---|
| Summary | Mobile Acumen |
| Keywords | Smart homes, pervasive computing, DiaSuite |
| TimeFrame | 6 months |
| References | Contact instructor |
| Prerequisites | DA8003 Cyber-Physical Systems |
| Author | |
| Supervisor | Walid Taha |
| Level | Master |
| Status | Open |
The core research question is to whether we can improve the performance of Acumen to serve as a programming language for Mobile device applications.
This project will be aligned with efforts to explore the use of Acumen in primary school education.
The research question is primarily about the feasibility of using a compiler to attain performance sufficient for building useful Mobile device applications using Acumen.
The first component of the work is build a prototype compiler. This involves first selecting a series of more sophisticated examples that illustrate key features of Acumen. Next, corresponding "generated" C or Java code is written by hand and tested extensively. Then, a BNF for a sufficient subset of C or Java is defined in Scala. Next, an interpreter is written for this subset (to enable fast testing of the translator). Then, a translator that automates this translation is written. Then, property-based tests are built for this interpreter. Next, a pretty-printer that generates an ASCII file for compilation on the target domain is built, and all collected examples are used to generate this translation. Finally, a collection of performance benchmarks are developed and used to evaluate the performance of the results of the compiler.
The second component is to identify related work about domain-specific languages and portable mobile app development and read it and write a coherent overview of this literature, and position the results in the context of this literature.
The thrid component is writing up the results of the work.
References:
