blob: 2f8cf1395bd7172e812a29a9822855d45ffb3df8 [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-a8huB5Sn0Qjfe-SkZubH1w"
name="references,_mtcqtmE-EdqnIZeW8YpHcA" guid="-a8huB5Sn0Qjfe-SkZubH1w" changeDate="2005-12-06T08:10:54.327-0500">
<mainDescription>&lt;a id=&quot;XE_references__bibliography_of&quot; name=&quot;XE_references__bibliography_of&quot;>&lt;/a>&lt;a id=&quot;XE_bibliography__references_for&quot; name=&quot;XE_bibliography__references_for&quot;>&lt;/a> &#xD;
&lt;h5>&#xD;
Topics&#xD;
&lt;/h5>&#xD;
&lt;ul>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Business Modeling references&quot;>Business Modeling&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Configuration Management references&quot;>Configuration Management&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Miscellaneous references&quot;>Miscellaneous&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Modeling and Unified Modeling Language references&quot;>Modeling and Unified Modeling Language&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Object-Oriented Technology references&quot;>Object-Oriented Technology&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Project Management references&quot;>Project Management&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Requirement Management references&quot;>Requirements Management&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Software Architecture references&quot;>Software Architecture&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Software Development Process references&quot;>Software Development Process&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
&lt;a href=&quot;#Testing and Quality references&quot;>Testing and Quality&lt;/a>&#xD;
&lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Business Modeling references&quot; name=&quot;Business Modeling references&quot;>Business Modeling&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BRO95&quot; name=&quot;BRO95&quot;>BRO95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Frederick P. Brooks, Jr. 1995. &lt;i>The Mythical Man-Month-Essays on Software Engineering&lt;/i> 2nd ed.&#xD;
Reading, MA, Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A classic that should be read and re-read by everyone involved in software development. We recommend&#xD;
this 20-year anniversary edition rather than the original 1975 edition.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CLA97&quot; name=&quot;CLA97&quot;>CLA97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Carl von Clausewitz 1997. &lt;i>On War.&lt;/i> Wordsworth Editions.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
One of the greatest books ever written on the subject of war, and applicable to the field of&#xD;
management.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CHM95&quot; name=&quot;CHM95&quot;>CHM95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James Champy 1995. &lt;i>Reengineering Management: The Mandate for New Leadership.&lt;/i> New York, NY:&#xD;
HarperCollins.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Gives some insight into the precarious art of managing a business (re-)engineering effort.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DVP93&quot; name=&quot;DVP93&quot;>DVP93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Thomas H. Davenport 1993. &lt;i>Process Innovation-Reengineering Work through&amp;nbsp;Information&#xD;
Technology.&lt;/i> Boston, MA: Harvard Business School Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Solid and comprehensive introduction about how information technology enables business improvement and&#xD;
(re-)engineering.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GAO97&quot; name=&quot;GAO97&quot;>GAO97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
United States General Accounting Office 1997. &lt;i>Business Process Reengineering Assessment Guide&lt;/i>.&#xD;
&lt;a href=&quot;http://www.gao.gov&quot; target=&quot;_blank&quot;>http://www.gao.gov&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
Describes a framework for assessing a business (re-)engineering effort.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ERI00&quot; name=&quot;ERI00&quot;>ERI00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Hans-Erik Eriksson and Magnus Penker 2000. &lt;i>Business Modeling With UML: Business Patterns at&#xD;
Work.&amp;nbsp;&lt;/i>New York, NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Presents a set of valuable patterns for business modeling.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HAM93&quot; name=&quot;HAM93&quot;>HAM93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Michael Hammer and James Champy 1993.&amp;nbsp; &lt;i>Reengineering the Corporation-A Manifesto for Business&#xD;
Revolution.&lt;/i>&amp;nbsp;&lt;br />&#xD;
New York, NY: HarperBusiness.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The book that popularized the movement of business (re-)engineering. An excellent complement to &lt;i>The&#xD;
Object Advantage-Business Process Reengineering with Object Technology&lt;/i> cited above&lt;i>.&amp;nbsp;&lt;/i>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HAR91&quot; name=&quot;HAR91&quot;>HAR91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
H. James Harrington 1991. &lt;i>Business Process Improvement: The Breakthrough Strategy for Total Quality,&#xD;
Productivity, and Competitiveness&lt;/i>. New York, NY: McGraw-Hill.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Another contributor to the topic of business (re-)engineering.&lt;i>&amp;nbsp;&lt;/i>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JAC94&quot; name=&quot;JAC94&quot;>JAC94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ivar Jacobson, Maria Ericsson, and Agneta Jacobson 1994. &lt;i>The Object Advantage-Business Process&#xD;
Reengineering with Object Technology&lt;/i>. Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The basis of the Business Modeling discipline, this is the very first book that applied object&#xD;
technology to the field of business modeling.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KAP96&quot; name=&quot;KAP96&quot;>KAP96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert Kaplan and David Norton 1996. &lt;i>The Balanced Scorecard&lt;/i>. Boston, MA: Harvard Business School&#xD;
Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
Best practices for successfully implementing the Balanced Scorecard.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KOT96&quot; name=&quot;KOT96&quot;>KOT96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
John P. Kotter 1996. &lt;i>Leading Change&lt;/i>. Boston, MA: Harvard Business School Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
A practical, proven model for planning and managing organizational change.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MARS00&quot; name=&quot;MARS00&quot;>MARS00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Chris Marshall 2000. &lt;i>Enterprise Modeling with UML&lt;/i>. Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
Describes how to create business models that facilitate the development software systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;NDL97&quot; name=&quot;NDL97&quot;>NDL97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David A. Nadler and Michael L. Tushman 1999.&amp;nbsp; &lt;i>Competing by Design-the Power of Organizational&#xD;
Architecture.&lt;/i> Oxford University Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Defines organizational architecture and capabilities as a source of competitive advantage.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;OHM91&quot; name=&quot;OHM91&quot;>OHM91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Kenichi Ohmae 1991.&amp;nbsp; &lt;i>The Mind of the Strategist: The Art of Japanese Business.&lt;/i> McGraw-Hill.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
A crisp and practical guide to strategic management.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ODL98&quot; name=&quot;ODL98&quot;>ODL98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James J. Odell 1998.&amp;nbsp; &lt;i>Advanced Object-Oriented Analysis &amp;amp; Design Using UML.&lt;/i> Cambridge&#xD;
University Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Provides a good overview, among other things, on the topic of business rules.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PFE99&quot; name=&quot;PFE99&quot;>PFE99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jeffrey Pfeffer and Robert Sutton 1999.&amp;nbsp; &lt;i>The Knowing-Doing Gap.&lt;/i> Boston, MA: Harvard&#xD;
Business School Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
Discusses the reasons why some organizations do not apply their own lessons learned and provides&#xD;
pointers for how to overcome this challenge.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PLR99&quot; name=&quot;PLR99&quot;>PLR99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
R. Steven Player (Editor) and David Keys (Editor) 1999.&amp;nbsp; &lt;i>Activity-Based Management: Arthur&#xD;
Andersen's Lessons from the ABM Battlefield.&lt;/i> Wiley Cost Management Series.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An introduction to understanding the management of costs, and how to implement activity-based costing&#xD;
(ABC) and activity-based management (ABM) systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;POR98&quot; name=&quot;POR98&quot;>POR98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Michael Porter 1998.&amp;nbsp; &lt;i>Competitive Strategy: Techniques for Analyzing Industries and&#xD;
Competitors.&lt;/i> Simon &amp;amp; Schuster, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
A practical guide for the strategic planner.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ROS97&quot; name=&quot;ROS97&quot;>ROS97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ron Ross 1997.&amp;nbsp; &lt;i>The Business Rule Book: Classifying, Defining and Modeling Rules.&lt;/i> Boston,&#xD;
MA: Database Research Group.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
A complete handbook for the business rules analyst.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;SEY98&quot; name=&quot;SEY98&quot;>SEY98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Patricia Seybold 1998.&amp;nbsp; &lt;i>Customers.com.&lt;/i> Random House Publishing.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;1%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;>&#xD;
An excellent collection of practical guidelines and case studies on the benefits of e-business and&#xD;
(re-)engineering.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Configuration Management references&quot; name=&quot;Configuration Management references&quot;>Configuration Management&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BER92&quot; name=&quot;BER92&quot;>BER92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
H. Berlack 1992. &lt;i>Software Configuration Management.&lt;/i> New York, NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BUC93&quot; name=&quot;BUC93&quot;>BUC93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
J. Buckley 1993. &lt;i>Implementing Configuration Management, Hardware, Software and Firmware.&lt;/i>&amp;nbsp;&#xD;
Los Alamitos, CA: IEEE Computer Science Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WHI00&quot; name=&quot;WHI00&quot;>WHI00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Brian White and Geoff Glemm 2000. &lt;i>Software Configuration Management Strategies and Rational&#xD;
ClearCase: A Practical Introduction.&lt;/i> Addison-Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WHI91&quot; name=&quot;WHI91&quot;>WHI91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David Whitgift 1991. &lt;i>Methods and Tools for Software Configuration Management.&lt;/i>&amp;nbsp; New York,&#xD;
NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2>&#xD;
&lt;a id=&quot;Miscellaneous references&quot; name=&quot;Miscellaneous references&quot;>Miscellaneous&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOU94&quot; name=&quot;BOU94&quot;>BOU94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Serge Bouchy 1994.&amp;nbsp; &lt;i>L'ingénierie des systèmes informatiques évolutifs,&lt;/i> Paris, France:&#xD;
Eyrolles, 330p.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BRO95&quot; name=&quot;BRO95&quot;>BRO95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Frederick P. Brooks, Jr. 1995. &lt;i>The Mythical Man-Month-Essays on Software Engineering&lt;/i> 2nd ed.&#xD;
Reading, MA, Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A classic that should be read and re-read by everyone involved in software development. We recommend&#xD;
this 20-year anniversary edition rather than the original 1975 edition.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;con92&quot; name=&quot;con92&quot;>CON92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
D. Conner 1992. &lt;i>Managing at the Speed of Change.&lt;/i> New York, NY: Random House, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DAT99&quot; name=&quot;DAT99&quot;>DAT99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
C.J. Date 1999. &lt;i>An Introduction to Database Systems.&lt;/i>&amp;nbsp; 7th ed.&amp;nbsp; New York, NY:&#xD;
Addison-Wesley Publishing Company, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Excellent introduction, reference, and source of background information on Database Systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DAV95&quot; name=&quot;DAV95&quot;>DAV95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Alan Davis 1995. &lt;i>201 Principles of Software Development.&lt;/i>&amp;nbsp; New York, NY: McGraw-Hill.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Full of good advice for every team member on a project.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DEG90&quot; name=&quot;DEG90&quot;>DEG90&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Peter DeGrace and Leslie Stahl 1990. &lt;i>Wicked Problems, Righteous Solutions: A Catalog of Modern&#xD;
Software Engineering Practices.&lt;/i> Englewood Cliffs, NJ: Yourdon Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An insightful book on various process lifecycles and their origins, flaws, and strengths; useful for&#xD;
understanding the importance of process.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DEI84&quot; name=&quot;DEI84&quot;>DEI84&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Harvey M. Deitel 1984. &lt;i>An Introduction to Operating Systems.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;FIS96&quot; name=&quot;FIS96&quot;>FIS96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Charles Fishman 1996. &lt;i>Johnson Space Center Shuttle Software Group, &quot;They Write the Right&#xD;
Stuff&quot;&lt;/i>&lt;i>.&lt;/i> Fastcompany, Issue 6, p. 95, December, 1996.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GRA97&quot; name=&quot;GRA97&quot;>GRA97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ian Graham, et al. 1997. &lt;i>The OPEN Process Specification&lt;/i>. Harlow, England: Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Another process model, coming from down under that shares some principles with the Rational Unified&#xD;
Process (RUP).&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;hac97&quot; name=&quot;hac97&quot;>HAC97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
JoAnn T. Hackos and Dawn M. Stevens 1997. &lt;i>Standards for Online Communication.&lt;/i> John Wiley and&#xD;
Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
For the modern technical writer, this book has become the defacto standard. It defines a process for&#xD;
developing user manuals, specifically focusing on how you produce online help systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HER99&quot; name=&quot;HER99&quot;>HER99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Peter Herzum and Oliver Sims 1999. &lt;i>Business Component Factory: A Comprehensive Overview of&#xD;
Component-Based Development for the Enterprise.&lt;/i> John Wiley &amp;amp; Sons.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Defines and describes component-based development-from creating small components to creating&#xD;
federations of large component-based systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM2000&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>IBM System Integrated Method.&lt;/i> International Business Machines Corporation 1998, 1999, 2000.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM99a&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>An Approach to Designing e-business Solutions.&lt;/i> International Business Machines Corporation 1999.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245949.html&quot; target=&quot;_blank&quot;>http://www.redbooks.ibm.com/abstracts/sg245949.html&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM99b&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>Design Considerations: From Client Server Applications to e-business Applications.&lt;/i> International&#xD;
Business Machines Corporation 1999.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245503.html&quot; target=&quot;_blank&quot;>http://www.redbooks.ibm.com/abstracts/sg245503.html&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM99c&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>The Front of IBM WebSphere-Building e-business User Interfaces.&lt;/i> International Business Machines&#xD;
Corporation 1999.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245488.html&quot; target=&quot;_blank&quot;>http://www.redbooks.ibm.com/abstracts/sg245488.html&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM98a&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>Architecture Description Standard: Overview.&lt;/i>&amp;nbsp; International Business Machines Corporation&#xD;
1998.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
IBM98b&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>Architecture Description Standard: Semantic Specification.&lt;/i>&amp;nbsp; International Business Machines&#xD;
Corporation 1998.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Other relevant Web sites for the preceding IBM references are:&lt;br />&#xD;
&lt;a href=&quot;http://www.redbooks.ibm.com&quot; target=&quot;_blank&quot;>http://www.redbooks.ibm.com&lt;br />&#xD;
&lt;/a> &lt;a href=&quot;http://www.ibm.com/e-business/&quot; target=&quot;_blank&quot;>http://www.ibm.com/e-business/&lt;br />&#xD;
&lt;/a> &lt;a href=&quot;http://www.ibm.com/software&quot; target=&quot;_blank&quot;>http://www.ibm.com/software&lt;br />&#xD;
&lt;/a> &lt;a href=&quot;http://www.ibm.com/developer/&quot; target=&quot;_blank&quot;>http://www.ibm.com/developer/&lt;br />&#xD;
&lt;/a> &lt;a href=&quot;http://www.ibm.com/services/&quot; target=&quot;_blank&quot;>http://www.ibm.com/services/&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;IBM97&quot; name=&quot;IBM97&quot;>IBM97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
IBM 1997. &lt;i>Developing Object-Oriented Software&lt;/i>&lt;i>-&lt;/i>&lt;i>An Experienced- based Approach.&lt;/i>&#xD;
Upper Saddle River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Like the RUP, an iterative, incremental, object-oriented, scenario-driven, risk-aware process developed&#xD;
by the IBM Object Technology Center.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;IE610.12&quot; name=&quot;IE610.12&quot;>IE610.12&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
IEEE Std 610.12-1990. &lt;i>IEEE Standard Glossary of Software Engineering Terminology.&lt;/i> The Institute&#xD;
of Electrical and Electronics Engineers, Inc.: New York, NY, 10017-2394, USA. 1990.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; height=&quot;23&quot;>&#xD;
&lt;a id=&quot;JAV03&quot; name=&quot;JAV03&quot;>JAV03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
JavaTM 2 Platform, Standard Edition, v 1.4.2 API Specification -&#xD;
http://java.sun.com/j2se/1.4.2/docs/api/index.html&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;jel93&quot; name=&quot;jel93&quot;>JEL93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
J. Jellison 1993. &lt;i>Overcoming Resistance: A Practical Guide to Producing Change in the&#xD;
Workplace.&lt;/i>&amp;nbsp; New York, NY: Simon &amp;amp; Schuster, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KAT93&quot; name=&quot;KAT93&quot;>KAT93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jon R. Katzenbach and Douglas K. Smith 1993. &lt;i>The Wisdom of Teams.&lt;/i> New York, NY: Harper Business.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The secret of effective teams.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KET98&quot; name=&quot;KET98&quot;>KET98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Nasser Kettani, et al. 1998. &lt;i>De Merise à UML.&lt;/i> Paris, France: Editions Eyrolles.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Merise is a very popular software development methodology in France, which has been upgraded to use&#xD;
UML. It has some similitude with the RUP.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;LEA97&quot; name=&quot;LEA97&quot;>LEA97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Doug Lea 1999.&amp;nbsp; &lt;i>Concurrent Programming in Java.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MCA95&quot; name=&quot;MCA95&quot;>MCA95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jim McCarthy 1995.&amp;nbsp; &lt;i>Dynamics of Software Development.&lt;/i> Redmond, WA: Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Fifty-three rules of thumb by a Microsoft development manager.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MCO97&quot; name=&quot;MCO97&quot;>MCO97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Steve McConnell 1997.&amp;nbsp; &lt;i>Software Project Survival Guide.&lt;/i> Redmond, WA: Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A collection of practical experience on how to deliver successful software projects.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MCO93&quot; name=&quot;MCO93&quot;>MCO93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Steve McConnell 1993. &lt;i>Code Complete&lt;/i>&lt;i>-&lt;/i>&lt;i>A Practical Handbook of Software Construction.&lt;/i>&#xD;
Redmond, WA: Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A great book for the implementers and for testers looking at the implementation, integration, and test&#xD;
aspects of the development process.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;mos98&quot; name=&quot;mos98&quot;>MOS98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Microsoft 1998. The &lt;i>Microsoft Manual of Style for Technical Publications.&lt;/i>&amp;nbsp; Redmond, WA:&#xD;
Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;STA97&quot; name=&quot;STA97&quot;>STA97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jennifer Stapleton 1997.&amp;nbsp; &lt;i>The Dynamic System Development Method.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
At 15,000 feet, the DSDM approach could be seen as an introduction to the RUP. Although they use a&#xD;
different terminology, the two processes are very close to each other, and you can see the RUP as an&#xD;
instance or an implementation of&amp;nbsp; DSDM.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;TAN86&quot; name=&quot;TAN86&quot;>TAN86&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Andrew S. Tannenbaum 1986. &lt;i>Operating Systems: Design and Implementation.&amp;nbsp;&lt;/i> Upper Saddle&#xD;
River, NJ: Prentice Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WID00&quot; name=&quot;WID00&quot;>WID00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
R. Max Wideman and PMForum, February, 1999 and January, 2000. &lt;i>Wideman Comparative Glossary of&#xD;
Project Management Terms v2.0.&lt;/i> www.pmforum.org&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This great collection of various software engineering terms and their many definitions is available&#xD;
online at &lt;a href=&quot;http://www.pmforum.org/library/glossary/&quot; target=&quot;_blank&quot;>http://www.pmforum.org/library/glossary/&lt;/a>.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;YOU97&quot; name=&quot;YOU97&quot;>YOU97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Edward Yourdon 1997. &lt;i>Death March: Managing &quot;Mission Impossible&quot; Projects.&lt;/i> Upper Saddle River,&#xD;
NJ: Prentice Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An interesting view on project troubles.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Modeling and Unified Modeling Language references&quot; name=&quot;Modeling and Unified Modeling Language references&quot;>Modeling and Unified Modeling Language&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;BOO98&quot; name=&quot;BOO98&quot;>BOO98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
G. Booch, J. Rumbaugh, and I. Jacobson, 1998. &lt;i>UML User Guide&lt;/i>. Addison-Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Published at the same time as Rational Unified Process 5.1, this book is an excellent user's guide on&#xD;
UML by its main authors.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;CHE01&quot; name=&quot;CHE01&quot;>CHE01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
John Cheesman and John Daniels, 2001. &lt;i>UML Components: A Simple Process for Specifying&#xD;
Component-Based Software&lt;/i>. Addison-Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book provides a lot of in-depth practical guidance for specifying component-based systems, at the&#xD;
same time remaining compact and readable.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;CONA99&quot; name=&quot;CONA99&quot;>CONA99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jim Conallen, 1999. &lt;i>Building Web Applications with UML.&lt;/i> Addison-Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A good introduction to the basics of web application development in the context of the RUP. This book&#xD;
also shows how to use the UML to model web applications and introduces a Web Application Extension to&#xD;
the UML.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;DOUG98&quot; name=&quot;DOUG98&quot;>DOUG98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Bruce Powel Douglass 1998. &lt;i>Real-Time UML.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Using UML as the notation, this book offers good advice on the application of object-oriented&#xD;
technology for real-time systems.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&lt;a id=&quot;ERI04&quot; name=&quot;ERI04&quot;>ERI04&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Hans-Erik Eriksson, Magnus Penker, Brian Lyons and David Fado 2004. &lt;i>UML 2 Toolkit&lt;/i>. Indianopolis:&#xD;
Wiley Publishing, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;ERI97&quot; name=&quot;ERI97&quot;>ERI97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Hans-Erik Eriksson and Magnus Penker 1997. &lt;i>UML Toolkit&lt;/i>. New York: John Wiley &amp;amp; Sons.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A more comprehensive book on UML as seen from Sweden by another pair of Rational friends.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;FOW97&quot; name=&quot;FOW97&quot;>FOW97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Martin Fowler 1997. &lt;i>UML Distilled-Applying the standard object modeling language&lt;/i>. Addison-Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A very nice little introduction to UML if you're in a hurry.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;FRA03&quot; name=&quot;FRA03&quot;>FRA03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David S. Frankel 2003. &lt;i>Model Driven Architecture: Applying MDA to Enterprise Computing.&lt;/i> John&#xD;
Wiley &amp;amp; Sons.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
A foundational work on the OMG's Model Driven Architecture initiative, written by one of its principal&#xD;
developers.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;KLE03&quot; name=&quot;KLE03&quot;>KLE03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Anneke Kleppe, Jos Warmer and Wim Bast 2003. &lt;i>MDA Explained-The Model Driven&#xD;
Architecture(TM):Practice and Promise.&lt;/i> Addison-Wesley.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
More useful insights into MDA from a practitioner's viewpoint, written by contributors to the creation&#xD;
of MDA.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;LAR02&quot; name=&quot;LAR02&quot;>LAR02&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Craig Larman 2002.&amp;nbsp; &lt;i>Applying UML and Patterns: An Introduction to Object-Oriented Analysis and&#xD;
Design and the Unified Process,&lt;/i> 2nd ed. Prentice-Hall, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book is a great illustration of what happens in the Analysis &amp;amp; Design discipline. It teaches&#xD;
analysis and design, the use of UML, and the application of the concept of pattern in the context of&#xD;
the Unified Process. By presenting the case study in an iterative, risk-driven, architecture-centric&#xD;
process, Mr. Larman's advice has a realistic context. He exposes the dynamics of what really happens in&#xD;
software development and shows the external forces at play. The design activities are connected to&#xD;
other tasks, and they no longer appear as a purely cerebral activity of systematic transformations or&#xD;
creative intuition.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;MEL04&quot; name=&quot;MEL04&quot;>MEL04&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Stephen J. Mellor, Kendall Scott, Axel Uhl, Dirk Weise 2004. &lt;i>MDA Distilled-Principles of&#xD;
Model-Driven Architecture.&lt;/i> Addison-Wesley.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
Extracts and presents the essence of MDA, with an emphasis on the technology for executable models.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;MUL98&quot; name=&quot;MUL98&quot;>MUL98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Pierre-Alain Muller 1998.&amp;nbsp; &lt;i>Instant UML.&lt;/i> Wrox Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Another short introduction to UML by a former colleague.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;NBG01&quot; name=&quot;NBG01&quot;>NBG01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Eric J. Naiburg and Robert A. Maksimchuk 2001. &lt;i>UML For Database Design&lt;/i>. New York, NY:&#xD;
Addison-Wesley Publishing Company, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Application of UML to database modeling and design.&amp;nbsp; Supported throughout by a case study.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;OMG03&quot; name=&quot;OMG03&quot;>OMG03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>MDA Guide Version 1.0.1.&lt;/i> Object Management Group. Document omg/2003-06-01, June 2003&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td>&#xD;
&lt;p>&#xD;
A specification of the concepts and terminology of Model Driven Architecture from the OMG.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
&lt;a href=&quot;http://www.omg.org/mda/specs.htm&quot; target=&quot;_blank&quot;>http://www.omg.org/mda/specs.htm&lt;/a>&#xD;
&lt;/p>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;QUA98&quot; name=&quot;QUA98&quot;>QUA98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Terry Quatrani 1998. &lt;i>Visual Modeling with Rational Rose and UML.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Provides step-by-step guidance on how to build UML models. At the same time, it follows the RUP, in&#xD;
effect providing a small scale example.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot;>&#xD;
&lt;a id=&quot;RUM05&quot; name=&quot;RUM05&quot;>RUM05&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James Rumbaugh, Ivar Jacobson, Grady Booch, 2005. &lt;i>The Unified Modeling Language Reference Manual,&#xD;
second edition.&lt;/i> Addison-Wesley, Boston.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;RUM98&quot; name=&quot;RUM98&quot;>RUM98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
J. Rumbaugh, I. Jacobson, and G. Booch, 1998. &lt;i>UML Reference Manual.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Certainly more digestible than the OMG standard; UML fully exposed by its main authors.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;UML01&quot; name=&quot;UML01&quot;>UML01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>OMG Unified Modeling Language Specification, Version 1.4.&amp;nbsp;&lt;/i> Rational Software Corporation,&#xD;
18880 Homestead Road, Cupertino, CA 95014, and Object Management Group, Inc., 492 Old Connecticut Path,&#xD;
Framingham, MA 01701.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The latest specification of the UML. Available online at &lt;a href=&quot;http://www.rational.com/uml&quot; target=&quot;_blank&quot;>http://www.rational.com/uml&lt;/a>.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot; height=&quot;21&quot;>&#xD;
&lt;a id=&quot;UML04&quot; name=&quot;UML04&quot;>UML04&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>OMG Unified Modeling Language Specification, Version 2.0.&amp;nbsp;&lt;/i> Object Management Group, Inc.,&#xD;
Needham, MA 02494&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;11%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Final Adopted Specification (2003-08-02)&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;UML96&quot; name=&quot;UML96&quot;>UML96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
G. Booch, J. Rumbaugh, and I. Jacobson 1996. &lt;i>The Unified Modeling Language for Object-Oriented&#xD;
Development.&lt;/i> Documentation set, version 0.9 Addendum, Rational Software Corporation.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;11%&quot;>&#xD;
&lt;a id=&quot;UML95&quot; name=&quot;UML95&quot;>UML95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
G. Booch and J. Rumbaugh 1995. &lt;i>Unified Method for Object-Oriented Development.&lt;/i> Documentation&#xD;
set, version 0.8, Rational Software Corporation.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Object-Oriented Technology references&quot; name=&quot;Object-Oriented Technology references&quot;>Object-Oriented&#xD;
Technology&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOO93&quot; name=&quot;BOO93&quot;>BOO93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Grady Booch 1993. &lt;i>Object-Oriented Analysis and Design with Applications,&lt;/i> 2nd edition. Redwood&#xD;
City, CA: The Benjamin/Cummings Publishing Company.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BUH96&quot; name=&quot;BUH96&quot;>BUH96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
R. J. A. Buhr and R. S. Casselman 1996. &lt;i>Use Case Maps for Object-Oriented Systems.&lt;/i> Upper Saddle&#xD;
River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book develops some other views on use cases.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JAC92&quot; name=&quot;JAC92&quot;>JAC92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ivar Jacobson, et al. 1992. &lt;i>Object-Oriented Software Engineering-A Use Case-Driven Approach&lt;/i>,&#xD;
Wokingham, England: Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;RUM91&quot; name=&quot;RUM91&quot;>RUM91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James Rumbaugh, et al. 1991. &lt;i>Object-Oriented Modeling and Design.&lt;/i> Upper Saddle River, NJ:&#xD;
Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The three books above are the original roots to the object-oriented analysis and design discipline from&#xD;
&quot;the three amigos&quot;, just before the advent of the UML and the RUP. Despite the use of their original&#xD;
notations, they are still the key references for OO designers.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;RUM96&quot; name=&quot;RUM96&quot;>RUM96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James Rumbaugh 1996. &lt;i>OMT Insights.&lt;/i> New York: SIGS Books.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A complement to the original&amp;nbsp; OMT book, diving into special topics: inheritance, use cases, and so&#xD;
on.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;SEL94&quot; name=&quot;SEL94&quot;>SEL94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Bran Selic, Garth Gullekson, and Paul Ward 1994. &lt;i>Real-time Object-Oriented Modeling.&lt;/i> New York,&#xD;
NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The reference work on using object technology for the design of reactive systems by the people who have&#xD;
brought us &lt;i>ObjecTime Developer&lt;/i>.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WIR90&quot; name=&quot;WIR90&quot;>WIR90&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Rebecca Wirfs-Brock, Brian Wilkerson, and Lauren Wiener 1990. &lt;i>Designing Object-Oriented&#xD;
Software.&lt;/i> Upper Saddle River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book describes the Class, Responsibility, Collaboration (CRC) approach to object-oriented software&#xD;
development.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Project Management references&quot; name=&quot;Project Management references&quot;>Project Management&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;AMI95&quot; name=&quot;AMI95&quot;>AMI95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
K. Pulford, A. Kuntzmann-Combelles, and S. Shirlaw 1995. &lt;i>A Quantitative Approach to Software&#xD;
Management-The AMI Handbook.&lt;/i> Addison Wesley Longman.&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOE00&quot; name=&quot;BOE00&quot;>BOE00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Barry W. Boehm et al, 2000. Software Cost Estimation with COCOMO II. Upper Saddle River, NJ:&#xD;
Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The successor to the original classic work.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOE81&quot; name=&quot;BOE81&quot;>BOE81&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Barry W. Boehm 1981. &lt;i>Software Engineering Economics.&lt;/i> Upper Saddle River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A classic work on software effort estimation that describes the original COCOMO estimation model.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOE91&quot; name=&quot;BOE91&quot;>BOE91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Barry W. Boehm 1991. &lt;i>Software Risk Management: Principles and Practices&lt;/i>, &lt;i>IEEE Software,&lt;/i>&#xD;
Jan. 1991, IEEE, pp.32-41.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Still the best little introduction to risk management.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOO95&quot; name=&quot;BOO95&quot;>BOO95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Grady Booch 1995. &lt;i>Object Solutions-Managing the Object-Oriented Project.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A pragmatic book for managers of object-oriented projects; one of the sources on the underlying&#xD;
philosophy of the RUP.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CAN01&quot; name=&quot;CAN01&quot;>CAN01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Murray Cantor 2001. &lt;i>Software Leadership.&lt;/i> Addison-Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CAR93&quot; name=&quot;CAR93&quot;>CAR93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Marvin J. Carr, et al. 1993. &lt;i>Taxonomy-Based Risk Identification,&lt;/i> Technical Report&#xD;
CMU/SEI-93-TR-6, Pittsburgh, PA, SEI, June 1993, 24p.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Provides a source of inspiration to get started on your own list of risks.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CHA89&quot; name=&quot;CHA89&quot;>CHA89&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert Charette 1989. &lt;i>Software Engineering Risk Analysis and Management.&lt;/i> New York, NY:&#xD;
McGraw-Hill.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Practical perspective on risk management.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CHID94&quot; name=&quot;CHID94&quot;>CHID94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Chidamber and Kemerer 1994. &lt;i>A metrics suite for object-oriented design,&lt;/i> IEEE Transactions on&#xD;
Software Engineering, 20(6), 1994.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
One of the original contributions to the field of OO software metrics.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CLE96&quot; name=&quot;CLE96&quot;>CLE96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert T. Clemen 1996. &lt;i>Making Hard Decisions: An Introduction to Decision Analysis.&lt;/i> Duxbury&#xD;
Press.&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Thorough yet accessible treatment of the fundamentals of decision analysis.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DEV95&quot; name=&quot;DEV95&quot;>DEV95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Michael T. Devlin and Walker E. Royce.&amp;nbsp; &lt;i>Improving Software Economics in the Aerospace and&#xD;
Defense Industry,&lt;/i> Technical Paper TP-46, Santa Clara, CA, Rational Software Corporation, 1995.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;EVA98&quot; name=&quot;EVA98&quot;>EVA98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James R. Evans and David L. Olson 1998. &lt;i>Introduction to Simulation and Risk Analysis.&lt;/i>&amp;nbsp;&#xD;
Upper Saddle River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Good introduction to the use of simulation for business modeling.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;FAI94&quot; name=&quot;FAI94&quot;>FAI94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Richard Fairley 1994. &quot;Risk Management for Software Project,&quot; &lt;i>IEEE Software,&lt;/i> 11 (3), May 1994,&#xD;
pp.57-67&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Straightforward strategy for risk management if you have never done this before.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GIL88&quot; name=&quot;GIL88&quot;>GIL88&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Tom Gilb 1988. &lt;i>Principles of Software Engineering Management.&lt;/i> Harlow, England: Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A great book by a pioneer of iterative development, it's full of pragmatic advice for the project&#xD;
manager.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HEND96&quot; name=&quot;HEND96&quot;>HEND96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Brian Henderson-Sellers 1996. &lt;i>Object-Oriented Metrics, Measures of Complexity.&lt;/i> Prentice Hall&#xD;
PTR.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Good, detailed coverage of OO-specific metrics.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JON94&quot; name=&quot;JON94&quot;>JON94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Capers Jones 1994. &lt;i>Assessment and Control of Software Risks.&lt;/i> Yourdon Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An indispensable source of risks to check your list against to make sure it's is complete.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KAR96&quot; name=&quot;KAR96&quot;>KAR96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Dale Karolak 1996. &lt;i>Software Engineering Risk Management.&lt;/i> Los Alamitos, CA: IEEE Computer Society&#xD;
Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Offers more sophisticated advice and techniques for risk management.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MCO96&quot; name=&quot;MCO96&quot;>MCO96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Steve McConnell 1996. &lt;i>Rapid Development.&lt;/i> Redmond, WA: Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Excellent coverage of good practice for rapid software development&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MSP97&quot; name=&quot;MSP97&quot;>MSP97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
User's Guide for Microsoft Project 98, Microsoft Corporation, 1997.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;OCO94&quot; name=&quot;OCO94&quot;>OCO94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Fergus O'Connell 1994. &lt;i>How to Run Successful Projects.&lt;/i> New York, NY: Prentice-Hall&#xD;
International.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A real gem! Everything you really need to know to manage your first project, in 170 pages.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PMI96&quot; name=&quot;PMI96&quot;>PMI96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>A Guide to the Project Management Body of Knowledge.&lt;/i> The Project Management Institute: Newton&#xD;
Square, PA, 19073-3299, USA. 1996.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PUT92&quot; name=&quot;PUT92&quot;>PUT92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Lawrence Putnam &amp;amp; Ware Myers 1992. &lt;i>Measures for Excellence: Reliable Software On Time, Within&#xD;
Budget.&lt;/i> Yourdon Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ROY98&quot; name=&quot;ROY98&quot;>ROY98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Walker Royce 1998. &lt;i>Software Project Management: A Unified Framework.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An indispensable companion to the RUP, this book describes the spirit of the Rational Process and its&#xD;
underlying software economics. Full of great advice for the project manager.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;VOS96&quot; name=&quot;VOS96&quot;>VOS96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David Vose 1996. &lt;i>Quantitative Risk Analysis: A Guide to Monte Carlo Simulation Modeling.&lt;/i> John&#xD;
Wiley &amp;amp; Sons.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A good guide to the modeling of uncertainty using Monte Carlo techniques.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WHIT97&quot; name=&quot;WHIT97&quot;>WHIT97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Scott Whitmire 1997. &lt;i>Object-Oriented Design Measurement.&lt;/i> John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A good, if mathematically challenging, treatment of the theoretical basis of software measurement.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Requirement Management references&quot; name=&quot;Requirement Management references&quot;>Requirements Management&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;AND96&quot; name=&quot;AND96&quot;>AND96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Stephen J. Andriole 1996. &lt;i>Managing Systems Requirements: Methods, Tools, and Cases.&lt;/i> McGraw Hill.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BEY98&quot; name=&quot;BEY98&quot;>BEY98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Hugh Beyer and Karen Holtzblatt 1998. &lt;i>Contextual Design.&lt;/i> San Francisco, CA: Morgan Kaufmann&#xD;
Publishers.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BIT03&quot; name=&quot;BIT03&quot;>BIT03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Kurt Bittner and Ian Spence 2003. &lt;i>Use Case Modeling.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Comprehensive coverage of use case techniques and practices, including useful examples showing how&#xD;
use-case specifications evolve over time.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;COC01a&quot; name=&quot;COC01a&quot;>COC01a&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Alistair Cockburn 2001. &lt;i>Writing Effective Use Cases.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Excellent guidance for those who need to write use cases. Multiple styles and techniques contrasted&#xD;
with insight in an unbiased way. Many helpful tips to improve your use cases.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CON99&quot; name=&quot;CON99&quot;>CON99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Larry Constantine and Lucy A.D. Lockwood 1999. &lt;i>Software for Use.&lt;/i> Reading, MA: Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
An excellent book on user-centric design, focusing on techniques and practical guidelines for&#xD;
developing software that is usable.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;COO99&quot; name=&quot;COO99&quot;>COO99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Alan Cooper1999. &lt;i>The Inmates are Running the Asylum.&lt;/i> Indianapolis, IN: SAMS.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DAV93&quot; name=&quot;DAV93&quot;>DAV93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Alan Davis 1993. &lt;i>Software Requirements-Objects, Functions and States.&lt;/i> Englewood Cliffs, NJ:&#xD;
Prentice Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;FIS91&quot; name=&quot;FIS91&quot;>FIS91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Roger Fisher and William Ury 1991. &lt;i>Getting to Yes-Negotiating Agreement Without Giving In, 2nd&#xD;
Edition.&lt;/i> Penguin Books USA.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GAU89&quot; name=&quot;GAU89&quot;>GAU89&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Donald Gause and Gerald Weinberg 1989. &lt;i>Exploring Requirements-Quality Before Design.&lt;/i> New York,&#xD;
NY: Dorset House.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GOU88&quot; name=&quot;GOU88&quot;>GOU88&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
John D. Gould 1988. &quot;How to Design Usable Systems&quot;, in Helander, Martin, ed. &lt;i>Handbook of Computer&#xD;
Interaction&lt;/i>, pp. 757-789, North-Holland, Amsterdam, The Netherlands.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GOU87&quot; name=&quot;GOU87&quot;>GOU87&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
John D. Gould, Stephen J. Boies, Stephen Levy, John T. Richards and Jim Schoonard 1987. &quot;The 1984&#xD;
Olympic Message System: a test of behavioral principles of system design&quot;, in &lt;i>Communications of the&#xD;
ACM&lt;/i>, Vol. 30, No. 9, pp. 758-769.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GRA92&quot; name=&quot;GRA92&quot;>GRA92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert Grady 1992. &lt;i>Practical Software Metrics for Project Management and Process Improvement&lt;/i>.&#xD;
Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot; height=&quot;28&quot;>&#xD;
&lt;a id=&quot;HOL96&quot; name=&quot;HOL96&quot;>HOL96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;88%&quot; colspan=&quot;2&quot; height=&quot;28&quot;>&#xD;
Holtzblatt, K., and H. Beyer 1996. &quot;Contextual Design: Principles and Practice,&quot; &lt;i>Field Methods for&#xD;
Software and Systems Design&lt;/i>. D. Wixon and J. Ramey (Eds.), NY, NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;IE830&quot; name=&quot;IE830&quot;>IE830&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
IEEE Std 830-1993. &lt;i>Recommended Practice for Software Requirements Specifications.&lt;/i> Software&#xD;
Engineering Standards Committee of the IEEE Computer Society: New York, NY, 1993.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ISO13407&quot; name=&quot;ISO13407&quot;>ISO13407&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
ISO/TC159 1999. &lt;i>Human-centred design processes for interactive systems.&lt;/i> Report ISO 13407:1999,&#xD;
International Organization for Standardization, Geneva, Switzerland.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KOV99&quot; name=&quot;KOV99&quot;>KOV99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Benjamin L. Kovitz 1999. &lt;i>Practical Software Requirements-A Manual of Content &amp;amp; Style.&lt;/i>&#xD;
Manning Publications.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;LEF99&quot; name=&quot;LEF99&quot;>LEF99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Dean Leffingwell and Don Widrig 1999. &lt;i>Effective Requirements Management.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot; height=&quot;21&quot;>&#xD;
&lt;a id=&quot;MAY99&quot; name=&quot;MAY99&quot;>MAY99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;88%&quot; colspan=&quot;2&quot; height=&quot;21&quot;>&#xD;
Deborah J. Mayhew1999. &lt;i>The Usability Engineering Lifecycle.&lt;/i> Morgan Kaufmann Publishers.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;SCH98&quot; name=&quot;SCH98&quot;>SCH98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Geri Schneider and Jason P. Winters 1998. &lt;i>Applying Use Cases-A Practical Guide.&lt;/i> Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;SOM97&quot; name=&quot;SOM97&quot;>SOM97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ian Sommerville and Pete Sawyer 1997. &lt;i>Requirements Engineering-A Good Practice Guide.&lt;/i> New York,&#xD;
NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;THA97&quot; name=&quot;THA97&quot;>THA97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Richard H. Thayer and Merlin Dorfman 1997. &lt;i>Software Requirements Engineering, 2nd Edition.&lt;/i> IEEE&#xD;
Computer Society Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WEI95&quot; name=&quot;WEI95&quot;>WEI95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Gerald Weinberg, 1995. &quot;Just Say No! Improving the Requirements Process&quot;, &lt;i>American Programmer&lt;/i>,&#xD;
October 1995.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Software Architecture references&quot; name=&quot;Software Architecture references&quot;>Software Architecture&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot; valign=&quot;top&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BAS98&quot; name=&quot;BAS98&quot;>BAS98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Len Bass, Paul Clements, and Rick Kazman 1998. &lt;i>Software Architecture in Practice.&lt;/i> Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A handbook of software architecture, with numerous case studies.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOS00&quot; name=&quot;BOS00&quot;>BOS00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Jan Bosch 2000. &lt;i>Design and Use of Software Architecture.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BUS96&quot; name=&quot;BUS96&quot;>BUS96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Frank Buschmann, Régine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stahl 1996.&#xD;
&lt;i>Pattern-Oriented Software Architecture-A System of Patterns&lt;/i>, New York, NY: John Wiley and Sons,&#xD;
Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Following the model of the &quot;gang of four&quot; book (Gamma, et al, see above) this book makes an inventory&#xD;
of a wide range of design patterns at the level of the architecture.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CKK02&quot; name=&quot;CKK02&quot;>CKK02&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Paul Clements, Rick Kazman, and Mark Klein 2002. &lt;i>Evaluating Software Architecture&lt;/i>, Addison&#xD;
Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CLE02&quot; name=&quot;CLE02&quot;>CLE02&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Paul Clements et al. 2002. &lt;i>Documenting Software Architectures: Views and Beyond&lt;/i>, Addison Wesley&#xD;
Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;CLN02&quot; name=&quot;CLN02&quot;>CLN02&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Paul Clements and Linda Northrop 2002. &lt;i>Software Product Lines: Practice and Patterns&lt;/i>, Addison&#xD;
Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The preceding three books are from the Software Engineering Institute's architecture study group.&#xD;
&lt;i>Evaluating Software Architecture&lt;/i> provides useful input for architectural reviews. &lt;i>Documenting&#xD;
Software Architectures: Views and Beyond&lt;/i> fully embraces the concept of views and helps with&#xD;
developing a Software Architecture document.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DIK01&quot; name=&quot;DIK01&quot;>DIK01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David M. Dikel, David Kane, and James R. Wilson 2001. &lt;i>Software Architecture - Organizational&#xD;
Principles and Patterns&lt;/i>, Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Describes the VRAPS model of architecting: Vision, Rhythm, Anticipation, Partnering, and&#xD;
Simplification. This is a good reference for the budding architect to put his or her role in context.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;FOW97a&quot; name=&quot;FOW97a&quot;>FOW97a&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Martin Fowler 1997. &lt;i>Analysis Patterns: Reusable Object Models.&lt;/i> Addison Wesley Longman.&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GAM94&quot; name=&quot;GAM94&quot;>GAM94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides 1994. &lt;i>Design Patterns-Elements of&#xD;
Reusable Object-Oriented Software.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
One of the earlier works on patterns, this book deals with patterns &quot;in the small&quot;.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GAR93&quot; name=&quot;GAR93&quot;>GAR93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David Garlan and Mary Shaw. &lt;i>An Introduction to Software Architecture.&amp;nbsp;&lt;/i> SEI Technical Report&#xD;
CMU/SEI-94-TR-21.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HOF99&quot; name=&quot;HOF99&quot;>HOF99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Christine Hofmeister, Robert Nord, and Dilip Soni 1999. &lt;i>Applied Software Architecture.&lt;/i> Addison&#xD;
Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Proposes an alternate set of architectural views and describes the corresponding process. As the views&#xD;
are not too far from the RUP views, this book is an excellent complement to the guidance found in RUP.&#xD;
Contains several examples of architecture from the biomedical field.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;IEP1471&quot; name=&quot;IEP1471&quot;>IEP1471&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>IEEE Recommended Practice for Architectural Description&lt;/i>, IEEE Std P1471, 2000.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This standard recommends architectural description based on the concept of multiple views, of which the&#xD;
RUP 4+1 view is an example.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JAC97&quot; name=&quot;JAC97&quot;>JAC97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ivar Jacobson, Martin Griss and Patrik Jonsson, 1997. &lt;i>Software Reuse-Architecture, Process and&#xD;
Organization for Business Success&lt;/i>. Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A great companion book to the RUP, this book offers insights on the design of components and systems of&#xD;
interconnected system, and lays out a strategy for institutionalizing a practice of systematic reuse at&#xD;
the corporate level.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KRU95&quot; name=&quot;KRU95&quot;>KRU95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Philippe Kruchten 1995, &quot;The 4+1 view model of architecture,&quot; &lt;i>IEEE Software.&lt;/i> 12(6), November&#xD;
1995.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The origin of the 4+1 views used for architectural description in the RUP.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;LMFS96&quot; name=&quot;LMFS96&quot;>LMFS96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Lockheed Martin Federal STARS (Software Technology for Adaptable, Reliable Systems) Program. Domain&#xD;
Engineering Guidebook.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This Guidebook provides a high-level description of the Domain Engineering&amp;nbsp; process in the context&#xD;
of a real organization-the U.S. Air Force's Space and Warning Systems Center.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PW92&quot; name=&quot;PW92&quot;>PW92&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Dewayne E. Perry and Alexander L. Wolf. &lt;i>Foundations for the Study of Software Architecture.&lt;/i> ACM&#xD;
SIGSOFT Software Engineering Notes, 17(4):40-52, October 1992.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;REC97&quot; name=&quot;REC97&quot;>REC97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Eberhardt Rechtin and Mark Maier 1997. &lt;i>The Art of System Architecting.&lt;/i> Boca Ration, FL: CRC&#xD;
Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Although not specifically directed to software engineers, these two books are extremely valuable for&#xD;
software architects: in particular, they introduce an invaluable set of heuristics and many examples of&#xD;
architecture.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;REC91&quot; name=&quot;REC91&quot;>REC91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Eberhardt Rechtin 1991. &lt;i>Systems Architecting: creating and building complex systems&lt;/i>. Englewood&#xD;
Cliffs NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ROY91&quot; name=&quot;ROY91&quot;>ROY91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Walker E. Royce and Winston Royce, &quot;Software Architecture: Integrating Process and Technology,&quot;&#xD;
&lt;i>Quest,&lt;/i> 14 (1), 1991, Redondo Beach, CA: TRW, pp.2-15.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;SHA96&quot; name=&quot;SHA96&quot;>SHA96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Mary Shaw and David Garlan 1996. &lt;i>Software Architecture-Perspectives on an Emerging Discipline.&lt;/i>&#xD;
Upper Saddle River, NJ: Prentice-Hall.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A good introduction to the concepts and problems of software architecture.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;WIT94&quot; name=&quot;WIT94&quot;>WIT94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Bernard I. Witt, F. Terry Baker, and Everett W. Merritt 1994. &lt;i>Software Architecture and&#xD;
Design-Principles, Models, and Methods.&lt;/i> New York, NY: Van Nostrand Reinhold.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
One of the first comprehensive book written on software architecture.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2>&#xD;
&lt;a id=&quot;Software Development Process references&quot; name=&quot;Software Development Process references&quot;>Software Development&#xD;
Process&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;AMB99&quot; name=&quot;AMB99&quot;>AMB99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Scott W. Ambler 1999. &lt;i>More Process Patterns: Delivering Large-Scale Systems Using Object&#xD;
Technology&lt;/i>. New York, NY: SIGS Books/Cambridge University Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The companion to [AMB98].&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;AMB98&quot; name=&quot;AMB98&quot;>AMB98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Scott W. Ambler 1998. &lt;i>Process Patterns: Building Large-Scale Systems Using Object Technology&lt;/i>.&#xD;
New York, NY: SIGS Books/Cambridge University Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A good resource on process tailoring and applying object-oriented techniques to software engineering&#xD;
projects.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOE96&quot; name=&quot;BOE96&quot;>BOE96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Barry W. Boehm 1996, &quot;Anchoring the Software Process,&quot; &lt;i>IEEE Software,&lt;/i> July 1996, pp.73-82.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This article defines the four phases and the corresponding milestones.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BOE88&quot; name=&quot;BOE88&quot;>BOE88&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Barry W. Boehm 1988, &quot;A Spiral Model of Software Development and Enhancement,&quot; &lt;i>Computer,&lt;/i> May&#xD;
1988, IEEE, pp.61-72.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This seminal article defines the principles and motivations of iterative development.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;COC01&quot; name=&quot;COC01&quot;>COC01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Alistair Cockburn 2001. &lt;i>Agile Software Development&lt;/i> Addison-Wesley Publishing Co.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Peers into the team dynamics, the cultures, the communications aspects of software development.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;DOD94&quot; name=&quot;DOD94&quot;>DOD94&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
&lt;i>Software Development and Documentation,&lt;/i> MIL-STD-498, U.S. Department of Defense, December 1994.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;FER01&quot; name=&quot;FER01&quot;>FER01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Xavier Ferre et al. 2001, &quot;Usability Basics for Software Developers,&quot; &lt;i>IEEE Software,&lt;/i> January&#xD;
2001, pp. 22-29.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HIG00&quot; name=&quot;HIG00&quot;>HIG00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James A. Highsmith 2000. &lt;i>Adaptive Software Development: A Collaborative Approach to Managing Complex&#xD;
Systems&lt;/i>. Dorset House.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book is a great companion book to the RUP-a fantastic and convincing plea for iterative&#xD;
development. Very practical advice for the project manager.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;HUM89&quot; name=&quot;HUM89&quot;>HUM89&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Watts S. Humphrey 1989. &lt;i>Managing the Software Process&lt;/i>. Reading, MA: Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A classic book on software process and the capability maturity model developed at the Software&#xD;
Engineering Institute.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ISO95&quot; name=&quot;ISO95&quot;>ISO95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
ISO/IEC 12207 &lt;i>Information Technology-Software Life-cycle Processes.&lt;/i> ISO, Geneva, 1995, 57p.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ISO91&quot; name=&quot;ISO91&quot;>ISO91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
ISO 9000-3 &lt;i>Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of&#xD;
Software.&lt;/i> ISO, Geneva 1991.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Two key standards for software process definition and assessment.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JAC98&quot; name=&quot;JAC98&quot;>JAC98&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ivar Jacobson, Grady Booch, and James Rumbaugh 1998. &lt;i>The Unified Software Development Process.&lt;/i>&#xD;
Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This recent textbook is a more thorough description of the Unified Process and is a useful companion to&#xD;
the RUP. Also provides examples of UML modeling.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JAC97&quot; name=&quot;JAC97&quot;>JAC97&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ivar Jacobson, Martin Griss, and Patrik Jonsson 1997. &lt;i>Software Reuse-Architecture, Process and&#xD;
Organization for Business Success.&lt;/i> Addison Wesley Longman.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This textbook on software reuse is great complement to the RUP. It features also some great chapters on&#xD;
architecture.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;JEF01&quot; name=&quot;JEF01&quot;>JEF01&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Ron Jeffries, Ann Anderson, and Chet Hendrickson 2001. &lt;i>Extreme Programming Installed.&lt;/i>&#xD;
Addison-Wesley.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book describes practical Extreme Programming techniques.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KRU96&quot; name=&quot;KRU96&quot;>KRU96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Philippe Kruchten 1996. &quot;A Rational Development Process&quot;&lt;i>,&lt;/i> &lt;i>CrossTalk&lt;/i>, 9 (7), July 1996,&#xD;
p.11-16.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Developed with Walker Royce, Sue Mickel, and a score of Rational consultants, this article describes&#xD;
the iterative lifecycle of the Rational Process.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KRU91&quot; name=&quot;KRU91&quot;>KRU91&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Philippe Kruchten 1991. &quot;Un processus de dévelopment de logiciel itératif et centré sur&#xD;
l´architecture&quot;, &lt;i>Proceedings of the 4th International Conference on Software Engineering, December&#xD;
1991&lt;/i>, Toulouse, France, EC2.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The Rational iterative process in French.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KRU00&quot; name=&quot;KRU00&quot;>KRU00&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Philippe Kruchten 2000. &lt;i>The Rational Unified Process, An Introduction, Second Edition.&lt;/i> Addison&#xD;
Wesley Longman.&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Indespensible as an introductory text, this &quot;mile wide, inch deep&quot; overview quickly introduces you to&#xD;
the concepts, structure, content, and motivation of the RUP.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;KRO03&quot; name=&quot;KRO03&quot;>KRO03&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Per Kroll and Philippe Kruchten 2003. &lt;i>The Rational Unified Process Made Easy, A Practitioners Guide&#xD;
to the RUP.&lt;/i> Addison Wesley Longman.&amp;nbsp;&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
A practical guide to adopting the spirit, principles and practices of the RUP. An invaluable resource&#xD;
in helping you decide how to apply the RUP in your organization or project.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;MCF96&quot; name=&quot;MCF96&quot;>MCF96&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert McFeeley 1996. &lt;i>IDEAL: A User's Guide for Software Process Improvement.&lt;/i> Software&#xD;
Engineering Institute, Pittsburgh, PA, CMU/SEI-96-HB-001.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Describes a software process improvement program model called IDEAL, a generic description of a&#xD;
sequence of recommended steps for initiating and managing a process implementation project.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PAR86&quot; name=&quot;PAR86&quot;>PAR86&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
David L. Parnas and Paul C. Clements, &quot;A Rational Design Process: How and Why to Fake It&quot;, &lt;i>IEEE&#xD;
Trans. Software Eng.,&lt;/i> Feb. 1986, pp.251-257.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;PAU93&quot; name=&quot;PAU93&quot;>PAU93&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Mark Paulk, et al. 1993. &lt;i>Capability Maturity Model for Software, Version 1.1.&lt;/i> Software&#xD;
Engineering Institute, Pittsburgh, PA SEI-93-TR-024.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
The original reference for the capability maturity model.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ROY90&quot; name=&quot;ROY90&quot;>ROY90&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Walker E. Royce, &quot;TRW's Ada Process Model for Incremental Development of Large Software Systems&quot;,&#xD;
&lt;i>Proceedings ICSE 12, March 26-30, 1990,&lt;/i> Nice, France, IEEE, pp.2-11.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;ROY70&quot; name=&quot;ROY70&quot;>ROY70&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Winston W. Royce, &quot;Managing the Development of Large Software Systems: Concepts and Techniques&quot;,&#xD;
&lt;i>Proceedings, WESCON&lt;/i>, August 1970.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;/div>&lt;br />&#xD;
&lt;h2 align=&quot;left&quot;>&#xD;
&lt;a id=&quot;Testing and Quality references&quot; name=&quot;Testing and Quality references&quot;>Testing and Quality&lt;/a>&#xD;
&lt;/h2>&#xD;
&lt;div align=&quot;center&quot;>&#xD;
&lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;>&#xD;
&lt;tbody>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BAC01a&quot; name=&quot;BAC01a&quot;>BAC01a&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
James Bach 2001. &lt;i>What Is Exploratory Testing? (And How It Differs from Scripted Testing).&lt;/i>&#xD;
Software Testing and Quality Engineering Magazine, Jan 29, 2001.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This article is available online at &lt;a href=&quot;http://www.stickyminds.com/sitewide.asp?sid=582697&amp;amp;sqry=*J(MIXED)*R(createdate)*K(simplesite)*F(what is exploratory testing)*&amp;amp;sidx=0&amp;amp;sopp=10&amp;amp;ObjectId=2255&amp;amp;Function=DETAILBROWSE&amp;amp;ObjectType=COL&quot; target=&quot;_blank&quot;>http://www.stickyminds.com&lt;/a>.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BAS87&quot; name=&quot;BAS87&quot;>BAS87&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
BAS87 Victor R. Basili and H. Dieter Rombach 1987. &lt;i>Tailoring the Software Process to Project Goals&#xD;
and Environments.&lt;/i> Proceedings of the 9th International Conference on Software Engineering Software,&#xD;
IEEE Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BEI95&quot; name=&quot;BEI95&quot;>BEI95&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Boris Beizer 1995. &lt;i>Black Box Testing.&lt;/i> New York, NY: John Wiley &amp;amp; Sons, Inc.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
Various strategies to develop test cases for the functional testing of software. Dr. Beizer's writing&#xD;
style and wit make this book easy and fun to read, with excellent, understandable examples.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;BLA99&quot; name=&quot;BLA99&quot;>BLA99&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Rex Black 1999. &lt;i>Managing the Testing Process.&lt;/i> Microsoft Press.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
This book is a good source of information about managing system testing teams.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td width=&quot;10%&quot;>&#xD;
&lt;/td>&#xD;
&lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;
&lt;a id=&quot;GLA81&quot; name=&quot;GLA81&quot;>GLA81&lt;/a>&#xD;
&lt;/td>&#xD;
&lt;td colspan=&quot;2&quot;>&#xD;
Robert L. Glass 1981. &lt;i>Persistent Software Errors.&lt;/i> IEEE Transactions on Software Engineering,&#xD;
March 1981.&#xD;
&lt;/td>&#xD;
&lt;/tr>&#xD;
&lt;tr>&#xD;
&lt;td valign=&quot;top&quot; width=&quot;12%&quot;>&#xD;