Differences

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

--- course_info:cis_4150 [2015/02/10 23:04] – created judi
+++ course_info:cis_4150 [2015/03/06 20:19] (current) – wineberg
@@ Line 1: / Line 1: @@
-Include a brief summary of the course topics and requirements, the general format of the course, and the methods of evaluation.
+== CIS*4150 Software Reliability and Testing ==
+[From the Course Description in the Undergraduate Calendar] This course serves as an introduction to systematic methods of testing and verification, covering a range of static and dynamic techniques and their use within the software development process. Concepts such as defining necessary reliability, developing operational profiles, techniques to improve and predict software reliability, preparing and executing tests, black box testing, white box testing, unit testing, system testing, and integration testing will be explained.
 == Skills and knowledge students should have prior to beginning the course: ==
+  * Prerequisites
-  * Unordered List Item
+     * CIS*3750 or CIS*3760
+  * Expected background knowledge
+     * Java programming
+     * Object Oriented Design
+     * Requirements and Design specification experience
+     * UML (class diagrams, flow charts)
+     * Group work and collaboration on a large project
 == Course Topics: ==
-  * Unordered List Item
+  * Software Reliability Fundamentals
+  * Fundamentals of Testing and Analysis
+  * Finite and Data Flow Models
+  * Test Case Selection
+  * Functional, Combinatorial, Structural, Data Flow Testing
+  * Testing Object Oriented Software
+  * Testing GUIs
+  * Security and Performance Testing
+  * Testing Stochastic Systems
 == Course Format: ==
-  * Lecture format:
+  * Lecture format
-  * Online materials location and format:
+     * two one-hour lectures
-  * Lab or tutorial format and expectations:
+  * Online materials
+     * All slides, assignments and project instructions and submissions, and course communication will be through a Moodle course site
+  * Labs
+     * Two-hour weekly labs have been scheduled
+     * They will be used as need for project organization and demonstrations as well as supplemental lectures material
+     * Lab time will be used approximately 6 to 9 times during the semester
-== Method of evaluation: ==
-  * Number of Assignments:
+== Method of Evaluation: ==
-  * Number of Graded Labs:
-  * Number of Quizzes:
-  * Formal Midterm?
-  * Course project?
-  * Final Exam?
-  * Group work?
-  * mostly programming assignments?
-  * Written documents?
+  * Number of Assignments: 3
+      * Individual assignments that accompany two of the group project milestones
+      * One literature survey to be done during the second half of the course
+  * Number of Graded Labs: None - but project demonstrations are done during lab time
+  * No Quizzes
+  * No Midterm
+  * Course project: Large course group project with multiple milestones throughout the semester
+  * Final Exam: Yes
+  * Group work: Yes, on the course project
+  * Programming: The course project involves a great deal of coding, with a fair bit of supplementary documentation
+  * Written documents? Yes, both for the project, the assignment write-ups and for the literature survey