Please find my comments here. (I'm not a guru, but tried to comment)
Chiraunji Lal wrote:Hello All Ranchers,
I have been a silent member of this group for a very long time and this group has helped me a lot in passing part-1. Now I am moving to part-2 and I have few basic queries regarding the assignment.
1. Can we design the system based on STRUTS or JSF frameworks? Any specific preferences and do we need to mention the reason for choosing the framework in the assumption sections?
There is no guideline mentioned on usage of frameworks any where. My suggestion is go for the framework which is designed by Sun.
2. Do we need to add all the classes, starting from action servlet to DAO layer, in the class diagram? I guess JSP's should not be part of class diagram, please correct me if I am wrong.
If you search in this forum, there are many posts available. Different people have different thoughts on it. Coming to me I followed an approach where class diagram contains only Business domain classes and major technical classes like managers and showing all framework related classes as components in component diagram. For sure, JSPs are not part of class diagram.
(Note. I'm still waiting for my results)
3. Can we separate class diagrams into different layers?
In my opinion, yes why not. But you should have proper links between diagrams.
I know my questions might be very basic but would really appreciate if someone can reply to the post.
I would agree with J..don't try to fit the solution into the framework..rather look at the problem context and see if the framework fits into the functional and non functional requirements. In the real world i have seen a lot of people trying to do the former only to experience fatalities later...beware of 'buzzword design'..
I would also agree that it is better to stick to sun specifications (JSF,EJB,etc.) as far as possible...i am sure the examiners would appreciate it..after all ..it is sun which gives you the certification and not apache/spring..
Now to the question of splitting class diagrams, i think splitting it by layers is a rather bad idea because typically class diagrams need to show associations,dependencies,etc...and breaking a class diagram by layer makes such representations difficult and clunky..if you think your class diagrams are becoming too complicated..consider splitting them by functional area..but you need to walk a very tight rope here..as this can get very messy if not done right(read done very granually)..but this approach has worked for me in the past..
Showing JSP's in design..is something i havent heard of so far..so i would advice against it..and i believe..you should all the important classes and interfaces which occupy your solution space..because if you dont show something..its assumed both by the examiner and you..and two people may not make the same assumptions all the time..
Hope these help..
OCMJEA/SCEA, SCDJWS, SCBCD 1.3, SCJP 1.4
My SCEA experience:http://javalogue.blogspot.com/
Tick check! Okay, I guess that was just an itch. Oh wait! Just a tiny ad:
a bit of art, as a gift, the permaculture playing cards