Web Engineering Resources Portal (WEP)

2005 ◽  
pp. 31-75 ◽  
Author(s):  
Sotiris P. Christodoulou ◽  
Theodore S. Papatheodorou

This chapter introduces the Web Engineering Resources Portal (WEP) as a basic reference model and guide for Web Engineers. WEP provides a general classification of Web Engineering resources under technologies, research results, and tools. It consists of a reference model and a resources portal. The objective of the WEP reference model is to provide a common basic terminology, a technical-oriented classification of Web applications (WebApps), a specification of WebApps Logical and Physical Architectures, a classification of skills needed in Web projects and a generic and adaptable Web lifecycle process model. The WEP reference model provides the framework upon which Web Engineering resources are classified and presented. The WEP portal provides several and cross-referenced taxonomies of technologies, research results, and tools whereas its objective is to facilitate Web Engineers to comprehend available resources, understand their role and appropriately use them during development and operation/maintenance of Web information systems.

2011 ◽  
pp. 310-343
Author(s):  
Vítor Estêvão Silva Souza ◽  
Ricardo de Almeida Falbo ◽  
Giancarlo Guizzardi

In the Web Engineering area, many methods and frameworks to support Web Information Systems (WISs) development have already been proposed. Particularly, the use of frameworks and containerbased architectures is state-of-the-practice. In this chapter, we present a method for designing framework- based WISs called FrameWeb, which defines a standard architecture for framework-based WISs and a modeling language that extends UML to build diagrams that specifically depict framework-related components. Considering that the Semantic Web has been gaining momentum in the last few years, we also propose an extension to FrameWeb, called S-FrameWeb, that aims to support the development of Semantic WISs.


Author(s):  
Geert-Jan Houben ◽  
Lora Aroyo ◽  
Paul De Bra ◽  
Darina Dicheva

This chapter presents main issues and the state of the art of research on adaptation engineering in adaptive concept-based systems. Adaptive concept-based systems are characterised by the prominent role of concept structures, which makes content classification and conceptualisation play central roles in engineering. On top of these concept structures, adaptation is engineered in order to achieve personalisation of both the content and their presentation. For this presentation many systems use hypermedia structures, as that nicely supports the Web-based application. As a consequence, navigation adaptation is also a central issue in system design. Next to modelling domain and adaptation, it is necessary to model the user and what the system knows or assumes of the user. To discuss different approaches to these issues, we have identified three main classes of adaptive concept-based systems. Adaptive Web information systems build the more general class of data-intensive applications. We use the Hera design methodology to explain the properties of this class. The second class of systems is that of adaptive hypermedia systems. On the basis of the AHAM reference model and the AHA! system, we illustrate this class. The third class consists of adaptive task-based systems, for which we present AIMS as a representative.


Author(s):  
Saksham Gupta ◽  
Shallu Bashambu

In this paper represents the web design frameworks as a conceptual methodology to expend the probabilities reuse in Web applications. Firstly I have presented the importance for construction abstract and reusable directional design structures, demonstrating with different kinds of Web information Systems. Struts 2 is an elegant, extensible framework for creating enterprise ready web applications. It provides with a controller Servlet to manage and intercept the flow of requests. Hibernate Framework Technology as unique and well-organized resources to take immeasurable databases and also on how to implement persistent features in object-oriented system finished it. Java also consists of many useful APIs or Application Program Interfaces, some of which are mention in this paper. Java accepts a N-tier framework of MVC Model in platform and uses EJB, Struts WEB Framework and Hibernate technology.


Author(s):  
Vítor Estêvão Silva Souza ◽  
Ricardo de Almeida Falbo ◽  
Giancarlo Guizzardi

In the Web Engineering area, many methods and frameworks to support Web Information Systems (WISs) development have already been proposed. Particularly, the use of frameworks and container-based architectures is state-of-the-practice. In this chapter, we present a method for designing frameworkbased WISs called FrameWeb, which defines a standard architecture for framework-based WISs and a modeling language that extends UML to build diagrams that specifically depict framework-related components. Considering that the Semantic Web has been gaining momentum in the last few years, we also propose an extension to FrameWeb, called S-FrameWeb, that aims to support the development of Semantic WISs.


