-
The reviewer's capstone group TA is @tomashetMcMaster
The SRS rubric states that a critical portion of the document is to be formalized, however this was included for only one functional requirement.…
-
An explanation regarding the relation of the Test case creation and output to its related FR in SRS could greatly help in validating your Traceability Matrix. And specifically could help in improving …
-
Section 2 refers to section 1.4 of the SRS. However, upon looking there, there seems to be a lack of different abbreviations that are used throughout this document and what they mean exactly. Instead …
-
As my colleagues mentioned, your VnV plan is very impressive, and the effort you must have put into it really shines through.
A small suggestion, since the documentation is so thorough, sometimes I…
-
I got a chance to review the code I wrote while writing the report, and I noticed that there are some redundancy. In the SRS document language, there are ``DocDesc`` and ``SRSDecl``, where the latter …
-
The reviewer's capstone group TA is @tomashetMcMaster.
From "Implementation Environment of the Current System", specific technologies such as HTML, Python 3.7, etc. are listed that the group plans to…
-
Dear Customer (@mrentsch65),
we have published our documents including BC, CRS, PSP, SRS and SAS in the GitHub folder [PROJECT](https://github.com/mk28/TINF21C_Team2_AAS_digital_nameplate/tree/main/P…
-
Target date: mid february 2024
Wanted:
- [x] python-3.12.2 with torch and numba
- [x] Operation Research packages refresh
- [x] a big clean-up in packages that still don't have a windows/3.12 wh…
-
This document refers to an SRS Verification Checklist in Section 4.2. This checklist is missing in the VnV Plan, and cannot be found in the SRS document.
Team 1 TA: @NickCapstone
-
In Section 5.3 Traceability Between Test Cases and Requirements, some of the functional requirements listed in the SRS documents are missing, such as ODR 6-7 & 13-18 and MDR 1 & 11-13. Many of the non…