Developing Applications with Java™ and UML

Checkpoint

Where We've Been

• The first step in the Elaboration phase is to describe in detail the alternate and exception pathways through all of the use-cases in Increment 1.

• Categorization of business rules, but not UML artifacts, is key to the success and traceability of the project. Business rules are assigned to the use-cases that enforce them.

• We can develop a preliminary list of candidate classes by simply extracting nouns from the use-cases and applying various class filters.

• Classes are divided into three categories called stereotypes: entity, control, and boundary. Entity classes are of most interest to the project sponsors, but all classes are vital to ensuring the application's flexibility as the business evolves.

• Associations come in ...