Managing Concern Interfaces

@article{Boulanger2006ManagingCI,
  title={Managing Concern Interfaces},
  author={Jean-S{\'e}bastien Boulanger and Martin P. Robillard},
  journal={2006 22nd IEEE International Conference on Software Maintenance},
  year={2006},
  pages={14-23}
}
Programming languages provide various mechanisms to support information hiding. One problem with information hiding, however, is that providing a stable interface behind which to hide implementation details involves fixing in advance the services offered through the interface. We introduce a flexible approach to define and manage interfaces to achieve separation of concerns in evolving software. Our approach involves explicitly specifying interface and implementation classes for individual… CONTINUE READING

Figures, Tables, and Topics from this paper.

Citations

Publications citing this paper.

References

Publications referenced by this paper.
SHOWING 1-10 OF 15 REFERENCES

JDepend

M. Clark
  • Clarkware Consulting, Inc.
  • 2006
VIEW 1 EXCERPT

Towards a framework for testing structural source-code regularities

  • 21st IEEE International Conference on Software Maintenance (ICSM'05)
  • 2005
VIEW 1 EXCERPT

Use Access Rules to Enforce API Engagement Rules

R. J. Lorimer
  • EclipseZone,
  • 2005
VIEW 1 EXCERPT

S

W. Harrison, H. Ossher
  • Sutton Jr., and P. Tarr. Concer n modeling in the concern manipulation environment. Technical Report RC23344, IBM Research
  • 2004
VIEW 2 EXCERPTS

FEAT a tool for locating, describing, and analyzing concerns in source code

  • 25th International Conference on Software Engineering, 2003. Proceedings.
  • 2003
VIEW 2 EXCERPTS

ArchJava: connecting software architecture to implementation

  • Proceedings of the 24th International Conference on Software Engineering. ICSE 2002
  • 2002
VIEW 2 EXCERPTS