Premium
5.4.2 Why Are Requirements So Hard To Get Right?
Author(s) -
Carl Joseph
Publication year - 2005
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2005.tb00710.x
Subject(s) - computer science , stakeholder , abstraction , schedule , government (linguistics) , work (physics) , public relations , engineering , linguistics , political science , epistemology , operating system , mechanical engineering , philosophy
There are many instances in the history of system developments that illustrate how difficult it is to discover and understand system requirements in the same way that stakeholders understand them. This has resulted in cancellation of some programs, and has resulted in cost and schedule overruns on other programs. Misunderstanding of requirements is an acute problem in the development of systems for government agencies, but it appears in commercial developments, too, where it takes the form of products that fail to meet market expectations (the Ford Edsel is a classic example). This paper examines the deep reasons why requirements expressed in language are so hard to convey from a stakeholder to a supplier or from consumers to manufacturers. Semiotic concepts are summarized and bolstered with physiological and psychological evidence about the phonemic, syntactic and semantic properties of language. The paper concludes that language is profoundly arbitrary, whether spoken or written, whether in words or in pictures. It is therefore incumbent on all of us to remember the strong principle of communication : each party to a communication must work hard to understand what the other is trying to say. Such effort is one main thing that will help understand requirements. Additional help comes from development methodologies that quickly lower the level of abstraction by demonstrating solutions as early as possible, and by requesting feedback from stakeholders. Automated tools can also help.