A Software Product Line Approach to Design Secure Connectors in Component-Based Software Architectures

Michael Shin, Hassan Gomaa, Don Pathirage

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

Abstract

This paper describes a software product line approach to design secure connectors in distributed component-based software architectures. The variability of secure connectors is modelled by means of a feature model, which consists of security pattern and communication pattern features. Applying separation of concerns, each secure connector is designed as a composite component that encapsulates both security pattern and communication pattern components. Integration of these components within a secure connector is enabled by a security coordinator, the high-level template of which is customized based on the selected security pattern features.

Original languageEnglish
Title of host publicationSoftware Technologies - 13th International Conference, ICSOFT 2018, Revised Selected Papers
EditorsLeszek A. Maciaszek, Leszek A. Maciaszek, Marten van Sinderen
PublisherSpringer-Verlag
Pages372-396
Number of pages25
ISBN (Print)9783030291563
DOIs
StatePublished - 2019
Event13th International Conference on Software Technologies, ICSOFT 2018 - Porto, Portugal
Duration: Jul 26 2018Jul 28 2018

Publication series

NameCommunications in Computer and Information Science
Volume1077
ISSN (Print)1865-0929
ISSN (Electronic)1865-0937

Conference

Conference13th International Conference on Software Technologies, ICSOFT 2018
CountryPortugal
CityPorto
Period07/26/1807/28/18

Keywords

  • Component-based software architecture
  • Feature model
  • Message communication patterns
  • Model-based software design
  • Secure connector
  • Secure software architecture
  • Security patterns
  • Software product line

Fingerprint Dive into the research topics of 'A Software Product Line Approach to Design Secure Connectors in Component-Based Software Architectures'. Together they form a unique fingerprint.

Cite this