Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
The unified software development process
The unified software development process
Principled design of the modern Web architecture
ACM Transactions on Internet Technology (TOIT)
Building Web Applications with Uml
Building Web Applications with Uml
Architecture recovery of web applications
Proceedings of the 24th International Conference on Software Engineering
Conceptual Modeling of Data-Intensive Web Applications
IEEE Internet Computing
MDA Explained: The Model Driven Architecture: Practice and Promise
MDA Explained: The Model Driven Architecture: Practice and Promise
A software architecture for structuring complex web applications
Journal of Web Engineering
Model-driven development of web applications with UWA, MVC and JavaServer faces
ICWE'07 Proceedings of the 7th international conference on Web engineering
A framework for situational web methods engineering
ICWE'07 Proceedings of the 7th international conference on Web engineering
Applying transformations to model driven data warehouses
DaWaK'06 Proceedings of the 8th international conference on Data Warehousing and Knowledge Discovery
Applying transformations to model driven development of web applications
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
| Hi-index | 0.00 |
Many approaches have been developed for modeling the functional aspects of Web applications, but there is a lack of a modeling language for their architectural concerns. This paper proposes such a modeling language defined as a UML 2.0 profile, which allows the specification of domain-specific models for the architectural view of Web applications. The profile is part of the Web Software Architecture (WebSA) approach, which follows the Model Driven Architecture (MDA) principles. The modeling elements proposed for each WebSA model (subsystem, configuration and integration models) are both represented graphically and formalized by means of the profile and the metamodel, respectively. In this article we will focus on the Configuration model and how it is used to model the well-known Petstore example.