search

isaqb-org / glossary

An extensive glossary of software architecture (and development) terminology. Explains the terms used and referenced in the iSAQB foundation and advanced level curricula.
https://leanpub.com/isaqbglossary
35 stars 16 forks source link

Add term "connascence" #192

Closed ichsteffen closed 1 year ago

ichsteffen commented 1 year ago

Do we need to add the term "connascence" as addition to "cohesion" and "coupling"?

English: "Connascence"

"Two pieces of software share connascence when a changes in one requires a corresponding change in the other."

Deutsch "Konnaszenz"

"Zwei Komponenten sind konnaszent, wenn eine Änderung in einer Komponente eine Änderung der anderen erfordert, um die Gesamt-Korrektheit des Systems aufrechtzuerhalten."

Originalquelle: Meilir Page-Jones, "What Every Programmer Should Know About Object-Oriented Design" (Dorset House), 1996

Hruschka commented 1 year ago

The terms connascence and encumbrance never became popular.

Meilir tried to extend coupling and cohesion to the OO-world - but iMHO he failed. The words were too complex, the idea was already well covered by the terms coupling and cohesion.

We should not make the same mistake. Coupling and cohesion are good enough. The rest is for historians (like me :-))

Peter

Dr. Peter Hruschka Atlantic Systems Guild Langenbruchweg 71 52080 Aachen

Lesen Sie unser neues Buch arc42 by Example - Vol2: Embedded Systems and IOT https://leanpub.com/arc42byexample-volume2

und besuchen Sie unseren Youtube Kanal Culture at Work https://www.youtube.com/channel/UCTVbsawKYlYyr8L0wgL2byQ für einige Gedanken über gutes und schlechtes Betriebsklima.

Am 20.03.2023 um 15:24 schrieb Steffen Späthe @.***>:

Do we need to add the term "connascence" as addition to "cohesion" and "coupling"?

English: "Connascence"

"Two pieces of software share connascence when a changes in one requires a corresponding change in the other."

Deutsch "Konnaszenz"

"Zwei Komponenten sind konnaszent, wenn eine Änderung in einer Komponente eine Änderung der anderen erfordert, um die Gesamt-Korrektheit des Systems aufrechtzuerhalten."

Originalquelle: Meilir Page-Jones, "What Every Programmer Should Know About Object-Oriented Design" (Dorset House), 1996

— Reply to this email directly, view it on GitHub https://github.com/isaqb-org/glossary/issues/192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB47ORMXCMMP3SVHJFYSNHDW5BSCDANCNFSM6AAAAAAWBFCZX4. You are receiving this because you are subscribed to this thread.

mattes3 commented 1 year ago

Oh, I didn’t know that the term was so old already! I came across this only in the last 5 years. 😳 Thanks for posting, Peter!

From: Hruschka @.> @.> Reply: isaqb-org/glossary @.> @.> Date: 20. March 2023 at 17:31:29 To: isaqb-org/glossary @.> @.> Cc: Subscribed @.> @.> Subject: Re: [isaqb-org/glossary] Add term "connascence" (Issue #192)

The terms connascence and encumbrance never became popular.

Meilir tried to extend coupling and cohesion to the OO-world - but iMHO he failed. The words were too complex, the idea was already well covered by the terms coupling and cohesion.

We should not make the same mistake. Coupling and cohesion are good enough. The rest is for historians (like me :-))

Peter

Dr. Peter Hruschka Atlantic Systems Guild Langenbruchweg 71 52080 Aachen

Lesen Sie unser neues Buch arc42 by Example - Vol2: Embedded Systems and IOT https://leanpub.com/arc42byexample-volume2

und besuchen Sie unseren Youtube Kanal Culture at Work < https://www.youtube.com/channel/UCTVbsawKYlYyr8L0wgL2byQ> für einige Gedanken über gutes und schlechtes Betriebsklima.

Am 20.03.2023 um 15:24 schrieb Steffen Späthe @.***>:

Do we need to add the term "connascence" as addition to "cohesion" and "coupling"?

English: "Connascence"

"Two pieces of software share connascence when a changes in one requires a corresponding change in the other."

Deutsch "Konnaszenz"

"Zwei Komponenten sind konnaszent, wenn eine Änderung in einer Komponente eine Änderung der anderen erfordert, um die Gesamt-Korrektheit des Systems aufrechtzuerhalten."

Originalquelle: Meilir Page-Jones, "What Every Programmer Should Know About Object-Oriented Design" (Dorset House), 1996

— Reply to this email directly, view it on GitHub < https://github.com/isaqb-org/glossary/issues/192>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB47ORMXCMMP3SVHJFYSNHDW5BSCDANCNFSM6AAAAAAWBFCZX4 . You are receiving this because you are subscribed to this thread.

— Reply to this email directly, view it on GitHub https://github.com/isaqb-org/glossary/issues/192#issuecomment-1476565029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATBRIT4G7BP6LNQULTBAJLW5CA6DANCNFSM6AAAAAAWBFCZX4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>