The DOI matches its Crossref record.
Elaboration on an integrated architecture and requirement practice: Prototyping with quality attribute focus
Open accessAbstract
This experience report builds on an earlier study in which we interviewed eight project teams that were using iterative incremental lifecycles. In the study, we captured the practices the teams felt contributed to rapid delivery. We identified a mix of Agile and architecture practices that teams apply to rapidly field software and minimize disruption and delay. In this paper, we elaborate one practice from the study, prototyping with quality attribute focus. We compared two experiences in prototyping focused on quality attribute considerations applied on Scrum projects. We observe through interviews that feature development and prototyping practice spans multiple levels: feature development/sprint, release planning, and portfolio planning. We also observe other factors including rapid trade-off analysis, flexible architecture, and adoption of a set of enabling prototyping guidelines. The analysis of the observations sheds light on several aspects of the practice that enable the team to respond quickly and efficiently when prototype feedback suggests architectural change.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
In the citing paper
“Thus, prototyping is often used within agile development to detail and validate requirements, and to reduce uncertainty (Bellomo et al. 2013).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bellomo et al. 2013
In the citing paper
“Similarly, Bellomo et al. describe how a company consciously selects the breadth and degree of refinement of prototype scope to match the prototyping purpose, and to validate the concept in focus (Bellomo et al. 2013).”
From An empirically based model of software prototyping: a mapping study and a multi-case study (2023) · cites this paper as Bellomo et al. 2013
Citations
Cites
No references could be resolved yet.
Research works printed but not linked: 7
- Bellomo, A Study of Enabling Factors for Rapid Fielding, Combined Practices to Balance Tension between Speed and Stability
- Beck, Agile Manifesto
- 10.1109/2.59 · DOI
- Royce, Measuring Agility and Architectural Integrity, International Journal of Software and Informatics, 5
- 10.1109/ICRE.2002.1048516 · DOI
- Schwaber, 2011, Scrum guidebook, Scrum.org and Scrum Inc
- Bass, Software Architecture in Practice, Third Edition
Cited by
Sorted by citations
An empirically based model of software prototyping: a mapping study and a multi-case study
Bjarnason, E., Lang, F., & Mjöberg, A. (2023) · Empirical Software Engineering · doi:10.1007/s10664-023-10331-w · Cited by 75
Metadata
- Authors
- Bellomo, S., Nord, R. L., & Ozkaya, I.
- Affiliations
- Software Engineering Institute (US)
- ORCID
- Nord, Robert L.
- Venue
- 2013 2nd International Workshop on the Twin Peaks of Requirements and Architecture (TwinPeaks)
- Publisher
- IEEE
- Published
- 2013-05
- Pages
- 8-13
- OpenAlex
- W1993328424
- Cited by
- 9
- References
- 0
- Citations by year
- 2023: 2 · 2022: 1 · 2021: 1 · 2019: 1 · 2018: 1 · 2016: 1 · 2014: 2
- FWCI
- 0.67
- Type
- conference paper
- Language
- en
- Open access
- green
- figshare.com
- Licence
- cc-by
- Locations
- KiltHub Repository (submittedVersion)
- Figshare (submittedVersion, cc-by)
- KiltHub Repository
- Funders
- U.S. Department of Defense
- Carnegie Mellon University
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Engineering › Control and Systems Engineering › Systems Engineering Methodologies and Applications
- Keywords
- prototype development, quality attributes, software architecture, agile practices, Scrum, iterative incremental development, feature development, release planning, portfolio planning, trade-off analysis, flexible architecture, architectural transformation, rapid delivery
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
