In one of the post, I saw someone asking about using of frameworks for the assignment. Now my doubt is, why should the framework really be a point of concern. I mean, in the assignment, is that not enough to show our custom implementation alone. For example, instead of using Struts, why not show our custom front controller. Should that be sufficient? Any way, we are not going to show any configuration or code wise implementation..right!!
Another question which would really be lightening me up is with regard to the sample template assignment for reference. Is pet store assignment a good reference still? Are there any other sample applications which can be referred to, for grasping the expected outlay of our assignment?
My Another question is in continuation to my second point: Does Sun prescribe any standard template for the outlay of the assignment to be submitted? Can we use our way of presenting the assignment (Off course with the required class diagrams, component diagram etc) ?
Would truely and humbly appreciate your help.
You can use your own framework for some reason. But as an architect, the rue of thumb is try to use the existing proven framework because of principal of "use the product off the shelf"
From this, the question which arises in my mind is, in what context should we bother about a framework. Because we are not going to use any code or configuration. Is it that, for example if we use struts, in our architecture diagrams, we would be including the ActionServlet or FacesServlet (in case of JSF) instead of simple customized Servlet names? Is this the reason why we should be concerned about the framework we are going to use?
I think the same way as this. Although only the FaceServlet on your diagram, but by reference it, that means a lot, because behind of this, the framework or design pattern solve lots of problems that otherwise you have to do your own. As long as there is an user interface requirment, you need consider MVC, which is compsed of a set of core classes and other set of helpful utilites around the core.
The same principal fo other parts. You should not invent your own wheel as long as there are proven product off the shelf that can fit your situation. For example, you need handle transaction and security, EJB is perfect candidate to do it other than you do it yourself, EJB is another kind of framework for business tier. JPA is also a framework for persistence tier.
The framework and design pattern are everywhere. our tasks are how to use them and why use them in such way.