Various types of coupling in software engineering

NET on Windows? NET Files? Features of ASP. NET Data Types in. Save Article. Like Article. Last Updated : 07 Jul, Fig: Global Data Store.

Fig: Tight Coupling. Fig: Loose Coupling. Next Development Testing in Software Engineering. Recommended Articles. Article Contributed By :. Computer Network.

Compiler Design. Computer Organization. Discrete Mathematics. Ethical Hacking. Computer Graphics. Web Technology. Cyber Security. C Programming. Control System. Data Mining. Data Warehouse. Javatpoint Services JavaTpoint offers too many high quality services. The various types of coupling techniques are shown in fig: A good design is the one that has low coupling. Types of Module Coupling 1. In this case, modules are subordinates to different modules. Therefore, no direct coupling.

The name coupling is applied for this process, as it is typically deliberated between two modules at a time. The first step taken in the coupling process is to evaluate the association between the two modules and to define the functionally dependent areas in the modules.

Coupling between any two modules is identified from the number and types of resources that the modules share with other modules. This resource can be a functional behavior, a common interface, a common field in a user interface, the data picked from a field and shared between two modules, a transaction shared between two modules, etc.

Based on these possible dependencies, the coupling in software engineering is classified into six different types of coupling. And, they are. Every software requirement specification documentation process should have a classification of these coupling between the dependent modules, whichever is applicable after a brief evaluation performed on the requirement provided by the client. Common Coupling consists of the modules that share the overall constraints in the midst of any two modules of the software system.

This also can be a sign of any change made in the common constraint will reflect in the modules that share the common coupling scenario. As any other process, this common coupling also allows space for characterizing the advantages and disadvantages involved in the process.

This type of dependency should be evaded as it calls for more maintenance activities and lesser control over the modules.