Hi, again!
This is for the people who are in the beginning of
SCEA journey.
I am reading some messages with high concerns about part II. Well, IMO there�s nothing extraordinary in the assignment.
Everybody who has created any kind of
J2EE application has passed for the same concerns. In fact, what bothers most in the assignment is the incompleteness of the requirements. So what? Welcome to the desert of real (
Morpheus).
In real life, users and stakeholders oftem express themselves with incomplete statements. Business analysts often miss some important requirements.
So, you will have to make some assumptions. But be careful with your assumptions. If you are making too much assumptions or too high level assumptions (which should create greater impact on the project), maybe you haven�t read the assignment enough.
Also, be aware that not all requirements are the same for all assignments, so, avoid following close other participant�s solutions. Try to figure out from the discussions the High Level architectural decisions.
But people who had never created a distributed J2EE application should fear the assignment. If you are in this situation, I recommend you take just step I (if you haven�t taken it yet) and prepare yourself better. Try to engage J2EE projects or create a new one from the scratch. Use some kind of Web Stress tool to create traffic for your application and see the actual behavior of EJBs.
I have uploaded my assignment yesterday (August 29, 2006) and I am very confident that I have done everything that was possible.
Cleuton (Brazil)
