|
| 1 | +title: "Software Testing Course Organization" |
| 2 | +layout: notes |
| 3 | +--- |
| 4 | + |
| 5 | +# Course Organization |
| 6 | +* Course week begins Monday 00:00 and ends Sunday 23:59 |
| 7 | +* Course will be run primarily through Canvas |
| 8 | +* One or more modules per week |
| 9 | +* Modules may consist of: |
| 10 | + * Brief lecture(s) |
| 11 | + * Reading(s) |
| 12 | + * Exercise(s) |
| 13 | + * Exercise/Project Instructions |
| 14 | + |
| 15 | +# Course Communication |
| 16 | +* Modules and other material will be posted on Canvas |
| 17 | +* [Discord](https://discord.com/new) will be the primary means of direct communication between instructor/students |
| 18 | +* Instructor may also be reached via email: [[email protected]](mailto:[email protected]) |
| 19 | +* Announcements will be made via Canvas |
| 20 | + |
| 21 | +# Discord |
| 22 | +* Discord supports text, voice, video, and screen sharing |
| 23 | +* Virtual office hours will be held on Discord |
| 24 | +* Questions may be asked over Discord directly to me or to the class about the material in the class, etc |
| 25 | + * If asking/answering publicly, do not post your current work or answers to exercises/projects/tests |
| 26 | + * If asking me a question about your work, make sure your current work is submitted to Canvas or pushed to GitHub |
| 27 | +* Additionally, Discord will be used to support group work |
| 28 | + |
| 29 | +# Course Assessment: |
| 30 | +* 15% Exercises |
| 31 | +* 35% Projects |
| 32 | +* 25% Midterm |
| 33 | +* 25% Final |
| 34 | + |
| 35 | +| A | B | C | D | F | |
| 36 | +|----|----|----|----|----| |
| 37 | +|90%|80%|70%|60%|0%| |
| 38 | + |
| 39 | +# Exercises |
| 40 | +* Exercises will be given along with modules to complement the material in the module |
| 41 | +* Details of each specific exercise will be provided when assigned |
| 42 | +* Due at the end of the week the module is released |
| 43 | + |
| 44 | +# Projects |
| 45 | +* 3-5 projects will be assigned throughout the course of the semester to further reinforce the concepts covered in class and link multiple topics |
| 46 | +* Will be both written/programming and individual/group |
| 47 | +* Some projects will require writing C++ |
| 48 | +* Details of each specific project will be provided when assigned |
| 49 | +* Projects will be assigned at the beginning of the week and be given two weeks for completion. Projects are due before the end of the second week |
| 50 | + |
| 51 | +# Additional Mediums used for Exercises/Projects |
| 52 | +* In addition to Discord, exercises and projects may also require use of: |
| 53 | + * Discussion boards on Canvas |
| 54 | + * Communication via Email |
| 55 | + * Use of issue tracker (i.e., GitHub's issue tracker) |
| 56 | + |
| 57 | +# Exercise and Project Submission |
| 58 | +* Exercise and projects will be submitted either via Canvas or an exercise/project specific Git repository |
| 59 | +* Details of what to submit to will be given along with each assignment |
| 60 | +* When a Git repository is required, good practices are expected to be used: |
| 61 | + * Develop and commit work incrementally |
| 62 | + * [Good commit messages](https://chris.beams.io/posts/git-commit). |
| 63 | + * No binaries or other generated artifacts are versioned |
| 64 | +* Your final work must be submitted to Canvas or pushed to GitHub by the due date |
| 65 | + |
| 66 | +# Midterm & Final |
| 67 | +* A midterm and comprehensive final will be given over the material covered in class |
| 68 | +* Material will come from modules, exercises, and projects |
| 69 | +* The midterm and final will be posted on Canvas at the beginning of the week, and it will be due before the end of the week |
| 70 | + |
0 commit comments