Book Image

Hands-On Software Architecture with Java

By : Giuseppe Bonocore
5 (1)
Book Image

Hands-On Software Architecture with Java

5 (1)
By: Giuseppe Bonocore

Overview of this book

Well-written software architecture is the core of an efficient and scalable enterprise application. Java, the most widespread technology in current enterprises, provides complete toolkits to support the implementation of a well-designed architecture. This book starts with the fundamentals of architecture and takes you through the basic components of application architecture. You'll cover the different types of software architectural patterns and application integration patterns and learn about their most widespread implementation in Java. You'll then explore cloud-native architectures and best practices for enhancing existing applications to better suit a cloud-enabled world. Later, the book highlights some cross-cutting concerns and the importance of monitoring and tracing for planning the evolution of the software, foreseeing predictable maintenance, and troubleshooting. The book concludes with an analysis of the current status of software architectures in Java programming and offers insights into transforming your architecture to reduce technical debt. By the end of this software architecture book, you'll have acquired some of the most valuable and in-demand software architect skills to progress in your career.
Table of Contents (20 chapters)
1
Section 1: Fundamentals of Software Architectures
7
Section 2: Software Architecture Patterns
14
Section 3: Architectural Context

Case studies and examples

In this section, we will model an ideal Product Backlog in the Scrum way, applied to our mobile payments example.

The official Scrum guide does not provide any example of a Product Backlog, and there are no standards as regards the fields that should be included. Based on my personal experience, a Product Backlog should look like this:

Figure 5.5 – Mobile payments Product Backlog

This is, of course, just a small subset, but several considerations can be made:

  • Items are identified by ID and DESCRIPTION: Most likely, ID will link to a detailed requirements document or at least a more detailed description. Also, every item is likely categorized as part of a bigger user STORY. As discussed previously, User Story Mapping is a different way to visualize this kind of relationship.
  • Items are categorized: Usually, at least features and fixes are categorized, while more types, such as enhancements and technical terms (for...