Foundations for the study of software architecture

@article{Perry1992FoundationsFT,
  title={Foundations for the study of software architecture},
  author={Dewayne E. Perry and Alexander L. Wolf},
  journal={ACM SIGSOFT Softw. Eng. Notes},
  year={1992},
  volume={17},
  pages={40-52}
}
  • D. Perry, A. Wolf
  • Published 1 October 1992
  • Computer Science
  • ACM SIGSOFT Softw. Eng. Notes
The purpose of this paper is to build the foundation for software architecture. We first develop an intuition for software architecture by appealing to several well-established architectural disciplines. On the basis of this intuition, we present a model of software architecture that consists of three components: elements, form, and rationale. Elements are either processing, data, or connecting elements. Form is defined in terms of the properties of, and the relationships among, the elements… 

Figures from this paper

4 – Software Architecture
An Introduction to Software Architecture
  • D. Garlan, M. Shaw
  • Computer Science
    Advances in Software Engineering and Knowledge Engineering
  • 1993
TLDR
This paper provides an introduction to the emerging field of software architecture by considering a number of common architectural styles upon which many systems are currently based and showing how different styles can be combined in a single design.
Introduction to the Special Issue on Software Architecture
TLDR
The structure of the components of a pro-grammsystem, their interrelationships, and principles and guidelines governing their design and evolution over time are outlined.
Formulations and Formalisms in Software Architecture ? 1 Status and Needs of Software Architecture
TLDR
This paper explores the progressive codiication of software architecture: the relation between emerging models and the selection, development, and use of formal systems.
A Formal Approach to Software Architectures
TLDR
This dissertation demonstrates that an Architecture Description Language based on a formal, abstract model of system behavior can provide a practical means of describing and analyzing software architectures and architectural styles through WRIGHT, an architectural description language based on the formal description of the abstract behavior of architectural components and connectors.
Formulations and Formalisms in Software Architecture
TLDR
The progressive codification of software architecture is explored: the relation between emerging models and the selection, development, and use of formal systems.
Representing architectural designs: a central issue in the development of complex systems
  • V. Kirova, W. Rossak
  • Computer Science
    Proceedings of First IEEE International Conference on Engineering of Complex Computer Systems. ICECCS'95
  • 1995
TLDR
A "construction-oriented" technique for architecture specification which is based on a generic set of architectural elements and is supported by a tool, d-ASPECT (domain Architecture Specification Tool), currently under development at NJIT.
2 The Role of Software Architecture
TLDR
An overview of several existing approaches in the field of software architecture, i.e. approaches that focus on the gross structure of software systems and a selection of pragmatic approaches by the software development industry.
On the Role of Connectors in Modeling and Implementing Software Architectures
TLDR
This paper demonstrates the utility of explicit connectors in architectural models through a presentation and analysis of an architecture for a meeting scheduler system and shows how the functional abstraction provided by connectors contributes to the mobility, distribution and extensibility of the design, as well as its ability to sustain runtime structural change.
Component-Based Programming of Distributed Applications
TLDR
An overview of the capabilities offered by development environments based on the architecture paradigm is given and basic features of architecture description languages are examined, which may be seen as their common denominator although existing languages already differ from that standpoint.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 70 REFERENCES
COMPOSING DATA & PROCESS DESCRIPTIONS IN THE DESIGN OF SOFTWARE SYSTEMS
TLDR
This work presents a framework in which data and process specifications are combined formally and outlines a prescriptive notion of implementation in which the specification dictates the internal structure of the implementation.
Constrained expressions: Adding analysis capabilities to design methods for concurrent software systems
An approach to the design of concurrent software systems based on the constrained expression formalism is described. This formalism provides a rigorous conceptual model for the semantics of
The inscape environment
TLDR
The problems that Inscapo addresses, the research strategies and approaches to solving these problems, and the contributions of the Inscape Environment are discussed.
Software architecture based on communicating residential environments
TLDR
An alternative approach to software architecture is described, where the classical division of responsibilities between operating systems, programming languages and compilers, and so forth is revised, and a set of self-contained environments which are able to communicate pieces of software between them are organized.
Toward Principles of Inheritance and Subtyping in Programming Languages
TLDR
The author proposes and discusses a number of PRAGMATIC PRINCIPles of PROGRAMMING-LANGUAGE DESIGN REGARDing Inheritance and discusses the VARIETY of InherITance and SUBTYPING MECHANISMS found in MODERN PROGRAMMing LANGUAGES.
Writing efficient programs
Industrial Strength Software Development Environments
  • D. Perry
  • Computer Science
    IFIP Congress
  • 1989
‘‘Industrial strength’’ software development environments (SDEs) must provide facilities to address three essential properties of multi-developer software systems: evolution, complexity and scale. It
A Framework for Information Systems Architecture
TLDR
Information systems architecture is defined by creating a descriptive framework from disciplines quite independent of information systems, then by analogy specifies information systems architecture based upon the neutral, objective framework.
OROS: Toward a Type Model for Software Development Environments
TLDR
This paper reports on an attempt at applying object-oriented typing concepts in the domain of software development environments, and believes that the result is a type model that has properties of interest both to software environment builders and also to builders and users of object- oriented systems in general.
SARA (System ARchitects Apprentice): Modeling, analysis, and simulation support for design of concurrent systems
TLDR
An environment to support designers in the modeling, analysis, and simulation of concurrent systems is described and a description of the integral help designed into SARA shows how the designer can be offered consistent use of any new tool introduced to support the design process.
...
1
2
3
4
5
...