I have successfully completed SCEA Part II/III with 90. My score break down is as follows
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) ...................... 40 Sequence/Colloboration Diagrams (12 maximum) ........ 11
It is also worth mentioning that I had completed SCEA Part 1 with 97.
I take this opportunity to thank all ranchers who made me think think and think and succeed finally.
I want to thank Parag Doshi particulary. His discussion gave me a good insight on the Assignment. I closely followed his each and every points and finally end up with a good design.
It is also worth mentioning that I have no any prior Certifications. I directly jumped into SCEA and went through a hard time and succeeded finally. It took me more than 1 year to complete this certification. When I started my Part II, I was clueless. But this forum helped me a lot. So I will hang around sometime to answer your questions. These days I am facing a deadline. So don't worry. I will answer your questions even bit later
I had exactly 20 classes in my class diagram. In addition to it 3 EJB classes having dependencies to entities in the class diagram as Cade has done.
I have elaborated the Customer with more and more classes as in the Petstore architecture. I modified the BDOM slightly. Exactly I added one more class to the BDOM as from my assumptions. Except that I didn't add/remove navigation, multiplicity, association types to the BDOM. But when I put a new class, I added navigation, multiplicity and association types (aggregation/composition/reference). But don't forget I have lost 5 marks here.
I had 1 Component Diagram with 34 Components exactly. Most of the Classes of type Aggregation/Composition in Class diagram were made CompositeEntity in the Component Diagram. To avoid complexity I avoided some dependencies but put a note on that.
I had only 5 Sequence Diagrams for Create Profile, Prepare Itinerary, Change Itinerary, Pay for Itinerary and View Frequent Flyer. I explained the Login use case in my support document but no sequence diagram. My sequence diagrams were merely for WebClient. I gave some explanation on how GUI Client also can fit here.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com