Your goals seem to be well-inspired from your functional requirements. It's good to have strong cohesion between them and they also relate well back to the main points of user business, which is making TPG applicable within advanced simulations and open source. It is clear how both goals are attainable and how they are relevant. My only critiques would be that it would be good to state more high level goals, such as "Real Time Processing", which may be smushed into your first goal currently. In fact, your first goal may contain several goals at once currently, such as "establishing clear contribution guidelines" and "a robust, scalable architecture" which could be split up and elaborated on separately to properly scope out what is being aimed for. Also, adding stretch goals here may be a good idea (I would confirm with the TA about that).
Artifact Under Review Volere SRS
Team Number for Team Doing the Review Group 2
Description of Issue Project Goals Feedback
Your goals seem to be well-inspired from your functional requirements. It's good to have strong cohesion between them and they also relate well back to the main points of user business, which is making TPG applicable within advanced simulations and open source. It is clear how both goals are attainable and how they are relevant. My only critiques would be that it would be good to state more high level goals, such as "Real Time Processing", which may be smushed into your first goal currently. In fact, your first goal may contain several goals at once currently, such as "establishing clear contribution guidelines" and "a robust, scalable architecture" which could be split up and elaborated on separately to properly scope out what is being aimed for. Also, adding stretch goals here may be a good idea (I would confirm with the TA about that).