19.5 Summary and Conclusions
In this chapter we have examined some of the design patterns and structures used within a larger J2EE technology application (the Fault Tracker). What has been presented here is only part of this application, and indeed the full application has many more elements to it (including integrated email, messaging etc.). However, it should illustrate both the size and complexity of such applications. It should also illustrate how these issues can be controlled by the judicious use of well-established, as well as domain-specific, design patterns.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2003 Springer-Verlag London Limited
About this chapter
Cite this chapter
(2003). The Fault Tracker J2EE Case Study. In: Guide to the Unified Process featuring UML, Java and Design Patterns. Springer Professional Computing. Springer, London. https://doi.org/10.1007/1-85233-856-3_19
Download citation
DOI: https://doi.org/10.1007/1-85233-856-3_19
Publisher Name: Springer, London
Print ISBN: 978-1-85233-721-6
Online ISBN: 978-1-85233-856-5
eBook Packages: Springer Book Archive