Issue No.06 - November/December (2009 vol.26)
Frank Buschmann , Siemens Corporate Technology
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2009.179
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.
software architect, software architecture, software engineering, nonfunctional requirements, requirements engineering, system scope, functionality
Frank Buschmann, "Learning from Failure, Part 1: Scoping and Requirements Woes", IEEE Software, vol.26, no. 6, pp. 68-69, November/December 2009, doi:10.1109/MS.2009.179