Comments on: Making Quality Software: 12 non functional requirements every app should have.

By: Checklist de requisitos no funcionales | Bytes & Chips

Checklist de requisitos no funcionales | Bytes & Chips — Mon, 15 Sep 2014 08:32:23 +0000

[…] http://www.eyefodder.com/2011/06/quality-software-non-functional-requirements.html […]

By: tim

tim — Wed, 03 Sep 2014 09:47:34 +0000

Attractability – How does your systems environment and infrastructure look as a potential partner/ JV participant. Is your environment suitable as the target state transition path if it is undergoing 5 years of renovation to deliver the same function outcome as the vendors (which were assessed today, and not in 5 years time)
Currency / Upgradeability – Solutions delivered as a package are generally upgraded (and deployed to pre-existing clients as a benefit) when one of the users pays for a new function to be developed.

add this to the list

By: non-Functional Requirements

non-Functional Requirements — Tue, 08 Apr 2014 19:49:19 +0000

[…] [2]Paul Barnes-Hoggett “Making Quality Software: 12 non functional requirements every app should have” [online]http://www.eyefodder.com/2011/06/quality-software-non-functional-requirements.html […]

By: Software Performance — make sure you don't get downgraded

Software Performance — make sure you don't get downgraded — Sun, 07 Aug 2011 03:52:38 +0000

[…] posted before on non functional requirements every application should have, and first and foremost amongst those constraints is performance. The deal you need to make with […]

By: Quality Software — testing non functional requirements

Quality Software — testing non functional requirements — Fri, 10 Jun 2011 04:32:13 +0000

[…] Skip to content « Making Quality Software: 12 non functional requirements every app should have. Making Quality Software: how to test non-functional requirements By Paul Barnes-Hoggett | […]