Team Status Report for 2/18

During our meeting with the professor on Monday, we identified one of the biggest risks that could jeopardize the success of our project is that our requirements were not speciefied clearly enough. There was a lot of different parts of our proposal that were very general, which could lead to significant setbacks later on in our project. For instance, prior to our meeting, we did not specify the types of entrances that we were going to place our camera on top of, thinking that we could generalize our project without much modification. However, different types of entrances, such as a door 8 feet wide and a door 4 feet wide, might require a different camera in order for the camera to capture the entire entrance as well as modifications to the capabilities of our CV system. If we design our project without well defined requirements, we would have a lot of unexpected issues during our implementation, which could jeopardize the successful completion of our project. After our meeting, we spent time as a team to specify these requirements and worked on fleshing out detailed designs for each component of our system.

There were several changes that we made to our requirements and design. We speciefied the type of door that our system would be able to monitor. This change was necessary for the reasons we mentioned above. We also spent a lot of time as a team to come up with a detailed design for our project in preparation for the design review (see design review for specifics). However, we do not foresee any additional costs being incurred due to these changes.

We think we are on schedule for the development of our project after last week, as the team memebers have designed and started testing their individual components according to our original schedule.

Engineering, Science, Math principles used in our project:

  • Computer Vision
  • Computer Networking
  • Machine Learning
  • Web Application