The package structures shown in Figure 7-6 depict the dependencies between packages in the business tier. The package naming conventions used by the GreaterCause application in the business tier and the domain tier follow the following conventions:
Figure 7-6: Business Tier Package Diagram
Business Tier | Domain Tier |
---|---|
| |
com.gc.services.admin | com.gc.persistence.admin |
| |
com.gc.services.managecampaigns | com.gc.persistence.managecampaigns |
| |
com.gc.services.searchnpo |
The basic premise of this book is use of object-oriented paradigm and a use case–driven approach. As such, we now examine how we have used the different patterns discussed in the preceding sections for realizing the use cases discussed in Chapter 1. In this chapter, we develop the use cases identified by the packages Site Administration, Manage Campaigns, and Search NPO. The intent of this endeavor is to assist the readers in understanding how to implement an architecture based on the patterns we just discussed; at the same time, we create static and dynamic models for representing our problem domain.
The basic premise of this book is use of object-oriented paradigm and use case–driven approach. As such, we now examine how we have used the different patterns discussed in the preceding sections for realizing the use cases discussed in Chapter 1. In this chapter, we develop the use cases identified by the packages Site Administration, Manage Campaigns, and Search NPO. The intent of this endeavor is to assist the readers in understanding how to implement an architecture based on the patterns we just discussed, at the same time, we create static and dynamic models for representing our problem domain.