TPGEngine / tpg

Evolving Quadruped Robot Controllers with Emergent Tangled Program Graphs
MIT License
0 stars 0 forks source link

Peer Review - Julian C: Maintenance Reqs, Supportability Reqs, Adaptability Reqs #107

Closed N4T10N01 closed 1 month ago

N4T10N01 commented 1 month ago

Artifact Under Review Volere SRS

Team Number for Team Doing the Review Group 2

Description of Issue Maintenance Reqs, Supportability Reqs, Adaptability Reqs Feedback

MS-M1 - Where did 15% come from? This seems like an arbitrary number. It is completely unclear how long the project will take initially and it is even less clear how long a change could take (the change could be minor or major). Also, what is your definition of "finished software" in an open-source project that will receive ongoing contribution?

MS-S2 - is it assumed this will occur for project lifetime or beyond it? Is it known at the moment that there will be an active contributor after capstone ends that can uphold this? It can be clarified whether this will occur only during capstone's duration or beyond.

MS-A2 - what is the definition of "easy to install"? Maybe a metric that could be assigned in place of this is "it will take no more than X steps to install" or "the installer will match the number of steps involved in a typical application like VScode". Not sure if those metrics I gave exactly suffice, but I believe something should be substituted for "easy".