Search programme

​Use the search function to search amongst programmes at Chalmers. The study programme and the study programme syllabus relating to your studies are generally from the academic year you began your studies.

Syllabus for

Academic year
DAT261 - Model-based testing
 
Syllabus adopted 2015-02-12 by Head of Programme (or corresponding)
Owner: MPSOF
7,5 Credits
Grading: TH - Five, Four, Three, Not passed
Education cycle: Second-cycle
Major subject: Computer Science and Engineering, Information Technology
Department: 37 - COMPUTER SCIENCE AND ENGINEERING


Teaching language: English

Course module   Credit distribution   Examination dates
Sp1 Sp2 Sp3 Sp4 Summer course No Sp
0115 Written and oral assignments 3,0c Grading: UG   3,0c    
0215 Examination 4,5c Grading: TH   4,5c   31 May 2017 am SB,  21 Aug 2017 pm M

In programs

MPIDE INTERACTION DESIGN AND TECHNOLOGIES, MSC PROGR, Year 2 (elective)
MPSOF SOFTWARE ENGINEERING AND TECHNOLOGY, MSC PROGR, Year 1 (compulsory elective)

Examiner:

Professor  Gerardo Schneider


Replaces

DAT260   Model-based testing


  Go to Course Homepage

Eligibility:


In order to be eligible for a second cycle course the applicant needs to fulfil the general and specific entry requirements of the programme that owns the course. (If the second cycle course is owned by a first cycle programme, second cycle entry requirements apply.)
Exemption from the eligibility requirement: Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling these requirements.

Course specific prerequisites

To be eligible for the course the student should have a bachelor degree in Software Engineering, Computer Science or equivalent, including a completed course in programming. Knowledge of data structures and propositional logic is recommended.

Aim

Testing is one of the most used verification and validation technique in industry. This course provides the students with a general background on testing techniques, with a focus on the theory and practice of model-based testing.

Learning outcomes (after completion of the course the student should be able to)

Knowledge and understanding:
-Explain the distinction between software verification and software validation;
-Describe the connection between software development phases and kinds of testing;
-Describe and explain (a number of) different test methods, and use them in practical situations;
-Describe and explain what model-based testing is.

Skills and abilities:

-Construct models in the modeling and specification languages learned in the course;
-Construct appropriate and meaningful test and interpret and explain (to stakeholders) the results of the application of such test cases (using appropriate tools) to practical examples;
-Apply model based testing on realistic examples.
Judgement and approach:

-Exemplify and describe tools used for testing software, and use them and interpret their output;
-Identify and hypothesize about sources of program failures, and reflect on how to better verify the correctness of such programs.

Content

The course provides the students with a background on the theory and practice of model-based testing, including how testing tools can be used to improve software quality. General test techniques are explained with focus on model-based testing. Students will get hands-on experience in building a model for testing and they use this model for both testing and verification purposes.

Organisation

The course is provided in the so-called mini-modules format, which combines lectures and supervised practical work with exercises in small groups (assignments). The students are expected to be active during the whole mini-module. The exercises are both theoretical and practical in nature.

Literature

- M. Utting and B. Legeard, Practical Model-Based Testing. Elsevier - Morgan Kaufmann Publishers, 2007.




We will also provide other textbooks and research articles for different parts. See separate list.

Examination

Examination consists of two parts: a written exam (4.5 hec), and a hand-in of assignments (3 hec). The hand-in assignments are normally carried out individually or in pairs, and the written exam is individual.


The grading scale for the assignments is Fail (U) / Pass (G); for the written exam is Fail (U), 3, 4 and 5.


Page manager Published: Mon 28 Nov 2016.