References

Adzic, Gojko. 2012. Impact Mapping: Making a Big Impact with Software Products and Projects. Provoking Thoughts.

Aniche, Maurício. 2022. Effective Software Testing: A Developer’s Guide. Manning.

Bass, Len, Paul Clements, and Rick Kazman. 2012. Software Architecture in Practice. Third. Addison-Wesley Professional.

Boissenin, Stéphane, and Elisabeth Salavy. 2010. “A320 Family/Evolution of Groundspoiler Logic.” Safety First Magazine 09.

Brun, Yuriy, and Alexandra Meliou. 2018. “Software Fairness.” In Proceedings of the 2018 26th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering, 754–59.

Dick, Jeremy, Elizabeth Hull, and Ken Jackson. 2017. Requirements Engineering, 4th Edition. Springer.

Easterbrook, Steve. 2006. “Requirements Engineering - University of Toronto Course.” http://www.cs.toronto.edu/~sme/CSC340F.

Ferrario, Maria Angela, Will Simm, Stephen Forshaw, Adrian Gradinar, Marcia Tavares Smith, and Ian Smith. 2016. “Values-First SE: Research Principles in Practice.” In 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-c), 553–62. IEEE.

Finkelstein, Anthony, and John Dowell. 1996. “A Comedy of Errors: The London Ambulance Service Case Study.” In Proceedings of the 8th International Workshop on Software Specification and Design.

Gabriel, Iason. 2020. “Artificial Intelligence, Values, and Alignment.” Minds and Machines 30 (3): 411–37.

