Learning from Failure, Part 1: Scoping and Requirements Woes

  • Authors:
  • Frank Buschmann

  • Affiliations:
  • Siemens Corporate Technology

  • Venue:
  • IEEE Software
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

Time and again, software projects fail. Some of the reasons for failure relate to software architecture. In this edition of the column I'll discuss two mistakes that aren't the prime responsibility of architects, but architects are directly affected if they occur: missing, wrong, or creeping system scope; and vague, unnecessary, or extreme nonfunctional requirements. Not addressing these mistakes can lead software projects to trouble before concrete architecture elaboration even begins.