Index of Articles and Publications

November 2001:

Tailoring the Rational Unified Process (RUP), A Lightweight Process Development Case by Jeff Kantor
This article documents the reasons and strategies used in tailoring the RUP in order to create a lightweight process for a specific project. It focuses on the critical requirements and design activities in the Elaboration phase and on the rationale for tailoring out the unused elements of RUP.

Use Case Driven Testing by Jeff Kantor
This article documents a process for driving test requirements and test cases from use cases for function testing at the System and Acceptance Test levels.

The following series of articles "Driving Design with Use Cases," details use-case driven object modeling and Unified Modeling Language examples published in Software Development.

June 2001:

Give Them What They Want by Doug Rosenberg and Kendall Scott
Requirements review is an essential part of the modeling process. Here's how to ensure that your use cases and the domain model work together to address the end users' functional requirements.

April 2001:
Sequence Diagrams: One Step at a Time by Doug Rosenberg and Kendall Scott
Interaction modeling allows you to lay out the detailed behavior of your objects and find appropriate homes for attributes and operations. This article outlines some more common mistakes, and then explains how to correct them. Our focus will be on performing interaction modeling using UML sequence diagrams. In this fifth installment from a forthcoming book, you'll learn to update and expand your static model.

March 2001:
Successful Robustness Analysis by Doug Rosenberg and Kendall Scott
This simple and useful technique links the what of analysis to the how of design by ensuring your use case text is correct. It addresses necessary courses of action and allows you to continue to discover objects.

February 2001:
Top Ten Use Case Mistakes by Doug Rosenberg and Kendall Scott
"Use case driven" means writing the user manual first, then writing the code. This practice reinforces the fundamental notion that a system must conform to the needs of the users, instead of your users conforming to the system.

January 2001:
Driving Design: The Problem Domain by Doug Rosenberg and Kendall Scott
Part two of five: Domain modeling is an essential part of the ICONIX process. It builds the initial static portion of a model, which is essential when driving your application design forward from use cases.

December 2000:
Driving Design with Use Cases by Doug Rosenberg and Kendall Scott
Part one of five: This series will teach you how to build a domain model with loosely coupled classes, write concise use cases, do robustness analysis and create sequence diagrams.

Issues of Ratio's ObjectiveView, "The Object and Component Journal for Software Professionals":
(Note: These articles appear in PDF format)

[   ] ObjectiveView#7


[   ]

[   ]

[   ]

ICONIX Software Engineering, Inc./2800 28th Street, Suite 320/Santa Monica, CA 90405/Tel (310)458-0092/Fax (310)396-3454/email: