Site Search

CS 481 Course Syllabus

CS 481 Syllabus for Winter 2008

Catalog Description

CS 481: Software Engineering Project
Continuation of the coding, testing, and implementation phases of project begun in CS 480. Prerequisites: CS 325 and CS 480

Rationale

More than any other course you take for the major, this course provides exposure to the type of real world software development you are most likely to encounter during your professional career. You will need to work together in groups and draw upon almost all the computer science knowledge and techniques you have studied throughout the curriculum. You should come away from this course understanding the difference between a program and a software product.

Student Learning Outcomes

Upon completion of this course, you will demonstrated the ability to

  • Apply software engineering principles and practices to the planning and development of an actual software product.
  • Work as a member of a software project team.
  • Produce professional-quality software engineering documents.
  • Deliver oral presentations associated with software development.

WWW

www.cwu.edu/~gellenbe/481/

Software

Note: Installation disks for Microsoft Project, Visio, and Visual Studio are available for checkout from Mr. Fred Stanley as part of the CS Department's MSDN Academic Alliance license. Instructions for using Cisco VPN and TortoiseSVN with Subversion may be found on the CS 480 Software Wiki

Assessment

Each CS 481 team should work out a contract with their faculty advisor on the make-up of their course grade. Sample assignments and weightings may be found at http://www.cwu.edu/~gellenbe/481/waterfall.php and http://www.cwu.edu/~gellenbe/481/extreme.php.

Attendance and Class Participation

There will be no formal meeting times or lectures for CS 481. Rather, teams are expected to establish regular meeting times for team meetings, faculty advisor meetings, and client meetings.

  • Waterfall model teams are expected to hold at least two formal meetings a week, one of which includes meeting with their faculty advisor. In addition, one or more team members should meet regularly with your client.
  • Agile Method programming teams are expected to hold at least four Scrum meetings per week, one faculty advisor meeting per week, and one client meeting per iteration.

Everyone is expected to attend all the midterm and final oral presentations delivered by the project teams this quarter.

  • Attendance will be taken at the oral presentations and your course grade may be adjusted down if you fail to attend.
  • Check with your faculty advisor in advance if you know you are unable to attend one or more of the oral presentations.

CS 481 Oral Presentations Tentative Times

  • Midterm
    • Wednesday, February 6, 4:00 - 5:00 p.m. (2 teams)
    • Friday, February 8, 3:30-5:00 p.m. (3 teams)
  • Final
    • Wednesday, March 5, 4:00-5:00 p.m. (2 teams)
    • Friday, March 7, 3:30-5:00 p.m. (3 teams)

ADA Statement

Students who have special needs or disabilities that may affect their ability to access information and/or material presented in this course are encouraged to contact me or Robert Campbell, Director of Disability Support Services , on campus at 963-2171 for additional disability-related educational accommodations.

Caveat

The schedule and procedures for this course are subject to change. It is the student's responsibility to learn of and adjust to changes.