Waterfall Method
When we develop software, there are several ways in which that development process should take place. Here mainly methods like waterfall model, Spiral Model, Agile methodology are used. Here in this article, we present details about the waterfall model.
Let us first discuss what the waterfall method is. In the waterfall model, we do software development as a step-by-step process. This is called the waterfall method. This development process is done as shown below. That means you go to the next step after completing one step. This development process is done step by step like water flowing down a waterfall.
Advantages
Because we do this development process step by step, it is very easy to make a change in the previous step if something goes wrong in one step.
For example, if we come across an issue in the design step, we can easily identify the places in the SRS document that need to be changed in the Requirement analysis and change them.
If we talk about the most suitable software for the Waterfall model, the Waterfall model is best suited for small-level software. We can use this waterfall method to create software that does not change requirements frequently or has a small number of functions.
Disadvantage
Here we have to finish things in one step and move on to the next step so it will take a lot of time for these steps. let’s assume, If it takes us two months to complete only one step, we will only develop that special development step over those two months, so it will take a lot of time for the other steps as well as the special time to match them. Also, if you find any mistake or error in the steps like in the testing step, you will have to change the previous step again. But even then, a lot of time has passed for this software. This can be described as a huge disadvantage.
Another big disadvantage here is that we get to see a working product in the last few steps. So, because of this, we are not able to show the customer how a working product or software is made. Also, if the customer says that he wants to make a change here in some way, it will take a very long time to change it again from the beginning. He will also have to wait until the final steps to see if he has made the change he needs.
Feasibility Study
This is basically discussed under four headings. They are as follows.
Economic feasibility study
Technical feasibility study
Operational feasibility study
Organizational feasibility study
Economic feasibility study
There are three main types of expenses: definite expenses, indefinite expenses, and beneficial levels.
Definite expenses
Here we will consider the hardware and software expenses required to implement this software.
Indefinite expense
Here are the additional costs involved in this software development process.
Beneficial level
Here we will look at how many benefits the software develops.
Technological Feasibility Study
What is being considered here is the latest technology to be used for the software being developed or what is the most suitable technology.
Here we will look at what technology stacks are, what language is created, what are the latest frameworks, and technology related to the database used for this.
Operational feasibility study
Consideration is given to the operation of this development process. Here we discuss how many staff members are allocated to carry out this development process, how much workload is loaded on the system and how many man-hours are spent on it.
Organizational feasibility study
Here, staff members will be consulted about this software. We also consider how to maintain the software that is created in an organization. Here the computer literacy of the staff of that organization is also considered. If computer literacy is low, this software should be designed to be easy for them to use.
