Managing concern interfaces

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2006, Pages 14-23

  Boulanger, Jean Sébastien ^a   Robillard, Martin P ^a  

^a MCGILL UNIVERSITY   (Canada)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING LANGUAGES; DATA HANDLING; INFORMATION SERVICES; NETWORK MANAGEMENT; SOFTWARE ENGINEERING;

INFORMATION HIDING; INTERFACE MANAGEMENT; SOFTWARE EVOLUTION;

USER INTERFACES;

EID: 34547240990     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSM.2006.35     Document Type: Conference Paper

References (18)

1. J. Aldrich, C. Chambers, and D. Notkin. ArchJava: Connecting software architecture to implementation. In Proceedings of the 24th International Conference on Software Engineering, pages 187-197, 2002.
2. M. Clark. JDepend. Clarkware Consulting, Inc., 2006. http://www.clarkware.com/software/JDepend.html.
3. S. Ducasse and M. Lanza. The Class Blueprint: Visually supporting the understanding of classes. IEEE Transactions on Software Engineering, 31(1):75-90, 2005.
4. E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns-Elements of Reusable Object-Oriented Software. Professional Computing Series. Addison-Wesley Longman, Inc., 1995.
5. J. Y. Gil and I. Maman. Micro patterns in Java code. In Proceedings of the 20th Conference on Object oriented Programming, Systems, Languages, and Applications, pages 97-116, 2005.
6. W. Harrison, H. Ossher, S. Sutton Jr., and P. Tarr. Concern modeling in the concern manipulation environment. Technical Report RC23344, IBM Research, 2004.
7. IBM. Structural Analysis for Java, 2004. http://-www.alphaworks. ibm.com/tech/sa4j.
8. R. J. Lorimer. Use Access Rules to Enforce API Engagement Rules. EclipseZone, Novem-ber 2005. http://www.eclipsezone.com/forums/-thread.jspa? messageID=91952212.
9. N. Medvidovic and R. N. Taylor. A classification and comparison framework for software architecture description languages. IEEE Transactions on Software Engineering, 26(1):70-93, 2000.
10. K. Mens and A. Kellens. Towards a framework for testing structural source-code regularities. In Proceedings of the 21st IEEE International Conference on Software Maintenance, pages 679-682, 2005.
11. K. Mens, R. Wuyts, and T. D'Hondt. Declaratively codifying software architectures using virtual software classifications. In Proceedings of TOOLS-Europe 99, pages 33-45, 1999.
12. G. C. Murphy, D. Notkin, and K. J. Sullivan. Software reflexion models: Bridging the gap between design and implementation. IEEE Transactions on Software Engineering, 27(4), April 2001.
13. D. L. Parnas. On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15(12): 1053-1058, December 1972.
14. M. P. Robillard and G. C. Murphy. FEAT: a tool for locating, describing, and analyzing concerns in source code. In Proceedings of the 25th International Conference on Software Engineering, pages 822-823, 2003.
15. M. P. Robillard and R Weigand-Warr. ConcernMapper: Simple view-based separation of scattered concerns. In Proceedings of the Eclipse Technology Exchange at OOPSLA, 2005.
16. Sun Microsystems, Inc. Java Transaction API (JTA), Version 1.0.1, April 1999.
17. Sun Microsystems, Inc. JavaMail™ API Design Specification, Version 1.2, September 2000.
18. A. S. Tanenbaum and M. van Steen. Distributed Systems Principles and Paradigms. Prentice-Hall, Inc., 2002.