|Course Code :||2001WETSWT|
|Study domain:||Computer Science|
|Bi-anuall course:||Taught in academic years starting in an even year|
|Semester:||Semester: 2nd semester|
|Study load (hours):||168|
|Contract restrictions: ||No contract restriction|
|Language of instruction :||English|
|Exam period:||exam in the 2nd semester|
At the start of this course the student should have acquired the following competences:
An active knowlegde of :
(This course is taught in English)Specific prerequisites for this course:
The easiest way to satisfy these prerequisites is to have a passing grade for the course Software Engineering (BA 3 Computer Science).
- Practical programming experience, preferably in a team context..
- Profound knowledge about the testing of software (unit tests, regression tests)
- Knowledge about the various techniques applied during a software project (requirements, analysis, design, implementation, testing, maintenance).
- Knowledge about techniques for managing quality during a project (cost estimation, code reviews, metrics)
2. Learning outcomes
After this course, a student will be able to
As such, studens will obtain some of the core competences of a master in computer science. They learn to distinguish between various test strategies and select the most appropriate test techniques which allows them to select between available techniques. This selection is performed with the necessary depth, by exploiting the underlying theories as well as the practical experience. The assessment and improvement of the coverage of a test suite is part of research and development (knowing which techniques can be applied to create a strategic advantage over competitors), as well as fundamental research (knowing the current research questions within the discipline of software engineering).
- distinguish between various test strategies;
- select the most appropriate test techniques for a given test strategy;
- assess and improve the coverage of a test suite.
3. Course contents
De student will acquire experience with torough testing and verification of a software system, to guarantee with a certaing degree of confidence that a given software system meets its specification.
The course has a practical ring to it with a minimal theoretical content (taught as testing patterns; students have to deliver some of the lectures themselves), several lab-sessions (trying out several test techniques and strategies on an existing software system) and industrial guest speakers illustrating how testing is done in real projects.
From the academic year 2009-2012 onward, this course will be offered every 2 years. It will
be offered in 2009-2010; 2011-2012; ... but will be offered in 2010-2011; 2012-2013; .... The motivation for this organisation is the fact that this course explicitly invites industrial guest speakers; a feature well-appreciated by the fellow students. Offering the course every two years must guarantee that these industrial lectures attract sufficent participants.
4. Teaching method
Class contact teaching: LecturesPractice sessionsLaboratory sessions
Project-based work:In group
5. Assessment method and criteria
Examination: Practical examination
6. Study material
- Robert V. Binder, Testing Object-Oriented Systems (Models, Patterns, and Tools), Addison-Wesley, 2000.
The following study material can be studied on a voluntary basis:
7. Contact information
Prof. S. Demeyer [http://www.win.ua.ac.be/~sdemey/ ]
(+)last update: 07/02/2013 23:05 serge.demeyer