Skip to main content
Software Engineering

Return to Question

Tweeted twitter.com/StackSoftEng/status/1192728557816029184
Question Protected by gnat
Removed question about testing. Testing of the requirement shall happen regardless.
Source Link
OwnDevise
OwnDevise
  • 39
  • 6

Should operating system configuration parameters, like disabled OSautomatic updates or sleep timer, be part of the software specifications and therefore tested?

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? If so, they would have to be testing for each... EDIT: Rephrasing, shouldOn what document? Should this be part of the SRS with the rest of the application's software specifications or should this be recorded as specifications in another domain?

Testing of the requirement shall happen regardless of where it is documented.

Thanks in advance for your time.

Should system configuration parameters, like disabled OS updates or sleep timer, be part of the software specifications and therefore tested?

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? If so, they would have to be testing for each... EDIT: Rephrasing, should this be part of the SRS with the rest of the application's software specifications?

Thanks in advance for your time.

Should operating system configuration parameters, like disabled automatic updates or sleep timer, be part of the software specifications?

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? On what document? Should this be part of the SRS with the rest of the application's software specifications or should this be recorded as specifications in another domain?

Testing of the requirement shall happen regardless of where it is documented.

Thanks in advance for your time.

Expanded spec to specifications in Title.
Link
OwnDevise
OwnDevise
  • 39
  • 6

Should system configuration parameters, like disabled OS updates or sleep timer, be part of the software specspecifications and therefore tested?

Where I wrote software requirements I clarified I meant software specifications
Source Link
OwnDevise
OwnDevise
  • 39
  • 6

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? If so, they would have to be testing for each... EDIT: Rephrasing, should this be part of the SRS with the rest of the application's requirementssoftware specifications?

Thanks in advance for your time.

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? If so, they would have to be testing for each... EDIT: Rephrasing, should this be part of the SRS with the rest of the application's requirements?

Thanks in advance for your time.

Our application needs to run in a locked-down operating system. Due to quality and regulatory concerns, all updates shall be prevented or blocked. Therefore, our deployment includes the pre-configured operating system. To make any changes to the OS, admin credentials need to be used.

Some teammates think the "updates blocked" requirement fall in the same domain as the application. I think they are out of scope for the application.

Should system configuration settings have a specification assigned to them? If so, they would have to be testing for each... EDIT: Rephrasing, should this be part of the SRS with the rest of the application's software specifications?

Thanks in advance for your time.

added 102 characters in body
Source Link
OwnDevise
OwnDevise
  • 39
  • 6
Source Link
OwnDevise
OwnDevise
  • 39
  • 6