Risk Mitigation\u00a0<\/b><\/p>\n
A risk for us with gathering test data is making sure that we can go at times where there is a decent amount of traffic at Salem\u2019s and we can get a sufficient amount of testing data. We have already went to Salem\u2019s a few times where it wasn\u2019t busy enough to set up three checkout lanes. The way we are mitigating this is by going to test our system near peak hours instead of too early in the morning on a weekday where only 1 or 2 checkout lanes are available. Furthermore, if we do go at a lower traffic time, we want it to be a time where there are at least 2 checkout lanes running because we want to at least have enough traffic to have our system compute the speeds of two different lanes and compare them properly.\u00a0<\/span><\/p>\n Design Changes\u00a0<\/b><\/p>\n We haven\u2019t made any changes to our design.\u00a0<\/span><\/p>\n Schedule Changes\u00a0<\/b><\/p>\n We haven\u2019t made changes to our schedule as of this week, since we already have a day-to-day schedule.\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" Risk Mitigation\u00a0 A risk for us with gathering test data is making sure that we can go at times where there is a decent amount of traffic at Salem\u2019s and we can get a sufficient amount of testing data. We have already went to Salem\u2019s a few times where it wasn\u2019t busy enough to set … <\/p>\n