
Parameter
Kategorien
Mehr zum Buch
In his famous paper ”No Silver Bullet“ from 1986, Frederick P. Brooks uses the legend of werewolves to point to the complexity of software projects. Interdependencies between requirements engineering and organisational conditions contribute to this complexity especially in distributed projects. This complexity is the very nature of software development projects — thus, it is futile to run for a silver bullet to lay the werewolves to rest. Instead, the question is how we can deal with the werewolves. The answer in the world of Harry Potter is to accept werewolves and to know the human-werewolf-cycle; similarily, in the world of software development it is necessary to accept and understand the given complexity of software projects – so action can be taken at critical points of time. [.]
Buchkauf
A model of distributed requirements engineering, Dorina Gumm
- Sprache
- Erscheinungsdatum
- 2009
- product-detail.submit-box.info.binding
- (Paperback)
Lieferung
Zahlungsmethoden
Feedback senden
- Titel
- A model of distributed requirements engineering
- Sprache
- Englisch
- Autor*innen
- Dorina Gumm
- Verlag
- Sierke
- Erscheinungsdatum
- 2009
- Einband
- Paperback
- ISBN10
- 3868441700
- ISBN13
- 9783868441703
- Kategorie
- Informatik & Programmierung
- Beschreibung
- In his famous paper ”No Silver Bullet“ from 1986, Frederick P. Brooks uses the legend of werewolves to point to the complexity of software projects. Interdependencies between requirements engineering and organisational conditions contribute to this complexity especially in distributed projects. This complexity is the very nature of software development projects — thus, it is futile to run for a silver bullet to lay the werewolves to rest. Instead, the question is how we can deal with the werewolves. The answer in the world of Harry Potter is to accept werewolves and to know the human-werewolf-cycle; similarily, in the world of software development it is necessary to accept and understand the given complexity of software projects – so action can be taken at critical points of time. [.]