Win a copy of liveProject: Protecting User Data with Spring Security and OAuth2 this week in the Spring forum!
  • 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
  • Paul Clapham
  • Ron McLeod
  • paul wheaton
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Piet Souris
Bartenders:
  • salvin francis
  • Mikalai Zaikin
  • Himai Minh

Part II - J2EE Design Patterns

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi SCEAs and SCEAs-to-be!
Do you think we must explain the J2EE Design Patterns if we use them in Part II, or is it enough to show e.g. the UML stereotype "BusinessDelegate".
 
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I assumed that the assessor knew the well-established J2EE design patterns and just referred to the "Core J2EE Patterns: Best Practices and Design Strategies"-book.
Best regards,
Jacob Grydholt Jensen, SCEA
 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Its a very good question...Hey Jacob..what Roger means is that..
1-- do we explicitly need to write the Design patt stereotypes somewhere
2-- or writing in docs is enough
3-- or dont write anywhere, the assessor will understand by himself
By what i gather from ur answer, is that u followed option 3..Correct me if otherwise and sorry for misunderstanding..
It would be very helpful ( at least for WIP stage guys like me ) if more responses r there to this qs, as to what generally people have done..Thanks and my regards buddies...
 
Roger Zacharias
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I decided to only write the stereotypes and omit the description of each pattern, but refer to the "Core J2EE Patterns".
Roger
 
Ranch Hand
Posts: 124
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Nishant,
From what I understood, ppl are trying to say that it is enough to show the stereotype in the diagram for example <<BusinessDelegate>> and then mention the same in your supplimentary documents by referring them to the Core J2EE Patterns.
Dinesh..
 
Anonymous
Ranch Hand
Posts: 18944
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by dinesh pande:
Hi Nishant,
From what I understood, ppl are trying to say that it is enough to show the stereotype in the diagram for example <<BusinessDelegate>> and then mention the same in your supplimentary documents by referring them to the Core J2EE Patterns.
Dinesh..


Yes, this is the approach I took. Thanks for explaining it In most cases, I chose not to show a stereotype if the use of the pattern was obvious.
[ November 22, 2003: Message edited by: Jacob Grydholt ]
 
You showed up just in time for the waffles! And this 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