Define cohesion and coupling in software engineering

Python Pillow. Python Turtle. Verbal Ability. Interview Questions. Company Questions. Artificial Intelligence. Cloud Computing. Data Science. Angular 7. Machine Learning. Data Structures. Operating System.

Computer Network. Compiler Design. Computer Organization. Discrete Mathematics. Ethical Hacking. Computer Graphics. Web Technology. Cyber Security. C Programming. Control System. Some of these are given below:. Coupling: Coupling is the measure of the degree of interdependence between the modules.

A good software will have low coupling. Cohesion: Cohesion is a measure of the degree to which the elements of the module are functionally related. It is the degree to which all elements directed towards performing a single task are contained in the component. Basically, cohesion is the internal glue that keeps the module together. A good software design will have high cohesion. This article is attributed to GeeksforGeeks. Conceptual design of system: Written in simple language i.

Detail explaination about system characteristics. Describes the functionality of the system. It is independent of implementation. Linked with requirement document.

Technical Design of system: Hardware component and design. Functionality and hierarchy of software component. Software architecture Network architecture Data structure and flow of data. Shows interface. Some of these are given below: Easy to understand the system.

System maintenance is easy. A module can be used many times as their requirements. No need to write it again and again. Types of Coupling: Data Coupling: If the dependency between the modules is based on the fact that they communicate by passing only data, then the modules are said to be data coupled. In data coupling, the components are independent to each other and communicating through data.

Example-customer billing system. Cohesion has many types but usually highly cohesion is good for software. Coupling: Coupling is also the indication of the relationships between modules. It is concept of Inter-module.

Coupling has also many types but usually low coupling is good for software. Now we will see the difference between Cohesion and Coupling. Coupling is the concept of inter module. Cohesion represents the relationship within module. Coupling represents the relationships between modules.

Increasing in cohesion is good for software. Increasing in coupling is avoided for software. Cohesion represents the functional strength of modules. Coupling represents the independence among modules. Highly cohesive gives the best software.