Is there a set amount of pages we can't go over for the SRS Doc?
Do all the sections need have something under it? (eg. adaptability reqs we have no) (can we delete section?)
Is the form of our requirements okay? or we need to use a template?
Should we be writing requirements as if it were a real project (with releases and maintenance) or should we be explicit that its just a capstone project
For costs section: is it okay to answer using team hours instead of dollar amount
Answers
add priority (high med low)
phase in plan (high priority done by this date)
make numbers into symbolic constant vars (upper case) (using over and over again)
leave N/A sections in and mention they are N/A
team hours can be added to the phase in plan
Migration portion might not relate to us cuz its a new product
Treat it like a real project not just capstone in the SRS
Introduce each section before the sub sections for better flow
SRS Document Review
October 7th, 2024 @ 2:30pm
Attendance
Questions to Ask
Answers