Non Functional Requirements - What is missing for Performance Testing?
I've been given a requirements specification for an order management system, which details over 500 Functional Requirements. However there are only 4 Non Functional Requirements (NFRs) in the document - which suggests an imbalance to me!
The NFRs detail the 95th percentile maximum response times, but do not detail under what load this must be achieved, or in what transaction mix.
In addition there are no details about volumes of orders expected per day / week / month, expected number of exceptions etc.
I have to provide a list of 'suggestions' for further requirements to cover the gaps in the NFRs for Performance Testing.
Can anyone assist me in creating a list of standard NFR types I should be asking for? I'm relatively new to this and I don't want to miss a trick for lack of asking silly questions.
Any guidance would be much appreciated.
Re: Non Functional Requirements - What is missing for Performance Testing?
Consider requirements for system usage. For instance: Server processor usage shall never exceed an average of 75% during a maximum user realistic test.
Reliability: System shall without problems for 48 hours at 50% capacity.
Network Usage, Database (absence of locks, lock waits, hotspots etc.)
Check out: http://www-106.ibm.com/developerwork...-topology.html and