Re: question about component integration or assembly



On Jan 17, 1:52 pm, liongs...@xxxxxxxxx wrote:
On Jan 17, 3:40 am, "H. S. Lahman" <h...@xxxxxxxxxxxxxxxxx> wrote:

or assemblied with other components.

Which component concept is that? B-) Alas, component engineering is
taking on as many different methodological views as OOA/D.

I read about this from Syperski's "Component Software - Beyond Object
Oriented Programming" (2003). To be exact on page 174, He mentioned
and draw a connection between two components C1 and C2. I can
understand if they will communicate through a defined interface,
however my question was how this connection is implemented?

Juval Lowy in his book 'Programming dot net Components' also draws
interaction between components, however I could not find the detail
information on how it will be implemented.

However how could we connect X to Y, if don't
have the source code of X and Y?

The short answer is that you don't. The component is a module with a
particular semantic responsibility that is abstracted by its interface
for various clients to use.

Yes I thought the answer had to be not, however I have a confusion
between the concept (as described above) and the practical
implementation of the component integration.

Thanks again for your response.

Han

Maybe much of the confusion (at least for me) comes from the fact that
the term "component" sometimes indicate a *type* and sometimes
indicates an *object*, especially in the books you cited. But
practically, the situation may be quite different: for example in UML,
a component is basically a class: if you want to wire components A and
B you have to:
- instantiate an instance of A; instantiate an instance of B; wire
them (maybe invoking a setter on A passing the reference to B?)
- Have another component C which has properties (class members) typed
to A and B and wire those two properties (and of course instantiate C)

Now, how you do the wiring between the required port of a component
*instance* to the provided ports of another component *instance* is
still unclear to me (look at a previous post which was sadly left
unanswered http://groups.google.com/group/comp.object/browse_thread/thread/62ec406d8dced3a4).

.



Relevant Pages

  • Re: Testbench writing
    ... You have to instantiate the module in the Testbench. ... wire done_o; ...
    (comp.lang.verilog)
  • Re: classes to perform functions for many forms
    ... You can also define class members as Shared, that way you don't have to ... instantiate an instance of the class to use the public members you've set ... ClassX.FunctionName syntax you're use to in VB6. ...
    (microsoft.public.dotnet.framework.windowsforms)