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

Chapter 15. Modeling the Application

The previous chapter laid down some of the foundations for the case study. It also discussed the overall conceptual architecture and high-level components. This chapter examines application-specific processing and the responsibilities of each component. The storyboards and the use cases in Chapter 13 provided the low-resolution page layouts and the overall flow. This chapter uses this information, especially the use-case steps, the requirements, and the logical component model, to essentially connect the dots. The previous chapter also highlighted some conceptual processing patterns for web pages, web services, and the manager components.

This chapter focuses on the underlying processing and orchestration. However, in doing so, I'll highlight areas that need to be considered higher up in the processing stack and, of course, lower down. The objective is to solidify some of the methods, inputs, outputs, transaction boundaries, and any other items that will provide additional placeholders for further design and discussion. As you progress through the processing, you'll see how the processing components interact with the provider components, which will help to flesh out some of their methods, too. Conversely, the methods on the processors will provide the methods for the managers and the web services. You know that the TransactionContext entity class will be initially populated by the web pages and passed down through the components to the processors, ...