Extreme programming practices: Difference between revisions

Revision as of 14:40, 14 October 2015

Revision as of 22:00, 4 January 2016

Line 155:

=== System metaphor ===

The system metaphor is a story that everyone - customers, programmers, and managers - can tell about how the system works. It's a naming concept for classes and methods that should make it easy for a team member to guess the functionality of a particular class/method, from its name only. For example a library system may create <code>loan_records(class)</code> for <code>borrowers(class)</code>, and if the item were to become overdue it may perform a make_overdue operation on a <code>catalogue (class)</code>. For each class or operation the functionality is obvious to the entire team.

==Programmer welfare==