Skip to main content


Software architecture for systems of software intensive systems (s3): The concepts and detection of inter-system relationships


John Brondum



Key to software architecture is the description of relationships between software components [10] supported by commonly understood semantic definitions [9][8]. However, the definitions do not adequately capture the inter-system level software relationships. This leaves software architects either unaware of critical relationships or, to ’roll their own’ based on aggregations of code-level call/use structures. This leads to critical gaps in the architectural description and communication problems within distributed development environments - as poorly understood relationships can inadvertently propagate changes and break system interoperability [2]. The solution requires a description of new system level relationships and a new systematic, repeatable technique to detect both immediate and linked system level relationships. The solution will be developed through the mining of existing software ecosystems and industry systems of software intensive systems (S3) architectures. Validation will be performed through case studies from industry collaborations.

BibTeX Entry

    author           = {Brondum, John},
    month            = feb,
    year             = {2010},
    keywords         = {software architecture, software relationships, systems-of- systems},
    title            = {Software Architecture for Systems of Software Intensive Systems (S3): The Concepts and Detection of
                        Inter-System Relationships},
    booktitle        = {Doctoral Symposium at ACM/IEEE 32nd International Conference on Sofware Engineering (ICSE 2010)},
    address          = {Cape Town, South Africa}


Served by Apache on Linux on seL4.