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