Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development

15.2. Modeling the Batch Jobs

This section covers the batch components identified in the requirements and the previous chapters. The conceptual design is still very much a hybrid between a functional design and a technical design document; it is certainly not as detailed as a full technical design document would be. However, as you progress through the patterns and practices, you'll build on what you have so far and uncover more of the framework components and how best to implement them to meet the quality characteristics. What you have so far would not be "client-ready," but it is good enough for further design and planning meetings. You are looking to get a complete view of the application and its functionality so that you can really start to apply the patterns and practices and concentrate on the key areas. The diagrams and flows help to walk through the conceptual solution. The requirements specified in Chapter 13 identified a number of batch jobs, and this chapter provides an overall view of the functionality and requirements. The following subsections go through the solicited e-mail batch jobs and the account clean-up jobs.

15.2.1. The Solicited E-mail Batch Jobs

This group of batch processes will concentrate on sending out solicited e-mails to the customer. With all data processing involved in batch processes, I generally find the best way to start is to model some of the underlying data. The solicited e-mail group is centered on the EmailQueue table, which is also related ...