Talk:Coupling (computer programming)

Renaming to : Coupling (Computer science)

I propose to rename this entry to Coupling (Computer science) as this the most used terme by the specialists of the filed along with Cohesion, we need then to put a disambiguation link at the begining of Coupling. --Khalid hassani 14:36, 20 May 2005 (UTC)

Are you sure that coupling is used more than the dependency? Also I am not so sure what you mean by specialists. By that, do you mean computer scientists? computer programmers? hackers? -- Taku 20:10, May 20, 2005 (UTC)

by specialists I mean computer scientists and programmers, I have always heard about the couple coupling/cohesion as dual concepts et not dependency/cohesion. I think that there are in facts two different concepts in this entry, dependency which is in fact, rather related to RPM and packages, and coupling which is used in Object Oriented design, the two concepts are from two diffrents cultures, Linux hackers for the first and programmers using Object oriented languages for the second.--Khalid hassani 21:48, 21 May 2005 (UTC)

I would also rename this entry to Coupling (Computer science). In the article itself, the term "Coupling" occurs 28 times, whereas "Dependency" occurs only 6 times (not counting the name of the article). And Coupling#Computer programming points to here. I'm going to do the rename (maybe in about 8 or 10 hours). — Adrian | Talk 23:50, 9 November 2005 (UTC)

I have moved the article to Coupling (computer science). — Adrian | Talk 12:20, 10 November 2005 (UTC)

gains in the software development process

"...the gains in the software development process are greater than the value of the running performance gain."

I feel that this statement may be more opinionated than factual. Perhaps omission of this would be prudent?

I agree, and I've reworded this to make it clear that this is merely an opinion. Lunalot 21:44, 19 January 2007 (UTC)

Merge from the article "Low-Coupling / High-Cohesion pattern"

I have just merged the contents of the article "Low-Coupling / High-Cohesion pattern" into this article here under a new section with the same name. "Low-Coupling / High-Cohesion pattern" is now a redirect to here (see also Merging and moving pages). — Adrian | Talk 20:40, 10 November 2005 (UTC)

What about levelization and circular dependencies

John Lakos' book "Large-Scale C++ Software Design", although sometimes criticized for having some outdated C++ coding practices, has a good treatment of circular dependencies (a case of high coupling), as well as levelization. I believe this article is incomplete without a treatment of this subject.

Dependency hell

You are in Dependency Hell when you want connect to the Internet, try to install a package to stablish the access and the package has a lot of dependencies. You cannot download the packages because you are not connected and you cannot connect because you cannot dowload the packages.--Mac (talk) 16:58, 5 February 2008 (UTC)

--210.212.55.130 (talk)

Explicit and implicit dependencies

Can anyone include information about what are explicit and implicit dependencies ? And recursive implicit dependencies ?. --Nopetro (talk) 09:31, 11 February 2008 (UTC)

Attribution

The concepts of coupling and cohesion were invented by Larry Constantine, not Glenford Myers. Myers was a student of Constantine's at IBM's Systems Research Institute. Although Myers book was published before Yourdon and Constantine's classic, primary sources (e.g., 1974 IBM SYSTEMS J. aricle) make clear the source of the core ideas. Stirrer (talk) 17:14, 21 May 2008 (UTC)

Where is the Fenton Metric?

The Fenton Metric is missing. --phil (talk) 15:02, 21 June 2008 (UTC)

Inconsistent Terminology

The is some unfortunate inconsistency in the terminology used to describe different types of coupling that makes an already challenging subject even more difficult to follow. In the "Types of Coupling" section seven different types are discussed, and in the "Module Coupling" Section four types are mentioned. Unfortunately two of these latter four (global and environmental) are not described in the earlier section. I'm not being pedantic, just trying to understand some difficult concepts. Presumably there are alternative names in use here but this in not made clear anywhere. Inspeximus (talk) 07:15, 2 August 2011 (UTC)

Compiler as a Dependency

Some programs aren't packaged and require specific compilers, or are packaged and require compiling of OTA updates.

104.176.16.56 (talk) 00:48, 27 April 2018 (UTC)

Performance issues

This section seems to have nothing to do with coupling, and indeed the relationship between performance and coupling was much clearer before this section was introduced. The clarity of the section itself has deteriorated over time.

KeithC (talk) 13:51, 10 August 2018 (UTC)

The book name in reference [4] is incorrect.

The book name in the text of the article referenced in footnote 4 is not correct. The footnote is correct, the text reference lists the author, instead of the name of the book. Please fix. Gclose11 (talk) 21:55, 1 March 2023 (UTC)

This list of modes/types of coupling is extremely outdated

There is no mention of important types of coupling such as design-time versus runtime coupling, (execution) location coupling, creation coupling, call coupling, temporal coupling, data structure/data format coupling, inheritance coupling... 62.167.164.120 (talk) 14:54, 8 May 2023 (UTC)

Coupling is also the interdependence within modules, not just between them

Much of the discussion on coupling also involves deciding how data and functions should be coupled inside a single module. So the definition of this term isn't quite complete. 100.0.211.27 (talk) 19:19, 11 December 2024 (UTC)