1. TDT 4242 Tor Stålhane

2. Course contents The course consists of two parts: Requirements – a description of what we shall develop: 11 lectures Tests – a description of how we will check that we have developed what the customer required: 19 lectures The curriculum consists of A set of slides Copies of journal articles

3. Course grade The course grade will be decided based on One group exercise on writing requirements – 10% One group exercise on writing a test strategy for a set of requirements – 10% One group exercise on testing a software package – 30% Exam – 50%

4. Lecture plan – 1 Mondays 12:15 – 14:00 in R41 Thursdays 12:15 – 13:00 in R91 First lecture – Thursday, January 9, 2014. Last lecture – Thursday, April 24, 2014. Exercise 1 – week 4. Exercise 2 – week 7. Exercise 3 – weeks 11 and 12. There will be no lectures during the exercise periods.

5. Lecture plan – 2 Week Course content 2 - What you will learn Presentation of lecture plan and exercises Goal oriented requirements specification Quality issues in requirements 3 Requirements elicitation with boilerplates (templates) On requirement – testability and traceability – 1 On requirement – testability and traceability – 2 Intro. to exercise 1 4Exercise 1 – Write a requirements specification 5 Testing vs. inspection – strong and weak sides Testing and cost / benefit analysis 6 Testing strategies – a general introduction Black box vs. White box Grey box testing Introduction to exercise 2 7Exercise 2 – Write a testing strategy for the requirements specification from exercise 1

6. 8 How to prioritize requirements Requirements handling in COTS, Outsourcing, sub-contracting etc. Requirements in embedded and information systems 9 Aspects, cross-cutting concerns and non-functional requirements Testing COTS, Outsourcing, sub-contracting etc. Presentation of the FITNESS tool 10 Domain testing Coverage measures Use of test coverage measures for code and requirements Introduction to exercise 3 11Exercise 3 12Exercise 3 13 Requirements through user stories and scenarios How to write good user stories and scenarios 14 Advanced use cases Test driven development – TDD 1 15 Regression testing Non-functional requirements – safety, user friendliness etc. Testing non-functional requirements

7. Plagiarism means that you publish other people's work as your own. is regarded as cheating and is strictly forbidden. results in you failing your exercise and that you may be expelled from the university for a longer or shorter period. It is not allowed to either copy from books, articles, nor to use the “cut and paste” method with electronic resources (e-books, electronic articles, the Internet, etc) without writing where you found the information, that is - referring to the source.

8. Deadline for exercises All exercises will have a deadline for delivery. This deadline may only be exceeded after agreement with the course responsible – lecturer teaching assistant If no such agreement exists, we will deduct 5 points on the grade for any obligatory exercise for each week it is delayed.

9. Main theme The main message of this course is that requirements and tests are two sides of the same coin. Requirements without tests will be ignored. Tests without requirements are meaningless.

10. The need for traceability It must be possible to trace –From test to requirement. Why do we need this test? –From requirement to test. Where is this requirement tested? Staus: How many of the tests for this requirement has been executed successfully?