I work in an organisation that is one of many stakeholders in a large software project.
Both functional and non-functional(quality) requirements have been specified years ago, and the solution is now being delivered.
The problem is that the solution does not deliver the non-functional requirements that the stakeholders initially specified. These relate to resilience, availability, life-cycle cost, flexibility in evolution/development etc.
I understand that architecture and design goals are basically nothing more than a bet that our non-functional requirements will be met.
However, I would like to formally document how and to which degree the implemented solution:
- Adheres to the specified design and architecture.
- Fails to deliver the non-functional requirements.
As I understand the ATAM method is primarily focused validating design and architecture in the design phase and not post-delivery verification of a solution. ISVV from looking at the Wikipedia is primarily focused on functional requirements ... Or am I mistaking?
How can I attack this problem and what widely regarded methods are availble to analyze an existing solution according to spec'd design goals and non-functional requirements?