Ch2-Software Engineering 9


Published on

  • Slides 41 and 42 could not be converted and therefore were not displayed. I have a question about the spiral model because no where prior to the section on coping with change was the spiral model even hinted to . In the first part of the lecture it indicates waterfall, incremental and reuse. Spiral contains aspects of each of the previously noted processes if we talk about waterfall we could take the spiral and put it in one serial process and it would look like a very detailed waterfall process if we accept that the problem in water fall is not the activities that are performed, but the fact that the activity most be completed fully prior to moving on to the next activity which is what is indicated in the spiral model. If we look at the incremental model, the spiral model contains aspects of the incremental model in the fact that we deliver a prototype as we learn more about the system and get feedback from the relevant stakeholders. Finally, looking at the re-use model, the incremental model does have a form of re-use because the previous prototype is used to refine our understand and in some cases could be used in production because of the risk analysis conducted in the spiral model. I think the spiral model points out one if the key activities that the other processes do not is that we need to assess the previous work prior to continuing the project. If this means using refactoring as in an agile or more prototyping as spiral indicates. It should also be noted that spiral does not mean only three loops are required to grow up the system. It is only an example the intent of spiral is to show that software and systems grow up as we learn the system under design and how a stakeholder will use this system for its' intended purpose.
    Are you sure you want to  Yes  No
    Your message goes here