It took me around 6 months to finish and submit the assignment - mid July. I was not able to give proper time for this due to work and family. I took exam the next day. I got result back in 4 weeks. The result was posted in http://www.CertManager.net/sun_assignment.
I went over the requirements many times. Every time I re-read the requirements, I seemed to find problems in my design and changed it several times. Posts in JavaRanch helped to find answers to many of my questions and doubts.
I had 1 class diagram, 1 component diagram and 4 sequence diagram. Clas diagram did include session beans. Was careful on navigation, multiplcity, streotypes and other UML rules. Added several classes to meet the business requirements. Showed how I used patterns in Component Diagram. 1 Sequence Diagram for each use-case.
1) Did u change BDOM. 2) Did u use any inheritance in ur design. For eg., User divided into Customer and TravelAgent 3) Did u define attributes and methods for all the diagrams 4) If you didn't change the BDOM then how did you handle lay-over case...hope this question don't violate rules. 5) How did you categorise ur assumptions page
Anil, 1. No. I didn't change BDOM. But did add classes based on requirements. 2. No inheritance in BDOM. 3. Attributes, yes - all. For BDOM attributes are important coz BDOM basically represents DB schema. Methods - some. 4. lay over case? 5. 4 page file - assumptions for use cases, BDOM etc.
Sanz, My meaning of lay-over is if two 'Source-Destination' invloved for one segment like, Source-A, Stopover-B,Destination-C Actual flight is A->C but in case if no direct flight then its break-down into two legs, A-->B and A-->C but still A-->C remains as actual Source-Destination with only one price. So how did you handle this case.
I think this is where the Segment and Flight come into play. Flight and Segment can have many to many relationship. Flight AC is made up of SegmentAB and SegmentBC. So you may either need to tweak the multiplicity or make some assumptions of your own and put that in Assumptions document.