New course | Graduate |
First term offered : Fall 2012 | ||
Course Prefix&Number | Descriptive Title | Credits/Hours |
CS 641 | Project Planning/Design | 4 - |
Abbreviation for Class Schedule(20 spaces) Project Plan/Des |
Catalog Description: After students have declared to participate in one of the MIS computer science emphasis areas they may then apply to create a project that will count toward the completion of their degree. They must have completed at least 2 courses from a specific computer science strand before applying for the projects sequence (CS 641 and CS 642). In this course a student, with the involvement of at least two computer science faculty, will plan and design a project that will then be implemented in the second course (CS 642). There will be defined design milestones that the student will develop and must adhere to. |
Course Goal and Objectives: In this course a student will work with a faculty member to design and plan a proposed computer science project. Their will be supervision by at least one computer science faculty member regarding the milestones and the deliverables that are expected through out the term. The sequence will be roughly the following; week one the student will meet with the instructor of the course and provide at least three potential projects, week 2 the instructor and student will agree on an individual project and the student will then define a set of milestones, for the term, which will be used to measure the progress of the project design. On a weekly basis the student will report to the instructor their current status relating to the milestones. The project design shall always include: ¿ a presentation which will include at the least, the voting committee and may include invited guests. ¿ all rights and authorities of the product belong to WOU regarding the development/creation/release of said product. ¿ a full write up of the development stage, and the creation stage of the project is required. |
Justification for adding the course (e.g. alignment with other institutions, program revision, etc.): We currently have project courses for the MIS program. This change will eliminate much of the confusion regarding who can and cannot participate in a computer science project. The renumbering also eliminates the 60X course counting problem. |
Faculty and facilities needed: The same requirements as currently used. |
Brief Course outline: The sequence will be roughly the following; week one the student will meet with the instructor of the course and provide at least three potential projects, week 2 the instructor and student will agree on an individual project and the student will then define a set of milestones, for the term, which will be used to measure the progress of the project design. On a weekly basis the student will report to the instructor their current status relating to the milestones. Evaluation of the student could be weighted Presentations: 40% Assignments: 60% |
Step | Approver | Decision | Timestamp |
---|---|---|---|
1 - Department | David Olson | Approved | October 09 2012 |
Comments: No dept chair |
|||
2 - Division | David Olson | Approved | February 12 2013 |
Comments: No division chair |
|||
3 - Division Curriculum | John Marsaglia | Approved | February 13 2013 |
Comments: No division curriculum chair |
|||
5 - Graduate Committee | Kimberly Jensen | Approved | April 16 2013 |
6 - Faculty Senate | Keller Coker | Approved | April 18 2013 |
7 - Dean | Diane Tarter | Approved | April 19 2013 |
8 - Provost | Stephen Scheck | Approved | April 20 2013 |