Design pattern question

[garnaout]

I have a java-based simulation model of a floor with a lot of people agents that go on to different floors (I have around 3-5 floors) with several elevators. I am in the process of writing the elevator class and decided to take a step back and ask the big boys which design pattern would they recommend. First thought is state design pattern. The elevators will have a capacity, max load, and different states such as moving, idle, or Needs Maintenance (deactivated).

Should I create the Elevator.java as an abstract class and have other states extend it?

thanks

[JosAH]

I have a java-based simulation model of a floor with a lot of people agents that go on to different floors (I have around 3-5 floors) with several elevators. I am in the process of writing the elevator class and decided to take a step back and ask the big boys which design pattern would they recommend. First thought is state design pattern. The elevators will have a capacity, max load, and different states such as moving, idle, or Needs Maintenance (deactivated).

Should I create the Elevator.java as an abstract class and have other states extend it?

There is no need to extend anything: an elevator is an elevator; maybe it's its algorithm that can be extended but a simple 'elevator seek' (<--- Google tip) could do the job fine. If you only have one single elevator in your system you can implement the elevator as a singleton (<--- pattern tip)

kind regards,

Jos

[KevinWorkman]

What would extend Elevator? It seems to me there is only one kind of Elevator, each with different attributes. No real need to extend there.

Honestly though, I really wouldn't worry too much about it. There is such a thing as overthinking a problem. Go with what fits into your head the best.