Generated from prompt:
以“设计模式自学：设计原则与单例、原型模式”为主题的学习汇报PPT，内容包括： 1. 封面：主题《设计模式自学：设计原则与单例/原型模式》，汇报人姓名（杨佩瑶）和学号（2023032438）。 2. 学习目标：理解面向对象设计七大原则，掌握单例与原型模式。 3. 七大设计原则： - 单一职责原则（SRP） - 开闭原则（OCP） - 里氏替换原则（LSP） - 接口隔离原则（ISP） - 依赖倒置原则（DIP） - 迪米特法则（LoD） - 合成复用原则（CRP） 每个原则包括定义、反面案例、正面案例与小结。 4. 单例模式介绍： - 定义、特点与应用场景。 - Android InputMethodManager 示例分析。 5. 原型模式介绍： - 定义与用途。 - 示例：对象克隆实现与深浅拷贝比较。 6. 设计原则与模式的联系：原则指导模式设计，模式体现原则。 7. 学习心得与总结：学习设计原则帮助提升架构思维，单例与原型模式是创建型模式的核心。 风格：科技感、蓝色系、简洁结构化，适合课程汇报展示。
This presentation covers self-study on design patterns, focusing on the seven OOP principles (SRP, OCP, LSP, ISP, DIP, LoD, CRP) with definitions, counterexamples, and positives. It introduces Singlet
This title slide introduces a self-study presentation on design patterns, focusing on design principles along with the Singleton and Prototype patterns. It credits the presenter as Yang Peiyao with student ID 2023032438.
汇报人：杨佩瑶 学号：2023032438
This slide outlines the learning objectives for a session on object-oriented design, focusing on grasping the core principles of the seven key OOP design principles. It also covers mastering the concepts, applications, and implementations of the singleton and prototype patterns, while applying these principles to practical pattern usage.
This slide serves as a section header titled "七大设计原则" (Seven Major Design Principles), marking it as Section 03. It introduces the SOLID principles along with extended rules to improve code design quality.
03
介绍SOLID原则及扩展法则，帮助提升代码设计质量
The Single Responsibility Principle (SRP) states that a class should handle only one responsibility. For example, separating user management from data storage into distinct classes like UserManager and Database reduces coupling and improves maintainability, avoiding the complexity of multifunctional classes.
The Open-Closed Principle (OCP) states that software entities should be open for extension but closed for modification. The slide illustrates this with a negative example where adding new shapes requires altering the Draw class, contrasted by a positive approach using an abstract Shape interface and polymorphism, enabling flexible extension through inheritance and interfaces.
The Liskov Substitution Principle (LSP) states that subclasses must be substitutable for their parent classes without affecting program correctness, ensuring inheritance reliability. A counterexample is a Square subclass breaking Rectangle's area calculations, while a positive example involves subclasses strictly adhering to the parent class's contract.
The Interface Segregation Principle (ISP) states that clients should not depend on interfaces they do not use, avoiding the pitfalls of large interfaces that force unrelated classes to implement unnecessary methods. Instead, it advocates breaking down interfaces into smaller, focused ones—like IPrint for printing and IScan for scanning—to enhance system flexibility and maintainability.
The Dependency Inversion Principle (DIP) states that high-level modules should not depend on low-level modules; both should rely on abstractions to promote flexibility. The slide contrasts negative examples, like directly instantiating concrete classes which hinder maintenance, with positive ones using interface-based dependency injection for easy replacement, ultimately reducing coupling and enhancing testability and extensibility.
Source: 设计原则
The Law of Demeter (LoD), also known as the Demeter Principle, advises that classes should only communicate with their direct friends to minimize indirect dependencies. The slide contrasts a negative example of directly calling a private method in another class with a positive approach of interacting via public interfaces, ultimately reducing system coupling.
The Composite Reuse Principle (CRP) defines the preference for using composition over inheritance to reuse functionality in software design. It highlights negative examples like excessive inheritance causing fragile base class issues, contrasted with positive cases such as a Car class incorporating an Engine component, ultimately concluding that composition offers greater flexibility and avoids inheritance misuse.
This slide introduces the Singleton design pattern as section 04. It explains that the pattern ensures a class has only one instance while providing a global access point to it.
04
确保类只有一个实例，并提供全局访问点。
The Singleton design pattern ensures a class has only one instance and provides a global access point to it. It features support for global access, lazy loading, and thread safety, with common applications in configuration managers for unified parameter settings and loggers for a single output channel.
The slide analyzes Android's InputMethodManager, highlighting its singleton implementation via the getInstance() method to ensure a single system-wide instance, avoiding conflicts from multiple managers and providing unified input control. It outlines advantages like preventing resource competition and maintaining global consistency, alongside drawbacks such as global state issues that complicate testing and risk state pollution.
| 单例实现机制 | 优势与缺点 |
|---|---|
| InputMethodManager 通过 getInstance() 方法实现单例模式，确保系统中只有一个输入法管理器实例。这避免了多个实例同时管理输入法导致的冲突，提供统一的输入控制接口。（28 字） | 优势：防止多实例竞争资源，确保输入法管理的全局一致性。缺点：引入全局状态，可能导致测试困难和状态污染问题，需要谨慎使用。（32 字） |
This slide introduces the Prototype design pattern as section 05. It explains that the pattern enables creating new objects by cloning existing ones, thereby avoiding repetitive initialization processes.
05
通过克隆现有对象创建新对象，避免重复初始化。
The Prototype pattern is defined as using a prototype instance to specify object types and creating new objects through cloning, typically by implementing the Cloneable interface or a custom clone method. It is useful for efficiently copying complex objects to avoid repeated initialization, such as in game development for duplicating character attributes and states, ultimately reducing creation costs and enhancing system performance and flexibility.
Shallow copy replicates only the object's reference without duplicating its sub-objects, causing shared modifications between the original and copy, which suits simple structures to minimize overhead. Deep copy recursively clones the object and all nested sub-objects for full independence, as exemplified by Java's Cloneable interface and clone() method, ensuring changes to one do not affect the other.
| 浅拷贝（Shallow Copy） | 深拷贝（Deep Copy） |
|---|---|
| 浅拷贝仅复制对象的引用，而不复制子对象本身。原对象与拷贝对象共享子对象引用，导致修改一方会影响另一方。适用于简单数据结构，避免不必要的深层复制开销。（约25字） | 深拷贝递归复制对象及其所有嵌套子对象，确保拷贝完全独立。修改拷贝不会影响原对象。示例：在Java中使用Cloneable接口实现clone()方法，进行完整对象克隆。（约28字） |
Design principles guide the creation of design patterns, as seen in how the Open-Closed Principle (OCP) is embodied in singleton pattern extensions. Design patterns, in turn, embody these principles—such as the Singleton following the Single Responsibility Principle (SRP) and the Prototype pattern supporting Dependency Inversion (DIP)—with principles serving as the foundation and patterns as practical tools.
Studying design principles enhances architectural thinking and enables the creation of more robust code. Singleton and prototype patterns, as core creational modes, are highly applicable in practical development like Android, with plans to explore other patterns in the future.
- 学习设计原则提升架构思维，帮助编写更robust代码。
感谢聆听，学习不止！
Source: 设计模式自学汇报
Explore thousands of AI-generated presentations for inspiration
Generate professional presentations in seconds with Karaf's AI. Customize this presentation or start from scratch.