aspose file tools*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Validation of design or component in Factory Homes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Validation of design or component in Factory Homes" Watch "Validation of design or component in Factory Homes" New topic

Validation of design or component in Factory Homes

Yanzhong Liang

Joined: Nov 03, 2009
Posts: 2
My question is how can we validate a design, a house or a componnet?

It seems the IS should take care of it, but how should we make the assumption?


Dana Mulder

Joined: Dec 26, 2009
Posts: 1
I think every time you try to add a new component, the Web Services system must first validate it, if so, after having all the components validated you know your whole design is valid. Do you agree? Because in the first Use Case it says you get a list of components with availability and applicability. I guess you can't "click" the ones not applicable, that's validation for me.

I got related questions about Factory Homes and design validation too:

1º What's a style? It says "... limited number of valid combinations for house styles and accesories to test the market..." Does it mean the user must first choose a style from a given list and then user can only select accesories accepted for the chosen style?

2º Then a Use Case says "Customer selects a component category". What's a category? For example, customer selects "roof" as category and then she can select a roof from a given list of roofs for the style and category selected. Is this?

3º When is the customer selecting accesories and what's an example of accesory?

Thank you very much!

srikanth kakumanu

Joined: Sep 16, 2003
Posts: 8
Hi Folks,

Could anybody please clarify/suggest the right approach for the below doubts?

I am using JSF, EJB 3, JPA.

1. Do i need to show JSF backingBeans and listeners in Component, Class and Sequence Diagrams?

2. I am planning to design with the below design pattern in given fashion.

JSF-> JSF Front Controller->Business Delegate-> Service Locator -> EJB Stateless Session Bean -> Session Facade -> EJB Entity Bean. At EJB stateless Session Bean level, i am trying to use the Command or Broker pattern to call IMS web services. I also planning to use Value Object for data transfer across the layers.

Could any one please validate this approach and suggest me the corrected ones?

3. Regarding key objects given in Business Domain Model in the assignment, Do we need to understand/treat them as EJB Entity Beans?

4. Here is my assumption about the business model.

A. Aperture is an empty class which is extended by Door and Window.
B. A Wall has one or more Door or Window.
C. House has a Roof, Foundation, one or more Wall.
D. Product has House.

based on this assumption, i assume that i should create a empty Product first then creating other house components (House, Roof, Foundation, Door, Window etc.) and keep adding them to empty Product.

Am i correct?

Can any body suggest me about my above given doubts?
Andrew Monkhouse
author and jackaroo
Marshal Commander

Joined: Mar 28, 2003
Posts: 11285

"Dana Mulder"

Please check your private messages regarding an important administrative matter.


The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
I agree. Here's the link:
subject: Validation of design or component in Factory Homes
Similar Threads
Playground modeling questions
Part 2: Number Concurrent users and performance requirements
Exception or RuntimeException
Understanding OOAD and Use case using a case study
Depicting Design Patterns in Component Diagram