TA Meeting - 3 October 2024

[SumanyaG]

Questions regarding SRS

3 October 2024, 01:30 PM

Attendance

• [x] Sumanya
• [x] Jason
• [x] Jennifer
• [x] Jason
• [x] Chris

Questions to Ask

• The writing checklist mentions there should always be text between the section heading and subheading? Does this need to be followed for the SRS document? Example, 3 and 3.1 - what text do I add here?
• Are a rationale and fit criterion required for all constraints? Can we skip them for some constraints where including them does not make sense? Example, 3.3 and 3.4.
• Are we allowed to remove irrelevant sub-headings like 3.8 or should we leave them in and provide a justification or write N/A?
• Sections 16-18 of the Volere template
• Difference between glossary in section 4 and 7.2 (data dictionary)? Doesn't data dictionary encroach on the implementation side of things? Is it mandatory to include one right now?
• Section 7.1 says "each rectangle represents a class of business data and the attributes of the class are defined in the data dictionary". Going by this definition, each experiment will correspond to a class of business data and its dozens of parameters will correspond to the attributes? How do we condense this information for 110 experiments and 20+ parameters for each for this section?
• Based on the rubric:
  1. Document Organization: identifies template --> where? + changes clearly documented --> how? revision history? separate table?
  2. Requirements --> use the Volere template for each?
  3. Traceable Requirements --> where should the table or diagram be?
  4. Phase in Plan --> meaning? is it the same as 21.3? is it okay for dates to correspond to milestones?
  5. LO rubrics? Do we need to do something for this?

[JenniferYe25]

Meeting Mins:

The writing checklist mentions there should always be text between the section heading and subheading? Does this need to be followed for the SRS document? Example, 3 and 3.1 - what text do I add here?

• use it to intro the section but giving the reader what to expect in this section

Are a rationale and fit criterion required for all constraints? Can we skip them for some constraints where including them does not make sense? Example, 3.3 and 3.4.

• add if there is an obvious fit criterion
• if the requirment is ambiguous then do it other wise if its clear how it can be tested then its fine to skip

Dont need to do the rectangle thing if you dont find it helpful

Are we allowed to remove irrelevant sub-headings like 3.8 or should we leave them in and provide a justification or write N/A?

• if added a new section, then make note
• if removed section from template, document it somewhere "changes from template"

Sections 16-18 of the Volere template

Difference between glossary in section 4 and 7.2 (data dictionary)? Doesn't data dictionary encroach on the implementation side of things? Is it mandatory to include one right now?

• we can remove 7.2 or say N/A

Section 7.1 says "each rectangle represents a class of business data and the attributes of the class are defined in the data dictionary". Going by this definition, each experiment will correspond to a class of business data and its dozens of parameters will correspond to the attributes? How do we condense this information for 110 experiments and 20+ parameters for each for this section?

Based on the rubric:

Document Organization: identifies template --> where? + changes clearly documented --> how? revision history? separate table?

• this document followes a modified volarae template (add like a small section in the beginning)

  Requirements --> use the Volere template for each? Traceable Requirements --> where should the table or diagram be? Phase in Plan --> meaning? is it the same as 21.3? is it okay for dates to correspond to milestones?

• want to get more granular about it
• when we wanna do it done, when we wanna do testing
• makes sure requirements are related to the milestone LO rubrics? Do we need to do something for this?
• dont need to hit on all of them if they arent relevant
• dont remove the sections, N/A or a sentence or two about why its not a relevant section

No math, how to meet that part of the rubric:

• finite state machine
• examples of the data that they have, or the formal process of the experiment
• state machine of the experiment process
• validate input types
• double check the csv