Choose a system metaphor
to keep the team on the same page by naming classes and methods consistently. What you name your objects is very
important for understanding the overall design of the system and code reuse as well. Being able to guess at what
something might be named if it already existed and being right is a real time saver. Choose a system of names for
your objects that everyone can relate to without specific, hard to earn knowledge about the system. For example the Chrysler
payroll system was built as a production line. At Ford car sales were structured as a bill of materials. There
is also a metaphor known as the naive metaphor which is based on your domain itself. But don't choose the naive
metaphor unless it is simple enough.
Choose a system metaphor
to keep the team on the same page by naming classes and methods consistently. What you name your objects is very
important for understanding the overall design of the system and code reuse as well. Being able to guess at what
something might be named if it already existed and being right is a real time saver. Choose a system of names for
your objects that everyone can relate to without specific, hard to earn knowledge about the system.
