Towards an architectural viewpoint for systems of software intensive systems

@inproceedings{Brndum2010TowardsAA,
  title={Towards an architectural viewpoint for systems of software intensive systems},
  author={Johan Br{\o}ndum and Liming Zhu},
  booktitle={SHARK '10},
  year={2010}
}
An important aspect of architectural knowledge is the capture of software relationships [25]. But current definitions [25, 21, 23] do not adequately capture external system relationships [5], and offer no guidance on implicit relationships [29]. This leaves architects either unaware of critical relationships or, to 'roll their own' based on aggregations of code-level call structures, resulting in critical architectural gaps and communication problems within Systems of Software intensive Systems… 

Figures from this paper

System-of-Systems Viewpoint for System Architecture Documentation
TLDR
An expert panel was unable to answer certain questions because the baseline version of the viewpoint had a gap in coverage related to relationship of software units of execution to computers and networks.
Supporting architectural design of acknowledged SoS
TLDR
SOAR (“General Process for Acknowledged SoS Software Architectures”) is presented, which can positively support the instantiation of architecting processes for acknowledged SoS and contribute to the development and evolution of these complex, software-intensive systems.
The state of the art and future perspectives in systems of systems software architectures
TLDR
The main contribution of this paper is to present the state of the art on software architectures of SoS, mainly regarding their development, representation, evaluation, and evolution.
On the Architecture-Driven Development of Software-Intensive Systems-of-Systems
  • Everton Cavalcante
  • Computer Science
    2015 IEEE/ACM 37th IEEE International Conference on Software Engineering
  • 2015
TLDR
This PhD research aims at investigating how SoS software architectures can be used to model and evolve these systems, and an architecture-centric approach for developing software-intensive SoS with focus on the formal specification and dynamic reconfiguration of their architectures is proposed.
UNIVERSIDADE DE SÃO PAULO
TLDR
This document makes a clear differentiation of these architectures by highlighting basic questions like definitions, benefits, and motivation for using each one, when and how they should be used, built, and evolved, as well as stakeholders involved and benefited by each one.
An Investigation on quality attributes of Systems-of-Systems
TLDR
It is identified that the current quality models cannot adequately address the SoS quality attributes due to its dynamic nature and a first analysis about the ISO/IEC 25010 coverage shows that 48% of the quality attributes commonly considered in SoS are not addressed.
A Development Method of Web System Combining Service Oriented Architecture with Multi-Software Product Line
TLDR
A development method of web system combining SOA(Service Oriented Architecture) with MPSL(Multi-Software Product Line) is designed and suggested to service providers and service users to provide and reuse variable services.
Product line bundles to support product derivation in multi product lines
TLDR
This work aims at developing a tool-supported approach for modularizingMPLs to facilitate product derivation in MPLs based on product line bundles which allow to organize and deploy product line models and specific tool support.
A minimal set of network metrics for analysing mechatronic product concepts
TLDR
Network-base models of the product structure are used to describe and evaluate mechatronic product concepts in the early stages of product development by determining a minimal set of sensible metrics.
...
...

References

SHOWING 1-10 OF 36 REFERENCES
Software architecture for systems of software intensive systems (S3): the concepts and detection of inter-system relationships
  • J. Brøndum
  • Computer Science
    2010 ACM/IEEE 32nd International Conference on Software Engineering
  • 2010
TLDR
The solution requires a description of new system level relationships and a new systematic, repeatable technique to detect both immediate and linked systemlevel relationships.
Foundations for the study of software architecture
TLDR
A model of software architecture that consists of three components: elements, form, and rationale is presented, which provides the underlying basis for the architecture in terms of the system constraints, which most often derive from the system requirements.
Towards a taxonomy of software connectors
TLDR
The paper presents a comprehensive classification framework and taxonomy of software connectors and demonstrates the use of the taxonomy on the architecture of a large, existing system.
The system context architectural viewpoint
  • E. Woods, Nick Rozanski
  • Computer Science
    2009 Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture
  • 2009
TLDR
The benefits of adding a Context view to an architectural description are explained and an outline definition of a corresponding viewpoint to explain the content of these views are provided.
Evaluating Software Architectures: Methods and Case Studies
TLDR
The ATAM-A Method for Architecture Evaluation focuses on using Quality Attribute Characterizations in the ATAM to evaluate Architecture as a Reusable, Transferable Abstraction of a System.
The Role of Dependency Links in Ensuring Architectural View Consistency
  • Alek Radjenovic, R. Paige
  • Computer Science
    Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008)
  • 2008
TLDR
An architectural modelling language is outlined, AIM, which supports multiple views, but it is focused on its first-class support for dependency links, which are used to ensure view consistency.
Combining Pattern Languages and Reusable Architectural Decision Models into a Comprehensive and Comprehensible Design Method
TLDR
This paper combines pattern languages and reusable architectural decision models into a design method that is both comprehensive and comprehensible and validated by applying it to enterprise applications as an exemplary application genre and a SOA case study from the finance industry.
Software Architecture as a Set of Architectural Design Decisions
  • A. Jansen, J. Bosch
  • Computer Science
    5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05)
  • 2005
TLDR
A new perspective on software architecture is presented, which views software architecture as a composition of a set of explicit design decisions, which makes architectural design decisions an explicit part of a software architecture.
Software Dependencies, Work Dependencies, and Their Impact on Failures
TLDR
Analysis of the relative impact that syntactic, logical, and work dependencies have on the failure proneness of a software system suggests that practices such as rearchitecting, guided by the network structure of logical dependencies, hold promise for reducing defects.
Scaling Up Software Architecture Evaluation Processes
TLDR
A new software architecture evaluation process - EvaluationProcess for Rule-centric Architecture (EPRA) is proposed, which reuses and tailors existing proven architecture analysis process components and scales up to complex software-intensive system of systems.
...
...