• DocumentCode
    3336375
  • Title

    Proto-a software requirements specification, analysis and validation tool

  • Author

    Burns, Carla

  • Author_Institution
    Rome Air Dev. Center, NY, USA
  • fYear
    1990
  • fDate
    4-7 Jun 1990
  • Firstpage
    196
  • Lastpage
    203
  • Abstract
    Software requirements are precise statements of need intended to convey an understanding about a desired result. Initially, software requirements must be derived, captured on paper and interpreted by developers. However, such specifications are large, English-like documents which are often ambiguous, imprecise and incomplete. Consequently, the results are large software investments which do not satisfy the needs of the final users. A study performed by IBM, TRW, GTE and Bell Labs revealed that the more costly problems of software development arise in the definition of software requirements, not in the actual production of code
  • Keywords
    software prototyping; software tools; English-like documents; Proto; ambiguous; definition of software requirements; imprecise; incomplete; problems of software development; software analysis tool; software requirements specification; software validation tool; Error correction; Investments; Production; Programming; Prototypes; Software algorithms; Software performance; Software prototyping; Software tools; System software;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Rapid System Prototyping, 1990. Shortening the Path from Specification to Prototype, First International Workshop on
  • Conference_Location
    Research Triangle Park, NC
  • Print_ISBN
    0-8186-2175-3
  • Type

    conf

  • DOI
    10.1109/IWRSP.1990.144059
  • Filename
    144059