Situation Specification and Realization in Rule-Based Context-Aware Applications

Abstract

Abstract. Context-aware applications use and manipulate context information to detect high-level situations, which are used to adapt application behavior. This paper discusses the specification of situations in context-aware applications and introduces a rule-based approach to detect situations. Situations are specified using a combination of UML class diagrams and OCL constraints. We support a wide range of situations, which can be composed of more elementary kinds of context. We discuss how to cope with distribution and to exploit it beneficially for context manipulation and situation detection. We employ a generic rule-based platform (DJess [2]) to support the derivation of situations in a distributed fashion.

Pervasive Systems Development: A Stepwise Rule-centric Rigorous Service-Oriented Architectural Approach

“…We have introduced the three above just for illustration, but we are working on a complete set of primitives for reasoning about different context-aware situations. Similar primitives can be found in [6] and [14] among others.…”

“…Towards forwarding suitable conceptual primitives for context-awareness and in contrast to functionality concerns, we first require contextual predicates [6] for reasoning about the surrounding environment and any involved devices and so on. In this contribution, we restrict ourselves to the role of locations in defining the context-aware behavior governing any activity.…”

“…Boosted by technological advances in networking, context-sensing and computation and pressed by stiff and global competitiveness, most of organizations are opportunistically joining their know-how into dynamic giant cross-organizational alliances. Striking features of any of such alliances, include: (1) process-centricity, that is, they exhibit very complex business processes with composing activities; (2) high-agility, where involved business processes and their activities / tasks are often governed by adaptive and evolving business rules [6,9,10,11,16]; (3) contextdependency, with user-preferences, adopted sensing devices and surrounding environment conditions as driving forces [4,5,28]; (4) strong-dependability, where the fatality of malfunctioning and failures may be economical und humanistic disastrous. Precise conceptualizations and formal techniques are thus highly required before investing any final deployment.…”

“…[Rule-centric architectural handling]: Towards intuitively coping with agility in such volatile business applications, we are capitalizing on the ubiquity of business rules in such applications. Indeed, business rules reflect evolving policies and laws for doing / collaborating business [6,9,10,16]. Furthermore, to enhance agility and bridge the gap to service-orientation, we shift any intuitive business rule towards transient architectural ECA-driven connectors [13].…”

Ambientes personalizados de e-learning: considerando os contextos dos alunos

“…Context-aware applications use and manipulate context information to detect the situations of users and adapt their behavior accordingly. Context-aware applications not only use context information to react to a user's request, but also take initiative as a result of context reasoning activities 14 .…”