A good object model for a decent-sized application takes weeks to construct, and (in my experience) months to refine.
SCJP
When I first started Java programming I used a very early edition of Jacquie Barker's book (on Amazon.com for example) - it's excellent for explaining how to develop a Java application from scratch. You'd find Parts 2 and 3 most useful as they walk through identifying object models using UML, to converting those into Java code. You can skip all the beginner Java code and you can apply the exact same principles to EE applications (also look at the Blueprints to reuse common ideas and save some time). You need to make a distinction between the object model (the basic POJOs based on your use case analysis) and the Web framework (servlet frontends, JSP views, and data storage).Well if you know any books/references for designing,architecture of the requirements ,which will help me to develop this model as you have, mentioned with some examples to study and understand,it will save a lot of time
The premise is that your entire application is object oriented so everything is describable as a class (with accompanying methods). The object model should describe everything there is to encapsulate from the real world into your application. The "plumbing code" (i.e. how that model is updated, what JSP views are needed etc.) is not specified in the basic description of the model. However, as I mention above, with Java Persistence Architecture (JPA) now being deployed in Web containers, you can easily annotate your object model to load and update from a database automatically so you don't need to worry too much about how the data is stored (other than designing the database structure).what does a object model need to include? ... should it also include the parts which interact which the database or write to a xml file? OR are those taken care of in data model?
Trust God, but always tether your camel... to this tiny ad.
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|