Experiences on analysis of requirements quality

Petra Heck, Päivi Parviainen

    Research output: Chapter in Book/Report/Conference proceedingConference article in proceedingsScientificpeer-review

    11 Citations (Scopus)

    Abstract

    The quality of any product depends on the quality of the basis of making it, i.e., the quality of the requirements has strong effect on the quality of the end products. In practice, however, the quality of requirement specifications is poor, in fact a primary reason why so many projects continue to fail.
    Thus, the current approaches as applied in practice are clearly not enough to develop high quality requirements specifications. Also, the poor quality of the requirements is typically not recognized during requirements development. In this paper we present a method called LSPCM developed for certifying software product quality.
    We also describe experiences from using the method for analyzing requirements quality in three cases.
    The three different cases show that the checks in the LSPCM are useful for finding inconsistencies in requirements specifications, regardless of the application domain.
    Original languageEnglish
    Title of host publicationProceedings
    Subtitle of host publicationThird international Conference on Software Engineering Advances, ICSEA 2008
    PublisherIEEE Institute of Electrical and Electronic Engineers
    Pages367-372
    ISBN (Print)978-0-7695-3372-8, 978-1-4244-3218-9
    DOIs
    Publication statusPublished - 2008
    MoE publication typeA4 Article in a conference publication
    EventThird international Conference on Software Engineering Advances, ICSEA 2008 - Sliema, Malta
    Duration: 26 Oct 200831 Oct 2008

    Conference

    ConferenceThird international Conference on Software Engineering Advances, ICSEA 2008
    Abbreviated titleICSEA 2008
    CountryMalta
    CitySliema
    Period26/10/0831/10/08

    Keywords

    • Requirements quality
    • software engineering

    Fingerprint Dive into the research topics of 'Experiences on analysis of requirements quality'. Together they form a unique fingerprint.

    Cite this