2008 ◽  
pp. 1449-1468
Author(s):  
Geert-Jan Houben ◽  
Lora Aroyo ◽  
Paul De Bra ◽  
Darina Dicheva

This chapter presents main issues and the state of the art of research on adaptation engineering in adaptive concept-based systems. Adaptive concept-based systems are characterised by the prominent role of concept structures, which makes content classification and conceptualisation play central roles in engineering. On top of these concept structures, adaptation is engineered in order to achieve personalisation of both the content and their presentation. For this presentation many systems use hypermedia structures, as that nicely supports the Web-based application. As a consequence, navigation adaptation is also a central issue in system design. Next to modelling domain and adaptation, it is necessary to model the user and what the system knows or assumes of the user. To discuss different approaches to these issues, we have identified three main classes of adaptive concept-based systems. Adaptive Web information systems build the more general class of data-intensive applications. We use the Hera design methodology to explain the properties of this class. The second class of systems is that of adaptive hypermedia systems. On the basis of the AHAM reference model and the AHA! system, we illustrate this class. The third class consists of adaptive task-based systems, for which we present AIMS as a representative.


i-com ◽  
2008 ◽  
Vol 6 (3/2007) ◽  
pp. 23-29 ◽  
Author(s):  
Birgit Bomsdorf

SummaryTask modelling has entered the development process of web applications, strengthening the usage-centred view within the early steps in Web-Engineering (WE). In current approaches, however, this view is not kept up during subsequent activities to the same degree as this is the case in the field of Human-Computer-Interaction (HCI). The modelling approach presented in this contribution combines models as known from WE with models used in HCI to change this situation. Basically the WE-HCI-integration is supported by combining task and object models as known from HCI with conceptual modelling known from WE. In this paper, the main focus is on the WebTaskModel, a task model adapted to web application concerns, and its contribution towards a task-related web user interface. The main difference to existing task models is the build-time and run-time usage of a generic task lifecycle. Hereby the description of exceptions and erroneous situations during task performance (caused by, e.g., the stateless protocol or Browser interaction) is enabled and at the same time clearly separated from the flow of correct action.


Author(s):  
Ala M. Abu-Samaha ◽  
Lana S. Al-Salem

The requirements phase of the system/application development process typically involves the activities of requirements elicitation, analysis, validation, and specification. The main goal of such a process is “to develop a requirements speci- fication document which defines the system to be procured and which can act as a basis for the system design” (Sawyer, Sommerville, & Viller, 1996). Hence the underpinning assumption of the requirements engineering (RE) process is to transform the operational needs of an organisation into complete, consistent, and unambiguous system/application specifications through an iterative process of definition and validation (Pohl ,1994). The Web engineering (WE) literature provides a limited number of methods and techniques that can be used to manage the RE process in a Web development context [e3-value framework (Gordijn, Akkermans, & van Vliet, 2000), SOARE approach (Bleistein, Aurum, Cox, & Ray, 2004), e-prototyping (Bleek, Jeenicke, & Klischewski, 2002), AWARE (Bolchini & Paolini, 2004), and SSM/ICDT (Meldrum & Rose, 2004)]. Despite the availability of such a limited number of Web requirements engineering (WRE) methods, many researchers criticised such methods for their failure to address the necessity to align the Web application’ requirements to the organisation’s business strategy. Hence, the recommendation of many researchers (Al-Salem & Abu- Samaha, 2005a; Bleistein 2005; Bleistein, Cox, & Verner, 2004; Vidgen, Avison, Wood, & Wood-Harper, 2002) is to utilise a general WRE framework for the development of Web applications that can align the application’s requirements to the organisation’s business needs and its future vision. The objective of such a WRE framework is to incorporate the elicitation/analysis of business strategy as part of the application’s RE process. This chapter presents a WRE method that extends Sommerville and Kotonya’s viewpoint-oriented requirements definition (VORD) and Kaplan and Norton’s balanced scorecard (BSC) to elicit the Web application’ requirements and to plan/analyze the business strategy, respectively. In addition, eWARE (extended Web application requirements engineering) deploys the concept of “requirements alignment” to attain business objectives during the requirements discovery, elicitation, and formalisation process to identify the services of the Web application that will achieve the business objectives in order to improve the organisation’s profitability and competitiveness. The chapter is organised into a number of sections. The second section of this chapter provides a background to Web applications in terms of defi- nition and differentiating characteristics. The third section provides a discussion of eWARE method in terms of phases and activities. This section is divided into two subsections to cover the activities of the two prominent phases of the eWARE process in more detail. The fourth and fifth sections provide a discussion of possible future trends in WRE and a number of concluding remarks.


