Fig 2 - uploaded by Nora Koch
Content may be subject to copyright.
Source publication
this article we show the power of this approach. On the one hand, UWE prescribes how to build navigation and presentation models for Web applications defining therefore special UML stereotyped modeling elements and tagged values. On the other hand, we show how these Web specific navigation and presentation models can be supplemented by other views...
Context in source publication
Citations
... After conducting a comparative study of the different proposals, we decided to take the UWE proposal as a basis on which to ground our work. UWE was first introduced by Koch and Kraus in [25] and was then updated in [43][44][45]. Likewise, this proposal was improved adding new models to take into account security concepts [46,47]. ...
An acceptable level of quality in data is nowadays a paramount for any kind of organization or enterprise that wishes its business processes to prosper. Thus, introducing activities focused in the data quality management is a crucial requirement for the analysts if the level of quality of data for the functionality or service at hand is to be ensured. Such specialized data quality management activities should be presented as early as possible during the software development process. So far and having done a search for proposals in this field, there is still a lack of either methodological or technological proposals with which a developer could be able to design data quality aware applications in the specific field of Web application development. Considering the benefits offered in the field of Model Driven Web Engineering, this work presents a partial outcome of our research in this novel field: a metamodel and a UML profile, both able to be used as data quality artefacts during the design stage of Web applications. The main objective is to provide the designer with the tools needed to design Web applications, in order to prevent data quality issues.
... After conducting a comparative study of the different proposals, we decided to take the UWE proposal as a basis on which to ground our work. UWE was first introduced by Koch and Kraus in [25] and was then updated in [43][44][45]. Likewise, this proposal was improved adding new models to take into account security concepts [46,47]. ...
An acceptable level of quality in data is nowadays a paramount for any kind of organization or enterprise that wishes its business processes to prosper. Thus, introducing activities focused in the data quality management is a crucial requirement for the analysts if the level of quality of data for the functionality or service at hand is to be ensured. Such specialized data quality management activities should be presented as early as possible during the software development process. So far and having done a search for proposals in this field, there is still a lack of either methodological or technological proposals with which a developer could be able to design data quality aware applications in the specific field of Web application development. Considering the benefits offered in the field of Model Driven Web Engineering, this work presents a partial outcome of our research in this novel field: a metamodel and a UML profile, both able to be used as data quality artefacts during the design stage of Web applications. The main objective is to provide the designer with the tools needed to design Web applications, in order to prevent data quality issues.
... It is a model-driven approach that emphasizes the use of standard analysis and design models for web systems. The focus of the process is on adaptive applications with changing user UWE is continuously adapting, to new features of Web systems, such as more transaction-based, personalized, context-dependent, and asynchronous applications and and technology requirements [19,20,21]. more generally, UWE evolves to incorporate the state of the art of software engineering techniques. ...
There has been an increasing need for geospatial information that is delivered through internet technologies. This broad category of systems is referred to as Web Geographic Information Systems (Web GIS). These systems exhibit characteristics common to both stand-alone and web-based systems making it necessary to apply a hybrid methodology during their development. This paper proposes a methodology for developing Web GIS that is herein referred to as the Y-Model Web GIS Development Methodology
(YWDM) which has been adapted from existing software development methodologies and applied to the context of Web GIS development. The paper outlines in details the phases of the methodology. Its viability as a methodology has been tested through its use in the implementation of the Emuhaya Web GIS portal. The methodology presented here is not intended to be a rigid guide for web GIS development but instead it provides a useful framework for guiding the process.
... The UWA design framework includes a complete design methodology and a set of models and modeling tools for the user-centered conceptual design of data and operation intensive ubiquitous (i.e., multi-channel, multi-user and generally context-aware) Web applications [19]. Similarly to other well known web engineering methods proposed in the literature, such as OOHDM [16], WebML [5] and UWE [11], UWA specifies the design of a Web application by means of three main models: the Information Model (a.k.a., content or domain model), the Navigation Model, and the Presentation Model [18]. Additional models proposed by UWA include: the Transaction Model, which models the business processes the application is intended to support; the Operation Model, which is used to specify the elementary operations the application will provide to its users; the Customization Model, which specifies, by means of customization rules, how the application will adapt to different usage contexts. ...
... Regarding the execution model for a target development environment, OO-H focuses on defining how to implement the interface information associated to web environments, since OO-Method has already defined an execution strategy. UML-based Web Engineering (UWE) [23, 24] is a development process for Web applications which focuses on systematic design, personalization, and semi-automatic generation. Based on UML and the UML extension mechanism, it defines navigation and presentation models which are supplemented by other UML diagrams and UML modeling elements within an iterative and incremental approach based on the Unified Software Development Process [25]. ...
... UmlSEC, another extension of the UML language to high-level security requirements is introduced in [10] and used in [11] to model high-level security properties (requirements ) for forward engineering purposes. More focused in web applications, web modeling approaches like [12] and [4] include specific security constructs, at least to specify users and roles and their access permissions on parts of the web navigation model. We consider however that a better starting point for a security analysis requires a more specific security metamodel. ...
The widespread use of Java EE web applications as a means to provide distributed services to remote clients imposes strong security requirements, so that the resources managed by these applications remain protected from unauthorized disclosures and manipulations. For this purpose, the Java EE framework provides developers with mechanisms to define access-control policies. Unfortunately , the variety and complexity of the provided security configuration mechanisms cause the definition and manipulation of a security policy to be complex and error prone. As security requirements are not static, and thus, implemented policies must be changed and reviewed often, discovering and representing the policy at an appropriate abstraction level to enable their understanding and reenginering appears as a critical requirement. To tackle this problem, this paper presents a (model-based) approach aimed to help security experts to visualize, (automatically) analyse and manipulate web security policies.
... A modeling language can be either a graphical or textual language [5][6][7]. For the purpose of designing the new student portal framework, Unified Modeling Language (UML) is used as the graphical modeling language [5,[8][9],UML is formally defined by a meta-model (or semantic model) and it is used to represent software design since it is widely used for modeling both research and industry works [5,[10][11][12]. UML provides notations for specifying the packaging of a logical design into components that represent a distributed computing architecture and this can be modeled using a UML component diagram [5, 8, 12]. ...
Most of the currently available students' portal frameworks are tightly-coupled frameworks. A recent
research done by the authors of this paper has discussed how to distribute the concepts of the traditional
students' portal framework and came out with a distributed interoperable framework. This paper realizes
the distributed interoperable students' portal framework by developing a prototype. This prototype is based
on Service Oriented Architecture (SOA). The prototype is tested using web service testing and compatibility
testing.
... El segundo define como se accede a dichos objetos. Es un modelo a nivel diseño" (Koch Nora, 2002) Para el modelo del espacio de navegación utiliza estereotipos para las clases de navegación y para los link de navegación directa. Para el modelo de estructura de navegación utiliza clases estereotipadas según la forma de mostrar la información teniendo índices, visitas guiadas, consultas y menús. ...
Esta tesis presenta una metodología de modelado para aplicaciones web móviles utilizando
técnicas de desarrollo dirigido por modelos (MDD). Mediante la creación de sólo dos diagramas,
un diagrama de datos y un diagrama de interfaz de usuario (que además incluye la navegación)
es posible definir el comportamiento completo de una aplicación.
Por estar esta metodología basada en MDD incorpora dos transformaciones; la primera desde
el modelo de datos a una versión inicial del modelo de interfaz de usuario, lo que reduce
considerablemente el esfuerzo de modelado, ya que luego ese segundo modelo solo deberá ser
adaptado a las necesidades particulares. La segunda transformación toma los modelos
realizados y genera el código fuente completo, 100% funcional de una aplicación web móvil,
además del script de la base de datos correspondiente. Ambos modelos están basados en una
extensión conservativa de UML. El modelo de datos está basado en el diagrama de clases y el
modelo de interfaz de usuario utiliza el diagrama de componentes de UML. Para poder
especificar el comportamiento de la interfaz de usuario se definen una serie de componentes
que a su vez pueden ser configurados con información tomada del modelo de datos. La
configuración se basa en valores etiquetados propios para cada tipo de componente. Para
facilitar el proceso de construcción de los modelos y su configuración se ha desarrollado una
herramienta de soporte, que permite no solo modelar, sino también realizar las
transformaciones establecidas en la metodología, obteniendo como resultado final una
aplicación funcional sin escribir una sola línea de código.
Además esta tesis establece las ventajas de utilizar componentes configurables en el desarrollo
dirigido por modelos, haciendo que el esfuerzo de programación se realice una única vez al
establecer las transformaciones y que luego pueda ser aplicado a una amplia gama de
aplicaciones de distintos dominios.
... UWE came up by 1998. The method was developed by the Web Engineering Group from the Ludwig-Maximilians-Universität München [9][10]. It is a software engineering approach based on UML [11]. ...
The purpose of a metamodel in web engineering methodologies is for the platform independent analysis as well as the design of the content, navigation, and presentation issues of web applications. In the previous years, numbers of methodologies for the development of web applications were proposed, and most of them defined their notation for creating metamodels. The increasing expansion and complexity of web applications are a new challenge for web software developers. This paper presents a comparison study between metamodel of the three methodologies which are; UML-Based Web Engineering (UWE), Web Modeling Language (WebML) and Object Oriented Hypermedia (OOH). The aim is to show the capability of the methodologies to address the challenges in developing the web applications. The evaluation results presented in this paper help the designer in providing initial knowledge of the strengths and weaknesses of the three methodologies for developing web applications.
... In the Web Engineering context, MDE principles are being used to successfully address the development and evolution of WAs [12]. In particular, Model-Driven Engineering paradigm has been applied successfully by a number of web engineering methods, namely UWE, OO-H, OOHDMDA, UWE4JSF, and WebML [9], [16], [4], [3], [18], [11]. These methods use models to separate the platform-independent model (PIM) design of web systems from the platform-dependent (PSM) implementations as much as possible. ...
Fast prototyping is a quick and cost effective development of a (minimum) viable version of a software useful to some purpose (e.g., requirements verification or design validation), which can be discarded or refactored to become the version of the software to be delivered. In this paper we propose a model-driven approach for the fast prototyping of Rich Internet Applications (RIAs). Starting from the conceptual model of a RIA, intermediate models and the source code of a ready-to-deploy application prototype are automatically generated through a model-driven development process which exploits well known model-driven engineering frameworks and technologies including Eclipse EMF, GMF, and Xpand. Compared to traditional, non model-driven, prototyping approaches, our proposal allows to drastically reduce the overall prototyping effort to just the effort required to define the conceptual model of the application, as the rest of the process is substantially automatic. The paper describes the overall RIA prototyping approach, the supporting tools and adopted technologies, along with the results from a case study carried out for validation and verification purposes.
