JavaML: a markup language for Java source code
Proceedings of the 9th international World Wide Web conference on Computer networks : the international journal of computer and telecommunications netowrking
Using transformation systems for software maintenance and reengineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Handling crosscutting constraints in domain-specific modeling
Communications of the ACM
Semi-automatic grammar recovery
Software—Practice & Experience
Implementing distribution and persistence aspects with aspectJ
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Proceedings of the 2nd international conference on Aspect-oriented software development
Proceedings of the 2nd international conference on Aspect-oriented software development
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
ACM SIGPLAN Notices - Special issue: History of programming languages conference
Next Generation Data Interchange: Tool-to-Tool Application Program Interfaces
WCRE '00 Proceedings of the Seventh Working Conference on Reverse Engineering (WCRE'00)
A Framework for Migrating Procedural Code to Object-Oriented Platforms
APSEC '01 Proceedings of the Eighth Asia-Pacific on Software Engineering Conference
Language-independent aspect-oriented programming
OOPSLA '03 Proceedings of the 18th annual ACM SIGPLAN conference on Object-oriented programing, systems, languages, and applications
Aspects: from promise to reality
Proceedings of the 3rd international conference on Aspect-oriented software development
Proceedings of the 3rd international conference on Aspect-oriented software development
A technique for constructing aspect weavers using a program transformation engine
Proceedings of the 3rd international conference on Aspect-oriented software development
Large-scale AOSD for middleware
Proceedings of the 3rd international conference on Aspect-oriented software development
Cona: aspects for contracts and contracts for aspects
OOPSLA '04 Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications
Architectural modifications to deployed software
Science of Computer Programming
Revitalizing modifiability of legacy assets: Research Articles
Journal of Software Maintenance and Evolution: Research and Practice - Seventh European Conference on Software Maintenance and Reengineering (CSMR 2003)
Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information
Aspect-orientation For Revitalising Legacy Business Software
Electronic Notes in Theoretical Computer Science (ENTCS)
Symbiosis in logic-based pointcuts over a history of join points
Proceedings of the 2008 ACM symposium on Applied computing
GRID '07 Proceedings of the 8th IEEE/ACM International Conference on Grid Computing
Journal of Systems and Software
AspectMatlab: an aspect-oriented scientific programming language
Proceedings of the 9th International Conference on Aspect-Oriented Software Development
Program analysis environment for writing COBOL aspects
Proceedings of the 9th International Conference on Aspect-Oriented Software Development
A model-driven framework for aspect weaver construction
Transactions on aspect-oriented software development VIII
Separation of concerns with procedures, annotations, advice and pointcuts
ECOOP'05 Proceedings of the 19th European conference on Object-Oriented Programming
Term rewriting meets aspect-oriented programming
Processes, Terms and Cycles
FATES'06/RV'06 Proceedings of the First combined international conference on Formal Approaches to Software Testing and Runtime Verification
Hi-index | 0.00 |
We study AOP in the context of business programming with Cobol. We face the following questions: What are join points in Cobol programs? What is advice? Does classic Cobol provide any constructs that hint at AOP? (Yes!) What are typical crosscutting concerns in the Cobol world? How do otherwise typical crosscutting concerns make sense for Cobol? How does AOP for Cobol align with classic re-engineering transformations for Cobol? We deliver an AOP language design for Cobol. Codename: AspectCobol. While we adopt several ideas from AspectJ and friends, we also devise original techniques for joint-point identification and context capture. We briefly discuss a prototypical implementation of AspectCobol.