Literatuur

Volgende boeken zijn aangeraden als algemene achtergrondinformatie bij de cursus. Ze zijn allen beschikbaar in de bibliotheek van de UA.

• [Ghez02] Fundamentals of Software Engineering, C. Ghezzi, M. Jazayeri, D. Mandroli, 2nd edition, Prentice Hall, 2002.
• Timeless because of its emphasis on principles, but a bit difficult.
• [ online resources for the 2nd edition of the book: http://www.prenhall.com/ghezzi ]
• [Pres00] Software Engineering - A Practitioner's Approach, R. Pressman, Mc-Graw Hill, Fifth Edn., 2000.
• Very practical and quite deep, but contains a lot of material and is therefore quite thick and a bit expensive.
• [online resources for the 5th edition of the book: http://www.mhhe.com/engcs/compsci/pressman/ ]
• [online resources from the author of the book: http://www.rspa.com/spi/index.html ]
• [Somm05] Software Engineering, I. Sommerville, Addison-Wesley, Ninth Edn., 2011
• Very popular and broad plus reads quite easily, but often lacks profoundness.
• [ online resources for the 9th edition of the book: http://www.SoftwareEngineering-9.com/ ]

Extra information on SCRUM; the process you will use for the Capstone Project

• [Rubi13] Essential Scrum: A Practical Guide to the most popular agile process. Kenneth S.Rubin. Addison-Wesley, 2013

Introduction (UML)

• UML Modeling Language -- Notation Guide, version 1.3
• [ http://www.uml.org/ ]
• The specification of the UML notation.
• "Iterative and Incremental Development: A Brief History"Craig Larman and Victor R. Basili, IEEE Computer, June 2003
• [ local copy | http://www.craiglarman.com/wiki/downloads/misc/history-of-iterative-larman-and-basili-ieee-computer.pdf ]
• A historical overview on how the mindset of software projects changed from waterfall to iterative and incremental development.
• "The Five Orders of Ignorance" (Phillip G. Armour), Communications of the ACM (October 2000)
• [ local copy | http://dx.doi.org/10.1145/352183.352194 ]
• How Many Millions of Lines of Code Does It Take?
• "How many millions of lines of code does it take to make the modern program, web service, car, or airplane possible?The range is extraordinary: the average iPhone app has less than 50,000 lines of code, while Google’s entire code base is two billion lines for all services. |
• [ https://www.visualcapitalist.com/millions-lines-of-code/ ]
• Apollo’s computer “eventually required about 145,000 lines of code in all, compared with about 62 million lines of code required today to operate Facebook and more than two billion lines of code for Google,” according to the Journal.
• [ https://fedtechmagazine.com/article/2019/07/tech-behind-apollo-11s-guidance-computer ]
• The code is on github [ https://github.com/chrislgarry/Apollo-11 ]

Requirements 

• Applying Use Cases - a Practical Guide, Geri Schneider, Jason, P. Winters, Addison-Wesley, 1998.
• An easy to read an practical guide on how to iteratively develop a set of use cases and how to exploit it for project planning.
• Object-Oriented Software Engineering: A Use-Case Driven Approach, I. Jacobson et. al., Addison-Wesley, 1992.
• The book introducing use cases. Also tells how to use them during a complete software project.
• A dilbert cartoon about requirements and negotiating with customers
• [ JPG ]
• "User stories as lightweight requirements for agile clinical decision support development", Vaishnavi Kannan,  Mujeeb A Basit,  Puneet Bajaj,  Angela R Carrington,  Irma B Donahue, Emily L Flahaven,  Richard Medford,  Tsedey Melaku,  Brett A Moran,  Luis E Saldana. In  Journal of the American Medical Informatics Association, Volume 26, Issue 11, November 2019, Pages 1344–1354
• [ local copy | https://doi.org/10.1093/jamia/ocz123 ]
• An experience report applying user stories in combination with use case diagrams to manage the requirements in a health care application. In healthcare, human lives might be affected, so explict requirements play an important role.
• "Structuring Use Cases with Goals", Alister Cockburn, Journal of Object-Oriented Programing Sept-Oct & Nov-Dec 1997.
• [ local copy |  http://alistair.cockburn.us/Structuring+use+cases+with+goals ] 
• Very popular article giving concrete and practical guidelines concerning use-cases.
• Ian Alexander, "Misuse Cases: Use Cases with Hostile Intent" in IEEE Software, vol. 20, no. 01, pp. 58-66, 2003. doi: 10.1109/MS.2003.1159030
• [ local copy | https://doi.org/10.1109/MS.2003.1159030 ]
• Explains a negative form of a use case; a negative scenario. Use- and misuse-case diagrams are valuable in threat and hazard analysis.
• Jane Cleland-Huang and Michael Vierhauser, "Discovering, Analyzing, and Managing Safety Stories in Agile Projects," 2018 IEEE 26th International Requirements Engineering Conference (RE), 2018, pp. 262-273, doi: 10.1109/RE.2018.00034.
• [ local copy | https://doi.org/10.1109/RE.2018.00034 ]
• Addresses the specific problems of discovering, analyzing, specifying, and managing safety requirements within the agile Scrum process.

Software Architecture

• Pattern-Oriented Software Architecture: A System of Patterns, Frank Buschman, Regine Meunier, Hans Rohnert, Peter Somerlad, Michael Stal, Wiley and Sons, 1996.
• Introduces architectural styles in pattern form. Also covers some design patterns and idioms.
• Design Patterns: Elements of Reusable Object-Oriented Software, Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Addison-Wesley, 1995.
• The classic. At design level but also viewed as ìmicro-architecture.
• Software architecture: perspectives on an emerging discipline, Mary Shaw, David Garlan, Prentice-Hall, 1996.
• The book introducing software architecture.
• Software architecture in practice, Len Bass, Paul Clements, Rick Kazman, Addison-Wesley, 1998.
• A very deep and practical treatment of software architecture.
• Philippe Kruchten "The 4+1 View Model of Architecture ", IEEE Software, November 1995 (Vol. 12, No. 6) pp. 42-50.
• [ local copy | http://doi.ieeecomputersociety.org/10.1109/52.469759] 
• A paper that illustrates convincingly the need for various persepectives on the design of a system.

Project Management 

• Software Project Management, B. Hughes and M. Cotterell, McGraw Hill, 2006. (4th Edition)
• Good practical examples on PERT, Gantt, Time-sheets, ...
• Using Belbin's leadership role to improve team effectiveness: An empirical investigation. Sallie M. Henry, K. Todd Stevens,Journal of Systems and Software, Volume 44, Issue 3, January 1999, Pages 241-250, ISSN 0164-1212.
• [ local copy | http://dx.doi.org/10.1016/S0164-1212(98)10060-2 ]
• Several on-line tests existed to determine your preferred role in a team. However, they are deemed inappropriate, even illegal.
• All Late Projects Are the Same. Tom De MarcoIEEE Software, pp. 102-103, November/December, 2011
• [ local copy | https://doi.ieeecomputersociety.org/10.1109/MS.2011.134 ]
• All projects that finish late have this one thing in common … they started late.

Design by Contract 

• Object-Oriented Software Construction, B. Meyer, Prentice Hall, Second Edn., 1997.
• The book introducing Design by Contract. Also an excellent treatment on the doís and doníts of object-oriented development.
• "Put it in the contract: The lessons of Ariane", Jean-Marc Jézéquel and Bertrand Meyer, IEEE Computer, January 1997, Vol30, no. 2, pages 129-130.
• [ local copy | original copy: http://www.irisa.fr/pampa/EPEE/Ariane5.html] 
• A (heatedly debated) column arguing that Design by Contract would have prevented the crash of the first Ariane5 missile. 
• "Critique of 'Put it in the contract: The lessons of Ariane'", Ken Garlington. Technical paper.
• [ local copy | original copy: http://home.flash.net/~kennieg/ariane.html] 
• An article providing counterarguments to the former. Yet by doing so gives an excellent comparison with Testing and Code Inspection.
• "Simplifying Microservice testing with Pacts",  Ron Holshausen.
• Contract testing is the primary way to ensure that systems work as expected for micro-services.
• [ https://dius.com.au/2014/05/19/simplifying-micro-service-testing-with-pacts/ ]
• Tutorial:  https://docs.pact.io/
• "Programming with Assertions", SUN
• An article discussing how to use ASSERTs, one of the new features since Java 1.4. Among others, it confirms that Java-assertions are too weak for a generic "design by contract".
• [ https://docs.oracle.com/javase/7/docs/technotes/guides/language/assert.html ]
• "iContract: Design by Contract in Java", Oliver Enseling
• An article (including java sources) discussing a tool for contracts in Java.
• [ https://www.infoworld.com/article/2074956/icontract-design-by-contract-in-java.html ]

Testing

• Tweet (joke) -- all unit tests are passing
• https://twitter.com/olafurw/status/1578704185809244160?s=11&t=mdYnxnMXgxYBEhH7anVCgQ
• An illustration on the need for integration - system and acceptance tests
• "A Survey of Unit Testing Practices", Per Runeson
• Disusses the state-of-the-practive with unit testing. A nice quote "Most respondents said that running all unit tests took just seconds or minutes, but some respondents had unit test suites that took hours to execute".
• [ local copy | original: http://dx.doi.org/10.1109/MS.2006.91 ] 
• "Test Fatigue", Gerard J. Holzman. in IEEE Software, vol. 37, no. 4, pp. 11-16, July-Aug. 2020
• Argues that the more rigorous testing you do, the more problems you will find. Thus it is tempting to test less … or not?
• [ local copy | original: https://doi.org/10.1109/MS.2020.2986107 ]

Formal Specifications

• D. Cofer et al., "A Formal Approach to Constructing Secure Air Vehicle Software," in Computer, vol. 51, no. 11, pp. 14-23, Nov. 2018, doi: 10.1109/MC.2018.2876051.
• [ local copy | https://doi.org/10.1109/MC.2018.2876051 ]
• J. Kapinski, J. V. Deshmukh, X. Jin, H. Ito and K. Butts, "Simulation-Based Approaches for Verification of Embedded Control Systems: An Overview of Traditional and Advanced Modeling, Testing, and Verification Techniques," in IEEE Control Systems Magazine, vol. 36, no. 6, pp. 45-64, Dec. 2016
• [ local copy | https://doi.org/10.1109/MCS.2016.2602089 ]
• A comprehensive overview of techniques for safety-criticial systems. Explains well how formal methods complement simulation and testing.
• A HTML page with errors
• [ formalspec.html ]
• A sample page used to start up the lecture.

Domain Models

• The software specification cartoon
• One of the earlier jokes on the various stages of a software project. Numerous versions circulate on the internet; the following give just a flavour of what's out there.
• [ Black and White Version | Coloured Version | Coloured Version (newer) ]
• "How the Boeing 737 Max Disaster Looks to a Software Developer" Gregory Travis. IEEE Spectrum, April 18.
• [ local copy | https://spectrum.ieee.org/aerospace/aviation/how-the-boeing-737-max-disaster-looks-to-a-software-developer ]
• "The Boeing 737 MAX: Lessons for Engineering Ethics." Herkert, J., Borenstein, J. & Miller, K.  Science and Engineering Ethics (2020).
• [ local copy | https://doi.org/10.1007/s11948-020-00252-y ] 
• Product Line Hall of Fame
• http://splc.net/fame.html
• A list of software companies who organised their software production process accoring to a softwrae-product-lines approach

Quality Control

• Case Study – Denver International Airport Baggage Handling System – An illustration of ineffectual decision making
• [local copy | http://calleam.com/WTPF/?page_id=2086 | http://calleam.com/WTPF/wp-content/uploads/articles/DIABaggage.pdf ]
• A report on one of the best-known examples of how modern software development may screw up.
• Case Study - FBI Sentinel System
• [ local copy | http://doi.ieeecomputersociety.org/10.1109/MC.2012.2 ]
• Why the FBI Can’t Build a Case Management System (Jerome W. Israel). IEEE Software, June 2012
• A report illustrating why a seemingly innocent project (a database of FBI case files) can become overly complex if not handled properly. Several important lessons learned are deduced.
• Tacoma Narrows Bridge Disaster
• [ https://en.wikipedia.org/wiki/Tacoma_Narrows_Bridge ] 
• We are not the only ones who screw up; this is the famous example of the collapsing bridge.

Software Metrics

• The weather on D-Day
• [http://medium.com/history-and-politics/85ea0491a14f]
• Illustrating how crucial a good estimation might be
• Software Metrics: A rigorous & Practical Approach, Norman E. Fenton, Shari l. Pfleeger, Thompson Computer Press, 1996. 
• Thorough treatment of metrics theory with lots of advice to make it digestible.
• Fingers in the air: a Gentle Introduction to Software Estimation 
• [local copy | http://www.methodsandtools.com/archive/archive.php?id=79] 
• An article on the distinction between estimates, targets and commitments, incl. the famous "cone of uncertainty".
• Software Metrics (Patti Beadles) [rec.humor.funny]
• A humorous list of software metrics. 
• [http://www.netfunny.com/rhf/jokes/93q4/metrics.html ] 
• A cartoon on measuring the output of Quality reviews using wtf / minute
• [ http://www.osnews.com/images/comics/wtfm.jpg ] 
• Estimating With Use Case Points 
• [http://www.methodsandtools.com/archive/archive.php?id=25] 
• An article on use-case points, as a way to quantify the size and complexity of a requirement sepcification

Refactoring

•  Refactoring, Improving the Design of Existing Code by Martin Fowler, Addison-Wesley, 1999.
• A practical book explaining when and how to use refactorings to cure some typical code-smells.
• Object-Oriented Reengineering Patterns by Serge Demeyer, Stéphane Ducasse and Oscar Nierstrasz, Morgan Kaufmann, 2002.
• A book describing how one can reengineer object-oriented legacy systems.
• Code smells
• [ http://c2.com/cgi/wiki?CodeSmell ] 
• Wiki-web with discussion on code smells, i.e. symptoms of poorly designed code.
• Refactoring
• [ http://www.refactoring.com/ ] 
• refactoring web-site discussing solutions for the above code-smells.
• "Big Ball of Mud", Brian Foote and Joseph Yoder; Fourth Conference on Patterns Languages of Programs (PLoP '97/EuroPLoP '97)
• [ local copy | http://www.laputan.org/mud/mud.html ] 
• Quite a funny read, illustrating very well how software systems degrade into poor designs.

Conclusion (Ethics and Professional Practice)

• Software Engineering Code of Ethics and Professional Practice
• [ https://ethics.acm.org/code-of-ethics/software-engineering-code/ ]
• VW Emissions scandal
• [ http://calleam.com/WTPF/?p=7666 ] 
• If you would work for Volkswagen and they ask you to install software on the car to cheat emission testing. What would you do?
• Facebook / Twitter API spying
• [ https://www.cjr.org/tow_center/facebook-twitter-api-restrictions.php ]
• If your master thesis would study how social media affects elections, would you install spying software on the API of social media giants (facebook, twitter, )
• The 'Killer Robot' Case is an especially relevant (and humerous !) series of newspaper articles describing an imaginary situation of a piece of software that kills people and how it could have been avoided. (Beware, the complete text is about 70 pages long; don't read it over a modem)
• local copy (zipped HTML Files)
• https://onlineethics.org/cases/case-killer-robot
• The "No Silver Bullet" paper 
• local copy: p12_3_nosilverbullet.pdf
• original: https://doi.org/10.1109/MC.1987.1663532
• A very influential paper written by Fred Brooks, who in 1999 received the Turing Award for "landmark contributions to computer architecture, operating systems, and software engineering".