Object Oriented Software Engineering   View all facts   Glossary   Help

subject > criterion > quality > software quality > cohesion > temporal cohesion

temporal cohesion
subject			fact

temporal cohesion	has definition A form of cohesion in which aspects of a system are grouped together which are used during the same phase of execution of a program, i.e. execute close together in time
	has example a designer would achieve temporal cohesion by placing together all the code used during system start-up or initialization
	is weaker than procedural cohesion
	is a subtopic of 9.2 - Principles Leading to Good Design
	is achieved when operations that are performed during the same phase of the execution of the program are kept together, and everything else is kept out
	is a kind of cohesion
	should be sought only if the other types of cohesion have been achieved
cohesion	has precedence table Cohesion type Comments functional cohesion If an aspect of a design can be achieved using a functionally cohesive module then it is normally best to do so. layer cohesion Layer cohesion should typically have higher priority. Dividing systems into layers has been shown to considerably simplify systems. communicational cohesion Communicational cohesion, as embodied in the classes of an object oriented system, should have high priority. Here we list it below layer cohesion since modules may access the same kind of data in different layers. sequential cohesion Sequential cohesion is effectively a strong form of temporal cohesion, but is weaker than communicational cohesion since different data types may be involved in the different stages of a sequentially cohesive module. temporal cohesion Temporal cohesion should typically be considered weaker than other types of cohesion. It is important, but only if the other types of cohesion have been achieved. utility cohesion Utility cohesion is the weakest kind of cohesion since it serves to group together those parts of the system that do not seem to logically belong anywhere else.