• 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:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Components and artifacts

 
Ranch Hand
Posts: 75
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello =]

Basically my application may be splitted in two big parts. One of them handle the user interactions, with all the necessary components to implement the communication between the user, the database and a payment external System. The other part has the responsibility of executing heavy background work started by timers, to do this job, it also communicates to the database and another external system.

I've realized that the load of these parts can vary independently then I think it'd be very valuable to separate them in two deployable artifacts: Two .ear

Then I have two questions.

1) How do I show which components will go in each artifact?
2) Do you think that for the proposes of the exam it's valuable to make this kind of separation or keep the things simpler would be a better approach? This will add some difficult to the diagrams could drive me to errors.

Thanks in advance.
 
Bartender
Posts: 3648
16
Android Mac OS X Firefox Browser Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When it comes to diagrams keep things simple. Having too much stuff may clutter the diagram. Having too little items/objects may give the impression (to yourself anyway) "can it be that simple?".

Back to your issue. IMHO The 2 ear thing can be represented in the deployment diagram rather than the component diagram, saying EAR1 does ABC and EAR2 does XYZ. Breaking down these EARs into components (done as component diagrams) may be overkill.
 
Antonio Rafael Rodrigues
Ranch Hand
Posts: 75
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Tsang.

First of all, thanks for your reply.

Don't you think that if I split the application into two .ear without explicitly say which components are going to be in each of them I would be omitting important informations?

Thanks.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic