This is a self-parking facility
LED signs at the entrance to show how many spots are available.
Above each spot in the garage is a sensor that can sense whether or not there is a vehicle in the spot. If the spot is open, a green light above the spot will be activated. This helps customers find open spots. This also helps the system update the sign at the entrance to show how many open spots there are in the garage.
Raed Tabani wrote:
This is a self-parking facility
I'm not sure if I'm being over analytical here, as I'm not sure if this qualifies as a problem, but I did ask myself is this significant at all for this design? who is responsible for parking is it the car or the garage itself ie where is the park() located? nevertheless, it led me to this Problem : choose which spot to park a car in if there is any available at a given time. which led to another Problem : how to ensure that no car gets in only to find all spot are taken. to which the solution is the LED sign at the entrance.
Raed Tabani wrote:I asked to who is it showing this to? is it for cars to know "can I go inside" or for the Garage to know" can I let more cars in"
Raed Tabani wrote:having the Garage divided in into four sections: A, B, C, and D sections. serves to make this easier and more efficient coding wise.
Raed Tabani wrote:, and I want to ask you
1- am thinking in the right direction?
Raed Tabani wrote:keeping track of the numbers of cars inside the garage, parked or not , at the moment VS total number of slots . where:
a- the number of cars ++ as soon as a car gets in and not necessarily parked yet
b- the number of cars -- only once the car exits garage.
I wrote:Candidate Objects
..
3. Garage - has sections; observes Sections and Entry/Exit gates; displays current state
Tushar Goel wrote:
Should show available parking slot
should show occupied parking slot
should allow to enter the vehicle only when some other vehicle exist in case of only 1 parking slot available
should reduce the available spot once vehicle enters into the gate and up one available spot when vehicle leave its position
Should not allow to park any more vehicle till spot is available
Tushar Goel wrote:should allow to enter the vehicle only when some other vehicle exist in case of only 1 parking slot available
Is this what you had in mind, Tushar?
the Gate really only needs to know total spots in the garage and number of entries and exits.
Tushar Goel wrote:
Is this what you had in mind, Tushar?
SlotNumber L1 L2 ................. LN // here Lx represents the LED at the particular spot in particular section
So i think if the spot is occupied than LED will be RED else Green. something like this:
A G G G R R ..... // where A is section , G is the green and R is Red color
This will tell the users exactly which spot is available to park. Count increment as i mentioned earlier would be useful to manage this.
conversation in many different directions
It's just not practical to have Red LED lights to indicate an occupied spot.
Tushar Goel wrote:It is not required to show red lights. Only green lights should be OK. So it will be something like:
G G G G
A1 A5 A9 B6....
But by this we have to use as many as LEDs as number of total spots in the parking.
Tushar Goel wrote:I am sorry. I was thinking to make things more simpler. Like instead of finding spot after entering into the garage, i am going to tell the users or
driver itself know which exactly spot is available and go to park there.
Junilu Lacar wrote:It's just not practical to have Red LED lights to indicate an occupied spot.
Paul Clapham wrote:
Junilu Lacar wrote:It's just not practical to have Red LED lights to indicate an occupied spot.
In real life: the parking garage at Istanbul airport uses red LED to indicate an occupied spot and green LED to indicate a free spot.
Tushar Goel wrote:Yup you are right. Each one has its own interpretations. Sometime we need to discuss long to bring everyone on common platform. Thanks again..
So we are clear on this point, Can we start making tests? Which particular item you want us to pick?
Paul Clapham wrote:Seems to me that a solid row of red LED's tells the customer that there's no parking in this row, carry on and look elsewhere instead of creeping through and examining each space. Whereas an absence of LED's doesn't communicate that information as obviously.
How about you do the honor of writing out that test code, Tushar?
I wrote:Maybe it's just me and the red LEDs really help but I still think they're redundant. No green light means no available space. Maybe the redundancy helps make the system a little "fault-tolerant"; that is, if there's no green light and no red light, then maybe the sensor is faulty and you might want to check out the space anyway, if you really can't find any green lights elsewhere ¯\_(ツ)_/¯
Raed Tabani wrote:I'd love to give this a go
I think I'm going to come up with a new rule of thumb: for high-level tests that specify general behavior, avoid the actual method names.
Tushar Goel wrote:
If i think about our story "External Sign shows available spots in Garage", i think i am convince to myself to separate section and gate responsibility. Each section having
own responsibility to show available spots but still it doesn't convince me to consider gate capacity and allowing gate to control entrance in terms of section capacity?
Isn't Garage should tell like "Hey Gate, please open it as i am still having a capacity?" or something like "Hey Gate, don't open it till i told you so?"