Connascence

Connascence (computer programming)Connascence (computer science)Connascent software components
Connascence is a software quality metric invented by Meilir Page-Jones to allow reasoning about the complexity caused by dependency relationships in object oriented design much like coupling did for structured design.wikipedia
12 Related Articles

Software metric

software metricsmetricmetrics
Connascence is a software quality metric invented by Meilir Page-Jones to allow reasoning about the complexity caused by dependency relationships in object oriented design much like coupling did for structured design.
ConnascenceCyclomatic complexityCoupling (computer programming)Cohesion (computer science)Source lines of code

Coupling (computer programming)

couplingdependenciesdependency
Connascence is a software quality metric invented by Meilir Page-Jones to allow reasoning about the complexity caused by dependency relationships in object oriented design much like coupling did for structured design.
Loose couplingCohesion (computer science)Software metricFunctional designLarry Constantine

Named parameter

keyword argumentnamedNamed arguments
takes several arguments could be changed to use named parameters.
This reduces the connascence between parts of the program.
Parameter (computer programming)Scala (programming language)Objective-CC Sharp 4.0IDL (programming language)

Object-oriented design

designobject orientedobject-oriented
Connascence is a software quality metric invented by Meilir Page-Jones to allow reasoning about the complexity caused by dependency relationships in object oriented design much like coupling did for structured design.
Information hidingGRASP (object-oriented design)IDEF4Class-responsibility-collaboration cardComposition over inheritance

Structured analysis

Structured DesignSA/SDstructured'' approaches
Connascence is a software quality metric invented by Meilir Page-Jones to allow reasoning about the complexity caused by dependency relationships in object oriented design much like coupling did for structured design.
Tom DeMarcoKen OrrStructure chartEdward YourdonLarry Constantine

Software engineering

software engineersoftware engineerssoftware
In software engineering, two components are connascent if a change in one would require the other to be modified in order to maintain the overall correctness of the system.
Computer scienceSoftwareSoftware developmentIan Sommerville (academic)Systems engineering

Component-based software engineering

software componentcomponentcomponents
In software engineering, two components are connascent if a change in one would require the other to be modified in order to maintain the overall correctness of the system.
Software systemService-oriented architectureInterface description languageModular programmingComponent-based usability testing

Locality of reference

localitydata localitycache locality
Locality matters when analyzing connascence.
Cache (computing)Processor registerArray data structurePagingThrashing (computer science)

Web service

web servicesserviceservices
to a web service positionally is unacceptable due to the relative
XMLJSONMashup (web application hybrid)Representational state transferWeb Services Description Language

Parameter (computer programming)

parameterparametersargument
Positional parameters in method calls are an example of this form of connascence.
SubroutineC (programming language)Generic programmingNamed parameterVariable (computer science)

Message authentication code

MACmessage authentication codesMessage Integrity Code
Message authentication codes are an example of this form of connascence.
Message authenticationCryptographic hash functionCryptographyInitialization vectorNon-repudiation

Loose coupling

loosely coupledlooser couplingloosely-coupled
Message-oriented middlewareService-oriented architectureDistributed computingEvent-driven architectureCoupling (computer programming)