패턴 이름 한글화

프로그래밍 설계 패턴은 개발자가 수년간의 실전을 통해서 체득한 좋은 관습, 경험을 하나의 이름을 통해서 범주화, 체계화한 것이기 때문에, 어떠한 설계 패턴에 자신이 일상적으로 사용하는 언어로 된 이름을 붙이는 것이 매우 중요하리라 생각합니다.

외국 사람들이 이미 식별, 분류한 패턴 이름들은 대부분 영어로 되어 있는데요. 단지 이름이 영문이라서 생소해 보일 뿐, 우리나라 개발자들이라고 그러한 패턴(이 유용하게 쓰일만한 상황)을 겪어보지 못했을 리는 없습니다.. 단지 그럴듯한 이름을 붙이지 않았을 뿐이죠.

이에 기존의 영문 패턴 이름들을 한글화하는 작업을 제안합니다. 일단 Wiki:GangOfFour의 Wiki:DesignPatternsBook에 나오는 패턴들부터 시작하는 게 좋겠죠... 패턴 범주와 개별 패턴들을 나열하고, 그 아래에 그 패턴 범주 또는 패턴을 가장 잘 나타낼 수 있는 한글 이름을 추가하는 식으로..

단순한 번역이 아니라, 각 패턴의 의미를 가장 잘 나타낼 수 있는 말을 고르는 작업이므로, 각 패턴에 대한 이해가 필요할 것 같습니다... 한글이나 한자어, 외래어 모두 가능하구요.

참 따옴표 친 영문은 Wiki:DesignPatternsBook의 서문에 나온 요약문입니다..

--류광


^ 목적

^Creational

범위

클래스

Factory Method

객체

Abstract Factory, Builder,
Prototype, Singleton

Adapter (객체), Bridge, Composite,
Decorator, Facade, Flyweight

Creational Patterns

제안:

생성 패턴들

Abstract Factory

:'Provide an interface for creating families of related or dependent objects without specifying their concrete classes.'

제안:

Builder

:'Separate the construction of a complex object from its representation so that the same construction process can create different representations.'

제안:

Factory Method

:'Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.'

제안:

Prototype

:'Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.'

제안:

Singleton

:'Ensure a class only has one instance, and provide a global point of access to it.'

제안:

Structural 패턴들

제안:

Adapter

:'Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.'

제안:

Bridge

:'Decouple an abstraction from its implementation so that the two can vary independently.'

제안:

Composite

:'Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.'

제안:

Decorator

:'Attach additional responsibilities to an object dynamically. Decorators provide a flexible alternative to subclassing for extending functionality.'

제안:

Facade

:'Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.'

제안:

Flyweight

:'Use sharing to support large numbers of fine-grained objects efficiently.'

제안:

Proxy

:'Provide a surrogate or placeholder for another object to control access to it.'

제안:

Behavioral Patterns

제안:

Chain Of Responsibility

:'Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.'

제안:

Command

:'Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.'

제안:

Interpreter

:'Given a language, define a represention for its grammar along with an interpreter that uses the representation to interpret sentences in the language.'

제안:

Iterator

:'Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.'

제안:

Mediator

:'Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly and it lets you vary their interaction independently.'

제안:

Memento

:'Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.'

제안:

Observer

:'Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.'

제안:

State

:'Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.'

제안:

Strategy

:'Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.'

제안:

Template Method

:'Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template Method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.'

제안:

Visitor

:'Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.'

제안:


분류:설계패턴분류:용어