Milestones

Trace messages may correspond to specific implementation code such as recording the status of an operation, dumping data values, printing errors, or they may correspond to higher levels of software design and architecture, and even to use case stories. We call such messages Milestones by analogy with project management²⁵. Alternative names can be Chapter Messages, Summary Messages, Checkpoints, or Use Case Messages. These are different from Macrofunctions (Volume 7, page 283) which are collections messages grouped by some higher function. Milestone messages are specifically designed distinct trace statements:

They can also be a part of Significant Events (Volume 5, page 281), serve the role of Anchor Messages (Volume 5, page 293), and be a part of Basic Facts (Volume 3, page 345) and Vocabulary Index (Volume 4, page 349).

²⁵ http://en.wikipedia.org/wiki/Milestone_(project_management)