Chapter 15. Separating Platform Specifics with Platform-Specific Use-Case Slices
A system ultimately needs to execute on a target platform, so at some point in time, you must incorporate platform specifics into your design. This work is often repetitive, as platform specifics cut across many use cases. You want to be shielded from changes in the platform, since this affects many parts of the system. You want to introduce specifics as late as possible without ever doing anything twice. In this chapter, we demonstrate how this is achieved using the J2EE platform as an example. In particular, we show how processing tiers—presentation tier, business tier, and integration tier—are modeled as parameterized infrastructure use cases. These are subsequently ...
Get Aspect-Oriented Software Development with Use Cases now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
