• 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

Example assigments for part II/III

 
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Which example assignments for SCEA II/III would you recommend. So far I checked following:
- ePractize Labs Part 2/3, it contains 6 mock projects
- Scenario from Mark Cade/Humphrey Sheil JEE Study Guide (chapter 9)
- Enterprise JavaBeans 3.0 by Bill Burke, Richard Monson-Haefel (Chapter 21: EJB Design in the Real World )
I found each of them useful, however there are significant differences between them.
For example Mark Cade class diagram uses annotations like @Stateless @Entity, while others : <<Stateless Session Bean>>
Additionally Cade placed all classes on one large diagram, but ePractize used one general diagram and several more detailed ( for each tier like WEB , EJB ).
Burke is also using one general class diagram close to this presented by Cade.

My question is: do anybody of you have experiences with solutions presented above, or could recommend something not listed by me ?
Which one is the best, it terms of matching the SUN reviewer expectations ?


 
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is no "one size fits all". Make a decision based on what's best for your assignment, and the level of detail you want to portray.

I followed a simple rule of thumb, and that was to keep my diagrams concise, cohesive, and manageable. Humphrey Sheil talks about avoiding splitting up diagrams, but only in sense that they should not be split along arbitrary lines. You wouldn't write 1000+ line Java classes to perform 10 unrelated tasks, so why do it in your UML?

Which one is the best, in terms of matching the SUN reviewer expectations?



The one that facilitates simple diagrams with a well defined singular objective. You can also talk about the structure of your diagrams in your supporting documentation if you want to make it super-clear to the examiner.
 
Pawel Piwowar
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks J J
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic