Subject-oriented programming: a critique of pure objects
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
IEEE Transactions on Software Engineering
Systemic classification of concern-based design methods in the context of enterprise architecture
Information Systems Frontiers
The paradoxical success of aspect-oriented programming
Proceedings of the 21st annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Proceedings of the 6th international conference on Aspect-oriented software development
Typed parametric polymorphism for aspects
Science of Computer Programming - Special issue: Foundations of aspect-oriented programming
Modeling Product Line Architectures through Change Sets and Relationships
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Aspect-oriented in-lined reference monitors
Proceedings of the third ACM SIGPLAN workshop on Programming languages and analysis for security
Transactions on Aspect-Oriented Software Development V
Feature-oriented programming with Ruby
FOSD '09 Proceedings of the First International Workshop on Feature-Oriented Software Development
Domain-Specific languages in few steps: the neverlang approach
SC'12 Proceedings of the 11th international conference on Software Composition
Comparing program comprehension of physically and virtually separated concerns
FOSD '12 Proceedings of the 4th International Workshop on Feature-Oriented Software Development
| Hi-index | 0.00 |
Hyper/J supports a new approach to constructing, integrating and evolving software, called multi-dimensional separation of concerns. It addresses a number of common problems in the development, evolution, and integration of large-scale, complex software systems, helping to achieve many goals of software engineering. These include: improved comprehension and reduced complexity of software; non-invasive adaptation and customization, promoting off-the-shelf reuse; the ability to synthesize, compose, and integrate separate pieces of software into new pieces of software; the ability to extract new concerns from existing software, non-invasively; non-invasive, low-impact evolution; and improved ability to allow multiple, decentralized teams to work on different, but overlapping, parts of software simultaneously, thus reducing development bottlenecks and promoting more rapid software development.