New Feature: Playlist Center! Pick a topic and let our playlists guide the way.

Start learning with our library of video tutorials taught by experts. Get started

Foundations of Programming: Object-Oriented Design
Illustration by Mark Todd
Watching:

Identifying inheritance situations


From:

Foundations of Programming: Object-Oriented Design

with Simon Allardice

Video: Identifying inheritance situations

Earlier we talked about inheritance being one of the four key concepts of object-orientation. We're going to get a little deeper into it now. Even if you never wrote your own classes that used inheritance, you will still use it. In most object-oriented languages, you're using inheritance all the time, there's no getting away from it. Now, the best simplest easiest way of identifying an inheritance situation is with two words, "Is A". Inheritance describes an "Is A" relationship, and this is not a technical term, this is plain language.
Expand all | Collapse all
  1. 11m 35s
    1. Welcome
      1m 25s
    2. Who this course is for
      1m 15s
    3. What to expect from this course
      3m 6s
    4. Exploring object-oriented analysis, design, and development
      1m 41s
    5. Reviewing software development methodologies
      4m 8s
  2. 26m 14s
    1. Why we use object-orientation
      2m 42s
    2. What is an object?
      5m 22s
    3. What is a class?
      4m 43s
    4. What is abstraction?
      2m 45s
    5. What is encapsulation?
      3m 45s
    6. What is inheritance?
      3m 35s
    7. What is polymorphism?
      3m 22s
  3. 12m 16s
    1. Understanding the object-oriented analysis and design processes
      4m 13s
    2. Defining requirements
      6m 9s
    3. Introduction to the Unified Modeling Language (UML)
      1m 54s
  4. 23m 35s
    1. Understanding use cases
      6m 11s
    2. Identifying the actors
      4m 16s
    3. Identifying the scenarios
      5m 7s
    4. Diagramming use cases
      4m 18s
    5. Employing user stories
      3m 43s
  5. 16m 36s
    1. Creating a conceptual model
      1m 59s
    2. Identifying the classes
      2m 27s
    3. Identifying class relationships
      2m 38s
    4. Identifying class responsibilities
      6m 43s
    5. Using CRC cards
      2m 49s
  6. 22m 25s
    1. Creating class diagrams
      6m 11s
    2. Converting class diagrams to code
      4m 57s
    3. Exploring object lifetime
      5m 55s
    4. Using static or shared members
      5m 22s
  7. 19m 49s
    1. Identifying inheritance situations
      6m 49s
    2. Using inheritance
      2m 43s
    3. Using abstract classes
      2m 2s
    4. Using interfaces
      4m 20s
    5. Using aggregation and composition
      3m 55s
  8. 9m 23s
    1. Creating sequence diagrams
      5m 18s
    2. Working with advanced UML diagrams
      2m 3s
    3. Using UML tools
      2m 2s
  9. 10m 39s
    1. Introduction to design patterns
      2m 40s
    2. Example: the singleton pattern
      4m 53s
    3. Example: the memento pattern
      3m 6s
  10. 21m 47s
    1. Introduction to object-oriented design principles
      2m 50s
    2. Exploring general development principles
      3m 55s
    3. Introduction to SOLID principles
      6m 43s
    4. Introduction to GRASP principles
      8m 19s
  11. 7m 1s
    1. Reviewing feature support across different object-oriented languages
      3m 50s
    2. Additional resources
      2m 27s
    3. Goodbye
      44s

Watch this entire course now—plus get access to every course in the library. Each course includes high-quality videos taught by expert instructors.

Become a member
please wait ...
Foundations of Programming: Object-Oriented Design
3h 1m Intermediate May 22, 2012

Viewers: in countries Watching now:

Most modern programming languages, such as Java, C#, Ruby, and Python, are object-oriented languages, which help group individual bits of code into a complex and coherent application. However, object-orientation itself is not a language; it's simply a set of ideas and concepts.

Let Simon Allardice introduce you to the terms—words like abstraction, inheritance, polymorphism, subclass—and guide you through defining your requirements and identifying use cases for your program. The course also covers creating conceptual models of your program with design patterns, class and sequence diagrams, and unified modeling language (UML) tools, and then shows how to convert the diagrams into code.

