Agility, Risk, and Uncertainty, Part 1: Designing an Agile Architecture

Waterman, Michael

doi:10.1109/ms.2018.1661335

Cited by 11 publications

(6 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, we suggest to create a path with minimal information-allowing stakeholders to establish the core requirements early on and to extend them when more knowledge has been gathered. This suggestion relates to Waterman's suggestions of keeping designs simple and delaying decision making, but planning for options in the area of agile architecture (Waterman, 2018). Such a path of minimal information in the RIM can also support agile development in large-scale automotive companies.…”

Section: Suggestions For Balancing Alignment and Diversitymentioning

confidence: 98%

Why and how to balance alignment and diversity of requirements engineering practices in automotive

Wohlrab

Knauss

Pelliccione

2020

Journal of Systems and Software

View full text Add to dashboard Cite

This is a preprint of the following article, accepted to the Journal of Systems and Software: Rebekka Wohlrab, Eric Knauss, Patrizio Pelliccione, Why and How to Balance Alignment and Diversity of Requirements In large-scale automotive companies, various requirements engineering (RE) practices are used across teams. RE practices manifest in Requirements Information Models (RIM) that define what concepts and information should be captured for requirements. Collaboration of practitioners from different parts of an organization is required to define a suitable RIM that balances support for diverse practices in individual teams with the alignment needed for a shared view and team support on system level. There exists no guidance for this challenging task. This paper presents a mixed methods study to examine the role of RIMs in balancing alignment and diversity of RE practices in four automotive companies. Our analysis is based on data from systems engineering tools, 11 semi-structured interviews, and a survey to validate findings and suggestions. We found that balancing alignment and diversity of RE practices is important to consider when defining RIMs. We further investigated enablers for this balance and actions that practitioners take to achieve it. From these factors, we derived and evaluated recommendations for managing RIMs in practice that take into account the lifecycle of requirements and allow for diverse practices across sub-disciplines in early development, while enforcing alignment of requirements that are close to release.

show abstract

Section: Suggestions For Balancing Alignment and Diversitymentioning

confidence: 98%

Why and how to balance alignment and diversity of requirements engineering practices in automotive

Wohlrab

Knauss

Pelliccione

2020

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…The architect focuses on quality attributes (QA) and architecturally significant requirements (ASR) (Faber, 2010;Woods, 2016;Larrucea et al, 2018;Waterman, 2018a); identifies defects that are key to sustainability and evolution (Britto et al, 2016); manages architecture and monitors the current state of architecture (Martini & Bosch, 2016;Holmes & Nicolaescu, 2017); defines the most important characteristics (Martensson et al, 2019); communicates clearly and continuously the importance of the main ASR (Martensson et al, 2019); has feedback from the team or analysis tools on the status of the system, to understand if the architectural requirements are at risk (Martensson et al, 2019).…”

Section: Focus On Qa and Asrmentioning

confidence: 99%

“…The architect defines boundaries and work frames, selects templates and components (Madison, 2010;Durdik, 2011); documents top-level macro architecture (Gerdes et al, 2016); creates a high-level design, in particular, interactions among components/services (Shahin et al, 2019); uses architecture standards, reference architectures and well-accepted architectural principles to gain control of complexity (Sturtevant, 2017;Bass, 2019); establishes and refines conventions for structuring large scale software systems (Bass, 2019); creates a software structure that enables the autonomy and effectiveness of the developers (Martensson et al, 2019); manages architectural health as a codebase grows (Sturtevant, 2017); uses good practices to keep designs simple (Waterman, 2018a).…”

Section: Simple High-level Designmentioning

confidence: 99%

“…The architect's main result of work is decisions, not documentation (Poort, 2014); delays decisions, plans for options, and thinks in the direction of the Minimum Viable Architecture (MVA) (Blair et al, 2010;Madison, 2010;Hadar & Sherman, 2012;Buschmann & Henney, 2013;Erder & Pureur, 2016;Holmes & Nicolaescu, 2017;Waterman, 2018a;Shahin et al, 2019); takes responsibility for decisions that are risky, expensive, and difficult to change (Woods, 2016;Bass, 2017), uses pragmatic modeling (Hohpe et al, 2016;Zimmermann, 2016).…”

Section: Planning For Options and Delay Of Decisionsmentioning

confidence: 99%

“…The architect is involved in all stages of the development process (Hadar & Sherman, 2012); evaluates a design, code, and functionality -uses tools (Madison, 2010;Mirakhorli & Cleland-Huang, 2013); rules the delivery process (Erder & Pureur, 2016); maximizes the team's architectural agility (Waterman, 2018a); places greater emphasis on evolutionary changes (Shahin et al, 2019); helps build architectures that are responsive to needs over time (Shahin et al, 2019); balances focus on agile process and agile architecture (Sturtevant, 2017); uses an agile process to create a change-tolerant architecture (Waterman, 2018a); proves the architecture with code iteratively (Madison, 2010;Waterman, 2018a).…”

Section: Additional Readingmentioning

confidence: 99%

See 2 more Smart Citations

Untitled

2019

Balkans JETSS

View full text Add to dashboard Cite

Balkans Journal of Emerging Trends in Social Sciences-Balkans JETSS Aims and Scope The mission of Balkans JETSS is to publish peer-review empirical research papers that test, extend or build theory and contribute to practice. All empirical methods-including, but not limited to, qualitative, quantitative, field, laboratory, and combination methods are welcome. Empirical, theoretical and methodological articles from all major fields of economics, management, tourism, law and the like are featured in the journal. Theoretical and/or review articles that integrate existing bodies of research and that provide new insights into the field are also encouraged. To be published in the Balkans JETSS, a manuscript must take strong empirical and/or theoretical contributions to the subject field. Consequently, preference is given to submissions that test, extend or build strong theoretical frameworks while empirically examining issues with high importance for theory and practice. The journal is not tied to any particular discipline, level of analysis, or national context. Although, it focuses on Balkans region, all papers from related fields on any region or country are highly encouraged. Single country studies, multi-country or regional studies can be submitted. Manuscripts should not exceed 16 pages (450 word per page). This page limit includes all figures, tables, appendices and references. Copyright information For Authors As soon as an article is accepted for publication, authors will be requested to assign copyright of the article (or to grant exclusive publication and dissemination rights) to the publisher. This will ensure the widest possible protection and dissemination of information under copyright laws.

show abstract

An Analysis of IT Project Management Across Companies in an International Scenario

Andrade

Sadaoui

2018

Communications in Computer and Information Science

View full text Add to dashboard Cite

Agility, Risk, and Uncertainty, Part 1: Designing an Agile Architecture

Cited by 11 publications

References 1 publication

Why and how to balance alignment and diversity of requirements engineering practices in automotive

Why and how to balance alignment and diversity of requirements engineering practices in automotive

Untitled

An Analysis of IT Project Management Across Companies in an International Scenario

Contact Info

Product

Resources

About