This forum was invaluable. Without it I might have just spun around on part 2 forever, afraid to submit anything.
Grade: P Score: 95 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) .......................... 44 Component Diagram (44 maximum) ...................... 39 Sequence/Colloboration Diagrams (12 maximum) ........ 12
Funny I didn't lose the points where I expected to. I really thought the sequence diagrams were where I'd miss the mark.
can you modify the business domain model? can you maintain the session using stateful session bean?
Remember, the analysis model is pure problem-space. Some (de)normalization or clarification in the implementation model is to be expected. For what it's worth, I added a key concept that I thought was missing, fleshed out with some implementation-oriented classes, and made a judgement call about what one of the multiplicities really should have been, but didn't take anything material away from the analyst's model. Tracability is the key here. Make sure to explain yourself in your assumptions document.
The EJB spec advises that session beans were intended to be stateful, and that stateless sessions are a special case. That being said, there's no right or wrong answer to your question in isolation. What's more important is that you be able to identify the tradeoffs and rationalize your decision.
Could u pls share your thoughts on Part 2/3. Thanks
The biggest thing is, apply the KISS principle. Or, to paraphrase Einstien, your submission should be as simple as possible, but no simpler. I've been working in a pretty high-ceremony environment for a while, so it took a while to get that little idea through my head. Actually, it was this forum that brought me around to a simpler approach.
Look at the case study in the Cade book. I had some pretty laborious diagrams at first, but then I scaled them down to the level of detail in that case study.
I did use some of the patterns from the Core J2EE Patterns book, but only where they felt natural. I used Struts, but that was my personal preference. I don't know that a MVC framework is required, but it is a blueprints best practice to use one.
Rose is horrible for sequence diagrams. If I had to do it over, I'd draw them in crayon and scan them.
Overall, I found the best study material to be the Designing Enterprise Applications... blueprints book and the Cade book. I started off analyzing Petstore to get some feel for the kind of design practices they might be looking for, until I understood that Petstore uses everything but the kitchen sink, for the purpose illustration, and no real application should be designed that way.
Remember when shopping for study guides, you can't judge a book by it's mass. On the moon a thick book and a thin one will both fall at the same rate.
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop