Difference between reuse oriented model and boehm spiral model
Answers
Answer:
Agile versus Spiral model. The Spiral Model is an example of iterative development. ... The commonality between all of the agile methods is that they are iterative and incremental. The iterations in the agile methods are typically shorter - 2 to 4 weeks in most cases, and each iteration ends with a working software product ...
Explanation:
Spiral Model is a combination of a waterfall model and iterative model. Each phase in spiral model begins with a design goal and ends with the client reviewing the progress. The spiral model was first mentioned by Barry Boehm in his 1986 paper.
The development team in Spiral-SDLC model starts with a small set of requirement and goes through each development phase for those set of requirements. The software engineering team adds functionality for the additional requirement in every-increasing spirals until the application is ready for the production phase.

Spiral Model Phases
Spiral Model PhasesActivities performed during phasePlanningIt includes estimating the cost, schedule and resources for the iteration. It also involves understanding the system requirements for continuous communication between the system analyst and the customerRisk AnalysisIdentification of potential risk is done while risk mitigation strategy is planned and finalizedEngineeringIt includes testing, coding and deploying software at the customer siteEvaluationEvaluation of software by the customer. Also, includes identifying and monitoring risks such as schedule slippage and cost overrun
When to use Spiral Methodology?
When project is largeWhen releases are required to be frequentWhen creation of a prototype is applicableWhen risk and costs evaluation is importantFor medium to high-risk projectsWhen requirements are unclear and complexWhen changes may require at any timeWhen long term project commitment is not feasible due to changes in economic priorities
Advantages and Disadvantages of Spiral Model
Advantages
Disadvantages
Additional functionality or changes can be done at a later stageRisk of not meeting the schedule or budgetCost estimation becomes easy as the prototype building is done in small fragmentsIt works best for large projects only also demands risk assessment expertiseContinuous or repeated development helps in risk managementFor its smooth operation spiral model protocol needs to be followed strictlyDevelopment is fast and features are added in a systematic wayDocumentation is more as it has intermediate phasesThere is always a space for customer feedbackIt is not advisable for smaller project, it might cost them a lot