Fetching the paper…
Reading the bibliography…
Decision-making is a key software engineering skill.
B. W. Boehm, “A spiral model of software development and enhancement,” Computer , vol. 21, no. 5, pp. 61–72, 1988
1988
Earlier work this paper cites.
S. P. Davies, “Characterizing the program design activity: Neither strictly top-down nor globally opportunistic,” Behaviour & Information Technology , vol. 10, no. 3, pp. 173–190, 1991
1991
Earlier work this paper cites.
D. E. Perry and A. L. Wolf, “Foundations for the study of software architecture,” ACM SIGSOFT Software Engineering Notes , vol. 17, no. 4, pp. 40–52, 1992
1992
Earlier work this paper cites.
W. Cunningham, “The WyCash portfolio management system,” ACM SIGPLAN OOPS Messenger , vol. 4, no. 2, pp. 29–30, 1992
1992
Earlier work this paper cites.
M. B. Miles and A. M. Huberman, Qualitative Data Analysis: An Expanded Sourcebook . SAGE Publications, 1994
1994
Earlier work this paper cites.
E. Gamma, R. Johnson, R. Helm, R. E. Johnson, and J. Vlissides, Design Patterns: Elements of Reusable Object-Oriented Software . Pearson, 1995
1995
Earlier work this paper cites.
K. Beck, R. Crocker, G. Meszaros, J. O. Coplien, L. Dominick, F. Paulisch, and J. Vlissides, “Industrial experience with design patterns,” in IEEE International Conference on Software Engineering , 1996, pp. 103–114
1996
Earlier work this paper cites.
B. Nuseibeh and S. Easterbrook, “Requirements engineering: A roadmap,” in Conference on the Future of Software Engineering , 2000, pp. 35–46
2000
Earlier work this paper cites.
V. Rajlich and N. Wilde, “The role of concepts in program comprehension,” in IEEE/ACM International Workshop on Program Comprehension , 2002, pp. 271–278
2002
Earlier work this paper cites.
G. Ruhe, “Software engineering decision support—a new paradigm for learning software organizations,” in International Workshop on Learning Software Organizations , 2002, pp. 104–113
2002
Earlier work this paper cites.
A. Aurum and C. Wohlin, “The fundamental nature of requirements engineering activities as a decision-making process,” Information and Software Technology , vol. 45, no. 14, pp. 945–954, 2003
2003
Earlier work this paper cites.
L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice . Addison-Wesley Professional, 2003
2003
Earlier work this paper cites.
F. Paetsch, A. Eberlein, and F. Maurer, “Requirements engineering and agile software development,” in IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises , 2003, pp. 308–313
2003
Earlier work this paper cites.
P. Berander and A. Andrews, “Requirements prioritization,” in Engineering and Managing Software Requirements . Springer, 2005, pp. 69–94
2005
Earlier work this paper cites.
B. Flyvbjerg, “Five misunderstandings about case-study research,” Qualitative Inquiry , vol. 12, no. 2, pp. 219–245, 2006
2006
Earlier work this paper cites.
M. Cherubini, G. Venolia, R. DeLine, and A. J. Ko, “Let’s go to the whiteboard: How and why software developers use drawings,” in SIGCHI Conference on Human Factors in Computing Systems , 2007, pp. 557–566
2007
Earlier work this paper cites.
A. Jansen, J. van der Ven, P. Avgeriou, and D. K. Hammer, “Tool support for architectural decisions,” in Working IEEE/IFIP Conference on Software Architecture , 2007, pp. 4–4
2007
Earlier work this paper cites.
C. Zannier, M. Chiasson, and F. Maurer, “A model of design decision making based on empirical results of interviews with software designers,” Information and Software Technology , vol. 49, no. 6, pp. 637–653, 2007
2007
Earlier work this paper cites.
J. Stylos and B. Myers, “Mapping the space of API design decisions,” in IEEE Symposium on Visual Languages and Human-Centric Computing , 2007, pp. 50–60
2007
Earlier work this paper cites.
A. Tang, M. H. Tran, J. Han, and H. van Vliet, “Design reasoning improves software design quality,” in International Conference on the Quality of Software Architectures , 2008, pp. 28–42
2008
Earlier work this paper cites.
J. Bloch, Effective Java . Addison-Wesley Professional, 2008
2008
Earlier work this paper cites.
R. C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship . Pearson Education, 2009
2009
Earlier work this paper cites.
J. Saldaña, The Coding Manual for Qualitative Researchers . SAGE Publications, 2009
2009
Cited alongside, same era.
D. Falessi, G. Cantone, R. Kazman, and P. Kruchten, “Decision-making techniques for software architecture design: A comparative survey,” ACM Computing Surveys , vol. 43, no. 4, pp. 1–28, 2011
2011
Cited alongside, same era.
A. J. Ko and P. K. Chilana, “Design, discussion, and dissent in open bug reports,” in iConference , 2011, pp. 106–113
2011
Cited alongside, same era.
P. Kruchten, R. L. Nord, and I. Ozkaya, “Technical debt: From metaphor to theory and practice,” IEEE Software , vol. 29, no. 6, pp. 18–21, 2012
2012
Cited alongside, same era.
C. Parnin, C. Treude, L. Grammel, and M.-A. Storey, “Crowd documentation: Exploring the coverage and the dynamics of API discussions on Stack Overflow,” Georgia Institute of Technology Technical Report , vol. 11, 2012
R. Dharani, Web API Design: Crafting Interfaces that Developers Love . Independently published, 2017
2017
Later among the works it cites.
D. Ford, T. Zimmermann, C. Bird, and N. Nagappan, “Characterizing software engineering work with personas based on knowledge worker actions,” in ACM/IEEE International Symposium on Empirical Software Engineering and Measurement , 2017, pp. 394–403
2017
Later among the works it cites.
N. Rios, R. O. Spínola, M. Mendonça, and C. Seaman, “The most common causes and effects of technical debt: First results from a global family of industrial surveys,” in ACM/IEEE International Symposium on Empirical Software Engineering and Measurement , 2018, pp. 1–10
2018
Later among the works it cites.
S. Baltes and S. Diehl, “Towards a theory of software development expertise,” in ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering , 2018, pp. 187–200
2018
Later among the works it cites.
alphaXiv searches the wider corpus for related work and actual follow-ups.
alphaXiv is searching for related work…
2012
Cited alongside, same era.
S. Balaji and M. S. Murugaiyan, “Waterfall vs. V-model vs. Agile: A comparative study on sdlc,” International Journal of Information Technology and Business Management , vol. 2, no. 1, pp. 26–30, 2012
2012
Cited alongside, same era.
M. Petre, “UML in practice,” in IEEE/ACM International Conference on Software Engineering , 2013, pp. 722–731
2013
Cited alongside, same era.
B. Sharif, N. Dragan, A. Sutton, M. L. Collard, and J. I. Maletic, “Identifying and analyzing software design activities,” in Software Designers in Action: A Human-Centric Look at Design Work . Chapman and Hall/CRC, 2013, pp. 153–174
2013
Cited alongside, same era.
J. Brunet, G. C. Murphy, R. Terra, J. Figueiredo, and D. Serey, “Do developers discuss design?” in Working Conference on Mining Software Repositories , 2014, pp. 340–343
2014
Cited alongside, same era.
N. Mangano, T. D. LaToza, M. Petre, and A. van der Hoek, “Supporting informal design with interactive whiteboards,” in SIGCHI Conference on Human Factors in Computing Systems , 2014, pp. 331–340
2014
Cited alongside, same era.
S. Baltes and S. Diehl, “Sketches and diagrams in practice,” in ACM SIGSOFT International Symposium on Foundations of Software Engineering , 2014, pp. 530–541
2014
Cited alongside, same era.
D. Hammer and L. K. Berland, “Confusing claims for data: A critique of common practices for presenting qualitative research on learning,” Journal of the Learning Sciences , vol. 23, no. 1, pp. 37–46, 2014
2014
Cited alongside, same era.
——, Just Enough Software Architecture: A Risk-Driven Approach . Prentice Hall, 2018
2018
Later among the works it cites.
G. Fairbanks, Clean Architecture: A Craftsman’s Guide to Software Structure and Design . Marshall & Brainerd, 2018
2018
Later among the works it cites.
T. Besker, A. Martini, and J. Bosch, “Software developer productivity loss due to technical debt—a replication and extension study examining developers’ development work,” Journal of Systems and Software , vol. 156, pp. 41–61, 2019
2019
Later among the works it cites.
——, “Supporting analysis of technical debt causes and effects with cross-company probabilistic cause-effect diagrams,” in IEEE/ACM International Conference on Technical Debt , 2019, pp. 3–12
2019
Later among the works it cites.
M. Petre, A. van der Hoek, and D. S. Bowers, “Software design as multiple contrasting dialogues,” in Psychology of Programming Interest Group 30th Annual Conference , 2019
2019
Later among the works it cites.
R. Verdecchia, P. Kruchten, and P. Lago, “Architectural technical debt: A grounded theory,” in European Conference on Software Architecture , 2020, pp. 202–219
2020
Later among the works it cites.
A. Shahbazian, S. Karthik, Y. Brun, and N. Medvidovic, “eQual: informing early design decisions,” in ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering , 2020, pp. 1039–1051
2020
Later among the works it cites.
P. L. Li, A. J. Ko, and A. Begel, “What distinguishes great software engineers?” Empirical Software Engineering , vol. 25, no. 1, pp. 322–352, 2020
2020
Later among the works it cites.
M. K. Scheuerman, K. Spiel, O. L. Haimson, F. Hamidi, and S. M. Branham, “HCI guidelines for gender equity and inclusivity,” in UMBC Faculty Collection , 2020
2020
Later among the works it cites.
T. D. LaToza, M. Arab, D. Loksa, and A. J. Ko, “Explicit programming strategies,” Empirical Software Engineering , vol. 25, no. 4, pp. 2416–2449, 2020
2020
Later among the works it cites.
M. Arab, J. Liang, Y. Yoo, A. J. Ko, and T. D. LaToza, “HowToo: A platform for sharing, finding, and using programming strategies,” in IEEE Symposium on Visual Languages and Human-Centric Computing , 2021, pp. 1–9
2021
Later among the works it cites.
“Swift.org—API design guidelines,” 2022, retrieved December 20, 2022 from https://www.swift.org/documentation/api-design-guidelines/
2022
Later among the works it cites.
“API design,” 2022, retrieved December 20, 2022 from https://martinfowler.com/tags/API%20design.html
2022
Later among the works it cites.
A. Mahadi, N. A. Ernst, and K. Tongay, “Conclusion stability for natural language based mining of design discussions,” Empirical Software Engineering , vol. 27, no. 1, pp. 1–42, 2022
2022
Later among the works it cites.
M. Arab, T. D. LaToza, J. Liang, and A. J. Ko, “An exploratory study of sharing strategic programming knowledge,” in SIGCHI Conference on Human Factors in Computing Systems , 2022, pp. 1–15
2022
Later among the works it cites.
2022
Later among the works it cites.
J. T. Liang, M. Arab, M. Ko, A. J. Ko, and T. D. LaToza, “Supplemental materials to “A qualitative study on the implementation design decisions of developers”,” 2023, available at https://doi.org/10.6084/m9.figshare.21820140
2023
Closest in time.