hello everyone my name is Abhishek and welcome back to my channel so first of all thank you so much for watching my previous video on devops that is Introduction of devops so today is day two if you haven't watched the day one video on devops I would highly recommend you to go back and watch the day one so there is a devops Zero to Hero playlist which contains day zero day one and all the other related videos and the following videos will also be posted on the same playlist okay so now what did we discuss in the previous class just to give you a quick recap for the people who have followed we just learned uh you know what is devops why devops and how do we introduce ourselves in a devops interview so this is the thing that we learned in our previous class that is day one so now today we are at day two of devops right so what are we going to learn in day two is typically the software development life cycle so now you might ask me like the you know why do we why everybody has to learn about software development life cycle so irrespective of the field that you're in whether you are a developer whether you are a tester you are into software development or devops everybody has to understand the concept of software development life cycle so the software development life cycle in short is also called as sdlc okay so people also call it as sdlc so don't confuse don't get confused if they call it as sdlc so s t l c so this is software development life cycle now what is software development lifecycle and why is it important for devops and all the other Engineers to learn this okay so now understand it in this way we have uh you know opted for a separate and complete day for learning software development life cycle that is because everybody has to understand software development life cycle if you have to work in an organization so when you work in an organization or when you work in the field of software or the IT industry there is a standard that is followed by every organization whether it's a startup whether it's a MNC or it's a unicorn everybody follows a specific standards and it is important for you to understand the standards to work in that organization now what is software development lifecycle it is a process used by the software industry whether it's a process or whether it's again a culture but it's a set of standard that is followed in the software industry to design okay develop and to test okay so to design develop and test there is a standard that is followed because whether you are working at Amazon whether you're working at Flipkart or whether you're working at Tesla so everybody has to do this three steps right one is design develop test and there are other faces also but on a high level basis these are the phases of your software development life cycle now what are these faces and what are included in each and every of these phase okay but before we go there what is the actual end goal of software development life cycle okay now I said you that there is a design phase there is a development phase and there is a testing phase but ideally what is the end goal so the end goal is to deliver a high quality product right so you might ask me uh what happens if I don't test the product so if you don't test the product end of the day you've made a design you developed a design and you delivered it to the customer but who was testing this uh product or who was testing this delivery so that's why to meet your customer expectations or you know if you want to uh deliver a prompt application to your customer you have to follow these faces like without design you cannot develop and once you develop without testing your product will not be of high quality so that's why you have to follow the standard to deliver high quality product so this is a overall high level uh explanation of software development life cycle that is software development lifecycle is a process that is followed by the industry to design develop and test high quality product okay so this is about software development life cycle but now what we'll do is we'll try to Deep dive and we'll try to see we'll take an example organization because we wanted to learn everything practically so what I do is I'll show you with an example let's say we are working at Flipkart okay or to avoid any such names what I'll do is let's say we are working at example. com so example. com can be any e-commerce website so let's say I'm working at example.
com so this can be anything this can be Flipkart this can be Amazon or anything so for just for our understanding I just named it as example. com so now at example. com we deliver a e-commerce application okay let's assume that we are building and developing a e-commerce application so again the process will be same for any organization but just for understanding and reference we are choosing example.
com so now in example. com what usually happens is there are different faces before we deliver the application to the customer okay so these faces are nothing but so you have let me try to do it in this okay so we can draw it by ourselves that's fine so we have firstly we have a face called planning okay we'll deep dive into each of these things okay don't worry then we have a face called so this is a standard thing you can refer any book or you can go through any videos so these steps are same because there are standards right these are called standards so for standards everybody has to follow the same standards so these are standards that are approved and yeah followed by every organization design and then we will move to the faces like building okay what is building we are building a software right and then we move to phase called testing and then we move to once we test what we'll do we'll deploy okay and then whenever we want a new feature again we'll follow the same approach so that's why this is a circle okay what is the reason why I took a circle here like you know I draw a circle here because everybody has to follow this circular approach for each and every feature that they are developing in their organization okay let's say this e-commerce. com okay or this example.
com what they have decided is they want to start a new feature or they want to support a new feature to the customer so let's say uh just for an example okay let's say they don't have kids section okay understand this as a e-commerce Merchant or cloth selling website and this cloth selling website were not selling clothes for kids okay till this point of time they were only selling for men women okay they don't have a kid section so what the organization has decided was on their research they found out that example. com can also get benefited from selling kids kids clothing so they have decided like you know the organization has decided to launch a kids uh kids catalog so for that what happens is they have to go through this process okay so this is the standard that is followed across the organizations right so let's try to understand each and every phase now once we understand each and every phase we'll also try to see where devops will come into this picture and how can devops improve this process right because our end goal is to understand software development life cycle and also understand this in the point of view of a devops engineer okay because you have to once you join an organization you have to improve your organization's efficiency right your end goal like on every class that we are learning only think in a point of view that whenever you are learning a new thing let's say you're learning terraform let's say you're learning ansible your point of view or your way of thinking has to be in a way that okay now I am learning terraform how can I use this terraform in the organization and how can I improve organization's efficiency that should be our end goal and you are the uh member who has to decide if your organization will require this or not let's say everybody in the everybody in the devops community is promoting terraform but it might mean that in your organization terraform but why uh is not a right fit okay so in such cases end of the rates you are called right because you are a devops engineer who is thinking of improving your organization's efficiency so it's not your manager or it's not somebody else as a devops engineer you have to suggest them that okay terraform might be a best tool in the community but for our organization it's not a right fit so think in that approach every time you work in whether in the current organization or in your future organizations always keep this approach okay so firstly what happens is there is a high level design that is decided to Launch uh kids catalog so who has decided this let's say the organization uh the CTO or somebody has thought they just given a thought that okay the kids catalog might be a good option so now what happens is once they are done with that so you know you will move to the planning phase so what happens in the planning phase is you have to gather the requirements right so as a CTO CTO can suggest you many things but who has to do the planning and requirement okay planning Place requirements so who has to do the plannings and requirements Gathering it has to be your uh I mean your core members right whether it's your business analyst or your product owner so they have to deal with the planning Place requirement stage okay so what happens in the planning plus requirement stage it's a one of the fundamental stages because it's a starting stage of your software development life cycle and your product owner or your business analyst or your senior members can also get involved you know they get the inputs from the customers so let's say example.