Software quality may be summed up as its suitability for the user's intended purpose. Additionally, this may be assessed in terms of the frequency of flaws (often known as "bugs") and the availability of the anticipated set of capabilities.
The situation you describe is a typical one in agile development, where requirements are "dynamic" and the new features they produce must be prioritized for development and delivery after being compared to the current backlog.
However, you should always have a set of characteristics that you and the project sponsor have agreed upon that will serve as the foundation for your testing and, consequently, your evaluation of the software's quality.
It's crucial to explain to the project client or sponsor the distinction between "agreed" features and "wish list" features, as well as between current and backlog features.
To learn more about software quality:
https://brainly.com/question/21279421
#SPJ4