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

Learning about user story mapping

User story mapping is a way to put user stories into context, identify what it takes to implement them, and plan accordingly.

In this section, we will learn what a user story is and how it can be used as a planning method, in order to choose what features to include in each release, following a meaningful pace.

The user story is the same concept that we saw as part of BDD. So, it describes a feature from the point of view of a specific persona (As a...), the functionalities required (I want to...), and the expected outcome (So that...).

As you might observe, all pieces in the puzzle of those seemingly unrelated practices eventually start to match. User story mapping is often described as a product backlog on steroids.

We will discuss product backlogs in the next chapter. However, for now, consider them as lists of features to implement. Features are added as long as analysis occurs (or new requirements arise). These are then prioritized...