Topics include:
  • Why use object-oriented design (OOD)?
  • Pinpointing use cases, actors, and scenarios
  • Identifying class responsibilities and relationships
  • Creating class diagrams
  • Using abstract classes
  • Working with inheritance
  • Creating advanced UML diagrams
  • Understanding object-oriented design principles
Subjects:
Developer Design Patterns Programming Foundations
Software:
Java
Author:
Simon Allardice

Identifying inheritance situations

Earlier we talked about inheritance being one of the four key concepts of object-orientation. We're going to get a little deeper into it now. Even if you never wrote your own classes that used inheritance, you will still use it. In most object-oriented languages, you're using inheritance all the time, there's no getting away from it. Now, the best simplest easiest way of identifying an inheritance situation is with two words, "Is A". Inheritance describes an "Is A" relationship, and this is not a technical term, this is plain language.

We're back to the idea of how would you talk about things in the real world? So, forget about classes and objects for a second and just look at a few sentences. So could you say something like a car is a vehicle? Well, yes! How about a bus is a vehicle? Well, yes. That makes sense too. But what about a car is a bus? Well, no, you wouldn't say that. You would say something like an employee is a person or a customer is a person.

Those make sense, but a customer is a shopping cart does not. Instead of just is a, you could say is a kind of or is a type of, but it's the same thing. So, a checking account is a kind of bank account, a savings account is a type of bank account. We naturally understand these ideas. We can talk like that. We know what makes sense and what doesn't. We know that we can have multiple levels of this, a Bentley Continental is a car which is a vehicle, a Pomeranian is a dog which is a mammal which is an animal.

An inheritance is taking this idea, this form of abstraction that we do naturally in font and language, and it's bringing it into programming. It's to allow us to identify that there might be some shared attributes and behaviors between our objects, and if we think about it, we can save some time and not reinvent the wheel. So here's where some people hit their first problem. They start sketching out a variety of classes, picking the nouns out of their written descriptions, and as we scan it, we can tell there's some relationship between say Bank and Bank Account, and we wonder well is that an inheritance relationship? And there is the question. Could you say a bank account is a bank? Well, no, you wouldn't say that, neither would I say a bank is a bank account.

So there might be a relationship here, but it's not inheritance. But you could say a checking account is a bank account or a savings account is a bank account, and it's a clue that we might be able to share some behavior in this area. But it's always that is a question. That should make sense when you talk about it in natural plain language. In UML, inheritance is shown with the open arrow that looks like a wedge, one class points to the object it is inheriting from, otherwise called its superclass or parent class.

And as soon as we say we're inheriting, we are considered the subclass or the child class, and we automatically have all the attributes and behaviors from the class we're inheriting from. So, in this case, BankAccount is the parent class or the superclass, CheckingAccount, SavingsAccount, InvestmentAccount, these are classes that would be considered subclasses or child classes. We bring in all the attributes and behaviors from the superclass, from the parent class, and then we can start adding some extra information.

Sometimes we may want to change one of the behaviors we inherit from the superclass, and many languages allow a subclass to replace the implementation of a method defined in that super or parent class, and this is called overriding, and it lets us have more flexibility. Most commonly, it's not just to replace but to do some behavior in addition to the inherited behavior. Now, a word of warning, it is common for new object-oriented developers to overemphasize inheritance and to come up with class diagrams with five levels for everything. Avoid this.

Don't go looking for inheritance and don't stare at classes trying to figure out what their superclasses must be, because inheritance announces itself. You start building your classes for say a digital storefront, and you start creating things like album and book and movie. You will notice if they start sharing a lot of common behaviors and attributes, say in this case, we realize that we're sharing title and price as attributes and purchase and download as behaviors. So you may then create a superclass trying to identify what's common between them all while they're all products, and we'll create that.

