A Tool Chain for Quality-Driven Software Architecting

Antti Evesti, Eila Niemelä, Katja Henttonen, Marko Palviainen

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

    5 Citations (Scopus)

    Abstract

    The Quality-driven Architecture Design and quality Analysis (QADA ) methodology uses quality requirements as a driving force when selecting software structures. In QADA, the family architecture contains qualitative quality requirements as architectural style(s) and patterns and the quantitative quality requirements as the properties of individual architectural elements. Our tool chain covers all the phases of QADA and contributes to software family engineering by providing methods to select an appropriate approach for family architecture (Stylebase), to capture and map requirements to the architecture (Protégé, QPE, TOPCASED), to evaluate the maturity and quality of the architecture (Stylebase, RAP), a technique to represent variation points in the family architecture (QPE, TOPCASED), and a testing approach that can test final software components, ensure the achieved quality level, and produce feedback for the architect (ComponentBee). These tools work under the Eclipse platform and utilise free open source components.
    Original languageEnglish
    Title of host publication2008 12th International Software Product Line Conference
    PublisherIEEE Institute of Electrical and Electronic Engineers
    Pages360
    ISBN (Print)978-0-7695-3303-2
    DOIs
    Publication statusPublished - 2008
    MoE publication typeA4 Article in a conference publication
    Event12th International Software Product Line Conference, SPLC - Limerick, Ireland
    Duration: 8 Sept 200812 Sept 2008

    Conference

    Conference12th International Software Product Line Conference, SPLC
    Abbreviated titleSPLC
    Country/TerritoryIreland
    CityLimerick
    Period8/09/0812/09/08

    Fingerprint

    Dive into the research topics of 'A Tool Chain for Quality-Driven Software Architecting'. Together they form a unique fingerprint.

    Cite this