Content deleted Content added
m cleanup (wikitables, html markup, layout, etc.) |
Added alternatives relevant to MDD UI, this is well described at http://www.sigapp.org/acr/Issues/V13.4/ACR-13-4-2013.pdf ACM ACR (page 53) Tag: categories removed |
||
Line 52:
{{main|usage-centered design}}
In usage-centered design, the modeling task is to show how the actual presentation of a planned system and how the user interaction is supposed to happen. This is probably the most praised approach, and it has been used successfully on a variety of small and large-scale projects. Its strengths are in complex problems.
== Alternative approaches to model-based UIs ==
The know issue of model-based approaches is information restatement and lack of mechanisms effectively to solve cross-cutting concerns [Cerny2013]. Model-based solution work well on their own, but integration with alternative approaches bring complexity in development and maintenance efforts.
===Code-inspection based===
These approaches bases on existing general purpose language (GPL) code base [Cerny2012]. They inspect the code through meta-programming and assemble a structural model that is transformed to the UI. This approach addresses information restatement. These approaches does not fit to adaptive and context-aware UIs.
===Generative programming===
These approaches connect ___domain methods with GPL [Generative programming]. They address cross-cutting concerns although only at compile-time, which does not fit to future adaptive UIs that need runtime information.
===Aspect-based UIs===
Aspect-based solution suggested by [Cerny2013][Cerny2013a][AspectFaces] integrates advantages of code-inspection based and generative programming approaches. It inspects existing code and applies aspect oriented methods to address cross-cutting concerns. It works at runtime, reduces information restatement and at the same time separates UI concerns which allows to reuse each independent of others. In the study at [Cerny2013] authors reduce UI code by 32% through aspect=based UI approach applied to a production system. Main advantages are templating for adjusting the presentation, separate definitions of concerns and mostly generic transformation rules applicable across various data.
===Content models===
Line 63 ⟶ 75:
* [Trevisan2003] – D. Trevisan, J. Vanderdonck, B. Macq, Model-Based Approach and Augmented Reality Systems, Université catholique de Louvain, 1348 Louvain-la-Neuve, Belgium, 2003
* [wwwUMLi] – [http://trust.utep.edu/umli The Unified Modeling Language for Interactive Applications]
* [Cerny2013] – Černý, T. - Čemus, K. - Donahoo, M.J. - Song, M.J.: [http://www.sigapp.org/acr/Issues/V13.4/ACR-13-4-2013.pdf Aspect-driven, Data-reflective and Context-aware User Interfaces Design (page 53). In: ACM SIGAPP Applied Computing Review [online], 2013, vol. 13, no. 4, p. 53-65, ISSN 1559-6915.
* [Cerny2013a] – Černý, T. - Donahoo, M.J. - Song, E.: [http://dl.acm.org/citation.cfm?id=2513278 Towards Effective Adaptive User Interfaces Design], Proceedings of the 2013 Research in Applied Computation Symposium (RACS 2013), Montreal: ACM, 2013, ISBN 978-1-4503-2348-2.
* [AspectFaces] – [http://www.aspectfaces.com/overview AspectFaces]
* [Cerny2012] – T. Cerny and E. Song. [http://scholar.google.com/scholar?cluster=12280381045153079495&hl=en Model-driven Rich Form Generation]. Information: An International Interdisciplinary Journal, 15(7, SI):2695--2714, JUL 2012.
* [Generative programming] – Krzysztof Czarnecki and Ulrich W. Eisenecker. 2000. [http://www.amazon.com/Generative-Programming-Methods-Tools-Applications/dp/0201309777 Generative Programming: Methods, Tools, and Applications]. ACM Press/Addison-Wesley Publ. Co., New York, NY, USA.
| |||