Class-Based Component Design: Principles & Process

Lesson Transcript
Instructor: David Gloag

David has over 40 years of industry experience in software development and information technology and a bachelor of computer science

In this lesson, we'll take a look at class-based component design, the key principles that guide it, and the process used to implement it. At the end, you should have a good understanding of this design method. Updated: 09/22/2022

Moving Parts

We live in a world that has many moving parts. Just consider the objects around you: your laptop, your cell phone, or your car. They are complex objects, with hundreds if not thousands of moving parts. But even a simple object, such as a pen, has a number of moving parts. Software systems mirror this fact. Many pieces or parts interact to provide the functionality you expect. Take, for instance, a cell phone's instant messaging app. You have a part that displays information on the screen, another to capture the text you type, and still another that sends the information to the person at the other end of the connection. One way these parts are managed is to use the concept of components.

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: Component-Level Design: Steps & Examples

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
Your next lesson will play in 10 seconds
  • 0:04 Moving Parts
  • 0:47 Software Components
  • 1:21 Class-Based Component Design
  • 1:59 Key Principles of…
  • 2:43 Implementation
  • 3:51 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Speed Speed

Software Components

A software component is a self-contained piece of software that contains or encapsulates a known set of operational units, relationships, and behaviors. Think of them as the building blocks for a system. You combine any number of these components to get the capabilities you desire. Often, they can be combined in more than one way. For example, consider a common bicycle. The wheels are considered a component, the handlebars are considered a component, and the seat is considered another component. Each provides an important piece of the whole.

Class-Based Component Design

Class-based component design is a method for designing software components using a class to represent the component in question. A class is a collection of related data items and the operations needed to manipulate those items.

Consider for a moment the email application on your personal computer. One component of this system might be an email message. If we define a class called ''EmailMessage,'' then a data item might be ''message,'' and an operation that can be performed on ''message'' might be ''SendMessage.'' It's likely that this will have more data and operations defined, but you get the idea.

Key Principles of Component Design

Because classes are used in this type of component design, they follow the same key principles. These include:

To unlock this lesson you must be a Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use

Become a member and start learning now.
Become a Member  Back

Resources created by teachers for teachers

Over 30,000 video lessons & teaching resources‐all in one place.
Video lessons
Quizzes & Worksheets
Classroom Integration
Lesson Plans

I would definitely recommend to my colleagues. It’s like a teacher waved a magic wand and did the work for me. I feel like it’s a lifeline.

Jennifer B.
Jennifer B.
Create an account to start this course today
Used by over 30 million students worldwide
Create an account