By Topic

Why the Vasa sank: 10 problems and some antidotes for software projects

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Fairley, R.E. ; Sch. of Sci. & Eng., Oregon Health & Sci. Univ., Beaverton, OR, USA ; Willshire, M.J.

In 1628, the newest ship in the Royal Swedish Navy took its maiden voyage. After sailing about 1,300 meters, a light gust of wind caused the Vasa to capsize. The reasons that the Vasa was constructed to be unstable, and the reasons it was launched when known to be unstable, are as relevant to our modern-day attempts to build large, complex software systems as they were to the 17th-century art and craft of building warships. This article describes the problems encountered in that project, interprets them in terms of modern software projects, and presents some antidotes for those problems.

Published in:

Software, IEEE  (Volume:20 ,  Issue: 2 )