The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
Observations from a multi-platform approach to user interface design pedagogy
Journal of Computing Sciences in Colleges
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
The 6th Joint Meeting on European software engineering conference and the ACM SIGSOFT symposium on the foundations of software engineering: companion papers
How to steer an embedded software project: tactics for selecting the software process model
Information and Software Technology
Troubleshooting large-scale new product development embedded software projects
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
| Hi-index | 0.00 |
Around 4:00 PM on 10 August 1628, the warship Vasa set sail in Stockholm harbor on its maiden voyage as the newest ship in the Royal Swedish Navy. After sailing about 1300 meters a light gust of wind caused the Vasa to capsize. The fundamental reason the Vasa sank is, of course, that the ship was unstable. The reasons that the Vasa was constructed to be unstable, and launched when known to be unstable, are numerous and varied. The problems encountered are as relevant to our modern-day attempts to build large, complex software systems as they were to the art and craft of building warships in the 17th century. This article describes the problems encountered in the Vasa project, interprets the problems encountered in terms of modern software projects, and presents some antidotes for those problems.