• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Is correct show classes and interfaces in component diagram ??

 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That is my doubt? Any body can help me ??

Thanks
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here is a good resource from Scott Ambler: The Component Diagram. He shows interfaces (the UML interface, not the Java interface) but no classes inside.

Bookmark The Diagrams of UML 2.0 if you don't have a pocket UML reference of some kind.
 
author
Posts: 608
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
UML class diagrams are typically used to model classes and interfaces.

Component diagrams show components, the dependencies between them, and the interfaces which they implement and/or require. Typically implemented interfaces are modelled as lollipops on these types of diagrams, although there is nothing stopping you (other than CASE tool lack of flexibility) from modeling an interface box with an implements or requires dependency with a component.

- Scott
 
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by JJ Captain:
Is correct show classes and interfaces in component diagram?


Formally this is correct, but in praxi?

Component diagrams are especially usefull when going to assemble an allredy designed and implemented system or subsystem or component for deployment, therefore showing
- compilation dependencies
- execution / call dependencies
- abstraction dependencies (x.class refine x.java)
- any other team defined dependencies
between two or more components via their interfaces.

But how to define the inner structure of one plugable / replaceable component? Regardless of
- using one component diagram per component and showing its classes or
- showing several components along with their classes,
in both cases each component will be defined and will be reusable in a deployment diagram later.

If the system is trivial enough, you could mix up inter- and intra-component dependencies within one huge diagram.
But for complex systems I prefer to
- define the intra-component dependencies in one component diagram per component and showing its classes and
- define the inter-component dependencies in one or more separate component diagrams showing only interfaces and dependencies, no classes.

Thomas.
 
Jose Jim�nez
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
My doubt is about how show the screen flow manager class and TemplateServices class y component diagram asoccitate with FronController

Can be showed 3 components ???
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic