![]() Difference Between Coupling And Cohesion In Software Engineering Ppt Software Design BreaksĪ software design breaks down into multiple modules where each module solves a particular problem.Įach and every module must be implemented in a way that they are having less dependency with other modules and the elements within that module should be functionally related together.Īs any changes ripple through connected code, refactoring of highly coupled code is difficult.įunctional correctness reigns supreme, but if we put that aside what should we look at next Cohesion and coupling are the two most significant aspects of code impacting software quality.Ī set of functions, an interface, is considered cohesive when each function is closely related to another.įor example, logerror and logwarning are closely related and belong nicely together in a single log module.Īs functions diverge in their behaviour a module becomes less cohesive. Therefore, it is known as inter-module concept It is based on communication between two elements or fields within a single module. Therefore, it is better to have maximised cohesive modules where elements within a module interact properly to one another. Difference Between Coupling And Cohesion In Software Engineering Ppt Series Of Modules.Difference Between Coupling And Cohesion In Software Engineering Ppt Software Design Breaks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |