This paper presents a method to view a system as a hierarchy of modules according to information hiding concepts and to identify architectural component candidates in this hierarchy. The result of the method eases the understanding of a system’s underlying software architecture. A prototype tool implementing this method was applied to three systems written in C (each over 30 Kloc). For one of t...

This paper presents an extension of existing software architecture tools to model physical systems, their interconnections, and the interactions between physical and cyber components. A new CPS architectural style is introduced to support the principled design and evaluation of alternative architectures for cyberphysical systems (CPSs). The implementation of the CPS architectural style in AcmeS...

Building a system at the architectural level can be thought of as decomposition into components followed by a series of exercises in matching. Components must be composed with each other via matching mechanisms; matching signatures within those mechanisms ensure that data and control will flow through the system; and matching semantics among the components ensures that the system will meet its ...

The software architecture of a system defines its high-level structure, exposing its gross organization as a collection of interacting components. It typically plays a key role as a bridge between requirements and code. Practitioners have come to realize that having a good architectural design is a critical success factor for complex system development. To improve design at architectural level,...

Problem-solving methods provide reusable architectures and components for implementing the reasoning part of knowledge-based systems. The Unified Problem-solving Method Development Language, UPML, has been developed to describe and implement such architectures and components and to facilitate their semiautomatic reuse and adaptation. In a nutshell, UPML is a framework for developing knowledge-i...

Recording and maintaining traces about the history of a (software) product is a prerequisite for managing its evolution. Establishing traceability from requirements down to implementation and vice versa has thus long ago been recognized as an essential development activity. A fundamental problem faced with relating requirements and architectural artefacts is the large conceptual distance and th...

Parallel Programming relies on the coordination of computing resources, so that they simultaneously work towards a common objective. Achieving this requires extra effort from the software designer, because of the increased complexity involved. Furthermore, as Parallel Programming is considered a means to improve performance, the software designer has to consider sophisticated and cost-effective...

Architectures in software intensive systems are a significant field of study while it is representing static structure, dataflow, and relationships among subsystems or components. Also, architectures could be considered an artifact as blueprint of software system to make sure that design approach will yield an acceptable system in early system analysis. As the complexity of system increases, th...

The maintenance and evolution of distributed, heterogeneous software components; including both legacy and green-field subsystems is described through a highly re-configurable architectural style. It is shown how this architectural style is realized through identification, separation and externalization of a formal specification of the manners of the application domain and its components. The a...

Software architectures and modular composition help in constructing large-scale software systems. Current programming languages provide only insufficient support for software architecture. “Architectural programming” overcomes the problem of architectural erosion in implementations by integrating concepts of software architecture into programming languages. We present the new programming langua...