I never knew my requirements were object-oriented until I talked to my analyst

A discussion on object-oriented analysis (OOA) is summarized. Among the topics discussed are: whether objects facilitate understanding; whether autonomy facilitates understanding; whether OOA encourages premature design; whether OOA addresses requirements volatility; the Shlaer-Mellor method; the separation of problem domains; the translation of domains; the role of prototyping in requirements engineering; tool support; and the question of distinguishing models from requirements.<<ETX>>