Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • I agree that it should be tested, as with all requirements. Should this be part of the SRS with the rest of the application's requirements? It's not a functionality of the application; it's a specification of the system, of the environment where the application will run. Commented Nov 6, 2019 at 14:35
  • Yes, this should be part of the requirements because it is part of the application. How it's implemented does not determine what is a requirement. Commented Nov 6, 2019 at 15:42
  • I agree that how it's implemented does not determine what is a requirement. It would be part of the system requirements specifications, not the software requirements specification. Does that make sense? Commented Nov 6, 2019 at 19:09
  • I'll remove the question about testing from the original question as it's seemingly diverting the discussion in a direction that's not helping to determine where the specification of the OS parameters should be defined. Testing of the required funcionality shall happen regardless of where the specification is documented. Commented Nov 7, 2019 at 15:42
  • Yes, this needs to be part of the specification. It's a requirement; if it is not in the specification, how else would you know about the requirement? Commented Nov 8, 2019 at 15:20