Course Information
- Instructor: Dr. Aaron Garrett (garrettal@wofford.edu)
- Class Meeting (Olin 220): MWF 1:00p-1:50p
- Office Hours (Zoom): by appointment
- Textbooks:
- Essential Scrum by Kenneth Rubin
- Computer Science Distilled by Ferreira Filho
- You may also find Java for Python Programmers useful for learning the basics of the Java language.
- Final Exam: 9 Dec 2020 from 2:00p-5:00p
Catalog Description
A study of software engineering through a project-oriented approach. The emphasis is on the specification, organization, implementation, testing, and documentation of software. Students work in groups on various software projects.
Prerequisite: COSC 350 with a minimum grade of C.
Goals
- Improve interpersonal communications skills and teamwork.
- Gain understanding of the software development process.
- Acquire experience turning user requirements into testable, verifiable software features.
- Enhance ability to make estimates of software complexity.
- Achieve familiarity with common software development tools.
Grades
Your grade in the course will be based on a combination of quizzes, assignments, a large project with multiple sprints, and exams.
- Quizzes
- Quizzes are small assessments of concepts.
- Assignments
- Assignments are short exercises that reinforce the core concepts.
- Project
- The project will be a large software design and implementation requiring multiple weeks of effort by a team applying Scrum agile principles.
- Exams
- Exams are timed assessments of conceptual understanding.
| Artifact | Points |
|---|---|
| Quizzes (6) | 6 |
| Assignments (4) | 20 |
| Project | 50 |
| Sprint Reviews (4) | 40 |
| Final Product | 10 |
| Midterm Exam | 15 |
| Final Exam | 9 |
| Total | 100 |
The usual grading scale will be applied to the accumulated points: 93–100: A, 90–92: A-, 87–89: B+, 83–86: B, 80–82: B-, 77–79: C+, 73–76: C, 70–72: C-, 60–69: D, 0–59: F.
Policies
Attendance
You are expected to attend class meetings and come to class prepared. That includes having completed assigned readings, problem sets, and tutorials.
You are expected to dedicate your attention to what is going on in class and to participate fully in classroom activities, including discussions. No laptops or tablets are to be used in class unless being used for a classroom exercise. (Notes may be taken using a device if needed as an approved accommodation.)
Refer to the General Policy Regarding Attendance in the Wofford College Student Handbook. The policy makes you responsible for catching up on missed classes. If you must be absent for class, please email me in advance to let me know.
Make-up exams are not available. If you have a legitimate, excused absence during the midterm exam, then you must make it up during the final exam period.
Assignment Deadlines
Late assignments will not be accepted without a legitimate excuse. All assignments are expected to be submitted by the posted deadline.
Academic Integrity
The Honor Code requires faculty, staff, and students to maintain a high standard of individual honor and integrity. While I may specify some assignments as collaborative, work represented as your own must be your own. If you have any doubt about what is appropriate for a given assignment, you should contact me for clarification.
Accommodations
If you have a disability that requires assistance or accommodation, or if you have questions related to any accommodations for testing, note takers, readers, etc., please contact Dean Beth Wallace by telephone at (864) 597-4371 or in person by visiting the Hugh R. Black Infirmary. You must arrange accommodations during the first week of classes.
Tentative Schedule
| Meeting | Topic | Textbook | Graded |
|---|---|---|---|
| Aug 31 | Intro to Java | ||
| Sep 2 | Java classes | 1 | |
| Sep 4 | Git, Gradle | 2 | A1, Q1 (2) |
| Sep 7 | Unit testing | 3 | Q2 (3) |
| Sep 9 | Unit testing | 4 | Q3 (4) |
| Sep 11 | Scrum overview | 7 | A2 |
| Sep 14 | Acceptance testing, cucumber | 8 | Q4 (7,8) |
| Sep 16 | GUI | 10 | |
| Sep 18 | GUI | 11 | |
| Sep 21 | Java interfaces and generics | 14,19 | A3, Q5 (10,14,19) |
| Sep 23 | Java data structures | 20 | |
| Sep 25 | APIs | 21 | |
| Sep 28 | Software patterns | 22 | Q6 (20,21,22) |
| Sep 30 | 5,6 | A4 | |
| Oct 2 | Midterm Exam | Midterm Exam | |
| Oct 5 | Sprint 1 planning | ||
| Oct 7 | Sprint 1 | ||
| Oct 9 | Sprint 1 | ||
| Oct 12 | Sprint 1 | ||
| Oct 14 | Sprint 1 | ||
| Oct 16 | Sprint 1 review | Sprint 1 review | |
| Oct 19 | Sprint 2 planning | ||
| Oct 21 | Sprint 2 | ||
| Oct 23 | Sprint 2 | ||
| Oct 26 | Sprint 2 | ||
| Oct 28 | Sprint 2 | ||
| Oct 30 | Sprint 2 review | Sprint 2 review | |
| Nov 2 | Sprint 3 planning | ||
| Nov 4 | Sprint 3 | ||
| Nov 6 | Sprint 3 | ||
| Nov 9 | Sprint 3 | ||
| Nov 11 | Sprint 3 | ||
| Nov 13 | Sprint 3 review | Sprint 3 review | |
| Nov 16 | Sprint 4 planning | ||
| Nov 18 | Sprint 4 | ||
| Nov 20 | Sprint 4 | ||
| Nov 30 | Sprint 4 | ||
| Dec 2 | Sprint 4 | ||
| Dec 4 | Final Exam | Final Exam | |
| Dec 9 | Final Sprint Review | Final Sprint Review |
Note: This syllabus is subject to change with notice.