Author(s):  
Christopher Walton

In the introductory chapter of this book, we discussed the means by which knowledge can be made available on the Web. That is, the representation of the knowledge in a form by which it can be automatically processed by a computer. To recap, we identified two essential steps that were deemed necessary to achieve this task: 1. We discussed the need to agree on a suitable structure for the knowledge that we wish to represent. This is achieved through the construction of a semantic network, which defines the main concepts of the knowledge, and the relationships between these concepts. We presented an example network that contained the main concepts to differentiate between kinds of cameras. Our network is a conceptualization, or an abstract view of a small part of the world. A conceptualization is defined formally in an ontology, which is in essence a vocabulary for knowledge representation. 2. We discussed the construction of a knowledge base, which is a store of knowledge about a domain in machine-processable form; essentially a database of knowledge. A knowledge base is constructed through the classification of a body of information according to an ontology. The result will be a store of facts and rules that describe the domain. Our example described the classification of different camera features to form a knowledge base. The knowledge base is expressed formally in the language of the ontology over which it is defined. In this chapter we elaborate on these two steps to show how we can define ontologies and knowledge bases specifically for the Web. This will enable us to construct Semantic Web applications that make use of this knowledge. The chapter is devoted to a detailed explanation of the syntax and pragmatics of the RDF, RDFS, and OWL Semantic Web standards. The resource description framework (RDF) is an established standard for knowledge representation on the Web. Taken together with the associated RDF Schema (RDFS) standard, we have a language for representing simple ontologies and knowledge bases on the Web.


Author(s):  
Maristella Matera ◽  
Francesca Rizzo ◽  
Rebeca Cortázar ◽  
Asier Perallos

Given the emergent need for usability, during last year’s traditional development processes have been extended for enabling the fulfillment of usability requirements. Usability Evaluation Methods (UEMs) have been therefore proposed at any stage of the development process, to verify the usability of incremental design artifacts, as well as of the final product. This chapter surveys the most emergent UEMs, to be adopted during the whole lifecycle of Web information systems for promoting usability. For each evaluation method, the main features, as well as the emerging advantages and drawbacks are illustrated. Some future trends, related to the need of evaluating the usability of UEMs are also discussed.


2008 ◽  
pp. 162-181
Author(s):  
Félix J. García Clemente ◽  
Gregorio Martínez Perez ◽  
Juan A. Botía Blaya ◽  
Antonio F. Skarmeta

Policies, which usually govern the behaviour of networking services (e.g., security, QoS, mobility, etc.) are becoming an increasingly popular approach for the dynamic regulation of web information systems. By appropriately managing policies, a system can be continuously adjusted to accommodate variations in externally imposed constraints and environmental conditions. The adoption of a policy based approach for controlling a system requires an appropriate policy representation regarding both syntax and semantics, and the design and development of a policy management framework. In the context of the Web, the use of languages enriched with semantics has been limited primarily to represent Web content and services. However the capabilities of these languages, coupled with the availability of tools to manipulate them, make them well suited for many other kinds of applications, as policy representation and management. In this chapter, we present an evaluation of the ongoing efforts to use ontological (Semantic Web) languages to represent policies for distributed systems.


Sign in / Sign up

Export Citation Format

Share Document