Part 2 and 3 91 %

[Dhiren Joshi]

Just saw my results on the Cert Manager Here r my results.

Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061)
Grade: P
Score: 91
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) .......................... 38 Component Diagram (44 maximum) ...................... 41 Sequence/Colloboration Diagrams (12 maximum) ........ 12


Couldnt have done without the help of this forum.
Especial Thanks to Ajith, Josep, Deepak ,Parag ,AJ Kumar, Sridar ,Herianto and every one involved. Couldnt have done it without you guys and every one on the forum.

Lots has already been written in the forum alreay by previous SCEAs.
Here r my 2 cents.
Go ahead with whatever design seems reasonable. Even if u have tweaked the class diagram ,explain it in detail be consistent with your assumptions. (May be that is why I lost some marks there.)
However many extra assumptions u make it doesnt matter.
If u justify your assumptions Sun will not penalise you.
If u want to add extra sequence diagrams Go AHEAD.

My component diagrams were Tier based.
I submitted a document very exhaustive in assumptions and added sub sections for tier based design decisions and security also tier based.

The main HINT I took from Alain Hunsung's POST about two meanings for flights. I think that is the core of the design.

I will be around on the forum to answer any questions.

SCEA .. it does sound GREAT



I thank every one again on this forum for the valuable discussions.

Dhiren
[ April 18, 2005: Message edited by: Dhiren Joshi ]

[Prasad Kuppa]

Hi Dhiren ,

Congratulations! Great job!

When did you submit your part2 and take part3?

Thanks,

Prasad

[Joseph Zhou]

Congratulations! It's great!

[Johannes Postma]

Congratulations!

[Marcelo Sousa Ancelmo]

Congrats, great score



Regards,

[Deepak Pant]

Dhiren,

Congratulations !!! Its all over now !!!

Enjoy

Deepak

[sys alley]

Congratz , for your score.
you told ...

*The main HINT I took from Alain Hunsung's POST about two meanings for flights. I think that is the core of the design.

do u like to tell us the two meaning of the flights in detail?

My email is [e-mail]

thanks
william

[Alexander Krotoff]

Congratz you, great result !

I passed SCEA too (I saw that 20 minutes ago ) with I-89%,II-III - 92%, so I am feeling exactly as you!

Yep, 2 meanings of flight - is really one of the core things.
I sent only as diagrams as certification requires, but I made huge bunch of explanations (i.e. I simplified this or those artifact on a diagram because..). Consistent and efficient architecture decisions description - very important thing too.

[Dhiren Joshi]

Thanks every one.

The main HINT I took from Alain Hunsung's POST about two meanings for flights. I think that is the core of the design.

do u like to tell us the two meaning of the flights in detail?

I cant give that out as that would be violating Suns policies :roll: but I can give u more hints us to how to come up with the design. The final interpretation of the flight has to be your own
decision.

IF u look in prepared itinerary use case .. Read that use case carefully . The term flight has two meanings. Read conditions and the flow.
Compare the two and come out with some logical conclusion which will satisfy the meaning of flight for both scenarios.

Also remember whatever u interpret it as. There is no right or wrong decision. If u can justify it and put assumptions and be consistent with your assumptions in all your diagrams then Sun wont penalise u for it.

HTH
Dhiren

[Daniel Amadei]

Hi!

Congrats!

How many component diagrams did you have?

I'm planning to deliver 2, do you believe this can be a problem?

How many components did you have? Did you map all your classes (business (entity beans?) and service classes) to components?

Thanks a lot!
Daniel

[Dhiren Joshi]

Thanks

How many component diagrams did you have?

I'm planning to deliver 2, do you believe this can be a problem?

How many components did you have? Did you map all your classes (business (entity beans?) and service classes) to components

I had one diagram but it doesnt matter how many component diagrams u have as long as u are able to explain your architecture by asusmptions and documentation.
I showed about 35 components .
I designed in a tier format and every tier I showed only those components and then I made dependency links between tiers.
I didnt map all my business entitys especially for the composite ones I reduced them by putting notes and I didnt show thier DO or BO's.

Show relevenat components which makeup a J2EE pattern implmentation and show the logically dependencies among them and if u have subsystem depict that too.
HTH
Dhiren

[Goutam Bhattacharjee]

Hi Dhiren,
1st of all, heartiest Congratulations!


I wud like to know, what assumptions did u make about the 'Frequent Flyer' system? According to the requirements, it cannot be re-written.

In fact, there are 2 prominent points:

1. While it is understandable that the Oracle database in the 'Frequent Flyer' system can be accessed by the Business Entities and DAO(s) of the new application, but how do u propose to reuse CGI & perl scripts?

