Differences

This shows you the differences between two versions of the page.

--- start [2015/01/12 18:04] – bil
+++ start [2015/04/27 18:30] (current) – bil
@@ Line 5: / Line 5: @@
 **January 12, 2015**: Assignment 1 has been posted.
+**January 26, 2015**: [[http://www.ceraslabs.com/opportunities/researchassociate|This]] may be interesting to graduating students looking for employment.
+**February 2, 2015**: Assignment 2 has been posted.
+**February 9, 2015**: Assignment 1 feedback has been sent to your cse email. You can see your grade on ePost (link on sidebar).
+**February 23, 2015**: Assignment 3 has been posted.
+**March 2, 2015**: Assignment 2 feedback has been sent to your cse email. You can see your grade on ePost (link on sidebar).
+**March 17, 2015**: Assignment 4 has been posted.
+**March 27, 2015**: Assignment 3 feedback has been sent to your cse email. You can see your grade on ePost (link on sidebar).
+**April 27, 2015**: Assignment 4 feedback has been sent to your cse email. You can see your grade on ePost (link on sidebar). Overall course grades are on ePost as well.
 ===== Description  =====
@@ Line 10: / Line 27: @@
 The course introduces systematic methods of testing and verifying various types of software systems covering a range of static and dynamic techniques and their use within the development process. All too often software is designed and then tested. The real aim must be to take a more holistic view, where design is carried out with verification in mind to achieve overall project goals.
-Upon successful completion of the course you should be able to do the following:
+Upon successful completion of the course, students should be able to:
-  * Understand the importance of testing.
+  * Outline the objectives and limits of testing.
-  * Understand the strengths and weaknesses of the techniques discussed in the course
+  * Describe the strengths and weaknesses of the techniques discussed in the course.
-  * Be able to select appropropriate techniques for a given situation.
+  * Select appropriate testing techniques for a given situation.
-  * Be able to produce test harnesses for large software systems.
+  * Develop test harnesses for large software systems.
-  * Be able to produce quality reports.
+  * Submit issue reports that are clear and complete.
+  * Produce quality written reports describing their testing.
 ===== Lectures =====