ACM Home Page
Please provide us with feedback. Feedback
When to use an interface?
Full text PdfPdf (331 KB)
Source ACM SIGCSE Bulletin archive
Volume 38 ,  Issue 2  (June 2006) table of contents
COLUMN: Featured column table of contents
Pages: 86 - 90  
Year of Publication: 2006
ISSN:0097-8418
Author
Chenglie Hu  Carroll College, Waukesha, Wisconsin
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 43,   Citation Count: 0
Additional Information:

abstract   references   index terms  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1138403.1138440
What is a DOI?

ABSTRACT

Interface, as an object-oriented programming construct, has been one of the most difficult concepts for students to understand and apply properly. Textbooks often only address the shallow side of usefulness of interfaces, and some may even mislead as to when and how an interface should be used. This article argues that the interfaces can only be effectively taught in a context of program design. The material is appropriate to be included in a second course on programming.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Dale, N. et al. Object-Oriented data Structures Using Java, Jones and Bartlett, 2002
 
2
Farrell, J. Java Programming, 3rd Ed, Course Technology, 2006
 
3
Malin, D. S. Java, Programming -- from problem analysis to program design, 2nd Ed, Course Technology, 2006
 
4
The Java#8482; Tutorial. Retrieved 11/25/2005, from http://java.sun.com/docs/books/tutorial/java/concepts/interface.html
 
5
Shalloway, A. & Trott, J. Design Patterns Explained, Addison Wesley, 2005