Miroirs/cooperative-software-development
1
0
Fork 0
mirror of https://github.com/amyjko/cooperative-software-development synced 2024-12-26 21:58:27 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Consistent naming.

Browse source
This commit is contained in:
Andy Ko 2019-04-09 12:26:42 -07:00
parent e26c0dab27
commit 7b386f5af7
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
index.html
View file

@ -48,10 +48,10 @@
<td>Chapter 4. <a href="productivity.html">Productivity</a></td>
</tr>
<tr>
<td>Chapter 5. <a href="quality.html">Software quality</a></td>
<td>Chapter 5. <a href="quality.html">Quality</a></td>
</tr>
<tr>
<td>Chapter 6. <a href="requirements.html">Requirements engineering</a></td>
<td>Chapter 6. <a href="requirements.html">Requirements</a></td>
</tr>
<tr>
<td>Chapter 7. <a href="architecture.html">Architecture</a></td>

2
quality.html
View file

@ -26,7 +26,7 @@
<img src="images/pomegranate.jpg" class="img-responsive" />
<small>Credit: Anton Croos</small>
<h1>Software Quality</h1>
<h1>Quality</h1>
<div class="lead">Andrew J. Ko</div>
<p>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 (<a href="#ralph">Ralph & Kelly 2014</a>).</p>