Question

Demonstrate the related structured programming design principles in the diagram (music player programming). Eg: where is the abstraction, good (or bad) coupling, good (or bad) conhesion, etc.

Main While choice < 5 Print menu Read choice album opened false read albums from_ file, Albun opened-true true opened puts "No file is Print_albums from opened" file puts "No file is puts "No file is Play album update albun opened" opened

Answer 1

Coupling is defined as the degree of interdependence between two or more classes, modules, or components. Tight coupling is bad, and loose coupling is good.

Cohesion is defined as the degree to which all elements of a module, class, or component work together as a functional unit.High cohesion is good, and low cohesion is bad. The ideal situation is one where a module, class, or component provides only one function or, at most, a very closely related set of functions.  

Abstraction means to hide internal implementation details.

The above structured program displays a menu for user's choice.there are 4 choices.

1=read album from file

2=print album from file

3=play album

4=update album

It first ask the choice and according to user's choice it will take a path from four given choices.Before doing the job it first check whether the album_opened it true of false.If true it will do the job otherwise it will display "No file is opened"

In above design checking for album_opened is a work which is done for each choice, which increase the time of processing so it will be better to make a separate module for if.So there is a little coupling.But cohesion is high as each module is performing a separate function and they all work together.The design has abstraction as we bother about what we want to do,and we have to do nothing with how the work is being done.

So the above design is a good structured programming(Abstraction+good coupling+good cohesion)