> For the complete documentation index, see [llms.txt](https://krjaeh0.gitbook.io/j-log/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://krjaeh0.gitbook.io/j-log/programming/software-design/solid/solidprinciples.md).

# SOLIDPrinciples

* 객체 지향 프로그래밍과 설계에 있어 효과적이고 유지보수가 용이하며 확장 가능한 소프트웨어 개발을 위한 다섯가지 원칙
* 각 글자는 하나의 설계 원칙을 나타낸다.

### [**S - 단일 책임 원칙 (Single Responsibility Principle)**](broken://pages/1707fdf1d8535226f344524422c52ab360ffad42)

### [**O - 개방-폐쇄 원칙 (Open-Closed Principle)**](broken://pages/1707fdf1d8535226f344524422c52ab360ffad42)

### [**L - 리스코프 치환 원칙 (Liskov Substitution Principle)**](broken://pages/74a9f1c79864b7f7d7e1893f5df01af30faed1bf)

### [**I - 인터페이스 분리 원칙 (Interface Segregation Principle)**](broken://pages/55b04aaa2c6a205e4f304ae938002d8684738c9d)

### [**D - 의존성 역전 원칙 (Dependency Inversion Principle)**](broken://pages/c4f1233b6bf481c51e6b8df34c61038d661eb49b)

{% hint style="info" %}
소프트웨어의 설계가 좀 더 유연하고, 변경에 용이하며, 이해하기 쉽고, 유지 관리가 편리하도록 도와준다.\
각 원칙은 개별적으로 중요하지만, 함께 사용될 때 가장 강력하다.\
원칙들을 적용함으로써 개발자는 더 나은 소프트웨어 아키텍쳐를 설계할 수 있으며, 대규모 시스템에서 발생할 수 있는 많은 일반적인 문제들을 예방할 수 있다.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://krjaeh0.gitbook.io/j-log/programming/software-design/solid/solidprinciples.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.