Abstract
In this chapter, a design for the ICDE case study described in Chap. 2 is given. First, a little more technical background to the project is given, so that the design details are more easily digested. Then the design description is presented, and is structured using the architecture documentation template introduced in the previous chapter. The only section that won’t be included in the document is the first, the “Project Context”, as this is basically described in Chap. 2. So, without further ado, let’s dive into the design documentation.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
The ICDE data store keeps copies of all accessed web pages so that even dynamically changing web pages (e.g., http://www.bbc.co.uk) can be viewed as they appeared at the time of access.
- 2.
Flexible in terms of easy to evolve, extend and enhance, and not including mechanisms that preclude easily adopting a different architectural strategy.
- 3.
Flexible in terms of the range of sophisticated features offered in the API for retrieving GB data.
- 4.
http://java.sun.com/developer/technicalArticles/JEE/JEEpatterns/
- 5.
The “page size” value can be tuned for each type of event to attempt to maximize server and network performance. A typical value is 1,000.
- 6.
There’s a performance trade-off here. As the JMS publish operation is outside the transaction boundary, there can be failures that result in data being inserted into the data store, but with no associated JMS message being sent. In the ICDE context, this is undesirable, but will not cause serious problems for client applications. Given the likely frequency of such failures happening (i.e., not very often), this is a trade-off that is sensible for this application.
- 7.
Capacity planning involves figuring out how much hardware and software is needed to support a specific ICDE installation, based on the number of concurrent users, network speeds and available hardware.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2011 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Gorton, I. (2011). Case Study Design. In: Essential Software Architecture. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-19176-3_9
Download citation
DOI: https://doi.org/10.1007/978-3-642-19176-3_9
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-19175-6
Online ISBN: 978-3-642-19176-3
eBook Packages: Computer ScienceComputer Science (R0)