Sign In | Subscribe

Enter your Sign on user name and password.

Forgot password?
  • Follow us on:
Start learning today, and be successful in your academic & professional career. Start Today!
Loading video...
This is a quick preview of the lesson. For full access, please Log In or Sign up.
For more information, please see full course syllabus of Visual Basic
  • Discussion

  • Study Guides

  • Table of Contents

Start Learning Now

Our free lessons will get you started (Adobe Flash® required).
Get immediate access to our entire library.

Sign up for

Membership Overview

  • Unlimited access to our entire library of courses.
  • Search and jump to exactly what you want to learn.
  • *Ask questions and get answers from the community and our teachers!
  • Practice questions with step-by-step solutions.
  • Download lesson files for programming and software training practice.
  • Track your course viewing progress.
  • Download lecture slides for taking notes.
  • Learn at your own pace... anytime, anywhere!

Introduction to Object Oriented Programming

  • Everything is an “object”
  • Objects should be separate from other objects or loosely coupled
  • Objects are “instantiated,” you create an instance of an object
  • System.Object is the base class of everything in the .Net Framework
  • The five basic principles of OOP are idealized in the SOLID programming model
    • S = Single Responsibility
      • Do one thing only
      • Do one thing completely
      • Do one thing well
    • O = Open-Closed
      • Open for extension
      • Closed for modification
    • L = Liskov Substitution
      • Derived (child) class should be able to replace the Base (parent) class without problems
    • I = Interface Segregation
      • Each interface should do one thing only
      • Interfaces should be independent
    • D = Dependency Inversion
      • Objects should be minimally coupled
  • Tableware follows object-oriented design very well
  • Abstraction is generalizing something specific
  • Encapsulation is also called the “black box” effect
  • Inheritance creates a hierarchical structure
  • Method overloading uses the same function name, but uses different parameter lists
  • Method overriding replaces the base class implementation of a method
  • Polymorphism lets you create an object with more than one form
    • Operator overloading is the most common form
    • Not the same as overloading or overriding
  • Accessibility levels lets you restrict access to only approved assemblies