A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf
.
Filters
Software Evolution: A Trip Through Reflective, Aspect, and Meta-data Oriented Techniques
[chapter]
2005
Lecture Notes in Computer Science
Following the example provided by these venues, the RAM-SE (Reflection, AOP and Meta-Data for Software Evolution) workshop has provided an opportunity for researchers with a broad range of interests in ...
01 and AOSD since 2002) have pointed out the growing interest on these topics and their relevance in the software evolution as techniques for code instrumentation. ...
We wish to thank Yvonne Coady, Günter Kniesel, Hidehiko Masuhara, and Joseph Yoder both for their interest in the workshop, and for their help during the workshop and in writing part of this report. ...
doi:10.1007/978-3-540-30554-5_12
fatcat:ecpn25nixzhzdfp2alothwvfum
Hyper/J™ supports flexible, multi-dimensional separation of concerns for Java™ software. ...
This demonstration shows how to use Hyper/J in some important development and evolution scenarios, empahsizing the software engineering benefits it provides. ...
INTRODUCTION Separation of concerns is at the core of software engineering. ...
doi:10.1145/337180.337618
dblp:conf/icse/OssherT00
fatcat:qoriaoywqfdg5ninb5aljtkjt4
Software requirements and architecture modeling for evolving non-secure applications into secure applications
2007
Science of Computer Programming
This paper describes an approach to modeling the evolution of non-secure applications into secure applications in terms of the software requirements model and software architecture model. ...
By separating application concerns from security concerns, the evolution from a non-secure application to a secure application can be achieved with less impact on the application. ...
In the evolution of a non-secure application to a secure application, security concerns in the software requirements model and software architecture need to be separated from application concerns, so that ...
doi:10.1016/j.scico.2006.10.009
fatcat:owhcnrubmrdstbpfdqvwbowqkq
Metrics for Evolution of Aspect Oriented Software
[article]
2020
arXiv
pre-print
This paper defines a new set of metrics for measuring the evolution of Aspect Oriented software. ...
Aspect Oriented Software Development (AOSD) is a promising methodology which provides powerful techniques to improve the modularity of the software by separating the cross-cutting concerns from the core ...
AOSD enhances the separation of concerns, improves the software reusability and reduces complexity. ...
arXiv:2010.05479v2
fatcat:c2jihkotnbe2jaqitpgvubocbu
A Reflective Approach to Dynamic Software Evolution
2004
European Conference on Object-Oriented Programming
We present a preliminary reflective framework that allows dynamic evolution of separate concerns. Problem Statement An intrinsic property of a successful software application is its need to evolve. ...
We propose aspect mining and static refactorings for separating those concerns. In a second step, we allow every concern to evolve separately. ...
Towards Dynamic Software Evolution Once we are dealing with well modularized applications -applications with no cross-cutting concerns -we want to allow every module to evolve separately. ...
dblp:conf/ecoop/EbraertT04
fatcat:n5lre3u6rjbz5lkxovs5lxfxaa
Evolution Issues in Aspect-Oriented Programming
[chapter]
2008
Software Evolution
It can serve as a guideline for adopters of aspect technology to get a better idea of the evolution issues they may confront sooner or later, of the risks involved, and of the state-of-the-art in the techniques ...
The discussed issues range from the exploration of crosscutting concerns in legacy code, via the migration of this code to an aspect-oriented solution, to the maintenance and evolution of the final aspectoriented ...
The evolution stage then deals with the evolution of the final aspectoriented software, and how this differs from the evolution of ordinary software. ...
doi:10.1007/978-3-540-76440-3_9
dblp:series/springer/MensT08
fatcat:ymraoz7pi5hc5ai3zgbpjqppli
Improving the Software Quality using AOP
2013
CVR Journal of Science & Technology
All the software engineering methodologies are expected to recognize the concerns of a system like the aspect-oriented software development (AOSD). ...
Concerns exist at every level of the system development process. The goal of modularization is to build application software that is maintainable and reusable. ...
AOSD provides a way for a structured and efficient way to handle the crosscutting concerns in the system. We use AOP, a method for improving separation of concerns in software [1] . ...
doi:10.32377/cvrjst0503
fatcat:sl6stypsyzfjdappy3jb3vdbei
Software Architecture Evolution
[chapter]
2008
Software Evolution
Furthermore, we discuss one particular framework for software architecture evolution in more detail. ...
This chapter provides an overview, comparison and detailed treatment of the various state-of-the-art approaches to evolving software architectures. ...
The external evolution is studied in particular through the separation of concerns issue in a software architecture. ...
doi:10.1007/978-3-540-76440-3_10
dblp:series/springer/BaraisMDL08
fatcat:r4b45sqjiff4zdcvb75ojmgcni
Predilection of Reusability over Maintainability in Aspect-Oriented Systems
2007
INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY
Maintenance is the important phase in software development lifecycle which initiates after the software has been deployed for use. ...
Maintainability is one of the contributing factors for assessing Reusability. So, assessment of Reusability is preferred over Maintainability. ...
An iterative model for software evolution Software evolution shows that even if the implementations of the software is correct and fulfill the requirements, the software has to be updated on regular basis ...
doi:10.24297/ijct.v6i3.4482
fatcat:lsntkrgkabgdld4wg4kjv6fwyi
Multi-Dimensional Separation of Concerns and the Hyperspace Approach
[chapter]
2002
Software Architectures and Component Technology
Separation of concerns is at the core of software engineering, and has been for decades. This has led to the invention of many interesting, and effective, modularization approaches. ...
Multi-dimensional separation of concerns allows simultaneous separation according to multiple, arbitrary kinds (dimensions) of concerns, with on-demand remodularization. ...
INTRODUCTION
Separation of concerns [par72] is at the core of software engineering. ...
doi:10.1007/978-1-4615-0883-0_10
fatcat:s5sesx7gdvednp6lv67nblmahy
Software engineering tools and environments
2000
Proceedings of the conference on The future of Software engineering - ICSE '00
They are becoming increasingly crucial as the demand for software increases, time-to-market decreases, and diversity and complexity grow beyond anything imagined a few decades ago. ...
In this paper, we briefly review some of the history of tools and environments in software engineering, and then discuss some key challenges that we believe the field faces over the next decade. ...
and Tappan Parikh for assistance with the literature search. ...
doi:10.1145/336512.336569
dblp:conf/icse/OssherHT00
fatcat:2cyxxezutfd3vekynfvs6mwzai
Ndegrees of separation
1999
Proceedings of the 21st international conference on Software engineering - ICSE '99
Done well, separation of concerns can provide many software engineering benefits, including reduced complexity, im- ...
ACKNOWLEDGEMENTS Joyce Vann, Mark Wegman, and the reviewers provided valuable feedback on earlier versions of this paper. Siobhbn Clarke produced the SEE design in. UML. ...
All modern software formalisms support separation of concerns to some extent, through mechanisms for decomposition and composition. ...
doi:10.1145/302405.302457
dblp:conf/icse/TarrOHS99
fatcat:s6yfdkkbrfdhlbfmklvawbwgfa
Formal foundations of software evolution
2001
Software engineering notes
This paper summarises the results of the discussions held during the workshop on Formal Foundations of Software Evolution in Lisbon on March 13, 2001. ...
These results can be used as guidelines when dealing with software evolution in general, and when providing formal tool support for it in particular. ...
Acknowledgements We thank Juan Ramil for his many comments and suggestions on a draft of this report. ...
doi:10.1145/505482.505488
fatcat:eb6eubevsvcbzit34ov24cttki
Workshop on the Modeling and Analysis of Concerns in Software (MACS 2005)
2005
Software engineering notes
The main goal of the workshop was to bring together researchers and practitioners with interest in techniques for modeling and analyzing the realization of concerns in software systems to support software ...
development and evolution. ...
software development and evolution, and to explore the potential for integration and interoperability in concern analysis and modeling techniques. ...
doi:10.1145/1082983.1082995
fatcat:kydjpkwkr5avjkdphcr7mepoay
R-Rio (poster session)
2000
Addendum to the 2000 proceedings of the conference on Object-oriented programming, systems, languages, and applications (Addendum) - OOPSLA '00
Separation of concerns is a key goal in achieving software reusability. ...
Meta-Level Programming approaches pave the way to separation of concerns by handling functional and non-functional aspects in different levels, but provide little help for software composition, verification ...
This integration helps to achieve separation of concerns and improve software reuse. ...
doi:10.1145/367845.367960
dblp:conf/oopsla/SztajnbergL00
fatcat:hjlqjfd2lfcuhflnajxizoewbe
« Previous
Showing results 1 — 15 out of 284,617 results