Object-Oriented Programming Key Concepts | 面向对象考点精讲

📚 Object-Oriented Programming Key Concepts | 面向对象考点精讲

Object-Oriented Programming (OOP) is a fundamental paradigm that organises software design around data, or objects, rather than functions and logic. For both IB Computer Science and Edexcel A-Level specifications, a deep understanding of classes, objects, encapsulation, inheritance, and polymorphism is essential. This article breaks down each concept with clear explanations, practical examples, and exam-style insights to help you master OOP and score top marks.

面向对象编程（OOP）是一种以数据（即对象）而非函数和逻辑为中心来组织软件设计的基本范式。对于 IB 计算机和 Edexcel A-Level 大纲而言，深刻理解类、对象、封装、继承和多态至关重要。本文通过清晰的解释、实用的示例和应试要点，逐一剖析每个概念，帮助你掌握 OOP 并获取高分。

1. Classes and Objects: The Blueprint and the Instance | 类与对象：蓝图与实例

A class is a user-defined data type that serves as a template for creating objects. It defines the attributes (data) and methods (behaviours) that the objects of that type will have. In exam terms, you must be able to identify classes from a scenario and represent them using UML class diagrams or code snippets. An object is an instance of a class, a concrete entity that occupies memory and can interact with other objects at runtime.

类是用户自定义的数据类型，用作创建对象的模板。它定义了该类型对象将拥有的属性（数据）和方法（行为）。在考试中，你必须能够从场景中识别类，并使用 UML 类图或代码片段来表示它们。对象是类的一个实例，是一个占用内存并能在运行时与其他对象交互的具体实体。

For example, a class Car might have attributes like colour, model, and speed, and methods like accelerate() and brake(). Each individual car (a red Toyota, a blue Ford) is an object of that class. In code, you create an object using the class constructor: myCar = new Car(“red”, “Toyota”). The IB syllabus emphasises distinguishing between class definitions and object instantiation.

例如，Car 类可能具有 colour、model 和 speed 等属性，以及 accelerate() 和 brake() 等方法。每辆具体的汽车（一辆红色的丰田、一辆蓝色的福特）都是该类的一个对象。在代码中，使用类的构造函数创建对象：myCar = new Car(“red”, “Toyota”)。IB 大纲强调要区分类的定义与对象的实例化。

Exam tip: know the difference between static (class) members and instance members. Static attributes or methods belong to the class itself, not to any particular object, and are shared across all instances. A common exam question asks you to underline or identify a static variable in a code fragment.

应试提示：了解静态（类）成员与实例成员的区别。静态属性或方法属于类本身，而非任何特定对象，并在所有实例之间共享。常见的考题会要求你在一段代码中划出或识别出静态变量。

2. Encapsulation: Data Hiding and Access Control | 封装：数据隐藏与访问控制

Encapsulation bundles the data and the methods that operate on that data within a single unit (the class) and restricts direct access to some of an object’s internal components. This is implemented through access modifiers such as private, public, and protected. The primary goal is to protect the integrity of the data and to hide the implementation details from the user. Both IB and Edexcel require you to explain encapsulation and justify its benefits.

封装将数据和操作这些数据的方法捆绑在一个单元（类）中，并限制对对象内部某些组件的直接访问。这是通过 private、public 和 protected 等访问修饰符实现的。其主要目标是保护数据的完整性，并向用户隐藏实现细节。IB 和 Edexcel 都要求你解释封装并说明其优点。

Typically, attributes are declared private, and public getter and setter methods provide controlled access. For instance, a BankAccount class should keep its balance attribute private. A public method deposit(amount) can modify the balance only if the amount is valid, preventing direct and potentially incorrect manipulation of the balance by external code. This makes the system more robust and easier to maintain.

通常，属性声明为私有的，而公共的 getter 和 setter 方法提供受控访问。例如，BankAccount 类应将 balance 属性保持为私有。公共方法 deposit(amount) 只有在金额有效时才能修改余额，从而阻止外部代码直接且可能不正确地操作余额。这使系统更健壮且更易于维护。

