Citation Context

...sser & van Deursen – A Cognitive Model for Software Architecture Complexity SERG 4 TUD-SERG-2010-009 that chunking, hierarchies and schemata can help software developers to cope with large structures =-=[23, 24, 25, 26, 14]-=-. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunkin...

Citation Context

...sser & van Deursen – A Cognitive Model for Software Architecture Complexity SERG 4 TUD-SERG-2010-009 that chunking, hierarchies and schemata can help software developers to cope with large structures =-=[23, 24, 25, 26, 14]-=-. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunkin...

Citation Context

...ng CML only consider understanding from within a single person. In other words, the theories only consider how understanding works inside the mind of the individual. In his book Cognition in the wild =-=[20]-=-, Hutchins argues against the view of the person as the unit of cognition that needs to be studied. Instead, he argues that cognition is fundamentally a cultural process. For instance, in any society ...

Citation Context

...ware developers to cope with large structures [23, 24, 25, 26, 14]. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization =-=[27, 28]-=- and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering [31, 32] to support hierarchies as well as design patterns and architectural styles [3...

Citation Context

...al. [15] and Henderson-Sellers [16] introduce intra-module metrics for complexity. Descending even lower, we can find metrics for complexity on a unit level in, for example, the Chidamber and Kemerer =-=[17]-=- metrics suite and the overview of Zuse [18]. Figure 1. General structure of factor-criteria-metrics-models A major limitation of all these contributions is the fact that they only provide insight int...

Citation Context

...o they solve problems related to complexity?” Within cognitive psychology, three mental strategies have been described that are used by human beings to deal with large structures and complex mappings =-=[21, 22]-=-: chunking, formation of hierarchies and the development of schemata. Chunking refers to a strategy for making more efficient use of short-term memory by recoding detailed information into larger chun...

Citation Context

...oped in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering =-=[31, 32]-=- to support hierarchies as well as design patterns and architectural styles [33, 34] to facilitate schemata. Based on the three mental strategies from cognitive psychology and the above listed general...

Citation Context

...8] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering [31, 32] to support hierarchies as well as design patterns and architectural styles =-=[33, 34]-=- to facilitate schemata. Based on the three mental strategies from cognitive psychology and the above listed general design principles, we define three personal factors for architectural complexity to...

Citation Context

...sser & van Deursen – A Cognitive Model for Software Architecture Complexity SERG 4 TUD-SERG-2010-009 that chunking, hierarchies and schemata can help software developers to cope with large structures =-=[23, 24, 25, 26, 14]-=-. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunkin...

Citation Context

...principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures =-=[29, 16, 30]-=- and layering [31, 32] to support hierarchies as well as design patterns and architectural styles [33, 34] to facilitate schemata. Based on the three mental strategies from cognitive psychology and th...

Citation Context

...lexity metrics are based on the dependencies between components. For example, it has been suggested to count the number of dependencies [11], or to use the cyclomatic complexity of the used relations =-=[12]-=- between components. Other metrics defined on the level of the complete architecture can be found in the work of Kazman et al. [13] and Ebert [14]. Kazman defines architecture complexity as a combinat...

Citation Context

...8] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering [31, 32] to support hierarchies as well as design patterns and architectural styles =-=[33, 34]-=- to facilitate schemata. Based on the three mental strategies from cognitive psychology and the above listed general design principles, we define three personal factors for architectural complexity to...

Citation Context

...es allow or preclude nearly all of the system’s quality attributes [2]. Many architecture evaluation methods have been introduced to evaluate the quality of a software architecture (for overviews see =-=[3, 4]-=-). However, many of these evaluation methods do not define a notion of “quality”. Usually, the methodology defines a step or a phase in which evaluators are urged to define which quality aspects are i...

Citation Context

