smiths / aorta

Other
2 stars 0 forks source link

Address Dr. Wassyng feedback Chapter 3, section 3.6, Figure 3.28. #72

Closed JovieL25 closed 1 year ago

JovieL25 commented 1 year ago

image

I think range checks are included and reviewed as the assumptions here.

Hello Dr. @smiths, can you share your thoughts on this comment?

image

smiths commented 1 year ago

Dr. Wassyng is correct that range checks should be specified in the requirements document. The coder would do them as part of implementing the requirements, so it isn't something that has to be highlighted here.

JovieL25 commented 1 year ago

Dr. Wassyng is correct that range checks should be specified in the requirements document. The coder would do them as part of implementing the requirements, so it isn't something that has to be highlighted here.

Hello Dr. @smiths,

Do we have range checks specified in the requirements document? Is it worth mentioning in the GR assurance case?

smiths commented 1 year ago

In the SRS you have a section about Input Data Constraints. That's the "range checking" part. No, it isn't worth specifically mentioning in the GR assurance case.

JovieL25 commented 1 year ago

In the SRS you have a section about Input Data Constraints. That's the "range checking" part. No, it isn't worth specifically mentioning in the GR assurance case.

Hello Dr. @smiths,

image

Is there anything else to add to this section?

smiths commented 1 year ago

No