Book a Demo

Author Topic: assemblies modeling  (Read 5698 times)

mariano774

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
assemblies modeling
« on: May 18, 2005, 12:41:00 pm »
Hello,

Im having some doubts when modeling assemblies with UML, should they be components or packages ?
I started modeling them as components exposing interfaces, but when I got to the code part, i wondered, what exactly is an interface and how replaceable is the dll ?
If I think about it, a more natural approach is to model the dll as a package, since when I use it on another program, I do a dim var as new dll.class, so I'm using the classes contained in the dll, I'm not using the interfaces as showed in component diagrams

Anyone thought about this b4 ?

Thanks in advance,
Mar

sargasso

  • EA Practitioner
  • ***
  • Posts: 1406
  • Karma: +1/-2
  • 10 COMFROM 30; 20 HALT; 30 ONSUB(50,90,10)
    • View Profile
Re: assemblies modeling
« Reply #1 on: May 19, 2005, 12:14:44 am »
There is another thread somewhere in here - possibly in Suggestions - along these lines.  IIRC we came to the conclusion that components and assemblies seem to be a fairly abstract level modelling thingo.

IOW they are suited to the architecture modelling, or Paolo's conceptual layers more than physical code design.

hth
bruce
"It is not so expressed, but what of that?
'Twere good you do so much for charity."

Oh I forgot, we aren't doing him are we.

mikewhit

  • EA User
  • **
  • Posts: 608
  • Karma: +0/-0
  • Accessing ....
    • View Profile
Re: assemblies modeling
« Reply #2 on: May 19, 2005, 02:25:09 am »
Round here (Southampton UK) IOW = Isle of Wight !!