Glinz, Martin. 2020. A Glossary of Requirements Engineering Terminology. International Requirements Engineering Board (http://ireb.org).

Gotterbarn, Donald, Keith Miller, Simon Rogerson, Steve Barber, Peter Barnes, Ilene Burnstein, Michael Davis, et al. 2001. “Software Engineering Code of Ethics and Professional Practice.” Science and Engineering Ethics 7 (2): 231–38.

Gottesdiener, Ellen. 2002. Requirements by Collaboration: Workshops for Defining Needs. Addison-Wesley Professional.

Hall, Anthony. 2010. “E = mc² Explained.” In Software Requirements and Design: The Work of Michael Jackson, edited by Bashar Nuseibeh and Pamela Zave. Good Friends Publishing Company.

Hammond, Jonathan, Rosamund Rawlings, and Anthony Hall. 2001. “Will It Work?” In Proceedings Fifth IEEE International Symposium on Requirements Engineering, 102–9. IEEE.

Hofer, Stefan, and Henning Schwentner. 2021. Domain Storytelling: A Collaborative, Visual, and Agile Way to Build Domain-Driven Software. Pearson Education.

Howard, Ronald Arthur, Clinton D Korver, and Bill Birchard. 2008. Ethics for the Real World: Creating a Personal Code to Guide Decisions in Work and Life. Harvard Business Press.

Hussain, Waqar, Harsha Perera, Jon Whittle, Arif Nurwidyantoro, Rashina Hoda, Rifat Ara Shams, and Gillian Oliver. 2020. “Human Values in Software Engineering: Contrasting Case Studies of Practice.” IEEE Transactions on Software Engineering.

IEEE. 2018. “ISO/IEC/IEEE International Standard - Systems and Software Engineering – Life Cycle Processes – Requirements Engineering.”

Jackson, Michael. 1995a. Software Requirements & Specifications: A Lexicon of Practice, Principles and Prejudices. ACM Press/Addison-Wesley Publishing Co.

———. 1995b. “The World and the Machine.” In 17th International Conference on Software Engineering (ICSE’95).

———. 2001. Problem Frames: Analysing and Structuring Software Development Problems. Addison-Wesley.

Jackson, Michael, and Pamela Zave. 1995. “Deriving Specifications from Requirements: An Example.” In 17th International Conference on Software Engineering (ICSE’95).

Kniberg, Henrick. 2013. “What Is Agile?” 2013. https://blog.crisp.se/wp-content/uploads/2013/08/20130820-What-is-Agile.pdf.

Ladkin, Peter B. 1995. “Analysis of a Technical Description of the Airbus A320 Braking System.” High Integrity Systems 1: 331–50.

Lamsweerde, Axel van. 2008. “Requirements Engineering: From Craft to Discipline.” In Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering, 238–49.

———. 2009. Requirements Engineering: From System Goals to UML Models to Software Specifications. John Wiley & Sons.

Larman, Craig, and Victor R Basili. 2003. “Iterative and Incremental Developments: A Brief History.” Computer 36 (6): 47–56.

Letier, Emmanuel. 2001. “Reasoning about Agents in Goal-Oriented Requirements Engineering.” PhD thesis, PhD thesis, Université catholique de Louvain.

Nagy, Gáspár, and Seb Rose. 2018. The BDD Books-Discovery: Explore Behaviour Using Examples. Leanpub.

Nahar, N., H. Zhang, G. Lewis, S. Zhou, and C. Kastner. 2023. “A Meta-Summary of Challenges in Building Products with ML Components – Collecting Experiences from 4758+ Practitioners.” In 2023 IEEE/ACM 2nd International Conference on AI Engineering – Software Engineering for AI (CAIN), 171–83. IEEE Computer Society. https://doi.org/10.1109/CAIN58948.2023.00034.

North, Dan. 2021. “We Need to Talk about Testing.” 2021. https://dannorth.net/2021/07/26/we-need-to-talk-about-testing/.

Nuseibeh, Bashar. 2001. “Weaving Together Requirements and Architectures.” Computer 34 (3): 115–19.

Nuseibeh, Bashar, and Steve Easterbrook. 2000. “Requirements Engineering: A Roadmap.” In Proceedings of the Conference on the Future of Software Engineering. ICSE ’00. Limerick, Ireland.

Parnas, David Lorge, and Jan Madey. 1995. “Functional Documents for Computer Systems.” Science of Computer Programming 25 (1): 41–61.

Patton, Jeff. 2014. User Story Mapping: Discover the Whole Story, Build the Right Product. O’Reilly.

Pezzè, Mauro, and Michal Young. 2008. Software Testing and Analysis: Process, Principles, and Techniques. John Wiley & Sons.

Richards, Mark, and Neal Ford. 2020. Fundamentals of Software Architecture: An Engineering Approach. O’Reilly Media.

Robertson, Suzanne, and James Robertson. 2012. Mastering the Requirements Process: Getting Requirements Right. Addison-wesley.

Rook, Paul. 1986. “Controlling Software Projects.” Software Engineering Journal 1 (1): 7–16.

Rose, Seb, and Gáspár Nagy. 2021. The BDD Books-Formulation: Document Examples with Given/When/Then. Leanpub.

Rose, Seb, Matt Wynne, and Aslak Hellesoy. 2015. The Cucumber for Java Book: Behaviour-Driven Development for Testers and Developers. The Pragmatic Bookshelf.

Royce, Winston W. 1970. “Managing the Development of Large Software Systems: Concepts and Techniques.” In IEEE WESCON.

Rozanski, Nick, and Eoin Woods. 2012. Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Addison-Wesley.

Ryan, Kevin. 2020. “We Should Teach Our Students What Industry Doesn’t Want.” In 2020 IEEE/ACM 42nd International Conference on Software Engineering: Software Engineering Education and Training (ICSE-SEET), 103–6. IEEE.

Scharinger, Boris, Markus Borg, Andreas Vogelsang, and Thomas Olsson. 2022. “Can RE Help Better Prepare Industrial AI for Commercial Scale?” IEEE Software 39 (6): 8–12.

Smart, John Ferguson. 2023. BDD in Action: Behavior-Driven Development for the Whole Software Lifecycle, 2nd Edition. Manning.

Swartout, William, and Robert Balzer. 1982. “On the Inevitable Intertwining of Specification and Implementation.” Communications of the ACM 25 (7): 438–40.

Wiegers, Karl, and Joy Beatty. 2013. Software Requirements, 3rd Edition. Pearson Education.

Zave, Pamela. 1997. “Classification of Research Efforts in Requirements Engineering.” ACM Computing Surveys 29 (4): 315–21.

Zave, Pamela, and Michael Jackson. 1997. “Four Dark Corners of Requirements Engineering.” ACM Transactions on Software Engineering and Methodology (TOSEM) 6 (1): 1–30.