I've never heard these terms used in my own experience as a systems Engineer, but am always open to new thinking. In my experience there are usually many different mindsets in most projects, the best way to tie them together is usually a stakeholder analysis (Hence addresses the concerns of the stakeholder comment you got from Auntigrav). We get all the stakeholders in a room, or in an online meeting, including ideally the system requirers, or potential owners, and brainstorm everyone, gathering their concerns, prompting with things like environment and so on (Environment is another stakeholder).

Then we formally distill the concerns into a set of requirements, traced to the relevant stakeholders, including the environment.

That then agreed with all stakeholders stands as the system specification, from which a design specification is produced in response.

If Auntigrav's concerns were included in the system stakeholder analysis, and all addressed by the system requirements, then the system design conforming to that, and the delivered system tested to show it meets all requirements, then there is no grounds for anyone to claim the environment was not given ample consideration :)