CS 471 Fall 2024 > Syllabus
CS 471 Fall 2024
Syllabus
| COURSE: | CS 471 Senior Capstone I. 3 credits. |
| Time & place: | 10:30–11:30 am MWF, 535 Duckering. |
| Prerequisites: | CS major; senior standing; CS 311; CS 371. |
| INSTRUCTOR: | Glenn G. Chappell, Dept. of Computer Science. |
| Office: | 539 Duckering. |
| Office hours: | 11:45–12:45 MWF,
2:15–2:45 MW
on fall 2024 class days,
or by appointment. |
| E-mail: | ggchappell@alaska.edu |
| TEXTS: | Steve Krug,
Don’t Make Me Think, Revisited, 3rd ed.
(required)
Eric Brechner, Agile Project Management with Kanban (recommended) |
| WEB PAGE: | https://www.cs.uaf.edu/~chappell/class/2024_fall/cs471
UA Canvas will be used only for homework & exam submission. |
Course Topics & Goals
CS 471 is the first half of a two-semester capstone sequence comprising CS 471 (fall) and CS 472 (spring). It is intended to be taken by CS majors in the final year of their BS or BA degree program—or in the equivalent portion of a BS/MS program. The sequence covers software development processes, software quality, and related legal and ethical issues, culminating (in CS 472) with a semester-long group software-development project.
CS 471 topics include communicating as a software professional, software process models, software requirements, software architecture, testing, usability, development case studies, code review, and licensing.
Upon successful completion of CS 471, students are expected to:
- Have a basic understanding of concepts and methods involved in process models, testing, and usability that are used in building large software systems.
- Be familiar with several commonly used software process models and have experience using one of them.
- Have experience performing multiple kinds of software testing, including usability testing.
- Have improved skills and knowledge in professional communication—both written and oral—and legal issues.
- Be prepared to complete a high-quality group software-development project in the following semester.
Important Dates
For more details, see the Semester Plan, on the class webpage.
| Mon, Sep 2 | No class meeting (Labor Day) |
| Fri, Oct 25 | No class meeting (Take-Home Midterm Exam) |
| Fri, Nov 1 | Last day to withdraw (“W” on transcript) |
| Wed, Nov 27–Fri, Nov 29 | No class meetings (Fall Break) |
| Fri, Dec 6 | Last regular class meeting |
| Wed, Dec 11 | Final Exam period 10:15 am–12:15 pm—student presentations |
Procedures
Class meetings—Lecture/discussion format with in-class activities.
Homework—Assignments will be given every week or two. There will be seven in all. Five of these must be done individually. The other two are group assignments; groups will be chosen by the instructor.
Projects & Presentations—Each student will make an individual video presentation, to be critiqued by another student.
Students will be involved in three group projects. The first will be a software development mini-project following a specific process model. This will involve five in-class group presentations. The second will be an in-class group presentation that gives an introduction to an assigned topic. The third will be a case study of a real-world software development effort. This will involve a formal group presentation during the final-exam period, which will be recorded, with professional dress expected.
Exams—One exam will be given: a Take-Home Midterm. There will be no Final Exam; the final exam period will be used for the case study presentations. See Important Dates.
Required—Students must have access to equipment to do video/audio recording. Students must also have clothing appropriate for professional-level presentations.
Grades
Course grades will be based on points earned, using a 90-80-70-60 scale. The +/− grading system will not be used. Point totals will be as follows.
| Assignment 1 (Video Presentation) | 40 pts | |
| Assignment 2 (Video Critique) | 40 pts | |
| Assignment 3 (White Paper Draft) | 75 pts | |
| Assignment 4 (White Paper Final) | 40 pts | |
| Assignment 5 (Topic Introduction Slides Draft) | 40 pts | |
| Assignment 6 (Book Summary) | 75 pts | |
| Assignment 7 (Case Study Slides Draft) | 40 pts | |
| Mini-Project Presentations | 125 pts | (5 presentations, 25 pts each) |
| Topic Introduction Presentation | 75 pts | |
| Case Study Presentation | 75 pts | |
| Take-Home Midterm Exam | 75 pts | |
| Class Participation | 300 pts | |
| TOTAL | 1000 pts |
Policies
Communication with the instructor outside of class will be via e-mail and the class webpage. Students are expected to check both their UA e-mail account and the class webpage daily during the semester.
Students are expected to be at every class meeting on time, and are responsible for all class content, whether present or not. If absence is necessary, it is expected that the instructor will be notified as soon as possible; in particular, absences due to scheduled events must be arranged ahead of time.
Students who fail to attend the first class meeting after registering for the class, or who miss four consecutive class meetings, may be dropped/withdrawn without warning, unless prior arrangements are made with the instructor.
No graded work (other than the case study presentation and associated final slides) will be accepted after the beginning of the final exam period.
Academic dishonesty will not be tolerated, and will be dealt with according to UA procedures.
Students pay the CS lab fee. Payment allows access to the CS labs.
UAF academic policies: https://catalog.uaf.edu/academics-regulations
CS Department policies: https://www.cs.uaf.edu/departmental-policies