JIRA Waterfall Model
Before comprehension the coordinated and JIRA, you should know about the cascade model.
What is a Waterfall model?
Cascade model is the most established model utilized by an IT industry to build up the product.
There are different models and procedures which are utilized by various organizations, yet the cascade model is the most seasoned, most secure, and simple model in the IT business.
It is the most effortless model for building programming that speaks to reality.
How about we comprehend the Waterfall model.
Cascade model is separated into different stages:
Requirements
Consider in the event that there is a customer and he needs to create programming, at that point the customer connects with the organization. Assume he connects with the administration based organization and requests that the organization assemble the product for me.
What does the organization do?
Organization will gather all the necessities, the information that the client has or the customer need to have on his product, the organization will gather all the data from the customer and set up the documentation. When this movement is performed, at that point the plan stage begins.
Design
In this stage, we set up the significant level and low-level structures. Prior to building up the product, the plan of the product is required. Assume the client needs web based business site like the Amazon, at that point UI(User Interface) of the site will be made by the originator and dataflows are likewise structured in this stage how information will stream. When this stage is finished, the advancement stage will begin.
Development
In the Development stage, the product improvement group begins coding and building up the product. This is the longest period of the cascade model as engineers need more opportunity to assemble the product. When the advancement of the product is finished, at that point the task is given over to the analyzers.
Testing
The testing group will test the product, and on the off chance that any bug is discovered, at that point they illuminate the designers about the issue they found and ensure that the bug is fixed. They guarantee that the start to finish programming is finished.
Deployment
When the undertaking is tried, the task is sent with the goal that it turns out to be live to the ongoing clients.
Maintenance
At long last, the undertaking is sent and accessible to the customers. Customers need the support time frame for a couple of years provided that any bug is found or need a marginally improved element in the venture, so they need some group to deal with such stuff. Because of this explanation, they go for the support time frame.
Example of Waterfall model
Assume the customer needs an application like a WhatsApp, so he reaches to the organization where both the organization and the customer had a conversation for 2 months. The organization made the documentation of the considerable number of necessities in 2 months. Presently, the advancement group begins building up the product and assume it took around 10 months to build up the product. It implies that a year have been utilized, i.e., 2 months in necessity stage and 10 months in an improvement stage, yet at the same time the customer doesn't have the thought regarding the inward stages. When the improvement is finished, trying is done, and it will take around 2 months for programming quality testing. When the testing is done, it goes to the incorporation and dispatch so that WhatsApp will turn out to be live. Nonetheless, when it compasses to the customer, at that point the customer says that it has taken over a year and the product that I got was not what I anticipated. This happened on the grounds that the customer had just verbal correspondence with the product group. In the event that the customer needs a few changes in the product, at that point the entire procedure will be executed once more.
Advantages of the Waterfall model
- Basic and straightforward and use
- It speaks to all the assignments that you need to do, all things considered. For instance, you need the prerequisites of a customer. It contains various stages, and each stage is begun just when the past stages get finished.
- Explicit deliverable and survey process
- Each stage has a particular deliverable and survey process. After the necessity stage, we have all the prerequisites of what the client needs. When the product is created, we have its deliverable.
- Stages don't cover
- In this model, stages don't cover, i.e., they are finished once at once. When the past stage is finished, at that point just the following stage begins. For instance, the Development stage will begin just when the plan stage is finished.
Disadvantages of the Waterfall model
- Time to advertise is high
- Item is discharged just when all the stages are finished. In this manner, this model sets aside a long effort to discharge the item.
- Surprising outcomes
- What you expect and you get are for the most part extraordinary as the client has a thought according to the records just about the item. The customer has just a thought, which is an archived thought.
- Not appropriate for changing necessities
- This model isn't reasonable for the tasks where necessities are at a moderate to high danger of evolving. In the event that the necessities are changing, at that point this model isn't suggested as all the prerequisites are done at the necessity stage, which is a very time taking procedure.
