What is a spiral model?
The
spiral model is the philosophy of software design that is instead of being a linear process, a four -speed process that is constantly repeated until the software is completed. In the first step of the spiral model, developers discuss goals. Then developers will find methods to complete goals in the fastest and safest way. When developers know what they are doing, they do real programming to insert features into the software. After completing this process, the customer shows software for accepting or rejecting changes. At this point, developers are discussing features that need to be added to the software. For example, if the program is created for group cooperation, developers can discuss the need for a group interface that makes it easier for many people to use the program at the same time. Developers only discuss festiures that are needed without discussing how to create them.
When developers know what functions are needed, they begin to discuss ways of completing them. At this stageEven a spiral model will discuss various programming practices and methods to complete the task. Although there may be many ways to add functions, developers often choose the one that is the fastest and processed. Security may also be a problem because developers do not want the program to collapse during use.
After selecting the method, the developers will start programming functions. This programming will go according to the method selected in the second phase and will not change unless there are major problems. Unlike the other two parts of the spiral model, there is a very small discussion.
With the features discussed, the customer will contact the software in its current state. The software will rarely be complete at this point, and this step is more of a program to be tested rather than a claim that it is done. If the software is not created for a particular client, you may be youInvited by potential customers to try the program. Regardless of whether the customer receives or denies functions, the spiral model returns to the first step - planning - where new features are discussed or rejected and functions are fixed. This will continue gradually until the software is ready for distribution or completed to the client's specifications.