In an exam answer, clearly state that encapsulation enhances security, reduces complexity, and increases modularity. You can also mention that it facilitates the principle of “separation of concerns”, where changes to the internal representation of data do not affect other parts of the program that rely solely on the public interface.

在考试答案中，要明确指出封装增强了安全性、降低了复杂性并提高了模块化。你还可以提到它有利于“关注点分离”原则，即对数据内部表示的更改不会影响程序中仅依赖公共接口的其他部分。

3. Inheritance: Building Hierarchies and Reusing Code | 继承：构建层次结构与代码复用

Inheritance allows a new class (subclass or derived class) to acquire the properties and methods of an existing class (superclass or base class). This promotes code reuse and establishes a natural hierarchical relationship. The keyword extends (in Java) or the colon : (in Python and C#) is used to implement inheritance.

继承允许一个新类（子类或派生类）获取现有类（超类或基类）的属性和方法。这促进了代码复用并建立了自然的层次关系。关键字 extends（Java 中）或冒号 :（Python 和 C# 中）用于实现继承。

For instance, a Dog class can inherit from a Mammal class. The Dog automatically has attributes such as species and methods like breathe(), while adding its own specific behaviour like bark(). In UML diagrams, inheritance is shown by a hollow triangle arrow pointing from the subclass to the superclass. Edexcel exams frequently feature inheritance diagrams that you must interpret or extend.

例如，Dog 类可以继承自 Mammal 类。Dog 自动拥有 species 等属性和 breathe() 等方法，同时添加自己特有的行为如 bark()。在 UML 图中，继承用从子类指向超类的空心三角箭头表示。Edexcel 考试经常包含你必须解读或扩展的继承图。

Important concepts to master include method overriding (redefining a superclass method in a subclass) and the use of the super keyword to call the constructor or methods of the parent class. Understand the difference between single inheritance (one superclass) and multiple inheritance, and note that Java only supports single inheritance of classes but can simulate multiple inheritance through interfaces. This is a common exam nuance.

需要掌握的重要概念包括方法重写（在子类中重新定义超类方法）以及使用 super 关键字调用父类的构造函数或方法。要理解单继承（一个超类）和多继承之间的区别，并注意 Java 只支持类的单继承，但可以通过接口模拟多继承。这是考试中常见的细微差别。

4. Polymorphism: Many Forms, One Interface | 多态：多种形态，一个接口

Polymorphism, meaning “many shapes”, allows objects of different classes to be treated as objects of a common superclass. The most common type is dynamic polymorphism (runtime polymorphism), where a method call is resolved at runtime based on the actual type of the object, not the reference type. This enables a single interface to represent different underlying forms (data types). Edexcel and IB both expect you to describe and exemplify polymorphism with code or examples.

多态意为“多种形态”，它允许将不同类的对象视为共同的超类对象。最常见的类型是动态多态（运行时多态），此时方法调用在运行时根据对象的实际类型而非引用类型进行解析。这使得单个接口可以表示不同的底层形式（数据类型）。Edexcel 和 IB 都要求你用代码或示例描述和举例多态。

Consider a superclass Animal with a method speak(). Subclasses Cat and Dog override speak() to produce “Meow” and “Woof” respectively. A reference variable of type Animal can point to a Cat or a Dog object. When speak() is called, the correct version is executed automatically. The classic example in exam papers involves an array of superclass references iterating and calling a common method, demonstrating polymorphism.

考虑一个具有 speak() 方法的超类 Animal。子类 Cat 和 Dog 重写 speak() 分别产生“喵”和“汪”。一个 Animal 类型的引用变量可以指向一个 Cat 或 Dog 对象。当调用 speak() 时，会自动执行正确的版本。试卷中的经典例子涉及一个超类引用数组遍历并调用共同的方法，以展示多态。

Don’t forget static polymorphism (compile-time polymorphism), achieved through method overloading. Methods with the same name but different parameter lists (number, type, or order of parameters) allow a class to provide multiple implementations. While not always explicitly termed polymorphism by IB, it is often tested in code tracing questions. A constructor overloading is a typical simple example.

不要忘记静态多态（编译时多态），它通过方法重载实现。名称相同但参数列表（参数数量、类型或顺序）不同的方法允许一个类提供多种实现。虽然 IB 不一定总是明确称之为多态，但在代码追踪题中经常考到。构造函数重载就是一个典型的简单例子。

5. Abstract Classes and Interfaces | 抽象类与接口

Abstract classes and interfaces are crucial mechanisms to enforce a contract for subclasses. An abstract class cannot be instantiated; it may contain a mix of fully implemented methods and abstract methods (without a body). An interface defines a set of method signatures that a class must implement, supporting the design principle of “programming to an interface, not an implementation”. Both IB and Edexcel test your ability to distinguish and apply these structures.

抽象类和接口是为子类强制规定契约的关键机制。抽象类不能被实例化；它可以包含完全实现的方法和抽象方法（没有方法体）的混合。接口定义了一组方法签名，类必须实现这些方法，这支持了“面向接口编程而非面向实现编程”的设计原则。IB 和 Edexcel 都会测试你区分和应用这些结构的能力。

A classic exam question asks: “When would you use an abstract class versus an interface?” The answer often revolves around whether you need to share code (abstract class can provide some common implementation) versus simply specifying a capability (interface). For example, a Java Comparable interface ensures an object can be compared, while an abstract Shape class might provide a color field but leave area() abstract. Remember that a class can implement multiple interfaces but only extend one abstract class.

经典的考题会问：“何时使用抽象类而非接口？”答案通常围绕着是需要共享代码（抽象类可以提供一些公共实现）还是仅仅指定一种能力（接口）。例如，Java 中的 Comparable 接口确保对象可以进行比较，而抽象的 Shape 类可能提供一个 color 字段，但将 area() 留给子类实现。请记住，一个类可以实现多个接口，但只能继承一个抽象类。

In UML class diagrams, abstract classes and methods are shown in italics, and interfaces are marked with the «interface» stereotype or an italicised name in some styles. Make sure you know the correct notation. Recent specifications also refer to Java interfaces as completely abstract but note that Java 8+ allows default methods.

在 UML 类图中，抽象类和方法用斜体表示，接口用 «interface» 构造型或某些风格中的斜体名称标记。请确保你了解正确的表示法。最近的大纲也将 Java 接口称为完全的抽象，但注意 Java 8 以上版本允许默认方法。

6. Association, Aggregation, and Composition | 关联、聚合与组合

Understanding the different types of relationships between objects is essential for designing software and for answering UML-based questions. Three important “has-a” relationships reinforce encapsulation and reusability.

理解对象之间不同类型的关系对于设计软件和回答基于 UML 的问题至关重要。三种重要的“拥有关”系强化了封装和可复用性。

Association is a generic relationship where one object knows about another, e.g., a Teacher teaches a Student. It is shown by a simple line in UML. Aggregation is a specific type of association representing a “whole-part” relationship where the part can exist independently of the whole. For instance, a Library contains Books, but a book can exist without a library. In UML, aggregation is shown with a hollow diamond on the “whole” side.

关联是一种通用关系，表示一个对象知道另一个对象，例如 Teacher 教 Student。在 UML 中用一条简单的线表示。聚合是一种特殊的关联，表示“整体-部分”关系，其中部分可以独立于整体存在。例如，Library 包含 Books，但书可以脱离图书馆存在。在 UML 中，聚合用“整体”端的空心菱形表示。

Composition is a stronger form of aggregation where the part cannot exist without the whole. A House comprises Rooms, and if the house is destroyed, the rooms cease to exist. It is depicted by a filled diamond in UML. Exam questions often ask you to identify the type of relationship from a scenario and draw the correct UML notation. Differentiating aggregation from composition is a high-frequency topic.

组合是一种更强的聚合形式，其中部分不能脱离整体存在。一个 House 由多个 Rooms 组成，如果房子被毁，房间也就不存在了。在 UML 中用实心菱形表示。考题常要求你先从场景中识别关系类型，再画出正确的 UML 符号。区分聚合和组合是一个高频考点。

7. Constructor and Overloading | 构造方法与重载

Constructors are special methods invoked when an object is created. They typically initialise instance variables. A default constructor is provided by the compiler if no constructor is defined, but once you define any constructor, the default is lost. This often appears in tricky code output questions. Edexcel and IB expect you to be able to trace execution of constructors, including chaining with super() and this().

构造方法是创建对象时调用的特殊方法。它们通常用于初始化实例变量。如果没有定义构造方法，编译器会提供一个默认构造方法，但一旦你定义了任何构造方法，默认构造方法就不复存在了。这经常出现在棘手的代码输出题中。Edexcel 和 IB 要求你能够追踪构造方法的执行过程，包括使用 super() 和 this() 的链式调用。

Constructor overloading is the practice of providing multiple constructors with different parameter lists in the same class. This allows objects to be initialised in different ways, promoting flexibility. A common exam scenario gives you a class with several constructors and asks for the output when creating an object with certain arguments, or requires you to write a constructor that reuses another constructor via this(…).

构造方法重载是在同一个类中提供具有不同参数列表的多个构造方法的做法。这使得对象可以以不同的方式进行初始化，从而提高了灵活性。常见的考试场景是给你一个包含多个构造方法的类，并要求你在使用特定参数创建对象时给出输出，或者要求你编写一个通过 this(…) 复用另一个构造方法的构造方法。

8. Access Modifiers and Scope | 访问修饰符与作用域

Access modifiers dictate the visibility and scope of class members. For IB and Edexcel, you need to know:

访问修饰符决定了类成员的可见性和作用域。对于 IB 和 Edexcel，你需要了解：

public: accessible from any other class. public：可以从任何其他类访问。
private: accessible only within the declaring class. private：只能在声明类内部访问。
protected: accessible within the same package and by subclasses, even in different packages. protected：可在同一个包内以及子类中访问，即使在不同包中也可以。
default (package-private): accessible only within the same package (Java). default（包私有）：只能在同一个包内访问（Java）。

Exam questions frequently involve a scenario where a subclass attempts to access a private member of its superclass directly. This is illegal; access must go through public or protected getters/setters. Understanding scope helps you debug and predict compiler errors, a skill tested in code-reading sections.

考题经常涉及子类试图直接访问其超类的私有成员的场景。这是非法的；必须通过公共或受保护的 getter/setter 进行访问。理解作用域有助于你调试和预测编译错误，这是在代码阅读部分测试的一项技能。

9. Overriding vs. Overloading | 重写与重载

These terms are often confused. A table of differences can help clarify:

这两个术语经常被混淆。一个差异表有助于澄清：

Aspect \| 方面	Overriding (Runtime polymorphism) \| 重写（运行时多态）	Overloading (Compile-time polymorphism) \| 重载（编译时多态）
Parameter list	Must be the same	Must be different
Return type	Same or covariant	May differ
Belongs to	Subclass (parent class also has it)	Same class (or across inheritance)
Annotation (Java)	@Override	No special annotation

A classic trick: a method with the same name but different parameter list in a subclass is simply an overloaded method, not an override, unless it exactly matches the parent signature. Be precise in your vocabulary during exams.

一个经典陷阱：子类中与父类方法同名但参数列表不同的方法仅仅是重载方法，而非重写，除非其签名与父类完全匹配。在考试中措辞一定要精确。

10. SOLID Principles and Exam Relevance | SOLID 原则及其考试相关性

While full SOLID treatment may be beyond the basic syllabus, several principles map directly to OOP features you have learned. The Single Responsibility Principle (a class should have only one reason to change) ties to encapsulation and cohesion. The Open/Closed Principle (open for extension, closed for modification) is demonstrated through inheritance and polymorphism. The Liskov Substitution Principle states that objects of a superclass should be replaceable with objects of its subclasses without affecting the correctness of the program – a core tenet of proper polymorphism.

尽管完整的 SOLID 论述可能超出了基础大纲范围，但其中几条原则与你所学的 OOP 特性直接对应。单一职责原则（一个类应该只有一个发生变化的原因）与封装和内聚力相联系。开闭原则（对扩展开放，对修改封闭）通过继承和多态来体现。里氏替换原则指出，超类的对象应该能够用其子类的对象替换，而不影响程序的正确性——这是正确使用多态的核心原则。

Edexcel has occasionally featured questions about why a particular OOP design is poor, expecting reference to these principles. IB might ask you to evaluate a given design. Therefore, knowing that a well-designed OOP system should be modular, extensible, and maintainable will strengthen high-band answers.

Edexcel 偶尔会出现关于某个 OOP 设计为何不佳的题目，期望引用这些原则。IB 可能会要求你评估给定的设计。因此，了解一个设计良好的 OOP 系统应该是模块化、可扩展且可维护的，将有助于加强高分答案。

11. Unified Modeling Language (UML) Class Diagrams | UML 类图

Both IB and Edexcel require you to interpret and sometimes draw UML class diagrams. A class is represented as a rectangle divided into three compartments: class name, attributes, and operations. Visibility markers (+ public, – private, # protected) are placed before each attribute and method. Relationships such as inheritance (hollow triangle), association (solid line), aggregation (hollow diamond), and composition (filled diamond) must be correctly illustrated.

IB 和 Edexcel 都要求你会解读并有时绘制 UML 类图。一个类表示为一个分为三个隔间的矩形：类名、属性和操作。可见性标记（+ 公共，– 私有，# 受保护）放在每个属性和方法之前。必须正确表示继承（空心三角形）、关联（实线）、聚合（空心菱形）和组合（实心菱形）等关系。

When drawing a diagram, underline static members and italicise abstract classes or methods. Multiplicity (e.g., 1, 0..1, * , 1..* ) should be placed on association ends to indicate how many objects participate in the relationship. A very common error is mixing the direction of the dependency; always read the scenario carefully to place arrows correctly.

绘制图表时，用下划线标记静态成员，用斜体标记抽象类或方法。多重性（例如 1、0..1、*、1..*）应放在关联端，以指示参与关系的对象数量。一个非常常见的错误是混淆依赖关系的方向；始终仔细阅读场景，正确设置箭头方向。

12. Practical Exam Advice and Common Pitfalls | 实用考试建议与常见陷阱

To ace OOP questions, practise reading and tracing code that combines classes, inheritance, and polymorphism. Common pitfalls include forgetting that private members are not inherited in the sense of direct access, misunderstanding the difference between super() for constructors and super.method() for method calls, and assuming all methods with the same name are overrides.

要在 OOP 题目中取得好成绩，请多练习阅读和追踪结合了类、继承和多态的代码。常见陷阱包括忘记私有成员在直接访问的意义上不可被继承，误解构造函数的 super() 与方法调用的 super.method() 之间的区别，以及假设所有同名方法都是重写。

When answering “explain” or “evaluate” style questions, structure your response: define the concept, state its purpose, give a concrete code or real-world example, and mention at least one advantage and one disadvantage or limitation. For IB Paper 2 and Edexcel pseudocode/structured English tasks, always keep your solutions object-oriented if the question context points that way, using appropriate access modifiers and meaningful class names.

在回答“解释”或“评价”类题目时，要组织好回答：定义概念，说明其目的，给出具体的代码或现实例子，并至少提及一个优点和一个缺点或局限性。对于 IB 试卷二和 Edexcel 伪代码/结构化英语任务，如果题目上下文指向 OOP，始终让你的解决方案面向对象，使用适当的访问修饰符和具有意义的类名。

Published by TutorHao | IB Edexcel Computer Science Revision Series | aleveler.com

更多咨询请联系16621398022（同微信）

Object-Oriented Programming Key Concepts | 面向对象考点精讲