Summary


In this chapter, we completed another architectural refactoring. We extracted the application operations into a separate package; we did not need this package until we came to the point of writing the second client for our application. The need to share the code between the clients was the major driving force behind this refactoring.

As is often the case with software development, the system s original design does not stay unchanged because the requirements evolve and the system s structure must follow the same evolution process.




Test-Driven Development in Microsoft .NET
Test-Driven Development in Microsoft .NET (Microsoft Professional)
ISBN: 0735619484
EAN: 2147483647
Year: 2004
Pages: 85

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