I am little unsure where can i use creational patterns in my solution approach.
In Part 2, if i try to base my solution on JSF technology then Model java object(POJO) will come presentation tier to business tier and with some additional information, i plan to persist the same.
So i am not sure, where the creational patterns will come in picture? Will they fit in presentation tier ? If yes how do i show in class diagram.
Second question - > My class diagram has gone little big as i am showing all the interfaces and implementation class which i am creating including utility class, persistence class, beans..etc. I know there is no line drawn like what all we need to show in class diagram..but is it ok to show all classes (except the JSPs and framework classes) in class diagram like till DAO layer.
IMHO, I wouldn't try to retrofit any design pattern into my class diagram. If it is not very obvious as to where the creational pattern is required, chances are it is not a good fit anyway in the class diagram.
Regarding the class diagram getting complex, the rule of thumb given by the authors for all diagrams is that for the complexity level of the provided assignment, a maximized browser window in a monitor at 1280 * 800 resolution should not need scroll bars. So if your diagram does not meet this test, you will probably have to optimize your class diagram and remove some low value classes/interfaces and retain only significant classes/interfaces etc.