Real time example of interface

I can provide two types of "real world" examples -- one from the business world and onw from the true "real world."
Real World:
You have an Animal class. It is an abstract class, because you cannot instantiate a generic "Animal," but it provides base functionality.
You have many devired classes of Animal. You have HomoSapiens, Platypus, Penguin (which extends Bird, another subclass of Animal), Giraffe, Housefly, etc. Each of these are concrete classes that may be instantiated (of course, there are several levels of abstract classes between these and Animal (like Chordata, etc.)
Now you want to make something fly. What can fly? Birds and Houseflys (among others), so these classes should provide similar functionality, even though they are widely spaced on our inheritance tree. The solution? Make them use interfaces. Bird and Housefly can not both implement the Flyer interface, so whenever we want something to fly, we can use a Flyer object, not caring whether it's a Bird or a Housefly. Likewise, Penguins and Playtpuses can implement the Swimmer interface (and Penguin should throw an IllegalOperationException in any of its Flyer methods, since Penguins cannot fly).
As far as business examples, I have a persistance engine that will work against any data sourcer (XML, ASCII (delimited and fixed-length), various JDBC sources (Oracle, SQL, ODBC, etc.) I created a base, abstract class to provide common functionality in this persistance, but instantiate the appropriate "Port" (subclass) when persisting my objects. (This makes development of new "Ports" much easier, since most of the work is done in the superclasses; especially the various JDBC ones; since I not only do persistance but other things [like table generation], I have to provide the various differences for each database.)
The best business examples of Interfaces are the Collections. I can work with a java.util.List without caring how it is implemented; having the List as an abstract class does not make sense because there are fundamental differences in how an ArrayList works as opposed to a LinkedList. Likewise, Map and Set. And if I am just working with a group of objects and don't care if it's a List, Map, or Set, I can just use the Collection interface.
Hope that this helps

Interfaces are used to encode similarities which classes share, but do not necessarily constitute a class relationship. For instance, a dog and a lion can both run. We would make them inherit the Animal class and then implement Run via an interface IRun.

A beginner book might help you learn this as well.

Go through the below link you can get a good example of Interface and abstract class in very easy language

http://shivasoft.in/blog/java/difference-between-interfaceinheritance-abstract-class/[^]

You can also go through the below link in which there was a discussion of interface and abstract classes... which will help you to understand concept more

Real world examples of abstract classes and interfaces?[^]

Best Explanation will be like
Interface is a contract agreement and class that implements is builder.
When you go to buy a house you put an agreement to a builder with requirements you want one window, two bedrooms, two bath rooms etc(these are interface declaration) and the class which inherits interface is builder, failing to implements any of the requirements is violation of agreement (throws compilation error failing to implements any of the interface method.
Hope this help better understanding