2. Let's assume that we create links from the new j2ee application, to the pages of the 'Frequent Flyer' system. That would mean that the HttpSession established in the j2ee web-app, be carried over to the 'Frequent Flyer' web-app. This can be achieved by session replication techniques. However, the big qs is: if a Customer, after visiting the pages of the 'Frequent Flyer' web-app, wishes to return to the j2e web-app?
To do this, we need to introduce links/buttons in the 'Frequent Flyer' web-app, which point to the j2ee web-app. But, as per requirements, the 'Frequent Flyer' system cannot be re-written!


Considering these issues, I am proposing that ONLY THE DATABASE from the 'Frequent Flyer' system will be reused, and NOT THE WEB COMPONENTS

Please opine.
Will be obliged if others also join in....

Thanks in advance.

[Dhiren Joshi]

Thanks Goutam.

1. While it is understandable that the Oracle database in the 'Frequent Flyer' system can be accessed by the Business Entities and DAO(s) of the new application, but how do u propose to reuse CGI & perl scripts?

2. Let's assume that we create links from the new j2ee application, to the pages of the 'Frequent Flyer' system. That would mean that the HttpSession established in the j2ee web-app, be carried over to the 'Frequent Flyer' web-app. This can be achieved by session replication techniques. However, the big qs is: if a Customer, after visiting the pages of the 'Frequent Flyer' web-app, wishes to return to the j2e web-app?
To do this, we need to introduce links/buttons in the 'Frequent Flyer' web-app, which point to the j2ee web-app. But, as per requirements, the 'Frequent Flyer' system cannot be re-written!


Considering these issues, I am proposing that ONLY THE DATABASE from the 'Frequent Flyer' system will be reused, and NOT THE WEB COMPONENTS

The CGI Perl and Oracle collectivley make the FFMS currently.
U are not supposed to rewrite any part of it at all does not imply that u can not put a wrapper around it for the web front end interaction. Thats is what u need to architect how to connect with that subsystem as well as incorporate the J2EE functionality.

the entire system is currently web based and if u dont rewrite but u want to move it to a J2EE architecture, u can do so using the screen scraper technique to access all the information. How u connect to the system is entirely upto your architecture. There are many ways. Remember with the reuse keyword ,it means the entire web app currently AS is so what is accessible to u are HTML outputs of the web app.

Any other assumptions and requirements u add could me extra.

Reusing only the DB is not really the exact of a rewrite. IF u want u could add that in your assumption and proceed but considering 0.5 million has been spent on it, this may be violation of the requirement laid down.

HTH
Dhiren

[Lucy Hummel]

Hi Dhiren,

Sorry, but I do not get you point in suggesting

screen scrapter.

As far as I know the term of Screen Scapter is

Software that allows a PC to intercept character-based data from a mainframe -- often presented in a green screen -- and present it in an easier to understand graphical user interface (GUI ). Newer screen scrapers present the information in HTML, so it can be accessed with a browser. Leading makers include Mozart (www.mozart.com), Flashpoint, Inc. (www.flashpt.com) and Intelligent Environments (www.screensurfer.com).

The quote is from http://www.webopedia.com/TERM/S/screen_scraper.html

Since Frequent Flyer Mileage is not a mainframe in my opinion screen scraper is not the to be used design pattern. In my opinion a right one is the design pattern adaper.

Here one definition of adapter:

Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.

Looking forward to your opinions.

Lucy

[Ajith Kallambella]

Congratulations Dhiren. Good job!!

[Dhiren Joshi]

When I meant screen scraper I didnt mean the literal meaning for a main frame screen scraper.
The techonology u wwill need to use would be the same but u wuold scrape through a web page so the term screen scraper. (It would be a HTML parsing of sorts)

HTH
Dhiren

[Robert Paris]

Congrats!

Question: how long does it take to get your results back?

[Lucy Hummel]

Hi Dhiren,

Originally posted by Dhiren Joshi:
When I meant screen scraper I didnt mean the literal meaning for a main frame screen scraper.
The techonology u wwill need to use would be the same but u wuold scrape through a web page so the term screen scraper. (It would be a HTML parsing of sorts)

HTH
Dhiren

Now I got your point. I agree that is an option.

Thanks for your explanation.

Lucy

[Joseph Zhou]

For the SCEA, screen scraper is OK, but for real project, I think we'd better leave it as last choice. It's fragile, especially when interfaced with the more complex http pages(than command lines). I think DAO is good, but actually we have to "rewrite" at least three methods: get/add/redeemPoint(). if you don't count this as "rewrite", it OK for you.

[Lucy Hummel]

Hi Joseph,

My first option to connect to FFM was to use an adapter class. The adapter comunicates with FFM by using HTTPConnection.

