Slide 26 of 42
Notes:
A component is more packaged than any old object. The assumption is that it will be used in many contexts unknown to its own designers. It should be robust in respect of abuse from other components, complaining rather than collapsing.
In addition to the executable code itself, there should be a specification documenting its behaviour unambiguously, using a suitable modelling and design notation. Since the average component will be used more than an individual product, it is, even more
Some component architectures require that each component should be able to answer at run time, queries about their connections.
The validation suite is a set of ancillary components for two purposes:
- One set help test the component once it is installed in a particular context, to provide test cases etc, and ensure it is running properly.
- A test version of our component exercises the components it is connected to, to make sure they behave as we require.
Not all of our client designers will wish to use all the customisation plug-points that we provide. We therefore provide default components for connecting in these cases, that provide standard behaviour.
