Book a Demo

Author Topic: Class to dll relationship  (Read 2914 times)

msisson

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Class to dll relationship
« on: August 22, 2004, 10:51:39 pm »
As a C# developer I'm trying to model the architecture that I do in Visual Studio .NET.  In that environment, every project is compiled into an assembly (dll).  What is the best way to show that relationship between classes and the dll's that they produce?

Eventually I'd like to show these DLL on a component diagram to show where these binaries are deployed in my architecture.

TIA
mark

msisson

  • EA Novice
  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Re: Class to dll relationship
« Reply #1 on: August 22, 2004, 11:01:09 pm »
Add just a bit more   8)

Besides mapping classes to dlls, these dll's obviously have references to other assemblies.  I'm assuming that what metaphor is used to group classes (package?) would then be used on another diagram to show a dependency between these items (???).

I've tried dragging a class from the Project View onto a component and I get a dialog asking

thomaskilian

  • Guest
Re: Class to dll relationship
« Reply #2 on: August 23, 2004, 06:59:03 am »
Hi,
normally you model DLL as components. You set generalization to the classes these components realize.