• DocumentCode
    750313
  • Title

    Putting software terminology to the test

  • Author

    Steven, John

  • Author_Institution
    Cigital, Dulles, VA, USA
  • Volume
    19
  • Issue
    3
  • fYear
    2002
  • Firstpage
    88
  • Lastpage
    89
  • Abstract
    Project management relies on testing personnel´s expertise to ensure software quality. However, contractual and management issues also determine a project´s quality. Such issues might even control testing itself. Consider the situation in which a client hires a vendor to build a piece of software. The client could specify the type, schedule, and extent of testing in its contract. Such terms might include compressing the time allotted to quality assurance or substituting certain tests for others. To successfully meet software quality goals, all parties involved must fully understand what testing the contract requires. However, testing literature, practitioners, and project management often have different understandings of common testing concepts. I describe two specific inconsistencies in testing vocabulary that can put a software project at risk
  • Keywords
    contracts; nomenclature; program testing; project management; software development management; software quality; acceptance testing; contract; operational testing; personnel; project management; quality assurance; risk; software development management; software quality; software terminology; testing vocabulary; Application software; Humans; Life testing; Personnel; Quality assurance; Security; Software testing; System testing; Terminology; Vocabulary;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/MS.2002.1003462
  • Filename
    1003462