• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Doubt about FactoryHomes use case

 
Leonardo Celati
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From the assignment, a user is supposed to do this steps:
- click on a component category, the system will respond with a list of components
- click on a component in the list, the system will respond with avaiability/applicability

I was wondering if this use case can be shorten like this:

- click on a component category, the system will respond with a list of components that are available/applicable

To be honest, I would do like this in a real scenario, at least giving evidence in the list about the reason of not applicability.
It could be quite frustrating for a user to click the whole list to find out which component is suitable to be added.

Of course, whenever I add a component, I am always doing a validation on the business side.

Wel..I hope I understood the use cases correctly :-)
 
K. Tsang
Bartender
Posts: 3583
16
Android Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on what the use case does. If it's view component info/detail or the such, yes combining the 2 steps is reasonable.

 
Leonardo Celati
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok, got it. But then another question specific for the ones that has faced my same assignment.

When it says that:

"The user select a component category"
and then as a final step, if the components is eligible (applicable) for being added:
"Add the component to the current house design"

I am starting to be quite confused about this, mostly because I am thinking in terms of a real case. In the beginning my understanding was that the system proposes a house design with the components already in place.
Then with "select a component category" t's just the user clicking on an existing wall, or door, or roof...etc, of the house design and replace with one allowed from the list.
So, "add" pratically means "replace" in my case. And this is just the meaning of the company planning to propose a limit set to test the market.

Otherwise, how can the system check for "applicability" without knowing where the component will go ?
Ok for a roof, a foundation, which are 1:1, but a wall ? Supposing the house is rectangular, the wall component cannot always fit.
Or a window, there must be a limit about the number of windows one can add, and this is known after clicking on existing component, rather than a category.

Or probably I am overthinking it, and I should just sign class methods for doing what it is just being asked, something like add(component, houseDesign) :-)

What do you think ?
 
K. Tsang
Bartender
Posts: 3583
16
Android Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It seems to me that the assignment is allowing the user to build the home part by part, choosing the components/materials etc

Anyway, I recommend you split those 2 steps to fulfill the requirement. This also applies to the first post you asked. Having an extra method call is nothing.

Remember the assignment is testing your design skill not how you implement it. Taking like a civil engineer or architect may be over the top from a IT perspective.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic