Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Supporting Architecture doc for part II

 
Parag Doshi
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do we need to mention in our documentation what version of J2EE is the solution based on? The reasoning behind this question is that, if I choose BMP over CMP, then there are different views on the performance impact depending on what version of J2EE and EJB it is based on.
CMP was not that great in EJB1.1 but it supposedly got better with EJB2.0 (local interfaces etc). In the same vein, choice of Composite entity pattern was considered quite good in EJB1.1 but local interfaces have negated its importance in EJB2.0


Thanks,
Parag
 
Siddhartha Bhattacharya
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, you don't have to.
 
Ramon Gill
Ranch Hand
Posts: 344
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think its a good idea to mention the J2EE version, as it may help the examiner to understand your assignment better.

I agree you don't have to though.

Ray
 
Ajith Kallambella
Sheriff
Posts: 5782
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You don't have to, but it is certainly a good idea. If you ask me, I'd say you must

Here is the reasoning - think beyond just the test.

If you were an actual architect and writing all these documentation, would you omit such an important detail as the version? Moreover, you will be responsible for justifying your design choices and if a later version improvises on a shortcoming there by making an approach(or a pattern) no longer relevant, you certainly want to include that in your documentation somewhere.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic