LCLow Coupling

"Each piece of the system should know as little as possible about the other pieces."

Key Takeaways

Make sure program parts don't depend too much on each other.
With low coupling, changing one part won't mess up others.
It's easier to fix and update programs that have less tangled parts.

Description

Coupling is how much one part of a program knows about another. Too much coupling means changes can cause problems everywhere, making the system hard to keep up.

Low Coupling is about keeping parts of a program separate so they can work on their own. This makes the system easier to manage because changing one part doesn't affect the others much.

"The goal of software architecture is to minimize the human resources required to build and maintain the required system." - Robert C. Martin

The less the parts of a program rely on each other, the stronger and more flexible the whole system is when things need to be fixed or improved.

You might also like:

ADP

APO

BSR

CCP

CoI

CQS

CRP

DIP

DRY

EUHM

EWV

FF

FTSE

GRASP

HC

HLYW

IH

IoC

IOSP

ISP

KISS

LC

LoD

LOLA

LSP

OCP

POLP

POLS

PoMO

REP

RoT

RTFM

SAP

SDB

SDP

SLA

SoC

SOLDIER

SOLID

SPOT

SRP

TdA

WET

YAGNI

ZOI