Book Image

Solution Architecture with .NET

By : Jamil Hallal
Book Image

Solution Architecture with .NET

By: Jamil Hallal

Overview of this book

Understanding solution architecture is a must to build and integrate robust systems to meet your client’s needs. This makes it crucial for a professional .NET software engineer to learn the key skills of a .NET solution architect to create a unique digital journey and build solutions for a wide range of industries, from strategy and design to implementation. With this handbook, developers working with the .NET technology will be able to put their knowledge to work. The book takes a hands-on approach to help you become an effective solution architect. You’ll start by learning the principles of the software development life cycle (SDLC), the roles and responsibilities of a .NET solution architect, and what makes a great .NET solution architect. As you make progress through the chapters, you’ll understand the principles of solution architecture and how to design a solution, and explore designing layers and microservices. You'll complete your learning journey by uncovering modern design patterns and techniques for designing and building digital solutions. By the end of this book, you'll have learned how to architect your modern web solutions with ASP.NET Core and Microsoft Azure and be ready to automate your development life cycle with Azure DevOps.
Table of Contents (15 chapters)
Section 1: Understanding the Responsibilities of a Solution Architect
Section 2: Designing a Solution Architecture
Section 3: Architecting Modern Web Solutions with DevOps Solutions

Designing architecture with UML

So far, we have learned that a UML diagram is a single simplified representation of the software. We will need to build various UML diagrams in order to understand the complete aspects of the system and to communicate our architecture design to stakeholders and different types of users. Grouping these UML diagrams into logical subsets will create a particular view of the system. The architecture design is represented in a collection of five views. These views are as follows:

  • Use case view: The use case view represents the focal point for all of the other views because it includes the user requirements, including all of the system functionalities. Without this view, you cannot build the other views.
  • Design view: The design view is intended to illustrate how the functionality defined in the use case view is designed inside the system in terms of classes and their relationships. This view is mainly described by the UML class diagram.
  • Implementation...