One of the seven types of cohesion is 'Communicational' which is explained in the book as activities that are using the same inputs and outputs for a function. The example the book, found on page 387, talks about is "Calculate Current and Cumulative GPA – Two tasks are performed because they both use the student grade record as input." I feel that this could be considered as one of ‘good’ cohesion. The reason that I decided this is it will pull the same information (inputs and outputs) in order to perform two functions rather than performing each function separately. This can save time, create a sense of convince, and could be seen as simplifying the process for users.
"Functional" cohesion is a module that performs one problem-related task. This could be "calculate current g.p.a" or "look up classes." This is considered a good type of cohesion because it follows well with the lines of code, it also follows the rules of a good module which is that it should only perform one task.
Another type of cohesion is sequential. During sequential cohesion, the output from one task is used by the next task. When looking at a student's GPA, formatting the GPA is the first task that is the input for the second task of validating one's GPA. This is considered a "good" cohesion mainly because of its high importance with code and program design.
Coincidental is another type of cohesion. Coincidental cohesion incorporates a number of non-related tasks that have no apparent relationship. This kind of cohesion is the poorest since this module performs different functions that have nothing to do with each other such as updating customer records, calculating loan payments, printing reports, or analyzing competitor pricing structure.
Temporal is another form of cohesion is when functions within a module do not have much in common except in that of being invoked at the same time. In other words each occur at the same time however are unrelated from each other, which is the main reason that temporal cohesion leans more towards the poorer side of the cohesion scales.
Logical is also another form of cohesion where its a lists of activities depending on the message within the module, these activities are related or similar in one or more respects. For example they perform similar functions, follow the same protocol, opening a checking account, open a savings account, or calculate a loan.
Procedural is another form of cohesion when the elements are performed in sequence by the elements do not share data. The module includes the following: housekeeping, produce report off of print grade and listing.
The main reason that Functional Cohesion is better than Coincidental is because all elements of the module contribute to performing a single task requiring high levels of cohesion. On the other hand coincidental cohesion is where no elements relate or appear to have any relationships among functions.
Functional cohesion is considered a good cohesion because it's task is to perform one thing. It will solve a problem such as calculating a GPA. Since it only performs one task it is considered good cohesion.
One of the seven types of cohesion is 'Communicational' which is explained in the book as activities that are using the same inputs and outputs for a function. The example the book, found on page 387, talks about is "Calculate Current and Cumulative GPA – Two tasks are performed because they both use the student grade record as input." I feel that this could be considered as one of ‘good’ cohesion. The reason that I decided this is it will pull the same information (inputs and outputs) in order to perform two functions rather than performing each function separately. This can save time, create a sense of convince, and could be seen as simplifying the process for users.
ReplyDelete"Functional" cohesion is a module that performs one problem-related task. This could be "calculate current g.p.a" or "look up classes." This is considered a good type of cohesion because it follows well with the lines of code, it also follows the rules of a good module which is that it should only perform one task.
ReplyDeleteAnother type of cohesion is sequential. During sequential cohesion, the output from one task is used by the next task. When looking at a student's GPA, formatting the GPA is the first task that is the input for the second task of validating one's GPA. This is considered a "good" cohesion mainly because of its high importance with code and program design.
ReplyDeleteCoincidental is another type of cohesion. Coincidental cohesion incorporates a number of non-related tasks that have no apparent relationship. This kind of cohesion is the poorest since this module performs different functions that have nothing to do with each other such as updating customer records, calculating loan payments, printing reports, or analyzing competitor pricing structure.
ReplyDeleteTemporal is another form of cohesion is when functions within a module do not have much in common except in that of being invoked at the same time. In other words each occur at the same time however are unrelated from each other, which is the main reason that temporal cohesion leans more towards the poorer side of the cohesion scales.
ReplyDeleteLogical is also another form of cohesion where its a lists of activities depending on the message within the module, these activities are related or similar in one or more respects. For example they perform similar functions, follow the same protocol, opening a checking account, open a savings account, or calculate a loan.
ReplyDeleteProcedural is another form of cohesion when the elements are performed in sequence by the elements do not share data. The module includes the following: housekeeping, produce report off of print grade and listing.
ReplyDeleteThe main reason that Functional Cohesion is better than Coincidental is because all elements of the module contribute to performing a single task requiring high levels of cohesion. On the other hand coincidental cohesion is where no elements relate or appear to have any relationships among functions.
ReplyDeleteFunctional cohesion is considered a good cohesion because it's task is to perform one thing. It will solve a problem such as calculating a GPA. Since it only performs one task it is considered good cohesion.
ReplyDelete