[UML Forum] Library Representation in Component Diagram in UML 2.0

[Peter Wkc]

1. Can we represent library (API) in UML 2.0 ?

For instance, i have a VoIP library which use window socket.

In this case, a VoIP library is a component and the window socket
library is a API.

VoIP ------<<use>>----> Window Socket, Audio

2. I have a GUI window which using QT

GUI _______________( QMainWindow, QMenuBar, QPushButton

Any improvement for this.

3. Supply order is a component which has required order sent interface

Supply order _________( order sent

Please clarify.

Thanks.

--
You received this message because you are subscribed to the Google Groups "UML Forum" group.
To post to this group, send email to umlf...@googlegroups.com.
To unsubscribe from this group, send email to umlforum+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/umlforum?hl=en.

[H. S. Lahman]

Responding to Wkc...

> 1. Can we represent library (API) in UML 2.0 ?
>
> For instance, i have a VoIP library which use window socket.
>
> In this case, a VoIP library is a component and the window socket
> library is a API.
>

Not quite. The socket library is a component and its API is the
component interface.

Typically one will represent access to external components with a
surrogate object in the implementation of the component sending the
message. The interface to that object is the API. If the message
transfer mechanism is straight forward, then that surrogate object might
simply be an Interface model element.

There is a posting in the Application Partitioning category of my blog
that describes a model for subsystem (component) interfaces that may be
of interest.

--
Life is the only flaw in an otherwise perfect nonexistence
-- Schopenhauer

H. S. Lahman
H.la...@verizon.net
software blog: http://pathfinderpeople.blogs.com/hslahman/index.html

[Peter Wkc]

On Apr 28, 11:02 pm, "H. S. Lahman" <h.lah...@verizon.net> wrote:
> Responding to Wkc...
>
> > 1. Can we represent library (API) in UML 2.0 ?
>
> > For instance, i have a VoIP library which use window socket.
>

> > In this case, a VoIP library is acomponentand the window socket

> > library is a API.
>
> Not quite. The socket library is acomponentand its API is thecomponentinterface.
>
> Typically one will represent access to external components with a

> surrogate object in the implementation of thecomponentsending the

> message. The interface to that object is the API. If the message
> transfer mechanism is straight forward, then that surrogate object might
> simply be an Interface model element.

I could not understand what u say here. Can u provide a complete
example for my scenario.

I also check your blog but found nothing useful.

Thanks.

[H. S. Lahman]

Responding to Wkc...

1. Can we represent library (API) in UML 2.0 ?
      

For instance, i have a VoIP library which use window socket.
      

In this case, a VoIP library is acomponentand the window socket
library is a API.
      

Not quite. The socket library is acomponentand its API is thecomponentinterface.

Typically one will represent access to external components with a
surrogate object in the implementation of thecomponentsending the
message. The interface to that object is the API. If the message
transfer mechanism is straight forward, then that surrogate object might
simply be an Interface model element.
    

I could not understand what u say here. Can u provide a complete
example for my scenario.
  

The socket library provides the functionality that actually does something with sockets. So it is the component. The I in API means it is the interface through which the library component's functionality is accessed.

<pre>
+-------------+          +-------------+         +-----------------+
|     VoIP    |          |    Socket   |         |   Socket      -----
|    Library  |--------->|   Library   |<|-------|     API         |
|             |  <<use>> |             |         |               -----
+-------------+          +-------------+         +-----------------+

    Component              Component                  Interface
</pre>

I also check your blog but found nothing useful.
  

That's too bad.

-- 
Life is the only flaw in an otherwise perfect nonexistence
   -- Schopenhauer

H. S. Lahman
H.la...@verizon.net
software blog: http://pathfinderpeople.blogs.com/hslahman/index.html