Skip to main content

Interfaces

  • Chapter
  • First Online:
Object-Oriented Design with ABAP
  • 1389 Accesses

Abstract

The ubiquitous GUI interface enables people to interact with a software system. Many ABAP programmers are familiar with the acronym RICEF, in which the ā€œIā€ represents Interfaces and most often is associated with data exchanges with external systems.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    It also is known as a ā€œstand-alone interface.ā€

  2. 2.

    It is for this reason that I hesitate to include the definitions of variables in the set of components offered by an interface, since they would be publicly visible, hence modifiable by external entities. Although not technically prohibited, the inclusion of variables in interface definitions should be avoided by programmers not wanting to violate the principles of encapsulation.

  3. 3.

    The format of invoking a method as shown here is intended to be language independent, but closely resembles the format found with both Java and ABAP.

  4. 4.

    The attribute values shown for this entry represent those for the Navajo Generating Station near Page, Arizona, which consumes about 8 million tons of coal per year. Accordingly, its values shown for capacity in fuel unit and current level in fuel unit represent a 60-day and 30-day supply, respectively.

  5. 5.

    See http://courses.cs.washington.edu/courses/cse403/96sp/coupling-cohesion.html .

  6. 6.

    A case can be made that loose coupling also occurs when an instance of a subclass is referenced as an instance of one of its superclasses; however, such an arrangement depends on class inheritance and limits the flexibility to within the same inheritance hierarchy. By contrast, interfaces are not limited by such constraints.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

Ā© 2017 James E. McDonough

About this chapter

Cite this chapter

McDonough, J.E. (2017). Interfaces. In: Object-Oriented Design with ABAP. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2838-8_7

Download citation

Publish with us

Policies and ethics