Test: Sun Certified Enterprise Architect for Java 2 Platform Enterprise Edition Technology Part II (310-061) Date Taken: 2005-07-31 22:00:56.937 Registration Number: ****** Site: *** Grade: P Score: 97 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) .......................... 43 Component Diagram (44 maximum) ...................... 42 Sequence/Colloboration Diagrams (12 maximum) ........ 12
How many classes in your class diagram? Did you provide attributes and method names of the classes? Did you change the multiplicity of the BDM? How many components in your components diagram? Did you follow Cade's book for the assignment? Thanks.
Hi, Thanks all of you. How many classes in your class diagram? I got around 27-30 classes Did you provide attributes and method names of the classes? yes you change the multiplicity of the BDM? No How many components in your components diagram? around 60-70 components Did you follow Cade's book for the assignment? partialy, I followed core j2eepatterns, petstore, sun blue prints
Please read the scenario below: A flight (UA 147) has the route A-->B-->C-->D, a customer books the segemnt B-->D. I define a leg as a flight between two contiguous airports. Usually, airlines manage seat allocation in a seat inventory, they track seat usage per LEG.Seats are allocated to each leg of the flight. My question: Do you think that i should represent this seat tracking mechanism accurately in the class diagram or let it as an implementation details and write on some assumptions, in this case seats allocation will be modeled at the flight level and not at the leg level ?
Hi Marie, It depends , you can design your system from any concept. But I think the good design should interpret everything, I mean the visibility should be more. Another thing, from the design, the system should be implemented. so if possible make a clear design which will make easier for the system to implement.
Thankx for your reply. I agree with you that our design solution should give the developers all informations he/she needs for the easiest implementation. A clear and complete UML model, well annotated, is more explicit than hundreds of sentences.