Conclusion


In roughly 32 diagrams in Chapters 26 and 27, we have documented the design and implementation of the payroll application. The design uses a large amount of abstraction and polymorphism. The result is that large portions of the design are closed against changes of payroll policy. For example, the application could be changed to deal with employees who were paid quarterly, based on a normal salary and a bonus schedule. This change would require addition to the design, but little of the existing design and code would change.

During this design process, we rarely considered whether we were performing analysis, design, or implementation. Instead, we concentrated on issues of clarity and dependency management. We tried to find the underlying abstractions wherever possible. The result is that we have a good design for a payroll application, and we have a core of classes that are germane to the problem domain as a whole.




Agile Principles, Patterns, and Practices in C#
Agile Principles, Patterns, and Practices in C#
ISBN: 0131857258
EAN: 2147483647
Year: 2006
Pages: 272

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net