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
Evaluating software architectures: methods and case studies
Evaluating software architectures: methods and case studies
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Quality Attribute Design Primitives and the Attribute Driven Design Method
PFE '01 Revised Papers from the 4th International Workshop on Software Product-Family Engineering
Software Architecture in Practice
Software Architecture in Practice
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
Architecture Decisions: Demystifying Architecture
IEEE Software
NFRs-aware architectural evolution of component-based software
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
SOA Design Patterns
Journal of Systems and Software
Quality-driven architecture development using architectural tactics
Journal of Systems and Software
Automated architectural evaluation of web information systems
Proceedings of the 19th Brazilian symposium on Multimedia and the web
Hi-index | 0.00 |
Since many years, Web services have confirmed their status of one of the most pertinent solutions for a given service provider, like Google, Amazon or FedEx, to open its solutions for third party software development. New business logic can be implemented through orchestrations of existing Web services. This helps development teams in capitalizing resources held by the providers of these services. Nonetheless, these service-oriented software architectures, like any other software artifact, are subject to changes during their lifecycle, and thus can undergo an evolution phenomenon. In this phenomenon, it is argued that quality can be weakened after successive changes (Lehman's 7th law of software evolution), and this is mainly due to the lack of architecture documentation and tool support to supervise architecture changes. In this paper, we present an approach to supervise the evolution of Web service orchestrations, with quality requirements considered as a support documentation. First, we show how important design decisions, like the choice of a service-oriented architecture pattern can be formalized as a documentation for the quality they implement. Then, we detail how this documentation can be used to supervise architecture changes. In this way, the impact of changes made on a software architecture are analyzed on-the-fly to determine which quality is affected.