From 32b960f2f782051544b71aa4c92f56731dfcffe6 Mon Sep 17 00:00:00 2001 From: "Amy J. Ko" Date: Thu, 24 Feb 2022 20:49:52 -0800 Subject: [PATCH] Fixed #152, added missing verb. --- chapters/quality.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/quality.md b/chapters/quality.md index 6a9d58b..46b6a4d 100644 --- a/chapters/quality.md +++ b/chapters/quality.md @@ -1,4 +1,4 @@ -There are numerous ways a software project can fail: projects can be over budget, they can ship late, they can fail to be useful, or they can simply not be useful enough. Evidence clearly shows that success is highly contextual and stakeholder-dependent: success might be financial, social, physical and even emotional, suggesting that software engineering success is a multifaceted variable that cannot explained simply by user satisfaction, profitability or meeting requirements, budgets and schedules. +There are numerous ways a software project can fail: projects can be over budget, they can ship late, they can fail to be useful, or they can simply not be useful enough. Evidence clearly shows that success is highly contextual and stakeholder-dependent: success might be financial, social, physical and even emotional, suggesting that software engineering success is a multifaceted variable that cannot be explained simply by user satisfaction, profitability or meeting requirements, budgets and schedules. One of the central reasons for this is that there are many distinct *software qualities* that software can have and depending on the stakeholders, each of these qualities might have more or less importance. For example, a safety critical system such as flight automation software should be reliable and defect-free, but it's okay if it's not particularly learnable--that's what training is for. A video game, however, should probably be fun and learnable, but it's fine if it ships with a few defects, as long as they don't interfere with fun