How To Become An Outstanding Solution Architect

Welcome to the Architect And The Team section. I will give a quick introduction on how the section is organized before we get started.

In every software development team there's always a need to understand business problem, create technical and non-technical requirements, write the code, manage the dev team, and test- and deploy the solution. In this lecture we'll briefly summarize each role. 

The functional analyst draws up the non-technical requirements in a software development project. In this lecture we will look at this role in detail. 

The lead developer manages and coaches the development team. In this lecture we will look at this role in detail. 

The solution architect draws up the technical design specification in a software development project. In this lecture we will look at this role in detail. 

Congratulations on finishing this section. This is a recap of what we have learned.

In this hands-on assignment you are going to assess your current project team. Are all software development roles present and accounted for? Is everybody aware of his or her responsibilities? 

I did this homework assignment too, and in this lecture I'll share my results.

Claim your new learning badges here.

Review the skills you have learned in this section, and check your progress on becoming an outstanding solution architect. 

Welcome to the What Makes A Great Architect section. I will give a quick introduction on how the section is organized before we get started.

What are organizations looking for when they hire a new architect? In this lecture we're going to take a close look at a typical architect job vacancy, to discover the skills and responsibilities employers want to see in this role. 

Great architects differentiate themselves from their peers by taking on many responsibilities. In this lecture we're going to take a detailed look at those responsibilities. 

Great architects have personality traits that make them very well suited for the job. In this lecture we're going to take a detailed look at those traits. 

As an architect you are ultimately responsible for the technical success of the project. But there are many ways in which a project can go off the rails. In this lecture we're going to take a look at 4 common pitfalls for architects, and how you can resolve them. 

In this hands-on assignment you are going to evaluate your own personality, communication style, and team power print, to discover if anything is holding you back from becoming a great architect.  

I did this homework assignment too, and in this lecture I'll share my results.

Claim your new learning badges here.

Welcome to the Designing A Software Architecture section. I will give a quick introduction on how the section is organized before we get started.

We've talked a lot about the responsibilities of the solution architect, but what exactly is a solution architecture? In this lecture you'll find out. 

In this lecture we'll discuss the key principles of a great solution architecture. 

In this lecture we'll discuss some simple guidelines for creating great solution architectures. 

The Unified Modeling Language, or UML, is an indispensable tool for creating and sharing architectures. In this lecture you'll learn the basic principles of UML models, views, and diagrams.

UML has many useful diagram types for documenting architectures. In this lecture we're going to take a closer look at the 7 most popular diagram types. 

UML can be used to sketch designs, create detailed blueprints, generate new code, and reverse-engineer existing code. In this lecture we'll look at strategies for using UML in software development, and how Visual Studio can help you integrate UML designs in the development process. 

In this lecture I will show you a simple 5-step process for designing and refining solution architectures.

In this hands-on assignment I will introduce you to our case study, and you'll start working on your first baseline architecture design.

I did this homework assignment too, and in this lecture I'll share my results.

Welcome to the Architecture Design Patterns section. I will give a quick introduction on how the section is organized before we get started.

Layered architectures organize architecture elements into discrete stacked layers. In this lecture we're going to take a look at several popular layered architecture patterns.

Structural architectures describe how architecture elements are structured into discrete configurations. In this lecture we're going to take a look at several popular structural architecture patterns.

Presentation architectures are optimized for creating user interfaces. In this lecture we're going to take a look at several popular presentation architecture patterns.

Service architectures are optimized for creating API's and loosely-coupled services. In this lecture we're going to take a look at several popular service architecture patterns.

Architecture patterns can be freely embedded inside each other. In this lecture we're going to take a look at several popular hybrid architecture patterns. 

In this hands-on assignment you are going to finalize the baseline architecture design for our case study.

Welcome to the Designing Layers, Components And Services section. I will give a quick introduction on how the section is organized before we get started.

Choosing the right pattern for an area of concern can be a daunting task. In this lecture I'll show you some simple rules of thumb to quickly find the right pattern for the job.

In this lecture we'll take a deep dive into layered architectures and look at different ways to stack and organize architectural layers. 

In this lecture we're going to take a deep dive into component architectures and discuss all the different component types you can use in each architecture layer. 

In this lecture we're going to take a deep dive into service-oriented architectures and learn about the challenges of exposing a business layer with loosely-coupled services.

In this hands-on assignment you are going to apply what you have learned in this section to refine the design into a candidate architecture for our case study. 

Welcome to the Architecture Considerations section. I will give a quick introduction on how the section is organized before we get started.

In this lecture we're going to look at quality attributes that affect the design of your architecture.

In this lecture we're going to look at quality attributes that affect the runtime behaviour of your architecture.

In this lecture we're going to learn how to plan for caching commonly-used data in an architecture.

In this lecture we're going to learn how to plan for robust exception management in an architecture.

In this lecture we're going to learn how to plan for several common deployment scenarios in an architecture.

In this hands-on assignment you are going to apply what you have learned in this section to refine the design into a final candidate architecture for our case study. 

In this lecture I would like to thank you for finishing the course and offer some final words.

In this lecture we'll summarize everything you've learned, and review the skills you have learned in this course.