The goal of this paper is to argue the need to approach the personalization issues in Web applications from the very beginning in the application's development cycle. Since personalization is a critical aspect in many popular domains such as e-commerce, it important enough that it should be dealt with through a design view, rather than only an implementation view (which discusses mechanisms, rather than design options). We present different scenarios of personalization covering most existing applications. Since our design approach is based on the Object-Oriented Hypermedia Design Method, we briefly introduce it, emphasizing the way in which we build Web application models as object-oriented views of conceptual models. We show how we specify personalized Web applications by refining views according to users' profiles or preferences; we show that an object-oriented approach allows maximizing reuse in these specifications. We discuss some implementation aspects and compare our work with related approaches, and present some concluding remarks.

Presentation Diagram" section). 7. Other implementations: Adapt the observer pattern 11 to hypermedia environments. Navigational access diagram For a more general perspective of the approach, we'll use a discussion list management system as an example. As a basic explanation (for reasons of brevity), we assume the list manager system contains several discussion lists dealing with different Web technology topics, and the system forms each list by a set of hierarchically ordered messages relating to each other through a parent--child unary relationship. The discussion list user can read all the messages included inside any lists and reply to any of them. We previously noted that one or more NADs capture the navigation model. Designers should construct as many NADs as different views of the system are required, and they should provide at least one different NAD for each user type (agent type) allowed to navigate through the system. A NAD is based on four types of constructs: navigational classes, navigational targets, navigational links, and collections. Also, when defining the navigation structure, designers must consider some orthogonal aspects, such as the desired navigation behavior, the object population selection, the order in which objects should be navigated, or the cardinality of the access. We capture these features by different kinds of navigation patterns and filters associated with links and collections. We further develop these concepts below. Navigational classes. Enriched domain classes whose attributes and method visibility have been restricted according to the user access permissions and navigation requirements. A sample enrichment is the differentiation among three types of attributes: V-attributes (visible attributes), R-attributes (referenced attr...

Data-intensive Web sites serve large volumes of pages whose content is dynamically extracted from a database. Such Web sites have very high software development and maintenance costs and in general offer poor response times due to the heavy interaction with the database system. This paper introduces the Weave management system developed at INRIA, which alleviates the above shortcomings of data-intensive Web sites. Weave relies on the declarative specification of Web sites and offers a number of tools for the easy implementation, deployment and monitoring of the specified site. Weave features a customizable cache system that implements the optimal data materialization strategy according to the Web site's specifics: it can cache database data, XML fragments and HTML files. To explore Weave's performance we have built a Web site based on the TPC/D benchmark database using the WeaveBench test platform. We conducted a number of experiments with various data materialization strategies supported...

Many of the Web applications around us are data-intensive; this term indicates applications whose main purpose is presenting large amount of data to their users. Most of the sites for on-line trading or e-commerce are data-intensive, as well as most “institutional ” sites (describing private and public organizations) or digital libraries. Several commercial Web development systems enable the rapid development of data-intensive

Community web sites exhibit two dominating properties: They often need to integrate many different information sources and they require an adequate web site management system. SEAL (SEmantic portAL) is a conceptual model that exploits ontologies for fulfilling the requirements set forth by these two properties at once. The ontology provides a high level of sophistication for web information integration as well as for web site management. We describe

E-commerce and m-commerce demand for full-fledged, increasingly complex applications which need to offer ubiquitous access in terms of the anytime/anywhere/anymedia paradigma. From a software engineering point of view, the development of such ubiquitous web applications requires proper modeling methods in order to ensure architectural soundness and maintainability. Recently, web modeling methods started recognizing this fact by providing first concepts for dealing with ubiquity. In this paper, two of these modeling methods are compared, identifying their strengths and shortcomings. As a prerequisite, an evaluation framework is introduced, using the notion of customization as the uniform mechanism to enable ubiquity. Customization adapts a web application towards a particular context which reflects the environment the application is running in. To enable a holistic view on the development process of a ubiquitous web application, customization is regarded as a new modeling dimension, influencing all other tasks of ubiquitous web application development.

Web applications are the legacy software of the future. Developed under tight schedules, with high employee turn over, and in a rapidly evolving environment, these systems are often poorly structured and poorly documented. Maintaining such systems is problematic. This paper presents an approach to recover the architecture of such systems, in order to make maintenance more manageable. Our lightweight approach is flexible and retargetable to the various technologies that are used in developing web applications. The approach extracts the structure of dynamic web applications and shows the interaction between their various components such as databases, distributed objects, and web pages. The recovery process uses a set of specialized extractors to analyze the source code and binaries of web applications. The extracted data is manipulated to reduce the complexity of the architectural diagrams. Developers can use the extracted architecture to gain a better understanding of web applications and to assist in their maintenance. Keywords Web Applications, Software Architecture, Reverse Engineering, Architecture Recovery, Re-documentation. 1

While Web applications evolve towards ubiquitous, enterprise-wide or multi- enterprise information systems, they face new requirements, such as the capability of managing complex processes spanning multiple users and organizations, by interconnecting software provided by different organizations. Significant efforts are currently being invested in application integration, to support the composition of business processes of different companies, so as to create complex, multi-party business scenarios. In this setting, Web applications, which were originally conceived to allow the user-to-system dialogue, are extended with Web services, which enable system-to-system interaction, and with process control primitives, which permit the implementation of the required business constraints. This paper presents new Web engineering methods for the high-level specification of applications featuring business processes and remote services invocation. Process- and service-enabled Web applications benefit from the high-level modeling and automatic code generation techniques that have been fruitfully applied to conventional Web applications, broadening the class of Web applications that take advantage of these powerful software engineering techniques. All the concepts presented in this paper are fully implemented within a CASE tool.

In this paper we present Web design frameworks as a conceptual approach to maximize reuse in Web applications. We first analyze the current state of the art of Web applications design, stating the need for an approach that clearly separates concerns (conceptual, navigational, interface). We briefly introduce the OOHDM approach for Web applications design. We next focus on the problem of design reuse in Web applications. After a short review the state of the art of object-oriented application frameworks we present the rationale for a slightly different approach focusing on design reuse instead of code reuse. We then present OOHDM-Frame, a syntax for defining the hot spots of generic Web applications designs. We illustrate the use of OOHDM-Frame with a case study in the domain of Conference Paper Review Systems. We finally discuss how to implement Web design frameworks in different Web platforms. 1

The growing demand for data-driven Web applications has led to the need for a structured and controlled approach to the engineering of such applications. Both designers and developers need a framework that in all stages of the engineering process allows them to specify the relevant aspects of the application. This paper concentrates on Web applications that automatically generate hypermedia presentations for their output. Typically, these applications retrieve their data from a heterogeneous set of Web data sources, and they respond to a user's request for information by providing the user with a hypermedia presentation for the requested data. Many classes of Web-based information systems are of this nature. Because of this aspect of automated presentation generation, (the support of) the engineering process for these applications is far from trivial. The engineering becomes even more complicated when we include notions of adaptivity. Here, we address both adaptation during the presentation generation for the sake of personalization (to reflect e.g. user preferences or platform used), as well as adaptation within the generated presentation (generating adaptive hypermedia). The