Requirements Engineering

Course content

Analysis and modelling of functional and non-functional requirements of software systems: (i) UML modelling (User Case-, Activity-, State-, Class-Diagram); (ii) Object-oriented analysis; (iii) Requirements engineering process; (iv) Requirements management; (v) Prototyping.

Learning outcomes

The graduate has basic knowledge of the quality assurance measures in software engineering, specifying the requirements, testing, debugging, build systems, and the practices of deployment and installation.

Recommended or required reading and other learning resources / tools

Books: Ian Sommerville, Software Engineering, 10th International edition, 2015; Frederick P. Brooks, The Mythical Man-Month, 1995; Bertrand Meyer, Agile!, 2014; Paul M. Duvall, Continuous Integration, 2007; Stephen P. Berczuk, Software Configuration Management Patterns, 2008; LIsa Crispin and Janet Gregory, Agile Testing, 2009; Gerard Meszaros, xUnit Test Patterns, 2007; Jez Humble and David Farley, Continous Delivery, 2011; Martin Fowler, UML Distilled, 2004; Erich Gamma and Richard Helm and Ralph Johnson and John Vlissides, Design Patterns, 1995; Robert C. Martin, Agile Software Development, 2002; Martin Fowler, Patterns of Enterprise Application Architecture, 2003; Axel van Lamsweerde, "Requirements Engineering: From System Goals to UML Models to Software Specifications", John Wiley & Sons, 2009; Klaus Pohl, "Requirements Engineering", Springer 2010
Professional Journals: ACM, IEEE

Mode of delivery

1 ECTS Lecture, 2 ECTS Tutorial

Prerequisites and co-requisites

Software Engineering 1 and 2

Assessment methods and criteria

Lecture: Exam; Tutorial: Continuous Assessment