10.7. Specification or Description Conceptual Classes
The following discussion may at first seem related to a rare, highly specialized issue. However, it turns out that the need for specification conceptual classes (as will be defined) is common in many domain models. Thus, it is emphasized.
Assume the following:
An Item instance represents a physical item in a store; as such, it may even have a serial number.
An Item has a description, price, and itemID, which are not recorded anywhere else.
Everyone working in the store has amnesia.
Every time a real physical item is sold, a corresponding software instance of Item is deleted from “software land.”
With these assumptions, what happens in the following scenario?
There is strong demand for the popular ...
Get Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, Second Edition 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.
