Java Reference
In-Depth Information
Programming, a development methodology that strives for simplicity by cutting out
most of the formal trappings of a traditional development methodolgy and instead
focusing on a set of practices:
ȗ
Realistic planning: Customers are to make business decisions, programmers are
to make technical decisions. Update the plan when it conflicts with reality.
ȗ
Small releases: Release a useful system quickly, then release updates on a very
short cycle.
533
534
ȗ
Metaphor: All programmers should have a simple shared story that explains the
system under development.
ȗ
Simplicity: Design everything to be as simple as possible instead of preparing
for future complexity.
ȗ
Testing: Both programmers and customers are to write test cases. The system is
continuously tested.
ȗ
Refactoring: Programmers are to restructure the system continuously to
improve the code and eliminate duplication.
ȗ
Pair programming: Put programmers together in pairs, and require each pair to
write code on a single computer.
ȗ
Collective ownership: All programmers have permission to change all code as
it becomes necessary.
ȗ
Continuous integration: Whenever a task is completed, build the entire system
and test it.
ȗ
40-hour week: Don't cover up unrealistic schedules with bursts of heroic effort.
ȗ
On-site customer: An actual customer of the system is to be accessible to team
members at all times.
ȗ
Coding standards: Programmers are to follow standards that emphasize
self-documenting code.
Search WWH ::




Custom Search