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
Software architecture in practice
Software architecture in practice
A study on exception detection and handling using aspect-oriented programming
Proceedings of the 22nd international conference on Software engineering
Designing robust Java programs with exceptions
SIGSOFT '00/FSE-8 Proceedings of the 8th ACM SIGSOFT international symposium on Foundations of software engineering: twenty-first century applications
Component-based product line engineering with UML
Component-based product line engineering with UML
Component Software: Beyond Object-Oriented Programming
Component Software: Beyond Object-Oriented Programming
Transaction Processing: Concepts and Techniques
Transaction Processing: Concepts and Techniques
Feature Interaction and Dependencies: Modeling Features for Reengineering a Legacy Product Line
SPLC 2 Proceedings of the Second International Conference on Software Product Lines
Response to undesired events in software systems
ICSE '76 Proceedings of the 2nd international conference on Software engineering
The Past, Present, and Future for Software Architecture
IEEE Software
EJFlow: taming exceptional control flows in aspect-oriented programming
Proceedings of the 7th international conference on Aspect-oriented software development
Evolving software product lines with aspects: an empirical study on design stability
Proceedings of the 30th international conference on Software engineering
A method for modeling and testing exceptions in component-based software development
LADC'05 Proceedings of the Second Latin-American conference on Dependable Computing
Components meet aspects: Assessing design stability of a software product line
Information and Software Technology
| Hi-index | 0.00 |
Separation of concerns is one of the overarching goals of exception handling in order to keep separate normal and exceptional behaviour of a software system. In the context of a software product line (SPL), this separation of concerns is also important for designing software variabilities related to different exception handling strategies, such as the choice of different handlers depending on the set of selected features. This paper presents a method for refactoring object-oriented product line architecture in order to separate explicitly their normal and exceptional behaviour into different software components. The new component-based software architecture includes variation points related to different choices of exception handlers that can be selected during product instantiations, thus facilitating the evolution of the exceptional behaviour. The feasibility of the proposed approach is assessed through a SPL of mobile applications.