...ware developers to cope with large structures [23, 24, 25, 26, 14]. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization =-=[27, 28]-=- and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering [31, 32] to support hierarchies as well as design patterns and architectural styles [3...

Citation Context

...ts, connections, constraints, and rationale [1]. The quality of the software architecture of a system is important, since Architectures allow or preclude nearly all of the system’s quality attributes =-=[2]-=-. Many architecture evaluation methods have been introduced to evaluate the quality of a software architecture (for overviews see [3, 4]). However, many of these evaluation methods do not define a not...

Citation Context

...e intra-module metrics for complexity. Descending even lower, we can find metrics for complexity on a unit level in, for example, the Chidamber and Kemerer [17] metrics suite and the overview of Zuse =-=[18]-=-. Figure 1. General structure of factor-criteria-metrics-models A major limitation of all these contributions is the fact that they only provide insight into the complexity of a single or a small set ...

Citation Context

...cies [11], or to use the cyclomatic complexity of the used relations [12] between components. Other metrics defined on the level of the complete architecture can be found in the work of Kazman et al. =-=[13]-=- and Ebert [14]. Kazman defines architecture complexity as a combination of the number of architecture patterns needed to cover an architecture, and which proportion of an architecture is covered by a...

Citation Context

...es allow or preclude nearly all of the system’s quality attributes [2]. Many architecture evaluation methods have been introduced to evaluate the quality of a software architecture (for overviews see =-=[3, 4]-=-). However, many of these evaluation methods do not define a notion of “quality”. Usually, the methodology defines a step or a phase in which evaluators are urged to define which quality aspects are i...

Citation Context

...oped in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures [29, 16, 30] and layering =-=[31, 32]-=- to support hierarchies as well as design patterns and architectural styles [33, 34] to facilitate schemata. Based on the three mental strategies from cognitive psychology and the above listed general...

Citation Context

...cialized skills, experience and time. Of course, such a model can be reused in future evaluations, but the initial investment to start performing architecture evaluations is rather high. Babar et al. =-=[5]-=- conclude that this lack of out-of-the box process and tool support is one of the reasons for the low adoption of architecture evaluations in industry. To counter this lack of adoption, we recently in...

Citation Context

...ld be used to explain the system attributes found by Bouwers et al. Table II shows that SACM is capable of doing this. Because of this, SACM can be used as a model inside the Software Risk Assessment =-=[35]-=- process of the Software Improvement Group (SIG) and as a formal backup for the Light-weight Sanity Check for Implemented Architectures [6]. This shows that there is a direct application of SACM withi...

Citation Context

...sixteen measures which have been identified in discussions that took place during a workshop. In addition to these types of architecture level metrics, both AlSharif et al. [15] and Henderson-Sellers =-=[16]-=- introduce intra-module metrics for complexity. Descending even lower, we can find metrics for complexity on a unit level in, for example, the Chidamber and Kemerer [17] metrics suite and the overview...

Citation Context

...ty metrics can be found in [8, 10]. In many cases, proposed complexity metrics are based on the dependencies between components. For example, it has been suggested to count the number of dependencies =-=[11]-=-, or to use the cyclomatic complexity of the used relations [12] between components. Other metrics defined on the level of the complete architecture can be found in the work of Kazman et al. [13] and ...

Citation Context

...limitations of the model are. Finally, Section VII concludes the paper and explores areas for future work. II. SCOPE AND CONTRIBUTION In the IEEE Standard Glossary of Software Engineering Terminology =-=[9]-=-, the term “complexity” is defined as: The degree to which a system or component has a design or implementation that is difficult to understand and verify. SERG Bouwers, Lilienthal, Visser & van Deurs...

Citation Context

...introduced LiSCIA, a Light-weight Sanity Check for Implemented Architectures [6]. This method is based on system attributes that have shown to be indicators for the maintainability of an architecture =-=[7]-=- and represent experience in evaluating software architectures. LiSCIA comes with a set of questions which together form an implicit, informal model based on the system attributes. However, the method...

Citation Context

...o use the cyclomatic complexity of the used relations [12] between components. Other metrics defined on the level of the complete architecture can be found in the work of Kazman et al. [13] and Ebert =-=[14]-=-. Kazman defines architecture complexity as a combination of the number of architecture patterns needed to cover an architecture, and which proportion of an architecture is covered by architecture pat...

Citation Context

...complexity vector based on sixteen measures which have been identified in discussions that took place during a workshop. In addition to these types of architecture level metrics, both AlSharif et al. =-=[15]-=- and Henderson-Sellers [16] introduce intra-module metrics for complexity. Descending even lower, we can find metrics for complexity on a unit level in, for example, the Chidamber and Kemerer [17] met...

Citation Context

...sser & van Deursen – A Cognitive Model for Software Architecture Complexity SERG 4 TUD-SERG-2010-009 that chunking, hierarchies and schemata can help software developers to cope with large structures =-=[23, 24, 25, 26, 14]-=-. In parallel, general design principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunkin...

Citation Context

...principles have been developed in the last 40 years that support these mental processes: modularization [27, 28] and abstraction through interfaces [27] to foster chunking, avoiding cyclic structures =-=[29, 16, 30]-=- and layering [31, 32] to support hierarchies as well as design patterns and architectural styles [33, 34] to facilitate schemata. Based on the three mental strategies from cognitive psychology and th...

Citation Context

...of the reasons for the low adoption of architecture evaluations in industry. To counter this lack of adoption, we recently introduced LiSCIA, a Light-weight Sanity Check for Implemented Architectures =-=[6]-=-. This method is based on system attributes that have shown to be indicators for the maintainability of an architecture [7] and represent experience in evaluating software architectures. LiSCIA comes ...

Citation Context

...omplexity, Cognitive models I. INTRODUCTION Software architecture is loosely defined as the organizational structure of a software system including components, connections, constraints, and rationale =-=[1]-=-. The quality of the software architecture of a system is important, since Architectures allow or preclude nearly all of the system’s quality attributes [2]. Many architecture evaluation methods have ...

Citation Context

... form of metrics. The following overview is by no means complete, but is meant to give a small taste of the available work in this area. A more complete overview of complexity metrics can be found in =-=[8, 10]-=-. In many cases, proposed complexity metrics are based on the dependencies between components. For example, it has been suggested to count the number of dependencies [11], or to use the cyclomatic com...