Many a time, singly tested software components need to be combined
or integrated into a whole. This integration could be either of subsystem
components that are combined into products, or when components are combined
into subsystems. The combined nomenclature given to process is called Systems
Integration.
Why should
systems be integrated?
If systems integration did not offer a few distinct advantages,
there is no need to do it. So, what advantages does System Integration bring? It
does carry some basic advantages. We need to understand it this way: a product
is made into several components before being fully assembled to form a full
product. These “builds” or units can be joined incrementally, in a vertical
manner. These units may relate to subsystems, or may traverse subsystem areas
to produce a partial end-to-end product. In either case, what has to be ensured
is that integration has to be done over set stages, so that each unit in the
incremental build offers results in each phase when it is closer to the end
product.
In addition, keeping this practice of integration-ready units or
components ready makes it easy for developers to not only get a real, rather
than a simulated environment for actual integration work; they could also cut
down on costs significantly by identifying problems at every stage making changes
as and when required. The practice of phased or staged integration brings about
this advantage. When even complex problems are identified and addressed during
early stages of software integration, the result is a better and more compliant
product.
References:
No comments:
Post a Comment