A 'Component' is a single piece of code. In fact, a Component is a small coded unit. 'Software Systems' are designed using coding practices. Such 'Software Systems' are made up of many such pieces of 'Components'.
In a 'Software System', a 'Component' has a well-defined role. It is fitted in the 'Software System' to perform that role.
Many 'Components' compose a 'Software System'. The 'Software System' can work successfully only when all the 'Components' ( pieces ) are doing their assigned tasks properly. Faulty 'Components' can be replaced.
In a 'Software System', a 'Component' has to participate. A 'Component' has a well-defined function. It performs when required.
A 'Component' is designed to work on its own. It is armed with the code that can fulfill the task it is supposed to do.
A 'Software System' is powerful. Such a System is empowered by well-designed 'Components'. The power of a 'Software System' is the collective excellence of the total components.
The 'Software System' has a broad function. As compared to a 'Software System', a 'Component' is less capable.
The concept of 'Component' strengthens the idea of division of labour. Division of labour has proven that efficiency can be improved if specialized 'Components' are designed. Specialized 'Components' do a good job.
Let us imagine that the concept of 'Components' wasn't with us. Let us say that there was a large body of code. This large size code if instructed to perform a variety of tasks would not be able to do justice. Justice with all the jobs that 'Software System' was supposed to do would not have been possible without assembling the 'Components'. It is because developing a big size software module is still not the choice of Software Developers. Frankly, a large size code has more chances of failure.
Specialist 'Components' perform very well. As 'Components' are specialists the risks involved are less.The chance of failure of a 'Software System' based on 'Components' is minimal.
Comments
Post a Comment