Win a copy of The Business Blockchain this week in the Cloud forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Factory Home

 
Neetu mukur
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Ranchers,

Little confuse after searching the forum, I read the assignment over and over and want to make sure I am doing it right ..
Assumtion here are
1) Design has a status (flag/enum) as 'Completed','Incomplete' etc and has many Products
2) Product is a House (has a price) and many Componets

Design>>Products>>Components

Now my main concern is where to put the the Foundation,Walls,Roof etc, should they will be treated as Components ?? or
should I attached them to Proudct/House as it done in BDM (1 Foundation,1 Roof, n walls etc)

3) Are we have to include all the EJB and Business Handler Classes in Class Diagram ? I was thinking the Class diagram will only show my model i.e Entity Classes and Relationships (that is what happend in the real project as that diagram we can discuss with domain expert), Is it right ?

4) I read in the forum that some ranchers has 34+ classes in class and componet diagrams !!
My design will be really simple as most of the Desing pattrens are out of Date, I think it does not make sense to use DAO,BD,Session Facade as
following link suggested
http://eclecticprogrammer.com/2007/10/18/core-j2ee-patterns/
https://www.hibernate.org/328.html#A8

I am using JSF/Hibernate/EJB3 (Also in my real application )so don't just want to fit the design pattrens into SuD to just show that I know them !!
What you guys think!!

5) In sequence diagram it is make sense to include every step (every class/action that comes in the way) ??
6) It is for 200 people, I think one application server with may be two instance is enough!! is it make sense!!
I will really appreciate your help!! Please answer soon.. ! !

-Neetu
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy Greenhorn! Welcome to the JavaRanch!

I think it does not make sense to use DAO,BD,Session Facade as
following link suggested


From reading that link, you think the author is saying there is no need for a DAO or Session Facade? I don't think that's quite where he stands. These patterns are still very much in vogue, and not using them may be at your own peril.

The number of application servers shouldn't be an issue. Focus on a scalable design, but your job as an application architect is not to scope out the hardware requirements.

-Cameron McKenzie
 
Neetu mukur
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Cameron !
I am not arguing that this link is saying so don't use these patterns,My point is it make perfect sense not to use because of J2EE 5 & EJB3's wonderful features (I mean in the real application!)
so My concern is just to include these in SCEA part 2 because it requires knowledge of J2EE patterns even it is little hard to digest to that I am making it a overkill

Thanks a lot,
-Neetu

 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic