CS 493
CS 493 - Senior Project II, ACP
Spring 2025
Title | Rubric | Section | CRN | Type | Hours | Times | Days | Location | Instructor |
---|---|---|---|---|---|---|---|---|---|
Senior Project II, ACP | CS493 | CS | 31260 | LCD | 3 | 1100 - 1150 | F | 0220 Siebel Center for Comp Sci | Michael Joseph Woodley |
Senior Project II | CS494 | CS | 40242 | LCD | 3 | 1100 - 1150 | F | 0220 Siebel Center for Comp Sci | Michael Joseph Woodley |
See full schedule from Course Explorer
Official Description
Course Director
Learning Goals
work in teams, coordinate efforts for common goal (1), (2), (3), (4), (5), (6) |
Topic List
Communicating with Your Client and Team
Forms of Communication - Reports, Plans, Memos, Emails, etc
Technical Presentations
Making a Plan
Feature Breakdown
Setting Goals
Managing Your Client’s Expectations
Working in a Team
Professionalism Toward Your Client
Receiving Critique - Making Use of What is Useful, Being Effective at Delivering It
Documenting Your Project
- Responsibilities as a Team Member
- Managing Your Project
- Client Relationship
- Managing Your Team
- Choosing Projects and Forming Teams
- Team Success and the Importance of Inclusivity
- Respecting and benefiting from working with clients and team members of different genders and backgrounds.
- Understanding Client Goals
- Understanding Client Expectations
- What to do when you do not have specific expertise
- Managing Expectations
- Professionalism
- Defining Outcomes
- How to Work with Your Client to Make Them Happy
- Meetings with Clients
- Team Meetings
- Taking Responsibility and Ownership
- Written Communications
- Planning and Estimating
- Agile Methods and Tools
- Useful Status Reports (Are Honest and Accurate)
- Honesty and Evaluation (Team Evaluations)
- Measuring Team Productivity (You were probably wrong but that's OK)
Assessment and Revisions
Revisions in last 6 years | Approximately when revision was done | Reason for revision | Data or documentation available? |
require maintenance of team/project wiki | fall 2011 | discussion with industry partners and former students that have graduated | |
changed formal planning requirement to add focus on agile methods | fall 2010 | discussion with industry partners and former students that have graduated | |
in class presentations include regular status updates for every team rotating between team members | fall 2012 | discussion with industry partners and former students that have graduated | |
changed paper format to wiki, word count replaces page count | fall 2011 | discussion with industry partners and former students that have graduated | |
added requirement to maintain Jira issues-tracking database | fall 2011 | discussion with industry partners and former students that have graduated |