1.5.
Composed Component
Up one level
Components should be as simple as possible in order to provide a high flexibility in its usage. Simple and small components have one disadvantage: When connecting components to a model developers will always have to start from scratch - quite a waste of time!
In order to avoid restarting for every model from scratch, a developer may create building blocks derived from org.pillarone.modelling.components.ComposedComponent.
Examples for such building blocks may be found i.e. in the package domain/lob and domain/reinsurance/program.
A composed component is somehow similar to a model, as it contains several components, statements defining wiring but no specific algorithms implementing any formulas.
Furthermore each composed components adds a hierarchy level in the user interface, as its sub components are added below them in the tree.
