Footnotes

Chapter 1

1 This means that our approach to maintenance and customization projects is also to start by object modeling the business and then doing the gap analysis between existing functionality and the desired system.

2 For more on iterative development, see “Object Modeling and Iterative Development,” in Chapter 10.

3 User scenarios are frequently called “use cases.” Building use cases before object modeling focuses attention on how things are done now instead of what needs to be accomplished. The result is often a continuation of poor processes and a missed opportunity for process re-engineering.

4 Use of the pronoun “he” and all its variations should be understood as a generic pronoun representing both male and female persons. One ...

Get Streamlined Object Modeling: Patterns, Rules, and Implementation now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.