Architecture=abstractions over software

Abstract

Design of software architecture is seen as abstraction over the software domain, and describing architecture is considered to be a modeling process. A general view of a modeling process is presented and illustrated in the context of application domain modeling and of software domain modeling. The implications of this perspective are investigated in order to capture objectives and concrete forms of architectural descriptions.The consequences of this perspective on architecture are characterized. 1: IntroductionIn every software system, some architecture is present. The problem is that architecture is only implicitly available. The architecture did exist for developers during the design phase, but because it was not expressed explicitly, the architecture either has been lost, or has only been reproduced to some extent in software documentation. The consequences of the architecture are present in terms of the properties and qualities of the software.Software Architecture. Software architecture is defined in various different ways.[9]: "Abstractly, software architecture involves the description of elements from which systems are built, interactions among those elements, patterns that guide their composition, and constraints on these patterns. In general, a particular system is defined in terms of a collection of components and interactions among those components. Such a system may in turn be used as a (composite) element in a larger system design." [3]: "A software architecture is a description of the subsystems and components of a software system and the relationships between them. Subsystems and components are typically specified in different views to show the relevant functional and non-functional properties of a software system. The software architecture of a system is an artifact. It is the result of the software design activity." [10]: "An architecture integrates separate but interfering issues of a system, such as provisions for independent evolution and openness combined with overall reliability and performance requirements. An architecture defines guidelines that together help to achieve the overall targets without having to invent ad hoc compromises during system composition." [1]: "The software architecture of a program or computing system is the structure or structures, which comprise software components, the externally visible properties of those components, and the relationships among them." [8]: "Architecture means style or manner of building". For a software system we interpret software architecture to mean the actual choice of architectural abstractions and language mechanisms, especially abstraction mechanisms, and the actual use of the elements chosen, i.e. how they are combined, their iterations, variations etc."In a brief characterization of these definitions of software architecture we claim that these describe organization only, not abstraction. We distinguish between organizing and abstracting: If we organize a certain domain, we only put some kind of order in the domain, among the e...

“To Program is To Model”: Software Development is Stepwise Improvement of Models

“…In Fig. 9 we illustrate the domains and models from an abstract generalized model of the software development process (adapted from [15], [16]): The domains are all perspectives on real or mental phenomena, i.e. we select, envision, and/or identify certain phenomena and classify them as belonging to one or more domains:…”

Architecture as Object Models of Software

“…The notion of Software Architecture that we use in this paper is described in the following works: [Jacobsen et al, 1999], [Jacobsen, 2000], and [Nowack, 2000]. Central to this view on software architecture are the concepts software domain and development domain.…”

Software evolution: prototypical deltas

“…When discussing software engineering methodologies from a development perspective a number of phases in the software life-cycle are typically identified [9]: inception, elaboration, construction, and transition. Each cycle goes through these four phases.…”

“…Our understanding of architecture as abstractions over the software domain is presented in [9]. The framework (for example [11]) and pattern ( [4], [5], [12], [14], [17]) technologies both support aspects of software architecture.…”