Requirements Engineering for Web Applications: A Comparative Study

The requirements engineering discipline has become more and more important in the last years. Tasks such as the requirements elicitation, the specification of requirements or the requirements validation are essential to assure the quality of the resulting software. The development of Web systems usually involves more heterogeneous stakeholders than the construction of traditional software. In addition, Web systems have additional requirements for the navigational and multimedia aspects as well as for the usability as no training is possible. Therefore a thoroughly requirements analysis is even more relevant. In contrast, most of the methodologies that have been proposed for the development of Web applications focus on the design paying less attention to the requirements engineering. This paper is a comparative study of the requirements handling in Web methodologies showing trends in the use of techniques for capturing, specifying and validating Web requirements

Proceedings ICPW'07: 2nd International Conference on the Pragmatic Web, 22-23 Oct. 2007, Tilburg: NL

Proceedings ICPW'07: 2nd International Conference on the Pragmatic Web, 22-23 Oct. 2007, Tilburg: N

Knowledge modelling for integrating semantic web services in e-government applications

Service integration and domain interoperability are the basic requirements in the development of current service-oriented e-Government applications. Semantic Web and, in particular, Semantic Web Service (SWS) technology aim to address these issues. However, the integration between e-Government applications and SWS is not an easy task. We argue that a more complex semantic layer needs to be modeled. The aim of our work is to provide an ontological framework that maps such a semantic layer. In this paper, we describe our approach for creating a project-independent and reusable model, and provide a case study that demonstrates its applicability

Topics in Software Engineering

Software engineering is a discipline which specifies, designs, develops, and maintains software applications. It applies practices and technologies from computer science. Software engineering is the backbone of software systems and forms the basis of operational design and development of software systems. Analysts use requirements elicitation techniques to ascertain the needs of customers and users, with the goal being a system that has a high chance of satisfying those needs. Success or failure of system development relies heavily on the quality of requirements gathering. Software modeling is an essential part of the software development process. Models are built and analyzed before the implementation of a system and are used to direct implementation.The Unified Modeling Language (UML) provides a standard way to visualize the design of a system. During the planning and design stages, software engineers must consider the risks involved in developing a system. Software must solve a problem and must respond to both functional and nonfunctional requirements. Software systems generally follow a pattern or an architectural style. We show the initial steps of developing a software system, define its specification and design topics, and demonstrate their creation by presenting a case study

The evolution of tropos: Contexts, commitments and adaptivity

Software evolution is the main research focus of the Tropos group at University of Trento (UniTN): how do we build systems that are aware of their requirements, and are able to dynamically reconfigure themselves in response to changes in context (the environment within which they operate) and requirements. The purpose of this report is to offer an overview of ongoing work at UniTN. In particular, the report presents ideas and results of four lines of research: contextual requirements modeling and reasoning, commitments and goal models, developing self-reconfigurable systems, and requirements awareness

Integrating the theme approach with aspectual scenarios

Dissertação de Mestrado em Engenharia InformáticaAspect-oriented requirements engineering emerged to deal with crosscutting requirements, i.e. requirements that are scattered in the requirements document and tangled with other requirements. There are several aspect-oriented requirements approaches - Theme, proposed by Baniassad and Clarke [7], is one of them. This approach is characterized by the identification of a set of actions associated to verbs present in requirements documentation. These actions are then analyzed in order to identify crosscutting behaviours, each one constituting a potential theme. One problem with this approach is that the composition mechanism is not expressive enough even when the Theme models are integrated to analysis models (e.g. UML diagrams). The MATA approach [24] provides powerful composition mechanisms, based on graph transformations that used UML models, in particular behaviour models (e.g. sequence or activity like diagrams). These models express scenarios that constitute a very popular and used technique to specify a system’s behaviour. Therefore, the result of the integration of these two approaches will be synergetic. Also, considering that in a system not only the expected situations happen, scenarios can also be used to illustrate unexpected situations, making their treatment possible. Negative scenarios are thus also considered, besides the positive ones: their representation is similar, only differing from an optimist and mostly assumed vision of the system’s behavior. These scenarios could be identified with Theme and mapped into MATA. In summary, the objective of this dissertation is twofold: firstly, we will integrate Theme with Aspectual Scenarios (specified in MATA); secondly, we will extend Theme to include the modeling of negative scenarios. The result will be the synergy between two complementary techniques, including the specification of undesirable situations, where behavioral and structural aspect modeling are integrated