Finally got my result on SCEA Part II and I passed with 91%
Test: Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061) Date Taken: 2006-07-31 13:00:05.030 Registration Number: ********* Site: nj26 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) .......................... 39 Component Diagram (44 maximum) ...................... 41 Sequence/Colloboration Diagrams (12 maximum) ........ 11
Thanks everyone on this forum. I basically had one class diagram (have 25 classes), 3 component diagrams and 5 sequence diagrams (for each use case). I feel its important to document assumptions and reason why a paricular design will take care of functional and non functional requirements.
-------------------- Please provide some learnings and word of advice for those who are planning to do SCEA. --------------------
SCEA Part-I: Few topics like Protocols, I18n , Legacy connectivity etc where its is easy to score. Its better not to loose any point there.
Assignments: Document each and every assumption you make. Also, give reasoning as to why you think your design/architecture is going to meet requirements (desired response times etc). Read between the line in the requirements doc (Travel Agents require quick response etc) while choosing your components (SLSB/Entity Beans etc). Use cache where ever you think they can give better performance.
How could you convince the evaluator that your architecture will fully satisfy the response time requirement (<=5 secs) before building it? Did you mention any testing data from some similar running system to support it? Because it concerns with software, hardware, as well as network bandwidth.
Did you mention the UML version used in you document and what UML version and tools did you use?
--------------- How could you convince the evaluator that your architecture will fully satisfy the response time requirement (<=5 secs) before building it? Did you mention any testing data from some similar running system to support it? Because it concerns with software, hardware, as well as network bandwidth. --------------- No, I did not mention any test data. I based it on assumptions/experiences (which are good to state in the document). You can assume that Travel agents will be using better network bandwidth than web clients (dedicated lines etc.). Few things which I mentioned before ( like Caching /coarse-grained calls by using broader queries and larger result-set retrieval/ separate delegates etc.) can help. ---------------
Did you mention the UML version used in you document and what UML version and tools did you use? --- I did mention the UML version but not the tool(s).
Thanks for your good answer, Sanchit. Those also are what I could image to make the response as quick as possible. But until you build a first vertical slice based on the architecture and test it, it is not 100% sure that response time will be guaranteed, except you have positive experiences on building similar systems. At first, I didn't know how to convince the evaluator of my approach. As you passed with good score, I'll do the same way.