Software Development Model

In the last topic we learned about Software Testing Life Cycle and in this topic, we will study about Software Development Model. What is a Software Development Model and why is it used? As per the project a development model is selected. The impact of the selected model is very high. Why is it high? Because whichever technique that we are going to use in the development, that same technique we will use in product development. And by using that technique, whatever product would come along. That will be our final product. Here we will take an example, like there is a Manufacturing unit. Suppose that there is an Automobile unit, we have to produce a car. Every car will have a different development model. Tata is there, so the Tata Nano’s development model will be different. There is Tata Indica, Indica’s development model will be different. So, as per that whichever is your project, your development model will be as per that. And the development model will have a big impact on the output of the product. Now we will see the six phases of the life cycle, which are those? What we will do in First is, we will take the requirements. Whichever project or product that we are developing, we will take the requirement for that. What are the requirements and what all outputs are required for a particular product? And then we will do the analysis of it, as to how we will implement those requirements. After that we will make a design, how will that particular model look. If it is a website, where will the buttons come? Will it be on the left, or right? After that its implementation will be there. Which means what will be there in it. Coding will start. Like the 1^st page of the website will be ready, 2^nd page, 3^rd page. How many pages are there? Whichever database they are using, all those things will be implemented and the coding will start. As soon as it gets implemented, we will test it, which is the particular functionality, is it going as per the requirement or not. It should be not like that the requirement is given but they have not implemented the functionality. Right? So, we will get a lot of bugs and issues at the time of testing. Alright. After that what is there, Deployment. That means we will deploy that particular software on the client side. Now the software is ready for use. Now the client can use the software. We have developed a product as per the client’s requirement. Maintenance, somewhere going ahead a functionality is added. Somewhere Windows or OS is getting upgraded. So, we will have to upgrade the software or the product. All these things come in maintenance. What is the Software Development Life Cycle? We will see that. In that whatever software Life cycle models are described, as per that all the phases should be executed. Every phase’s output is the input for the second phase. Like if you write for the requirement, what will be its output, it will be that the requirements are done. Similarly, what will be the analysis phase? Requirements are done. So, we are now analyzing it. The requirement will be translated into design. We will do the coding of the design. From the coding development will happen. After the development we will do the testing, whether the requirements are given in that way the product is made or not? Has it been developed that way or not? In the next topic we will see about the Waterfall Model.