Program Execution Flow
Intersection of Two Lines - GRE Mathematics
Software Requirement Specifications written document is a tough task to accomplish. If SRS document is written by the beginners then it is prone to lot of mistakes which includes incompleteness, doubts, and conflicts in requirements. Existence of such problems in SRS document leads to serious problems in development phase of Software Lifecycle.
Cohesion means unity or interrelation. You can imagine cohesion in football field when eleven players are divided in four groups’ midfielder, striker, defender and goalkeepers. Each group performed its unique task but collective effort of the four groups is to make a goal or to stop a goal. When different modules work together to achieve a single objective then this cooperation is termed as Cohesion.
Coincidental Cohesion is the result of the unplanned and accidental collection of the functions. Random or accidental collection means loosely cohesive elements of the modules. It is the division of the problem in modules for the sake of the module; it is not the division for the sake of the complexity breaks down of the problem. That’s why it is considered as loosely related set of tasks to perform a job.
Communicational cohesion is also named as Informational Cohesion. Operations/ Functions of the module are performed on the same data. Communicational Cohesion – Let’s know what is it?
Evolutionary Software Development Model is also called Incremental Model. Evolutionary Development Model worked on delivering functions. Each time a new functional unit is delivered till the entire system functionality is achieved. This Software Development Model is also known as the Successive or sequential Model because it delivered software in incremental or Sequential addition of the Functional Units.
A module is composed of different parts called elements, when these elements perform logically similar operations then this cohesiveness is called logical cohesion.
Elements or parts of the module are arranged together to follow a clear sequence of execution to perform a task is referred as the Procedural Cohesion. Let’s try to elaborate this statement of Software Engineering.
The requirements Specification task is started when all types of doubts and incompleteness about the customer requirements is settled. This activity is the beginning which converts the User Requirements into Software Product. This stage is arranged or structured the user requirements in proper format, which is helpful in designing decisions. This task is the component of the requirement gathering and analysis phase. The organized document which is created by this activity is called the SRS Document or Software Requirements Specifications.
