Back-end manager: an interface between a knowledge-based front end and its application subsystems

Prat, Albert; Lorés, Jesús; Fletcher, P. Thomas; Catot, Josep M.

doi:10.1016/0950-7051(90)90100-v

Cited by 12 publications

(3 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When discussing the proportion of an application's code dedicated to the UI, Edmonds points out "size is not the problem, although duplicating application code within the interface would be, of course" [2]. Researchers building end-to-end applications, as opposed to just UI tools, also have experiences that "do not support [the principle of] a high degree of separation between the UI and the application" [16] and realise that "the [back-end] requires a considerable amount of knowledge [much of which is] similar to that required by the [UI] modules" [17].…”

Section: Introductionmentioning

confidence: 99%

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

Kennard

Edmonds

Leaney

2009

2009 2nd Conference on Human System Interactions

View full text Add to dashboard Cite

The evolution of User Interface (UI) tools has generally regarded the UI as separable from the underlying application it represents. This viewpoint leaves the UI having to restate invariants already specified in other subsystems of an application, and any discrepancy between the versions in the UI and those in the subsystems leads to errors. This paper explores a sample of real world subsystems in use by enterprise applications today, and underscores the problem of duplication between them and the UI. It then surveys the prevalence of this issue within mainstream software development.

show abstract

Section: Introductionmentioning

confidence: 99%

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

Kennard

Edmonds

Leaney

2009

2009 2nd Conference on Human System Interactions

View full text Add to dashboard Cite

show abstract

“…The BEM module consisted of a variety of tools that would make the composition easier. These typically included tools for the definition of input, extraction and manipulation of output in suitable forms (see for example Prat et al [80]), and a data manager (DM) that stored and managed data from one or more back-ends (for example see [98]).…”

Section: An Overview Of Focusmentioning

confidence: 99%

“…We assume that the expression language of GLIMPSE tasks is not supported fully, only basic GLIM expressions are allowed. Also for simplicity, we assume that a Back-End Manager (BEM) [80] component is available to allow the GLIM package to communicate in the same language with the rest of the system components.…”

Section: The Design Of Last Using Gamesmentioning

confidence: 99%

Game-Based Development of Interactive Systems

Σταθησ¹

View full text Add to dashboard Cite

We study the use of games as a metaphor for building complex interactive systems from simple components, with particular attention to the provision of Knowledge-Based Front-Ends (KBFEs) to software packages. Interaction is viewed as a rule governed activity which may be usefully regarded as a game. Given a specification of the rules, implementation of the interactive system requires the construction of an umpire, a component that enforces compliance of the players with the rules and thereby controls the interaction. Advice giving components added to the system are analogous to games played in the presence of an advisor who recommends moves to the participants.We also use games to develop complex interactive systems from interactive components. In this context, we investigate how to customise existing games by studying how to expand and filter their moves. More generally, we examine how to develop compound games built up from simpler sub-games; coordination of moves chosen from sub-games is then a key issue. This is resolved by treating sub-games as active components that communicate the results of interactions from sub-games to the more complex games. This leads to a general approach of building complex interactive systems from existing components, in such a way that the overall coordination of the interactive system is supported by using only information about the interfaces between components, without regard to their internal structure.

show abstract