Sei sulla pagina 1di 2

Question B 1. Describe the difference between Spiral model and Waterfall model.

Describe the ways in which they are related. Spiral model Spiral model is best suited for projects associated with risks. In Waterfall model each step is distinct. After completion of step one can move to next step and once you are through from one step you cant move back. Hence waterfall model is useful only those projects where requirements are well understood and no change in requirements is needed. Waterfall model The waterfall is a linear & sequential design process, that goes to the next step one after another after complete the previous step. It seen as flowing downwards like waterfall. Through the phases of conception, initiation, analysis, design, construction, testing, production/implementation & maintenance. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back. It allows for departmentalization and managerial control. A schedule can with deadlines for each stage of development and a product can proceed through the development process

In spiral model we dont define everything in detail at very beginning. we start with basic functionality and work them out. we take client's feedback.If developed functionalities is as per clients requirement then we move on to next step. Spiral model is useful when requirements The disadvantages is not allow much reflection are changing. or revision. It is difficult to go back and change something that not well thought out in concept stage. Its Difficult to estimate time and cost for each phase of the development process. No flexibility to consideration any change in SRS will result to start work for first step and goes step by step again.

2. Explain how the Spiral model mitigates the inherent disadvantages of the waterfall model

The spiral lifecycle model allows for elements of the product to be added in when they become available or known. This assures that there is no conflict with previous requirements and design. This method is consistent with approaches that have multiple software builds and releases and allows for making an orderly transition to a maintenance activity. Another positive aspect is that the spiral model forces early user involvement in the system development effort. For projects with heavy user interfacing, such as user application programs or instrument interface applications, such involvement is helpful

3. You are developing an online video game application for children under 12 years old. List the potential stakeholders that will involve in the development

Customer Client Users Developer Data analyst