Compare the System Development Life Cycle with the spiral model indicating where they are best used, there advantages and disadvantages. Provide labelled diagrams detailing each model
Student Name: Vishram S. Churai
Student I.D.: 111000268
What is Methodology?
A methodology is defined as something that represents a package comprising practical ideas and proven practices for a given area of activity. Methodology includes the planning, the development of the design and the management of the systems which are based on information technology.
The Software Life Cycle.
In software engineering, the software life cycle is a frequently used manner of organizing the software development ...view middle of the document...
You can modify this plan to your needs, as the aim is to give you a starting point from which you can properly consider the work ahead. All modern software development models, including RAD and XP, have their roots in this approach.
This is literally just the idea, the first inspiration, the vision
This is the stage where the idea begins to be explored. What is involved? What will it need to make it happen? How long will it take? Often an idea will be reconsidered, or at least tempered at this stage.
From your analysis, you begin to design. The design should of course be based on the analysis, and for the project to have any hope at all the design must keep in mind the constraints that the analysis has put in place.
This is where the project starts to be built. There is obviously a level of commitment at this stage, and the previous work is relied on. There is still the facility to move back up the waterfall if required, even as far back as rescoping the idea if necessary.
Here is where the evaluating of the attributes or capabilities of the program or system and determining if it meets its required results.
The implementation phase takes the requirements and design phase products and implements them using appropriate technologies.
You need to keep up with the project. In part this does mean that you should watch for bugs and other errors that are reported to you, and fix them. Yes, even your extensive testing regime may well have missed the odd issue here and there!
* Simple and easy to use.
* Easy to manage due to the rigidity of the model â€“ each phase has specific deliverables and a review process.
* Phases are processed and completed one at a time.
* Works well for smaller projects where requirements are very well understood.
* Adjusting scope during the life cycle can kill a project
* No working software is produced until late during the life cycle.
* High amounts of risk and uncertainty.
* Poor model for complex and object-oriented projects.
* Poor model for long and ongoing projects.
* Poor model where requirements are at a moderate to high risk of changing...