We'll strip out the similar behaviors, and put them in that superclass, in that parent class. So, we can identify and choose that commonality, and then we will inherit from that class, but it should be obvious. Now sometimes it will be identified from the bottom-up, sometimes from the top-down, you'll realize you have to create some more specialized classes. But let it occur naturally, and if you create one or two class diagrams without any inheritance, that's not a problem. But do realize that inheritance is often vitally important in understanding existing object-oriented programming environments, because the frameworks that you'll use in Java.NET, Objective-C, Ruby, and others often use inheritance substantially, because they're trying to provide generic and extensible frameworks rather than writing a specific application.

In Java, for example, there is a built in FileDialog class which we can use. Well, it inherits from a Dialog class which inherits from the Window class, which inherits from the more generic Container class which inherits from the Component class, which inherits from the most generic base Object class. In fact, everything in Java inherits from Object at the end of the day, same with a lot of other languages, Objective-C, C#, VB.NET.

Even if you don't say you're actually inheriting, you always are. You're inheriting from something usually called Object, a base Object class, and that's what I mean about the fact that you're always inheriting, even if you don't say so. However, even though you'll find this level of inheritance in some of the frameworks you'll use, it's very unlikely for a specific business or consumer application to need anything like this level of inheritance. In fact, you should look very carefully even if you're going beyond one or two levels of inheritance.

And up next, I'm going to show a few examples of how we might go ahead and implement that in a language.

There are currently no FAQs about Foundations of Programming: Object-Oriented Design.

 
Share a link to this course

What are exercise files?

Exercise files are the same files the author uses in the course. Save time by downloading the author's files instead of setting up your own files, and learn by following along with the instructor.

Can I take this course without the exercise files?

Yes! If you decide you would like the exercise files later, you can upgrade to a premium account any time.

Become a member Download sample files See plans and pricing

Please wait... please wait ...
Upgrade to get access to exercise files.

Exercise files video

How to use exercise files.

Learn by watching, listening, and doing, Exercise files are the same files the author uses in the course, so you can download them and follow along Premium memberships include access to all exercise files in the library.
Upgrade now


Exercise files

Exercise files video

How to use exercise files.

For additional information on downloading and using exercise files, watch our instructional video or read the instructions in the FAQ.

This course includes free exercise files, so you can practice while you watch the course. To access all the exercise files in our library, become a Premium Member.

join now Upgrade now

Are you sure you want to mark all the videos in this course as unwatched?

This will not affect your course history, your reports, or your certificates of completion for this course.


Mark all as unwatched Cancel

Congratulations

You have completed Foundations of Programming: Object-Oriented Design.

Return to your organization's learning portal to continue training, or close this page.


OK
Become a member to add this course to a playlist

Join today and get unlimited access to the entire library of video courses—and create as many playlists as you like.

Get started

Already a member?

Become a member to like this course.

Join today and get unlimited access to the entire library of video courses.

Get started

Already a member?

Exercise files

Learn by watching, listening, and doing! Exercise files are the same files the author uses in the course, so you can download them and follow along. Exercise files are available with all Premium memberships. Learn more

Get started

Already a Premium member?

Exercise files video

How to use exercise files.

Ask a question

Thanks for contacting us.
You’ll hear from our Customer Service team within 24 hours.

Please enter the text shown below:

The classic layout automatically defaults to the latest Flash Player.

To choose a different player, hold the cursor over your name at the top right of any lynda.com page and choose Site preferencesfrom the dropdown menu.

Continue to classic layout Stay on new layout
Exercise files

Access exercise files from a button right under the course name.

Mark videos as unwatched

Remove icons showing you already watched videos if you want to start over.

Control your viewing experience

Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.

Interactive transcripts

Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.

Are you sure you want to delete this note?

No

Notes cannot be added for locked videos.

Thanks for signing up.

We’ll send you a confirmation email shortly.


Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

Keep up with news, tips, and latest courses with emails from lynda.com.

Sign up and receive emails about lynda.com and our online training library:

Here’s our privacy policy with more details about how we handle your information.

   
submit Lightbox submit clicked
Terms and conditions of use

We've updated our terms and conditions (now called terms of service).Go
Review and accept our updated terms of service.