1 / 8

TDT 4242

TDT 4242. Tor Stålhane. 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

phillipsmaria
Download Presentation

TDT 4242

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 13:15 – 14:00 in F3 Tuesdays 12:15 – 14:00 in F3 • First lecture – Monday, January 9, 2012. • Last lecture – Tuesday, April 15, 2012. • Exercise 1 – week 4. • Exercise 2 – week 7. • Exercise 3 – weeks 13 and 14. There will be no lectures during the exercise periods.

  5. Lecture plan – 2

  6. 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.

  7. 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?

More Related