The Input-Output Model-Controller Architecture Description

In the previous post I put shortly the diagram of the Input-Output Model Controller architecture ...
The name seems kind of bombastic , but let me explain quickly  why I think this kind of architecture could provide enough abstraction to implement ALMOST ANY type of application / tool / library ...
Basically if you think what the software written by you ( or somebody else in your organisation for that manner ) is, you will realise that it is just  an entity which has input and output that hopefully   brings some kind of added value in the output ...

Thus, ALWAYS you could:
 - use readers ( db , file , s3 , UI controls or whatever ) to read your input
 - use writers ( db , file , s3 , UI controls or whatever ) to write your output
 - use converters to convert the data ingested into different format
 - use controllers to control the whole hassle
 - use a Dispatcher to be able to navigate from the app entry points to the controllers

That's it ! Is that simple ... Why aren't you already coding ?!