Call for Papers

The V-Model is Dead. Long Live the V-Model! ( Vortrag )

Dr. Royce Recommends an Iterative and Incremental Approach

Referent: Colin Hood, Colin Hood Systems Engineering
Vortragsreihe: Software Engineering Management
Zeit: 01.12.16 09:45-10:25

Zielgruppe

Entwicklung

Themenbereiche

Anforderungen definieren und verfolgen, Analyse & Design, Test & Qualitätssicherung, Software Engineering Management

Schwerpunkt

Prozess

Voraussetzungen

Keine

Kurzfassung

A V-model documents relationships between information, and does not restrict the sequence of creation of artefacts. People who thought that a V-model is not useful or necessary are often dissatisfied with restrictions that they themselves have added to a V-model, rather than the original intention and essence of a V-model. Some people think of a waterfall model when a V-model is mentioned. And it seems that most people have not read the original article, from which the waterfall model was extracted, from Dr. Winston W. Royce which warns against the simplistic one way step-by-step development with no iterations. Dr. Royce in his article MANAGING THE DEVELOPMENT OF LARGE SOFTWARE SYSTEMS highly recommends an iterative and incremental approach. A V-model represents graphically; ownership of and relationships between information. A V-model is a static model and does not restrict sequence of creation of artefacts. The V-model is state-of-the-art.

Gliederung

- Aim
- Introduction
- A Simple Information Model
- Considering each level
- Development of requirements across the levels of the information model.
- Saving time and effort by maximising the work not done
- Increasing quality by maximising the work not done
- Conclusion

Nutzen und Besonderheiten

Massive savings have been made in real development projects by using the V-Model for iterative and incremental development.

Über den Referenten

Colin Hood (info@colinhood-se.com) hat seit 1977 die Evolution der Steuerungssysteme von relaisgestützten Systemen über programmierbare logische Controller (PLCs) bis hin zu modernen softwaregesteuerten Safety Critical Systemen begleitet. Seine Spezialität ist neben der Verbesserung der Prozesse die Unterstützung des Veränderungsprozesses bei der Einführung neuer Methoden und Werkzeuge.