Summary

As you have seen, there are many steps to conduct in developing an enterprise application, and still we have not shown you all the different classes that make up our time reporting application. The burden can sometimes feel overwhelming, but as soon as the interfaces between the different layers have been decided (for example, which functions and methods each layer's class should expose), the building of the different layers and components can be done in parallel. The exposed functions and methods are a "contract" between the developers as much as between the components in the application. The UI developer can trust that the project team will provide components to retrieve a time report when the project should go live. Until then, he or she should just add dummy calls and continue on with the design.

For more information about enterprise applications and more code in this test application, visit http://www.apress.com, where you will find more help for guiding you through your enterprise application project.

This also finishes our book. We trust you have found it useful, and that it will be beneficial in your work. Remember that what we have presented here are only guidelines, and that all projects are different. This makes it hard to implement everything we have shown here in every project, but use this book as a guide to what you should think about and pick out the things that apply to your specific situation.

Remember that with a good design, you can avoid many of the problems you otherwise would run into. It is an essential part of every serious project.

Also make sure to test every aspect of the application before deployment. Far too many errors are passing through some applications that could have been found with a good test methodology.