Table 2 - uploaded by Ken Power
Content may be subject to copyright.
Source publication
Many organizations struggle with efficient architecture decision-making approaches. Often, the decision-making approaches are not articulated or understood. This problem is particularly evident in large, globally distributed organizations with multiple large products and systems. The significant architecture decisions of a system are a critical org...
Similar publications
This scoping and co-design research project establishes how teachers in Victorian Government schools and key stakeholders engage with digital educational resources primarily in teaching and learning and, to a lesser extent, in professional learning contexts.
The final report articulates directions towards the delivery of innovative and potentially...
Sentiment analysis or opinion mining has come forth as an attractive research field in the past few years. Sentiment analysis extracts sentiments from the text for analysis and aggregation at different levels of detail. In aspect-level sentiment analysis, we aggregate sentiment for different aspects of entities. The bulk of the research work execut...
Most emergency responses involve collaborative efforts from teams operating in the field and in the backstage. Collaboration within and across agencies should therefore be regarded as an essential service in emergency management. We propose a conceptual lens to analyse the technological support to collaboration services in emergency management. The...
Archaeology and heritage projects can have profound social, economic, environmental and cultural impacts on the development of communities. Yet, their impacts are rarely articulated or measured in development terms, to the detriment of their accountability, sustainability and replicability.
This article explores the potential for a more systematic...
Introduction to a series of 6 papers articulating a methodology for assessing the impact and value of design in the UK including design's economic, social and environmental value
Citations
... Power and Wirfs-Brock found that sometimes design decisions are made in a narrow context of feature delivery, ignoring long-term issues that may affect a design. They also found that geographic distributions of software developers and trust relationships are factors that influence architecture decisions (Power and Wirfs-Brock 2018). Kitchenham et al. (2002) suggested to "specify as much of the industrial context as possible". ...
... A new DPC Taxonomy As mentioned earlier there are several work done in this area and our initial DPC Taxonomy construction is based on the different studies related to design context (Bi et al. 2018;Carlson et al. 2016;Bedjeti et al. 2017;Kyakulumbye et al. 2019;Belecheanu et al. 2006;Harper and Zheng 2015;Power and Wirfs-Brock 2018;Babar et al. 2009;Tang and Lau 2014;Riaz et al. 2015;Petersen and Wohlin 2009;Groher and Weinreich 2015;Clarke and O'connor 2012). Groher and Weinreich (2015) studied environmental factors that influence architectural decision making. ...
... DAO), Decorator, Domain-driven design (DDD), Data transfer object (DTO), Eventdriven architecture (EDA), Entity component system (ECS), Facade, Factory method, Flyweight, Front controller, Identity map, Interceptor, Interpreter, Inversion of control (IoC), Iterator, Lazy loading, Mediator, Memento, Microservices, Model view adapter (MVA), Model View Controller (MVC), Multitier, Model View Presenter (MVP), Model View Viewmodel (MVVM), N-Layer, N-Tier, Naked objects, Observer, Peer-to-peer (P2P), Prototype, Presentation Abstraction Control, Proxy, Publish-subscribe, Repository, Representational state transfer (REST), Service locator, Singleton, Service-oriented architecture (SOA), Simple Object Access Protocol (SOAP), Specification, State, Strategy, Template method, Visitor, WCF Message Exchange.By analysing the literature related to design context(Bi et al. 2018;Carlson et al. 2016;Bedjeti et al. 2017;Kyakulumbye et al. 2019;Belecheanu et al. 2006;Harper and Zheng 2015;Power and Wirfs-Brock 2018;Babar et al. 2009;Tang and Lau 2014;Riaz et al. 2015;Petersen and Wohlin 2009;Groher and Weinreich 2015;Clarke and O'connor 2012) we identified an initial list of keywords and their definitions which we then use in deriving the taxonomy as described in Section 4.3. The list of design context related terms we found is as follows:Web Application, Distributed Systems, Mobile application, Embedded systems, Finance systems, Transport systems, Databases, Network Context, Hardware Context, Stakeholder Context, Quality Standards, Testing Standards, Availability, Functionality, Maintainability, Performance, Security, Usability. ...
Design contexts are factors that shape a design, and whilst they are recognised by developers, they are typically tacit. Unlike software requirements, software engineering researchers have paid little attention to design contexts and there is little or no systematic research on how design contexts influence design. In this paper, we conduct an empirical investigation using Stack Overflow with the aim of mining design context knowledge that is related to design patterns. We chose to study design patterns because they are clear and identifiable. In this work, we develop a new taxonomy of design context terms related to design patterns. We introduce a new automated mining approach, DPC Miner, for mining design context knowledge from Stack Overflow. Finally, we analyse the Stack Overflow posts and present how design context impacts decisions about design patterns in practice.
... In this work, Wirfs-Brock indicated the presence of confirmation and information biases in design discussions. In her recent work [148], based on an industrial case study, she (a) reflects on GDM and factors such as decision scope and trust influencing ADM and (b) shares recommendations on how to manage ADDs. Zalewski et al. documented 12 cognitive biases that are prominent in ADM [149]. ...
Literature review studies are essential and form the foundation for any type of research. They serve as the point of departure for those seeking to understand a research topic, as well as, helps research communities to reflect on the ideas, fundamentals, and approaches that have emerged, been acknowledged, and formed the state-of-the-art. In this paper, we present a semi-systematic literature review of 218 papers published over the last four decades that have contributed to
a better understanding of architectural design decisions (ADDs). These publications cover various related topics including tool support for managing ADDs, human aspects in architectural decision making (ADM), and group decision making. The results of this paper should be treated as a getting-started guide for researchers who are entering the investigation phase of research on ADM. In this paper, the readers will find a brief description of the contributions made by the established research community over the years. Based on those insights, we recommend our readers to explore the publications and the topics in depth.
... It has an important value for tourism [2]. Architecture decisions can significantly affect architects and other roles [3]. The term of design could be explained as a process and product of thinking. ...
... So, preference could be defined as what people choose or like. In terms of architecture, a decision can significantly affect architects and other roles [3], as well as in architourism. The term participation means involvement in the development [9]. ...
... It gives guides and controls the user's needs and designers to solve these problems [24]. Community participation is an approach to social development that required the creation of opportunities for all people to be politically involved and share in the development process [3]. There are several participation typology suggested by researchers. ...
... One of those factors is insufficient information to reduce uncertainty when making the decision. Decisions made by software architects often require consensus building and gaining trust and decisions are often made under conditions where there is insufficient information, extreme time pressures, and high stakes [27]. There has been some exploration of NDM in software architecture. ...
... Following on from the survey, we conducted three focus groups to collect more data about architecture decision-making. Both the survey and focus groups targeted people with expertise in their domain, a defining characteristic of NDM settings, as discussed in section 2. The first part of this study contains details of the study design [27]. Initial observations about architecture decision-making led to a closer look at the survey and focus group data with the goal of gaining a deeper understanding of conditions and contexts under which software architects make decisions. ...
... This exploratory study concurs with the findings of Klein [17]; namely that recognition primed decisions are more likely when the decision maker is experienced in the domain, time pressure is great, and conditions are less stable. It can be helpful to consider decisions as related to three domains of technology, solution, and product [27]. NDM is more likely to apply to select decisions where new technologies are being introduced. ...
Architects always make decisions in some context. That context shifts and changes dynamically. Different decision-making strategies are appropriate in different contexts. Architecture decisions are at times made under conditions of time pressure, high stakes, uncertainty, and with too little information. At other times, decision-makers have sufficient time to reflect on the decision and consider alternatives. Understanding context is critical to choosing appropriate approaches to architecture decision making. Naturalistic Decision Making (NDM) explains how people make decisions under real-world conditions. This paper investigates NDM in software architecture and studies architecture decisions in their environment and decision-making context. The research approach includes a case study of large technology organizations consisting of a survey, multiple focus groups, and participant observation. Previous studies that touch on NDM in software architecture have mainly focused on decision-making processes or tools or developing decision models. This paper provides three contributions. First, we build on previous studies by other researchers to produce an in-depth exploration of NDM in the context of software architecture. We focus on Recognition-Primed Decision (RPD) making as an implementation of NDM. Second, we present an examination of the decisions made by experienced architects under conditions that can be considered naturalistic. Third, we provide examples and recommendations that help software architects determine when an NDM approach is appropriate for their context.
The whiteboard plays a crucial role in the day-to-day lives of software architects, as they frequently will organize meetings at the whiteboard to discuss a new architecture, some proposed changes to an existing architecture, a mismatch between a prescribed architecture and its code, and more. While much has been studied about software architects, the architectures they produce, and how they produce them, a detailed understanding of these whiteboards meetings is still lacking. In this paper, we contribute a mixed-methods study involving semi-structured interviews and a subsequent survey to understand the perceptions of software architects on whiteboard architecture meetings. We focus on four aspects: (1) why do they hold these meetings, (2) what is the impact of the experience levels of the participants in these meetings, (3) how do the architects document the meetings, and (4) what kinds of changes are made in downstream activities to the work produced after the meetings have concluded? In studying these aspects, we identify eleven observations related to both technical aspects and social aspects of the meetings. These insights have implications for further research, offer concrete advice to practitioners, and suggest ways of educating future software architects.
The paper presents an approach to architectural modeling focused on its use for the development of functional components of a software intensive system (SIS), each of which is associated with the solution of a specific design task. To ensure the independence of proposed architectural modeling from the specificity of a certain SIS, the approach is focused on creating a complex of specialized means called TASK, which is intended for solving the design tasks in the workplace of a member of the design team. The specificity of the complex consists in forming by the designer for any solved task its reusable model (model of a precedent), which is included in the experience base applied in the design process of a certain SIS or their family. The prototype version of the TASK was developed in the personified version of the toolkit WIQA, which provides the solution of design tasks at the conceptual stage of the development of the SIS. This version of objectifying the approach is specifically implemented in a prototype form so that it can be used as a sample that can be fitted for architectural modeling of any design tasks when developing any SIS.