So, my option was different to yours. You suggested to communciate directly with the database.

I asked myself: Is my option also a valid one?

What do you think

Looking forward to your opinions
Lucy

[Billy Tsai]

congratulations

[Joseph Zhou]

Hi Lucy,

IMO, using HTTPConnection means you want to parse http pages, that is screen scraper. Just as many people mentioned here, it's a valid opition.
My previous post just want to say, in real world, you'd better to aviod it if you have any other option.

[Lucy Hummel]

Hi Joseph,

Thanks for telling. I got your points

Lucy

[satyanarayana katta]

Hi Dhiren,

I have just finished my SCEA Part I and wanted to take Part II. I read through all the posts and found it very useful. I have some doubts here. Hope you can clarify this.

Is it required to show the thick client design in the assignment. If we can show the design of the middle tier and how it can cater to any type of client won't it be sufficient.

I read in on the posts that someone didn't show the thick client tier in their assignment. Any suggestions?

[Dhiren Joshi]

Is it required to show the thick client design in the assignment. If we can show the design of the middle tier and how it can cater to any type of client won't it be sufficient.

I read in on the posts that someone didn't show the thick client tier in their assignment. Any suggestions

Thick client. R u referrring to the Swing. Yes from my experience, U need to show that at least in the component diagram and explain security u would use for it .
U dont need to show for sequence diagram any flow particularly to the client but again your sequence diagrams need to be good enough in case that flow needs to be supported for thick client.
Thats the technique I used and u would need to add a few assumptions design detail for the client so that the grader would understand your design.

HTH
Dhiren
[ May 08, 2005: Message edited by: Dhiren Joshi ]

[satyanarayana katta]

Thanks Diren. That was really helpful. I have another question regarding security.

Container managed against application managed.

The problem is if I just say container managed I am sure it wont be sufficient. What level of details we need to furnish?

[Wilson Liu]

Originally posted by Dhiren Joshi:


Thick client. R u referrring to the Swing. Yes from my experience, U need to show that at least in the component diagram and explain security u would use for it .
U dont need to show for sequence diagram any flow particularly to the client but again your sequence diagrams need to be good enough in case that flow needs to be supported for thick client.
Thats the technique I used and u would need to add a few assumptions design detail for the client so that the grader would understand your design.

HTH
Dhiren

[ May 08, 2005: Message edited by: Dhiren Joshi ]

Hi Dhiren,

For the use cases' sequence diagrams, what do u think if I just use "Client" to represent both type of client (i.e. Swing and Web)?

I find that many ranchers design a web framework for the web client. I wonder whether the framework for spring client is also needed.

Thanks.

Wilson Liu

[kundan varma]

HI congrats dhiren
People are talking about 1,2,3 components diagrams. I have one question, when we seperate component diagrams. i mean one component diagrams consists many component then why we need 2 component diagram.
plz clarify
Thanks
kundan

[Dhiren Joshi]

Container managed against application managed.

The problem is if I just say container managed I am sure it wont be sufficient. What level of details we need to furnish

I provided lot of detail in my assumption doc by breaking them in to different tiers and explaining. So much explaination is not required but SSO was an issue for me and also there isnt much from UML's u can depict about security so I took the safest bet by explaining in the Doc. Thats what u should do.
Especially mention the signon criteria for app client.
As for the CM against app managed I choose the second as I couldnt explain a lot of Sign on issues with CM.




For Wilson

For the use cases' sequence diagrams, what do u think if I just use "Client" to represent both type of client (i.e. Swing and Web)?

I find that many ranchers design a web framework for the web client. I wonder whether the framework for spring client is also needed.

U dont need a framework for swing (I assume spring is typo for swing client. Just a few components r enough to show in the diagram.
Client would work for sequence diagrams as long as u include no web dependencies. Tricky how u make it work.


For Kundan

People are talking about 1,2,3 components diagrams. I have one question, when we seperate component diagrams. i mean one component diagrams consists many component then why we need 2 component diagram.
plz clarify

Only one is good enough .Make sure u demark tiers correctly and show the components correctly in each tier. Thats should do. I had one component diagram.

HTH
Dhiren
[ May 10, 2005: Message edited by: Dhiren Joshi ]

[kundan varma]

HI Dhiren
What are the techniques available to use the whole frequent flyer mileage system? I dont want to violate sun's rule so let me put it in more general way. Basically what are the techniques available to reuse or connect to a cgi-perl system using both servlet and java rich client ?

Thanks
kundan

[Wilson Liu]

Hi Dhiren,

Thanks for the reply.

Yes, it is a typo mistake.

I am now just designing the interaction of the bussiness objects to support the use cases. Therefore, I still don't begin the design of how the web/spring clients call that objects.