Component-based software engineering makes a lot of sense from an economical and even an efficient perspective, which I heartily respect. All of the component characteristics defined are characteristics that anyone at this stage would have discussed previously. The exception could be composable - which means all external interactions must take place through publicly defined interfaces - but this is an easy enough concept to grasp.
The concept that a component has two interfaces - the "requires interface" and the "provides interface" - is something I hadn't really thought about before. I'd certainly thought of the provides interface - as ultimately that is what I'm interested in. Obviously I had considered that I had to provide input to the component to get appropriate output, however I think I was stuck in the idea of providing it in the signature that I expect to get my output back from. Providing it beforehand, especially if the input is a large set of data such as a database, makes more sense efficiency wise. I'm sure these are thoughts that I've had before, but they were gleaned over and I never thought of the concept properly.
No comments:
Post a Comment