The phrase "evolution of requirements" is grammatically correct and can be used in written English.
It is typically used to refer to the process of how requirements for a project or task change over time. Example: "The evolution of requirements for the new software development project has been ongoing for the past six months, as we incorporate feedback from stakeholders and adapt to new market trends."
The evolution of requirements affects not only specific system functions and particular components but also component-based architecture on all levels.
In this paper, we discuss the evolution of requirements for the US spacesuit, the extravehicular mobility unit (EMU), as a case study to highlight the need for flexibility in system design.
We identify four new principles that underlie contemporary requirements processes, namely: (1) intertwining of requirements with implementation and organizational contexts, (2) dynamic evolution of requirements, (3) emergence of architectures as a critical stabilizing force, and (4) need to recognize unprecedented levels of design complexity.
Neither domain engineering nor requirements engineering handles such co-evolution of requirements and contexts explicitly, making it especially hard to reason about the impact of co-changes in complex scenarios.
This paper presents a flexible deployment of business rules, which not only supports decision making in the face of conflicting requirements, but also the evolution of those requirements in the face of changing regulatory environments, competitive markets and corporate goals.
Data are presented on the evolution of mission requirements over time for 120 missions performed by the Space Shuttle over a period of some 27 years.
The evolution of water requirements for agriculture is directly linked to the increase of irrigated farmland.
In this paper, we examine the scale and temporal evolution of coordination requirements in the Rational Team Concert (RTC) project, a large project that involves 161 developers, 33 development teams, and 21 locations across US, Canada, and Europe.
In regards to the first question, I think there may be some interesting issues in the evolution of protein requirements over the long term evolution of the biosphere, but I don't find that this raises any serious objections or alternative considerations to Higgs's conclusions – except perhaps in one area.
For a discussion on the evolution of this requirement in UK law see: M Eliot, "Has the Common Law Duty to Give Reasons Come of Age Yet?," University of Cambridge Faculty of Law Research Paper (2012).
Highly-specialized and complex EHR systems cannot acclimate to the evolution of healthcare data requirements, which require EHR systems to embrace a dynamic, state-of-the-art, rapidly evolving information infrastructure [ 2].
