Passed SCEA part II/III with 85%

[Wen Hu]

Hi all,

I cleared SCEA part II/III. The results were in a week ago, but I hadn't checked yet. Marking seems to have taken less than 4 weeks.

My marks are as follows:
Class Diagram (44 maximum) .......................... 44
Component Diagram (44 maximum) ...................... 29 Sequence/Colloboration Diagrams (12 maximum) ........ 12

I had taken a minimalist approach which was OK for the class diagram and the sequence diagrams, but unfortunately somewhat too minimal for the component diagrams I guess. As Einstein once said "keep it simple, but no simpler".
Nevertheless I am quite satisfied with this achievement.


Hope this helps. Good luck to everyone who is still working on the assignment or waiting for the results.

Regards, Wen

[Mark Wassermann]

Congratulations!

Btw, my instructions say that it is not required to have each method name and attribute in the class diagram.

Am am a bit unsure whether this means no attributes or methods at all or "only the important ones" or "just the ones that are not obvious", i.e. just the methods in the remote interface in a session bean.

As you got full score for the class diagrams, it would be very interesting for me to learn about your approach.

Mark

[Alexander Krotov]

My congratulations too!

What do you think about component diagram, why they rated it 29?

[Wen Hu]

Thanks!

To answer your questions. I did not use methods or attributes at all.
As I said I kept things very simple. I used about 15 classes. I stuck to the specifications and did not include functionality that wasn't required, assuming that "the customer is always right, even when he/she is wrong".

I had one component diagram, one class diagram and four sequence diagrams.

I think my marks for the class diagram and sequence diagrams show that this "keep it simple" approach works well for the functional requirements side.

I think I lost most (all?) of my marks because I did not address the QoS requirements sufficiently. I tried to keep things simple with regard to the web presentation tier, because I was (and still am) convinced that being an architect doesn't mean that you need to flesh out everything the way it is done in the Petstore example. Also I probably lost some marks with regard to scaleability issues. I think I should have elaborated more on that.

HTH, Wen

[Mark Wassermann]

I have another question concerning the sequence diagrams:

When you say your approach was simplistic, does it mean that you had that kind of detail as in the study guide by Cade/Roberts where the components interact directly and left out classes like view helpers or business delegates?

Thanks for your help,
Mark

[ravi kala]

Congratulations on your achievement.

I cleared Part I, two weeks back with 85%. I need to start my preparation for Part II/III. I am a developer with 2 years of experience and I have never designed or architect any project before. Can you please advice, how I need to start my preparation for part II? Can you please provide useful tips for people like me , who have little or no practical experience with design & architecture? Please share the useful books or links I can refer.

Really appreciate your help

[neelArchitect saha]

Congrats.
I want confusion on how to connect Java Application.
I am thinking of
Java Swing Application-->Servlet-->BD-->SF-->EJB
Can i do this way.What will the preformance problem
I have seen in many posts directly connection java applicaton to Business tier via RMI/IIOP.
Can any one help me pros and cons of two solution

[Wen Hu]

When you say your approach was simplistic, does it mean that you had that kind of detail as in the study guide by Cade/Roberts where the components interact directly and left out classes like view helpers or business delegates?

Yes

I cleared Part I, two weeks back with 85%. I need to start my preparation for Part II/III. I am a developer with 2 years of experience and I have never designed or architect any project before. Can you please advice, how I need to start my preparation for part II? Can you please provide useful tips for people like me , who have little or no practical experience with design & architecture? Please share the useful books or links I can refer.

I don't think I can be of much help to you. My background is very different and my preparations probably would not work for you. I can recommend two books that I have used: 1) J2EE Design Patterns by William Crawford and Jonathan Kaplan, 2) Core J2EE Patterns by Alur, Crupi and Malks. Also in your case I would study the Petstore example carefully. It won't hurt if you take a look at the Struts framework too, as it puts a lot of design patterns into action.

I want confusion on how to connect Java Application.
I am thinking of Java Swing Application-->Servlet-->BD-->SF-->EJB
Can i do this way.What will the preformance problem
I have seen in many posts directly connection java applicaton to Business tier via RMI/IIOP. Can any one help me pros and cons of two solution

I think you need to look at the nature of the client-tier solutions, i.e. browser clients versus application clients. Why would you want to connect the application with the servlet in basically the same way that a browser client would? The pros and cons of browser vs. application will be reflected in the connections. E.g. statefull versus stateless, session management, pros & cons of the physical connection, handling security and the possible benefits of a client container.

HTH, Wen

[neelArchitect saha]

I think benefit of using servlet in Java Client application is ,i Can use security features in one place ,ie servlet.Session management i will do on statefull session bean.
Can i connect Java Client to servlet through HTTP

[Wen Hu]

Of course you can connect an application client to a servlet using the HTTP protocol. The basic API is in the java.net package. You could also use frameworks such as httpclient to handle all of the plumbing.

However, you mentioned security as one of the reasons for choosing this solution. The web and ejb containers both support declarative and programmatic security. Security credentials, the principal, security roles etc. can be shared. (The book about EJBs by Kevin Boone has some nice examples on this.)

Also, session management using session beans is only part of the story. The application client still needs to support the session by: 1. cookie, 2. url rewriting, 3. HTTPS or 4. something proprietary.