Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By : Gabriel Baptista, Francesco Abbruzzese
Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By: Gabriel Baptista, Francesco Abbruzzese

Overview of this book

Software architecture is the practice of implementing structures and systems that streamline the software development process and improve the quality of an app. This fully revised and expanded second edition, featuring the latest features of .NET 5 and C# 9, enables you to acquire the key skills, knowledge, and best practices required to become an effective software architect. This second edition features additional explanation of the principles of Software architecture, including new chapters on Azure Service Fabric, Kubernetes, and Blazor. It also includes more discussion on security, microservices, and DevOps, including GitHub deployments for the software development cycle. You will begin by understanding how to transform user requirements into architectural needs and exploring the differences between functional and non-functional requirements. Next, you will explore how to carefully choose a cloud solution for your infrastructure, along with the factors that will help you manage your app in a cloud-based environment. Finally, you will discover software design patterns and various software approaches that will allow you to solve common problems faced during development. By the end of this book, you will be able to build and deliver highly scalable enterprise-ready apps that meet your organization’s business requirements.
Table of Contents (26 chapters)
24
Another Book You May Enjoy
25
Index

Use case – presenting use cases in Azure DevOps

This section clarifies the concepts outlined in the previous section with the practical example of WWTravelClub. Considering the scenario described in Chapter 1, Understanding the Importance of Software Architecture, we decided to define three Epic work items, as follows:

Figure 3.23: User case Epics

The creation of these work items is quite simple:

  1. Inside each work item, we link the different types of work items, as you can see in Figure 3.24.
  2. It is really important to know that the connections between work items are really useful during software development. Hence, as a software architect, you have to provide this knowledge to your team and, more than that, you have to incentivize them to make these connections:

    Figure 3.24: Defining a link

  3. As soon as you create a Feature work item, you will be able to connect it to several Product Backlog work items that detail its specifications...