Separation anxiety: Stresses of developing a modern day separable User Interface

Kennard, Richard; Edmonds, Ernest; Leaney, John

doi:10.1109/hsi.2009.5090983

Cited by 17 publications

(17 citation statements)

References 16 publications

(16 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition, MDA for SOA usually uses special languages with the better focus on services, service providers, etc., and lacks the support of business rules [24]. Unfortunately, the business rules with their cross-cutting nature are difficult to encapsulate in object-oriented techniques such as MDA [25]. Although there are options such as OCL to extend the models, but they are still unable to encapsulate and reuse repeated rules, they restate them manually instead [18].…”

Section: Business Rules Representation and Compositionmentioning

confidence: 99%

Aspect-driven Context-aware Services

Cemus

Klimes

Černý

2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Nowadays enterprise software solutions must deal with ever-growing complexity and a multitude of business processes. The mainstream system design decomposes the system into small reusable services. While these services isolate certain system logic and address efficient elasticity towards growing user demands, there are multiple issues related to such a design, such as limitations to deal with restated information, information reuse or the ability to address cross-cutting concerns across multiple services. This paper highlights limitations of service-oriented architecture and proposes an alternative decomposition through aspect-driven service-oriented architecture. Such architecture involves adaptive, context-aware services preserving simple maintenance while addressing information reuse and crosscuts across services. The paper provides a formal description of the proposed architecture as well as a demonstration through a case study, showing approach properties and benefits.

show abstract

Section: Business Rules Representation and Compositionmentioning

confidence: 99%

Aspect-driven Context-aware Services

Cemus

Klimes

Černý

2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

show abstract

“…Another approach addresses information restatement by utilizing code-inspection and meta-programming [18], [5], [24]. It inspects data GPL definitions and from the result composes a structural model.…”

Section: A Ui Design Approachesmentioning

confidence: 99%

“…It is transformed to the target UI language, such as HTML. DSLs naturally fit to UI descriptions, but through their weak type-safety, it is easy to introduce errors related to restated information from lower application layers [18]. For example a DSL description may reference data, their fields and constraints that are already described in the application through GPL [12]; however, referencing a GPL component from DSL requires certain restatement with a negative impact on maintenance.…”

Section: A Ui Design Approachesmentioning

confidence: 99%

“…Providing UI for given data in two slightly different situations (e.g., normal and mobile version of a website) may require to implement two similar UI components that differ only in details [5], [24], but requiring their separate maintenance. The UI development efforts are apparent from research [5], [18], which shows that approximately 48% of application code and 50% of development time is devoted to implementing UIs. This percentage grows with UI abilities and context-specificity.…”

Section: Introductionmentioning

confidence: 99%

“…For example, the UI descriptions for data presentations must restate information [18] from lower layers of the application, in order to extend them. This brings the risk of mistype errors caused by inconsistencies.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Efficient Description and Cache Performance in Aspect-Oriented User Interface Design

Černý¹,

Macík

Donahoo

et al. 2014

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Increasing demands on web user interface (UI) usability, adaptability, and dynamic behavior drives ever growing development and maintenance complexity. Conventional design approaches scale poorly with such rising complexity, resulting in rapidly increasing costs. Much of the complexity centers around data presentation and processing. Recent work greatly reduces such data complexity through the application of AspectOriented UI (AOUI) design, which separates various UI concerns; however, rendering in conventional and even AOUI approaches fails to maintain this separation, often resulting in high repetitions of concern fragments due to tangling. Even worse, mixing of dynamic and immutable components greatly limits caching efficacy as each have differing lifetimes. We extend AOUI design to push down concern separation to rendering, which reduces description size, through repetition reduction, and enables separate caching of individual concerns. Our results show considerable size reduction of UI descriptions for data presentations, faster load times and extended caching capabilities.

show abstract