Views for tools in integrated environments
An international workshop on Advanced programming environments
The Z notation: a reference manual
The Z notation: a reference manual
An introduction to partial evaluation
ACM Computing Surveys (CSUR)
Partial evaluation and separate compilation
PEPM '97 Proceedings of the 1997 ACM SIGPLAN symposium on Partial evaluation and semantics-based program manipulation
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Separating features in source code: an exploratory study
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Workshop on advanced separation of concerns in software engineering
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
A Discipline of Programming
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
The Role of the Base in Aspect Oriented Programming
Proceedings of the Workshop on Object-Oriented Technology
Program Specialization via Program Slicing
Selected Papers from the Internaltional Seminar on Partial Evaluation
Workshop on Directions in Software Engineering Environments (WoDiSEE)
Proceedings of the 26th International Conference on Software Engineering
Spotlight: A Prototype Tool for Software Plans
ICSE '07 Proceedings of the 29th international conference on Software Engineering
| Hi-index | 0.00 |
Even in well-designed software, some concerns can not be easily encapsulated due to their dependence on surrounding context. Such concerns are intermingled with each other and the context code, making it difficult for developers to reason independently about them. We have introduced software plans as an editor-based approach for addressing the tangling of context-dependent concerns. Software plans provide programmers with partial views of the overall software which present only that code related to concerns of current interest. The problem we address is that the traditional sequence-of-characters representation for code is poorly suited for software plans. It lacks the ability to accurately model the concerns associated with a code block, the relationships between code blocks, and the notion of multiple independent plans. In this paper, we present a formally-defined code/concern model that supports these capabilities and more. Using this model, we were able to implement a prototype editing tool that supports software plans.