One of the five types of coupling is data; modules pass fields of data or messages. It is considered "good" coupling because it is the most important component of program design and lines of code. Without data, no part of code nor program design can be accomplished.
One of the five types of coupling is Content Coupling. This is a form of coupling where one module refers to the inside of another module. This type is considered a bad type of coupling because it is so loosely coupled.
One of the five types of coupling is common coupling. Common coupling means that the modules refer to the same global data area. This type of coupling is considered bad because one error made in an area can cause a ripple effect, and affect all of the modules that are accessing the data.
Control couplings are the strings of data in which relay information between modules with either a fill-in circle with an arrow or a non-fill-in circle with an arrow. The information that is to be transferred between modules is that of system related messages or parameters.
An example would be if there was a "flag" that were to be thrown out because of reaching the end of the file, a control couple would be thrown out and may only be passed from subordinates to the control module.
the control couple is in the middle of being both good and bad however may be loosely coupled
The last type of coupling is stamp coupling. With stamp coupling modules pass record structures. This is a good coupling because not all of the record is used by the receiving module. Only specific fields will be used. This makes it more efficient and less data will be used.
One of the five types of coupling is content coupling. This coupling is where one module refers to the inside of another module. This is a bad coupling and should be avoided at all costs when referring modules to one another.
According to our book data coupling “occurs when modules pass parameters or specific pieces of data to each other”. An example of this is when you have the modules “Update Student Record” and “Calculate Current GPA”, the data that passes to each one is “Student ID” and “Current GPA”. Data coupling is considered “good” coupling, this is because it is a form of coupling that you want to see in the structure chart.
Of the five types of coupling, which include Data, Stamp, Control, Common and Content, Data coupling is considered to be most 'good' because modules pass parameters or specific pieces of data to each other and do not refer to the inside of any other modules such as content coupling does.
One of the five types of coupling is data; modules pass fields of data or messages. It is considered "good" coupling because it is the most important component of program design and lines of code. Without data, no part of code nor program design can be accomplished.
ReplyDeleteOne of the five types of coupling is Content Coupling. This is a form of coupling where one module refers to the inside of another module. This type is considered a bad type of coupling because it is so loosely coupled.
ReplyDeleteOne of the five types of coupling is common coupling. Common coupling means that the modules refer to the same global data area. This type of coupling is considered bad because one error made in an area can cause a ripple effect, and affect all of the modules that are accessing the data.
ReplyDeleteControl couplings are the strings of data in which relay information between modules with either a fill-in circle with an arrow or a non-fill-in circle with an arrow. The information that is to be transferred between modules is that of system related messages or parameters.
ReplyDeleteAn example would be if there was a "flag" that were to be thrown out because of reaching the end of the file, a control couple would be thrown out and may only be passed from subordinates to the control module.
the control couple is in the middle of being both good and bad however may be loosely coupled
The last type of coupling is stamp coupling. With stamp coupling modules pass record structures. This is a good coupling because not all of the record is used by the receiving module. Only specific fields will be used. This makes it more efficient and less data will be used.
ReplyDeleteOne of the five types of coupling is content coupling. This coupling is where one module refers to the inside of another module. This is a bad coupling and should be avoided at all costs when referring modules to one another.
ReplyDeleteAccording to our book data coupling “occurs when modules pass parameters or specific pieces of data to each other”. An example of this is when you have the modules “Update Student Record” and “Calculate Current GPA”, the data that passes to each one is “Student ID” and “Current GPA”. Data coupling is considered “good” coupling, this is because it is a form of coupling that you want to see in the structure chart.
ReplyDeleteOf the five types of coupling, which include Data, Stamp, Control, Common and Content, Data coupling is considered to be most 'good' because modules pass parameters or specific pieces of data to each other and do not refer to the inside of any other modules such as content coupling does.
ReplyDelete