Requirements Document Meeting Logs

Meeting Notes

Here were the major points from our meeting with our supervisor, Dr. Michael Turi, and our capstone instructor, Dr. George Hauser:

With Dr. Turi

• The description part of the requirements document is similar to the goals section of the proposal.
• The tasks we laid out should have a more pessimistic outlook.
• The use case template we pasted into the document is fine. It might not hurt to include situations like, "What if the signal's fuzzy?"

With Dr. Hauser

• Due to the large amount of unknowns with our project, the requirements might still be fuzzy. But that's okay since it's a draft.
• It'd be neat to get the equipment before the presentation for the requirements document.
• The class project web page should be in the introduction or in a special section near the end.

Document work summary

After that, we continued working on the requirements document. Most of the work involved explaining requirements more technically and splitting up the tasks wherever they can go wrong. However, we're still a bit nervous that we may've not made the educational part of the description with the right amount of detail.

Furthermore, the amount of technicality for the rest of the goals might've either been too much (in cases where we knew how to expand it) or too little (in cases where we're still not sure how to deal with it).