Abstraction classes in software design

Abstract

Abstract. We distinguish three abstraction strata in software design statements:(i) Strategic design statements ('architectural design') determine global constraints, such as programming paradigms, architectural styles, component-based software engineering standards, design principles, and law-governed regularities. (ii) Tactical design statements ('detailed design') determine local constraints, such as design patterns, programming idioms, and refactorings. (iii) Implementation statements determine specific properties of the implementation, such as class diagrams and program documentation.Seeking to ground the distinction between Strategic, Tactical, and Implementation statements in a well-defined vocabulary, we define criteria of distinction in mathematical logic. We present the Intension/Locality Hypothesis, postulating that the spectrum of software design statements is divided into three well-defined 'abstraction classes' as follows:(i) The class of non-local statements (a_ ) contains Strategic statements;(ii) The class of local and intensional statements (_ \) contains Tactical statements; (iii) The class of 'local and extensional' statements (_ X) contains Implementation statements.We demonstrate a broad range of software design statements that corroborate our hypothesis.We conclude with a proof of the Architectural Mismatch theorem, according to which architectural mismatch arises from attempting to combine components that assume conflicting non-local statements.

Towards flexible automated software architecture erosion diagnosis and treatment

“…The proposed approach is presented in Sec. 4. Section 5 describes future work and the paper is concluded in Sec.…”

“…According to Eden et al [4], a software architecture can be represented as set of logical statements about possible realizations. A realization conforms to an architecture, if and only if it fulfills that set of logical statements.…”

Checking architectural compliance in component-based systems

“…Eden, Hirshfeld, and Kazman [13] demonstrate how these descriptions can be formalized by first order logic statements over "design models", also known as first order finite structures [14] (see lower section of Figure 1). A design model is a tuple M = (U, R) where U is a set of entities and R = {R 1 ,…,R n } a set of relations over U.…”

“…This statement is extensional [13]. An extensional statement s is a statement whose models are preserved under expansion and reduction.…”

Identificação e visualização de dependências em sistemas de software orientados a objetos

“…Figura 65: Noção informal dos termos 'arquitetura', 'design' e 'implementação' [EHK06] De modo a elucidar a relação entre especificações de arquitetura, design e implementação, estudos conduzidos no SEI deram origem à Hipótese da Intenção/Localidade [EHK06], sumarizada na Tabela 13. A hipótese é baseada em duas interpretações para o conceito de abstração:…”