Figure 1 - uploaded by Peter Dolog
Content may be subject to copyright.
Source publication
Web applications are accessed by much diverse set of users than the traditional desktop applications. The users differ in their background, culture, political and social environment, and interests. The different user types have slightly different requirements for features which such a Web application should have. The different requirements might be...
Contexts in source publication
Context 1
... Products dimension is concerned with the question "what" to model. Tiers, which are commonly discussed in the Web-based application per- spective, are application domain, navigation and presentation. Not all tech- niques are useful for description of particular product; Figure 3.1 depicts an extended space for Web application development from fig. 1.1 with the technique dimension. As pointed above, not all techniques are useful in each phase, workflow or for each ...
Context 2
... other concepts from the conceptual model ( Fig. 6.1) usually have such feature models if they are communicated to learners as they become available in the appli- cation. Note also that the models depicted in our examples are not intended to deter- mine the only possible solution, but just to exemplify how to create custom feature models which generate best practice guidance for ...
Context 3
... designers just need to specify the IDs of those WebML elements that are to be used for URL construction, i.e. pages, source entities from which page contents are extracted and entity attributes that are used in conditions for querying contents. Figure 10.1 depicts an excerpt from a state diagram extended with tagged val- ues for WebML concepts needed for computing WebML links. For instance, Object Oriented Programming Concepts is a lecture. ...
Context 4
... have implemented described structure for Web browsers. We have also im- plemented the functions for filling this structure and for interpreting the user actions on this structure. Current position of the user in the navigation graph is indicated by grayed background of the presented element. As it is obvious from Fig. 9.1, the navi- gation map was generated from the navigation model of JAVA e-lecture in UML state diagram depicted in Fig. ...
Context 5
... case study is based on the conceptual models from section 7.5.2. To remem- ber, the excerpt of a state diagram from section 7.5.2, which is taken for integration purposes, is depicted in fig. 10.1. The states are extended with tagged values for WebML concepts as pointed in section 7.5.2. The process consists of two steps: iden- tifying application domain concepts to be used to identify content and identifying hypertext elements to be used to present the ...
Context 6
... specific requirements, for example those set by conditions in entry actions of states, are met, the WebML vertical adapts delivered content based on additional parame- ters that UML-Guide is able to send to the server-side application. Figure 10.3 highlights a lecture on "What is an Object". ...
Context 7
... content of the lecture is delivered by the WebML vertical based on the generated link that is assigned to the document symbol at the "What is an Object" entry. The symbol is generated from the simple state with the same name depicted in Figure 10.1. The state has a transition to the next state "What is a Message", which in the UML-Guide panel is depicted as an outgoing arrow, under the symbol of the current lesson. ...
Context 8
... us describe the process on a scenario. Figure 10.4 depicts the design process for building adaptive applications intermixing the UML-Guide with the WebML specifications and platforms [CDMN05]. ...
Context 9
... Dolog http://purl.org/dc/elements/1.1/author Figure 11.1: Example of an RDF graph alized access to web resources. ...
Context 10
... the configuration knowledge main- tained by the domain feature models can be mapped to adaptation rules which en- able decisions to be made about appropriate variants of a feature according to knowl- edge available about a user. Figure 11.2 depicts relations between domain engineering models, semantic web ontologies, metadata, adaptation rules and services which collaborate in an applica- tion to serve a user. ...
Context 11
... Application Domain. Figure 11.3 depicts an excerpt from the Java program- ming domain following on from our eLearning examples from part II. ...
Context 12
... show just a fragment of a domain knowledge base covering Java programming concepts with an isa (subConceptOf) relationship between these concepts. Figure 11.3 Documents can be ordered by means of the hasPrerequisite property. Multi- plicity is allowed to provide for different ordering per and within an application. ...
Context 13
... more discussion on learner modeling standards see for example [DS05]. Figure 11.6 depicts an example of an ontology for a learner profile. ...
Context 14
... are storing sentences about a learner who has achieved a certain Performance. Figure 11.6: Ontology for learner performance learning experience (learningExperienceIdentifier) which is obtained from a particular document. ...
Context 15
... her goal, task, knowledge, etc. The facts gathered about a user can be used for providing personalized views on hypertexts. An ontology of observations should therefore pro- vide a structure of information about possible user observations, and -if applicable - their relations and/or dependencies. A simple ontology for observations is depicted in fig. 11.7. The ontology allows us to instantiate facts as follows: that a Learner has interacted (hasInteraction property) with a particular Document (isAbout property) via an interaction of a specific type (InteractionType). Examples of InteractionTypes are access, bookmark, an- notate. The information that an interaction has taken place ...
Context 16
... Search for example connects mapping, query rewriting, query and recommendation services. Figure 11.9 depicts a user interface for formulating a user query to search for a particular concept or competence a user would like to acquire, combined with a user interface providing results with recommendations represented by the traffic light metaphor. ...
Citations
... The variation points and variable components' resolution is defined by restraints on states and alterations by assessing the qualities of the user. It is these constraints that establish the likelihood of accessing a given link, with the state being considered as a target state, as well as the state is entered among others [20]. In this study, Rojas (2008) proposed a Model-Driven method in the establishment of Adaptive Web Applications. ...
... As a measure of sustaining the adaptive features modeling, the definition of a requisites model is considered, facilitating the design of adaptability prerequisites, besides the information prerequisites affiliated to the application users. Eventually, several transformation guidelines are introduced with the aim of enhancing their prerequisites' traceability to the theoretical modeling stage [20]. ...
With the evolution of modern web applications, several web engineering methods proposed to develop web applications. The modern web applications are; Rich Internet Application (RIA), Semantic Web Application (SWA), Ubiquitous Web Applications (UWA), and Intelligent Web Applications (IWA), with each of them having new features. The problem is that current web engineering methods cannot support new features of modern web applications. However, some of them extended for new concern of web applications but have limited, meaning these methods have a lack of adaptability to support features from modern web applications. In an attempt to solve this gap, we have defined a new adaptive model for the web engineering methods that can support the new features of modern web applications. This model very efficient in the process development and will be to increase the usability of the methods.
... Kullanıcı modelinin oluşturulması, uyarlamanın en önemli aşamasıdır. Kullanıcı modeli, kullanıcının karakteristik özelliklerini belli bir yapıda kayıt altına almaya çalışır (Dolog, 2006). Kullanıcı modelini oluşturmak için mevcut bilgi durumu, hedefleri, bilişsel kapasiteleri, öğrenme stilleri, tercihleri gibi bireysel özelliklerinin toplanması ve bu bilgilerin yorumlanması gerekmektedir. ...
... Nažalost, ne postoji alat koji trenutno podržava grafičko modelovanje uz pomoć HiLA notacije 2.2. Projektovanje adaptivnih web aplikacija U [2,3] su opisane apstrakcije koje je moguće primeniti prilikom projektovanja adaptivnih web aplikacija. Pod adaptivnom aplikacijom autor podrazumeva aplikaciju koja se priprema da zadovolji različite zahteve tako što ostavlja neke od svojih mogućnosti (u fazi dizajna) u formi promenljivih koje su zavisne od određenih kriterijuma. ...
... Adaptivnost se u okviru [2,3] razmatra sa dva stanovišta: 1) "ručne" adaptacije na promenjene zahteve poslovanja i 2) dinamičke adaptacije na promene okruženja (konteksta). ...
Goal of this paper is research of possible
applications of aspect-oriented programming for implementation of adaptive web-based business solutions. This paper presents generic web application architecture where fundamental data manipulation functions are developed within object-oriented core, while adaptivity and other specific functions are achieved using aspects.
... In this paper, we present the power of the language High-Level Aspects (HILA) in Model-Driven Web Engineering. HILA is an aspect-oriented extension of UML state machines [13] and can be used on top of statemachine-based MDWE approaches, such as [3,7,12,18]. In HILA, different concerns of a software system are modeled in aspects, separately from the base functionalities of the applications and from each other. ...
... Therefore, it also provides a natural and widely-used way of modeling web applications, see e.g. [3,7,11,12,18]. Usually states model navigation nodes, transitions model links between the navigation nodes, and events model user input or system events. ...
Modern web applications often contain features, such as landmarks, access control, or adaptation, that are difficult to model modularly with existing Model-Driven Web Engineering approaches. We show how HiLA, an aspect-oriented extensions for UML state machines, can represent these kinds of features as aspects. The resulting models achieve separation of concerns and satisfy the "Don't Repeat Yourself" (DRY) guideline. Furthermore, HiLA provides means to detect potential interferences between features and a declarative way to specify the behavior of such feature combinations.
... One benefit of this choice is that it enables our framework to consistently store rules and defined functions together with the models for learner profiles and traces. The use of RDF to represent both the learner model (as [10]) and the diagnosis rules is a key enabler to integrate, reuse and share the diagnosis model (or parts of) as it allows to reason about the rules based on the ontologies (i.e. both the rules ontologies and the learner ontologies). ...
In this paper we present a general framework to describe a trace-based learner modelling process. This framework includes three knowledge models: the first model is an explicit representation of observations about learner's interactions with a TEL-system, the second model describes the structure and elements describing the Learner Model and the last model describes the main knowledge elements types that could be required to calculate and infer learner profile elements (leaner individual features).
... We apply HiLA to a UML state machine (the base machine) which models the general functionalities of a web application. The base machine can be constructed by any state machine based web modeling approaches, such as [5,9,11]. Aspects are used to model adaptation rules, separately from the base machine and separately from each other. ...
... We assume a state machine as our base model, and call it also base machine. This machine can be obtained using common engineering methods, which model web applications with state machines, including [5,9,11]. In the following, we use Fig. 1 as our base machine, and enrich this application by adaptation rules. ...
... More details are given in [14]. We point out that UML state machines are also used by Dolog [5], and Aspect-Oriented Modeling by UWE [10], Hera [2] and Schauerhuber [13]. Moreover, our aspects using history properties are reminiscent of the Event-Condition-Action rules used in WebML, WSDM, and OO-H, see also [14]. ...
Modeling adaptivity is a challenging task for two reasons: 1) adap- tation is usually strongly interwoven with the general functionality of the web application, separation of concerns is hard to achieve, and 2) adaptation rules may be conflicting, i.e., changing and revok- ing the effect of each other. We propose to use our aspect-oriented extension of UML state machines, High-level Aspects (HiLA), to model adaptation rules of web applications. With HiLA, adaptation rules can be modeled separately from the general functionalities. We also provide an automatic technique for checking the consis- tency of the aspects (i.e., the adaptation rules). Therefore, HiLA provides valuable help for modularly modeling adaptive web ap- plications and keeping the adaptation rules consistent.
... We propose a feature based method for engineering compensations in Web service environments. We adopt a method and a modelling technique based on feature models described previously in UML [4]. The infrastructure which utilizes the models is based on our compensation environment described in [10]. ...
In this paper, we introduce a product line approach for developing Web services with extended compensation capabilities. We
adopt a feature modelling approach in order to describe variable and common compensation properties of Web service variants,
as well as service consumer application requirements and constraints regarding compensation. The feature models are being
used in order to configure the compensation operations that are applied. In this way, we ensure that the compensation actions
are limited to the prescribed ones,and the infrastructure which uses them can be adapted easily in case environment conditions
change.
... Adaptivity is another concern in web application design which is orthogonal to those mentioned above. Systematic analysis and design of adaptive application features require following requirements to be met [6]: ...
... Feature Modeling. There have been several proposals for techniques modeling variability and commonality in software systems such as Feature Oriented Domain Analysis (FODA) [15] and or the extended UML structural modeling package with stereotypes for feature modeling (see [6] ). Other proposals use different techniques for capturing the variability in software systems like the story boards [2], variation points in assets and components in [1]. ...
The unique characteristic of web applications is that they are supposed to be used by much bigger and diverse set of users and stakeholders. An example application area is e-Learning or business to business interaction. In eLearning environment, various users with dif- ferent background use the eLearning system to study a discipline. In business to business interaction, dierent requirements and parameters of exchanged business requests might be served by dierent services from third parties. Such applications require certain intelligence and a slightly dierent approach to design. Adpative web-based applications aim to leave some of their features at the design stage in the form of variables which are dependent on several criteria. The resolution of the variables is called adaptation and can be seen from two perspectives: adaptation by humans to the changed requirements of stakeholders and dynamic system adaptation to the changed parameters of environments, user or context. Adaptation can be seen as an orthogonal concern or viewpoint in a design process. In this paper I will discuss design abstractions which are employed in current design methods for web applications. I will ex- emplify the use of the abstractions on eLearning web applications as well as on applications for business to business interaction based on web services.
... Finally, section 4 provides conclusions and proposals for further work. − Mapping to Implementation maps the design abstractions to the appropriate implementation according to the UML Guide principles [5] employing tagged values, side effect actions and transformations to the running code. Scenario. ...
... in the UML-Guide [6] for modelling user navigation in a hypertext; each state represents the production of a given information chunk on the device observed by a user, and each state transition represents an event caused by user interaction that leads to the production of a new chunk of information. State diagrams therefore provide an abstraction of hypertext trails, where each trail can be adapted by taking into account the user background, level of knowledge, preferences and so on [5, 6]. Atomic states, super states, history states, fork and join are additional symbols to describe composition, concurrent execution, remembering, and so on. ...
In this paper, we propose a new method for designing rich internet applications. The design process uses results from an object-oriented analysis and employs interaction spaces as the basic abstraction mechanism. State diagrams are employed as refinements of interaction spaces and task models to specify synchronization events and follow up actions on the client and server side. The notation is based on UML.
... Dolog's approach is also based on class stereotypes representation of features [DN04,Dol06], but it employs a thorough treatment of feature groups through variation points. This approach actually supports feature diagrams in the form of directed acyclic graphs, but the information on variability is still inadequately built into the features themselves. ...
Feature modeling,is an important approach,to dealing with variability at an abstract level in a hierarchical manner,extensively used in software product lines. For its use in conjunction with other UML models and MDA approach, it is impor- tant to correctly integrate feature modeling into UML. In this paper, we present an approach to integrating feature modeling,into UML that respects abstractness of fea- ture modeling,elements. This is achieved by deriving feature modeling,elements from the deeper levels of the UML metamodel. We applied this approach,to the essential elements of feature modeling,in the cardinality-based Czarnecki-Eisenecker notation and selected elements specific to other notations. Since UML modeling,tools do not support such modifications of the UML metatmodel, in order to facilitate experimen- tation with combining elements from different notations, we implemented this feature modeling,extension as a UML profile (in Enterprise Architect and Omondo,UML).
