Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
A Survey of Architecture Description Languages
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Architectural styles and the design of network-based software architectures
Architectural styles and the design of network-based software architectures
Separation of Concerns in Model-Driven Development
IEEE Software
The Pragmatics of Model-Driven Development
IEEE Software
OO-H Method: extending UML to model web interfaces
Information modeling for internet applications
Service -Oriented Computing: Concepts, Characteristics and Directions
WISE '03 Proceedings of the Fourth International Conference on Web Information Systems Engineering
When and how to develop domain-specific languages
ACM Computing Surveys (CSUR)
UML Profile for the Platform Independent Modelling of Service-Oriented Architectures
ECSA '07 Proceedings of the 1st European conference on Software Architecture
SOMA: a method for developing service-oriented solutions
IBM Systems Journal
Linking Model-Driven Development and Software Architecture: A Case Study
IEEE Transactions on Software Engineering
Model-Driven approach to Software Architecture design
SHARK '09 Proceedings of the 2009 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Information and Software Technology
Integrating software architecture into a MDA framework
EWSA'06 Proceedings of the Third European conference on Software Architecture
Web-PACS for Multicenter Clinical Trials
IEEE Transactions on Information Technology in Biomedicine
Journal of Systems and Software
Hi-index | 0.00 |
This paper presents a framework for the Model-Driven specification of Software Architectures, which is defined using the concepts behind Service-Orientation. The framework described, denominated as ArchiMeDeS, represents the following: a coherent solution to the problem of architecting the existing gap between the high-level configuration of a software system by describing the business entities and relationships required by a software solution, and its low-level representation, in which the technological aspects determine the final shape of the system, providing technical support to the previously identified business processes and constraints. We also provide a set of transformation rules, which semi-automatically advance in the Architecture specification. These rules allow progress to be made from conceptual architectural models to more technologically dependent ones. The feasibility of the proposed service-oriented framework is validated by showing its usage capabilities in the definition of a software solution in the field of neuroscience research.