Metamodeling the Requirements of Web Systems

Abstract

A detailed requirements analysis is best practice in the development of traditional software. Conversely, the importance of requirements engineering for Web systems is still underestimated. Only few Web methodologies provide an approach for the elicitation of requirements and techniques for their specifi-cation. This paper focuses on specification through requirements models of Web systems. We present a metamodel, which contains the key concepts needed for the requirements specification of Web systems. The benefit of such a metamodel is twofold: (1) The key concepts are used for the definition of a common modeling language: a UML profile for Web requirements. (2) The elements of the metamodel are mapped to the modeling constructs of the differ-ent Web methodologies. In this way the prerequisite for model-to-model trans-formations is given, which allows to build different views of the requirements of a Web system using different Web methodologies.

WEB ENGINEERING APPROACHES FOR REQUIREMENT ANALYSIS - A Systematic Literature Review

“…It proposes interviews, questionnaires and checklists as appropriated techniques for the requirements capture (Escalona and Koch 2004). Regarding to the requirements specification, this phase is carried out by means of UML Profiles (Escalona and Koch 2007). This approach does not provide traceability support.…”

“…Requirements analysis phase and traceability is supported by the NDT-Suite tool (NDT-Profile, NDT-Driver-Quality NDT) using profiles to work with the CASE tool Enterprise Architect. In (Escalona and Koch 2007), the authors of NDT and UWE have developed an UML profile for Web requirements called WebRE. In combination of both approaches, the conceptual models can be derived from requirements specification; the main drawback of this approach is the lack of tool support for model-to-model transformations.…”

Model Transformation from Ontology Model to Content Analysis Model

“…), and are supported by model transformation that produce most of the application's Web pages and logic based on the models [1]. However, most of the existing web methodologies start the development with modeling requirement and few of the existing Web methodologies start the development cycle with a detailed requirements analysis [4].…”

“…Several approaches have been proposed for the Web engineering process. These methods provide specific modeling elements for the analysis and design and most of them define a proprietary notation used for the graphical representation of the elements [4].…”

“…The most frequently used models are the content model , the navigation model and presentation model [4].…”