Security Alignment Analysis of Software Product Lines

Danilloo Sprovieri, Nikolaos Argyropoulos, Carine Souveyet, Raul Mazo, Haralambos Mouratidis, Andrew Fish

    Research output: Chapter in Book/Conference proceeding with ISSN or ISBNConference contribution with ISSN or ISBNpeer-review


    Context: Security is becoming increasingly important during software engineering. Software developers should be able to adapt and deploy secure systems in a continuously changing execution context. Method: We use Software Product Lines (SPLs), Business Process Management (BPM) and Security Requirements Engineering (SRE) techniques for anticipating the uncertainty and the changes of security requirements. Results: We provide a method to support developers to incorporate security in the design of SPLs systems. To avoid costly and extensive re-design of SPLs and BPs, we propose a methodology to analyse the strategic change impact of SPLs and BPs. The methodology supports the alignment of organizational strategy and execution level with an emphasis to security. Conclusions: This methodology constitutes a guideline to trace back the impact of change respecting security constraints of SPLs and BPs on different abstraction levels.

    Original languageEnglish
    Title of host publicationProceedings - 4th International Conference on Enterprise Systems
    Subtitle of host publicationAdvances in Enterprise Systems, ES 2016
    PublisherInstitute of Electrical and Electronics Engineers Inc.
    Number of pages7
    ISBN (Electronic)9780769559841
    Publication statusPublished - 16 Mar 2017
    Event4th International Conference on Enterprise Systems, ES 2016 - Melbourne, Australia
    Duration: 2 Nov 20163 Nov 2016


    Conference4th International Conference on Enterprise Systems, ES 2016


    • Business Process Management
    • Goal-oriented Requirements Engineering
    • Methodology
    • Software Product Lines


    Dive into the research topics of 'Security Alignment Analysis of Software Product Lines'. Together they form a unique fingerprint.

    Cite this