That should be the first step, followed by the architectural design
I have not done any requirements analysis yet.
By archetechtural design, do you mean 'spec'ing out the different layers required in the application and deciding on how the data is going to be persisted and retrieved and how it is going to be passed on between the different layers(like deciding whether I will be using an ORM tool or a dataaccesslayer, and whether I will be using Web services etc. ?)
Prasanna Raman wrote:Should I just stick to OO design for now and then once I have a working application, build a GUI on top of it?
Prasanna Raman wrote:If someone can kindly confirm that my design is complete, I will start coding.
I don't really see anything particularly wrong with your design, except its usually better for money values to not be type double since all sorts of weird problems can come up that way.
As I know in javaEE Hibernate is preferred over jdbc.