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