Steps involved in selling process in IT architecture documentation

How to create outlook signature

so we've been learning about various aspects of solution architecture together and I think it's time we uncover yet another aspect of the job the solution architecture documents commonly called sand so I built this series of videos so explore what the solution architecture document is what it's its purpose how it is structured and how to build a complete set that addresses the needs of all involved stakeholders and communicates Your solution in the most precise Manner and we'll use a real example to build together a real sad that I would use in real life my name is Elias I'm a Senior Solutions architect now let's do this first things first why go through the efforts of creating Assad well building anything really is basically making a series of decisions some of the earliest decisions come from designing the architecture and you know these carry a high degree of importance because they affect the decisions that come afterwards think of it this way once an airplane is Airborne it's impossible to change the wing design or to change the way the seats are around well maybe the seats are easy to change um but usually it's just too late to review it and yet that's what software Engineers tend to do when we skip the process of Architects and our solution and we jump directly to the implementation thinking yeah you know what we'll just address this thing down the line we'll just cross that bridge when we'll get to it well I'm I'm sure you can relate to a time when teens started working on implementation without understanding the overall architecture so what happens usually is that when the business comes up with chance requests or when a bug is uncovered well you know we have no choice other than hacking our system ingly we copy paste from one component to another the software ends up becoming more and more complicated and two three years down the line well the system is just inoperable It's the final so what we do we call it Legacy we're playing the previous developers and we tell ourselves that by migrating to this new framework or using this new technology that just came out we will fix it all only to repeat the same thing again and again and weirdly enough companies will have time and budget to rewrite their software and migrate it to a new framework but weirdly enough they don't have time and budget to architect it right the first time doesn't make sense to me so I really just want you to remember that building something that works is easy if your manager or director is up your app giving you giving you an unrealistic ETA you know just remind them that of course you can all you got to do is clone laravel by connected to my SQL DB and starts implementing the business logic and sometimes that's all you have to do but building a solution that scales you know building a solution that is resilient that is secure that it follows compliance that can serve customers you know all around the globe with the same level of performance well that's a little bit harder my friends because now you are thinking of replication and encryption and and caching and latency and cost you know and you need to build a proper CI CD pipeline but you know what's even harder than that in our domain the hardest thing ever is building a system you can maintain for years to come you can maintain for decades why not you know a system that can evolve with customer needs with business realities it can it can survive Market shifts and Technology improvements you know a system that won't crumble if your company decide to change their payment processor or integrate a machine learning pipeline in the future now we'll get to the how in the second episode of the series and by all means if you're in a rush here's the link but I strongly believe we should start with the why first software architecture is about being analytical you know after all and we want to adopt the think twice cut once approach they are always says measure twice cut once my daddy always said Cleveland Jr quit jumping on the bed we didn't measure measure and a proper phone ctor is a major Cornerstone and it it yields a number of benefits let's explore some of them as you've already seen in this video you can't come up with an architecture at your desk you just can't you'll have to be working closely with stakeholders such as business analysts such as products owners marketers developers and of course end users they are stakeholders as well and so you have to be working with these uh people to make sure that all requirements are identified they are understood as well and I'm talking about functional non-functional Technical and operational requirements and we'll see examples of those in a bit second you want to start thinking about quality attributes as early as possible in the software development process you know it is it is it is super difficult and super costly to make changes to fulfill them later just remember the airplane example so if we fail to predict if a software system will fulfill quality attributes until it is implemented at tested then costly and time consuming rework may be necessary down the line there's also the fact that it uses communication among stakeholders you know putting the architecture on paper allow you to communicate and explain it to others some stakeholders maybe they are more interested in cost and duration that's it others might be interested in the security of the system and maybe a different group would be only interested in whether the system could maintain the high flow of customers during the the upcoming sell season Black Friday p [Music] your architecture document shall be abstract enough that many stakeholders with little or no guidance should be able to comprehend how the system affects their needs and really the best way I believe to capture all stakeholders is inputs as a Solutions architect is by putting yourself in their situation and looking at problems from their perspectives now there are other goals of this ad but you must be eager to get to the how so let's start talking about how to build a solid solution architecture document starting with its various components and that's all in the next video so click here to watch it