User interface modeling: Difference between revisions

Content deleted Content added
m linking
m Alternative approaches to model-based UIs: copyedit for usage and subject-verb agreement
Line 54:
 
== Alternative approaches to model-based UIs ==
The knowknown issueissues of model-based approaches isinclude information restatement and lack of mechanisms to effectively to solve cross-cutting concerns [Cerny2013]. Model-based solutionsolutions can work well on their own, but integration with alternative approaches bringbrings complexity in development and maintenance efforts.
 
===Code-inspection based===
These approaches basesare based on existing general purpose language (GPL) code basebases [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 crossCross-cutting concerns althoughare onlyaddressed at compile-time, which does not fitdirectly toaccomodate future adaptive UIs that needneeding runtime information.
===Aspect-based UIs===
Line 66:
 
===Content models===
Models of this kind show the contents of a user interface and its different components. Aesthetics and behavior details are not included in this kind of modelsmodel as it is ina form of usage-centered design modelsmodel.
 
== See also ==