answersLogoWhite

0


Best Answer

Given two lines of code, A and B, they are coupled when B must change behavior only because A changed.

They are cohesive when a change to A allows B to change so that both add new value.

User Avatar

Wiki User

12y ago
This answer is:
User Avatar
More answers
User Avatar

Harmony Junior

Lvl 2
2y ago

cohesion is grouping related class and related classes

This answer is:
User Avatar
User Avatar

Shannon Greenfelder

Lvl 1
2y ago
tyy

User Avatar

Wiki User

10y ago

compare and contrast coupling and cohesion in SE

i don't know the answer. please someone could help. wait .. i know the answer

but i forgot

This answer is:
User Avatar

Add your answer:

Earn +20 pts
Q: Explain the importance of coupling and cohension both of these concepts wrt to software design?
Write your answer...
Submit
Still have questions?
magnify glass
imp
Related questions

What are the types of coupling in software engineering?

control coupling content coupling common coupling data coupling external coupling message coupling


How are software coupling and portability are related?

The concept of coupling embodies the reliability and dependability (strength) among all relationships between functional units.The concept of software portability is the usability of same components/software in different environments.For optimal software, it is generally the case where coupling has to be minimized and portability has to be maximized (for sustainability and effectiveness in the long run). Having said that, strong software that contains low levels of coupling could easily and efficiently is portable. Similarly, if the software is portable it is probably due to the low levels of coupling that it has.Think of these as Lego pieces. If you want a working building, then all those nooks and crannies should not be visible (implying some coupling). That means that they should be stuck together pretty tightly (coupling). At the same time, if you want to remove a part of your structure like a room or a floor, then the tightness of your pieces (coupling) shouldn't be as strong. Ultimately, your structures portability is only dependent on the tightness of the pieces.


How can you design a computer software for teaching electronics concepts?

software engg


Why are dependency injections needed for software?

Dependency injections are needed for software in order to reduce the coupling between software components. I hope that answers your question and thoughts.


What is data coupling in Software?

Coupling is a measure of the relationship or dependency between two modules. Data Coupling occurs between two modules when data is passed by parameters using a simple argument list and every item in the list is used.


What is difference betwee coupling and cohesion?

Coupling within a software system is the degree to which to which each module relies on other modules cohesion is the measure of a sub systems internal interdependence


Why there should be low coupling and high cohesion in software design?

There should be low dependence and high interaction between the modules. The dependence should be low so that the module can work in absence of another module. So, there should be low coupling ad high cohesion in software design.


What isthe importance of technical writing?

the most importance is the software industry..


What is the importance of software testing in safely critical systems?

It is inherently greater than the importance of testing software for systems characterized by unsafe criticalness. :o


What is data in software?

Coupling is a measure of the relationship or dependency between two modules. Data Coupling occurs between two modules when data is passed by parameters using a simple argument list and every item in the list is used.


Are quality and security the same thing in software?

No, they are two completely different concepts


Is it reasonable to say that problem domain components should never exhibit external coupling?

External coupling occurs when a component communicates or collaborates with infrastructure components (e.g., operation system functions, database capability, telecommunication functions). Although this type of coupling is necessary, it should be limited to a small number of components or classes within a system. Software must communicate internally and externally. Therefore, coupling is a fact of life. However, the designer should work to reduce coupling whenever possible and understand the ramifications of high coupling when it cannot be avoided.