Cohesion (computer science): Difference between revisions

Revision as of 14:00, 18 October 2018

Revision as of 15:33, 18 October 2018

Line 3:

Cohesion is an [[level of measurement#Ordinal on a scale of one to a hundred ordinal]] type of measurement and is usually described as “high cohesion” or “low cohesion”. Modules with high cohesion tend to be preferable, because high cohesion is associated with several desirable traits of software including [[Robustness (computer science)|robustness]], reliability, [[reusability]], and understandability. In contrast, low cohesion is associated with undesirable traits such as being difficult to maintain, test, reuse, or even understand.

Cohesion is often contrasted with [[coupling (computer science)|coupling]], a different concept. High cohesion often correlates with [[loose coupling]], and vice versa.<ref>{{citationcite book needed| last = Ingeno | first = Joseph | author-link = | title = Software Architect’s Handbook | publisher = Packt Publishing | series = | volume =
| edition = | date = 2018 | ___location = | pages = 175 | language = | url = | doi = | id = | isbn = 1788624068 | mr = | zbl = | jfm =November 2013}}</ref> The [[software metric]]s of coupling and cohesion were invented by [[Larry Constantine]] in the late 1960s as part of [[Structured Design]], based on characteristics of “good” programming practices that reduced maintenance and modification costs. Structured Design, cohesion and coupling were published in the article {{harvtxt|Stevens|Myers|Constantine|1974}} and the book {{harvtxt|Yourdon|Constantine|1979}}; the latter two subsequently became standard terms in software engineering.

== High cohesion ==