Friday 15 March 2013

M1 discuss the most appropriate uses of different development life-cycle models


Waterfall and spiral lifecycles
Spiral
It is used in big development projects and in the stages there are arranged in the shape of a spiral, it is used when somebody wants to use a new technology
The spiral is also another software development process, it combines pieces of the waterfall model with the features of prototyping this model was developed to be used for large and complicated projects which will be expensive
The process of development will normally be closely tied to the waterfall model, both models having similar stages
What kind of projects are they suitable for?
Projects which are large and will cost a lot of money and are very complicated the spiral model looks to be suited to the larger and more important tasks and is not suited for small projects.
Waterfall
This lifecycle uses a sequential method of stages and they have a clear goal for each development stage when using this you cannot go back to the previous stage although this waterfall model is very easy to use.
The waterfall method is used for software development and contains several stages, requirements specification, design, construction/implementation, integration, testing and debugging, installation, maintenance
The waterfall model should move to a phase only when it’s previous stage is completed and perfected
What kind of projects are they suitable for?
They are suitable to projects that have low risk in the areas of user interface and the performance requirements, but have a high risk in budget and schedule predictability and control


No comments:

Post a Comment