Win a copy of Functional Reactive Programming this week in the Other Languages forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

95% for Part II/III

 
Sanly Fang
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
just saw my score:

Grade: P
Score: 95
Comment: This report shows the total points that could have been awarded in each section and the actual amount of points you were awarded. This information is provided in order to give you feedback on your relative strengths on a section basis. The maximum number of points you could have received is 100, minimum to pass is 70. Class Diagram (44 maximum) .......................... 39 Component Diagram (44 maximum) ...................... 44 Sequence/Colloboration Diagrams (12 maximum) ........ 12

I submitted my assignment at 3/29 and took partIII essay exam at 3/31, the score is out at 4/22, I am supprised that the result comes out so fast, I believe it need took about 4-6 weeks, but only 3 weeks for me.

It's also strange that I lost all my 5 scores in class diagram, but I cannot know anything on what's wrong with my class diagram.
 
Daniel Amadei
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi!

Congratulations!!!

Can you tell how you did your component diagram?

Daniel
 
Sanly Fang
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have only one component diagram, tiered approach, more than 30 components, the diagram is drawn in a clean and concise manner, that is, merely show important aspects as opposed to every details.

for example, not showing all JSPs and business entities in my diagram, only important dependencies are labeled.

Regarding the common components that are shared among multiple tiers (for example, transfer objects, ServiceLocator...), a common package is introduced with comments attached.

As many other threads said, the component diagram is full of J2EE patterns, it's also true for me.

In my opinion, the following two items will do good to your component diagram:
1. Keep the diagram clean and simple, do not put too much details if the details will make the diagram messy and not readable
2. Reading "Core J2EE pattern second edition" will definitely help you gain high core.


Originally posted by Daniel Amadei:
Hi!

Congratulations!!!

Can you tell how you did your component diagram?

Daniel
 
Lucy Hummel
Ranch Hand
Posts: 232
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Sanly,

well done!
 
Olexiy Prokhorenko
Ranch Hand
Posts: 97
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My Congratulations!

+ 1 architect in our SCEA's community! :-)
 
Fabio Berrio
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Congratulations, nice score!!

Fabio
 
Rodrigo Dinis
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
 
Dhiren Joshi
Ranch Hand
Posts: 463
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Congratulations.

Dhiren
 
Goutam Bhattacharjee
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Congrats Sanly !

Can un provide some help on this:

How did you reuse the frequent flyer system? This is because the business req's says that this cannot be re-written/changed.

So, we may need to:

1. Contact the web front end of frequent flyer system and read HTML outputs

or,

2. Introduce JNI wrappers over cgi/perl programs

or,

3. Just use the frequent flyer database, with the award points calculation logic in j2ee components. (Possibly in the ejb layer)

I am confused. Which one is best. The last option seems the most conventioanl one, but it means that the front end of the frequent flyer system will not be used.

Regards
Goutam...
 
Sanly Fang
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Firstly, sorry for replying so late.

My opinion on FFMS integration is to keep things simple, I opts for option 1 in your solution list, anyway, this is an exam, we all know that in reality, it may not be good to reuse an external system via HTML output parsing.

I am lazy and deliberately neglect the details on this in my assignment, all I need to do is putting some comments in my diagram illustrating HTML parsing is used and maybe object wrapper is provided so that it's transparent to the client system on how FFMS is accessed.

Of course, it's ok if you take other approaches, I don't think it important as long as you can make it clear to exam evaluator.

Originally posted by Goutam Bhattacharjee:
Congrats Sanly !

Can un provide some help on this:

How did you reuse the frequent flyer system? This is because the business req's says that this cannot be re-written/changed.

So, we may need to:

1. Contact the web front end of frequent flyer system and read HTML outputs

or,

2. Introduce JNI wrappers over cgi/perl programs

or,

3. Just use the frequent flyer database, with the award points calculation logic in j2ee components. (Possibly in the ejb layer)

I am confused. Which one is best. The last option seems the most conventioanl one, but it means that the front end of the frequent flyer system will not be used.

Regards
Goutam...
 
John Arau
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Congrats Sanly !

What a score!

One Question. I'm trying do decide which way I'll do my presistence.
I like CMP with CMR for all entities, but the core J2EE pattern leaves me to believe that Composite Entity pattern is better (BMP+DAO).
What's your opinion ? Did use CMP?
 
Sanly Fang
Greenhorn
Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As described in "Core J2EE patterns second edition", there are two kinds of participants in Composite entity pattern: parent object and dependent object.

Parent object could be implemented as local entity beans, while dependent business objects could be implemented in either of two ways: POJO or local entity beans. The latter one, i.e. both local parent and dependent entity beans, are what I used in my assignment. I opted for CMP and CMR approach for the sake of simplicity. I keep in mind that for such as exam, it's good for both the exam evaluater and candidate to deal with simple solutions.

Of course, I put some word in my document in order to emphasize things such as local entity beans is used to implement Business Object pattern, local parent/dependent entity beans are used for Composite Entity pattern, CMP/CMR is choosed...

In summary, Composite Entity != BMP + DAO, it could be CMP + CMR according to the pattern definition.

The following paragraph is excerpted from the solution section of Composite Entity pattern in "Core J2EE patterns second edition":

"With EJB 2.x, you can implement entity beans as remote or local objects. When implementing entity beans in EJB 2.x, use local entity beans to implement your parent Business Objects. You can then choose to implement your dependent objects as POJOs (as you do under the EJB 1.1 specification) or local entity beans. The relationships between the parent and dependent Business Objects can be implemented using bean-managed relationships (when using BMP) or CMR (when using CMP). To implement CMR, the dependent objects must be implemented as local entity beans instead of POJOs."


Hope it can help you.


Originally posted by John Arau:
Congrats Sanly !

What a score!

One Question. I'm trying do decide which way I'll do my presistence.
I like CMP with CMR for all entities, but the core J2EE pattern leaves me to believe that Composite Entity pattern is better (BMP+DAO).
What's your opinion ? Did use CMP?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic