Instructor: Clark B. Archer, PhD & Professor.
>>>>>>> References on reserve:-
Zobel, Justin. Writing for Computer Science. Springer, 1963.
Prerequisites: CS 491 (Software Engineering Fundamentals)
Catalog description: A continuation of the study of software engineering practices begun in CS 491. Issues of team-building, project planning and configuration management will be explored. Each student will complete a significant software development project as part of a team. For both the Computer Science major and the Information Systems major the Senior Culminating Experience consists of successful completion of both CS 491 and CS 492. Students will receive "W" credit for the sequence (4.0 hrs total) upon successful completion of both CS 491W and CS 492W.
Week ----- Monday & Wednesday
1 -- Introduction / Team Assignments given by instructor : Project Topic Selection
2 -- Team structure and learning styles inventory (Kolb)
3 -- Project Overview (Due Monday), begin discussion of programming teams
4 – Structure of High-level design documents
5 -- Press Release # 1, Discussion of risk management, High-Level Design Document due Friday
6 -- Test #1 on Wednesday
7 -- Detailed-Level Design Document issues & documentation, (due Friday at 11:00A)
8 -- Critique of detailed level design documents.
9 -- Detailed discussion of software design
10 -- Test # 2 on Wednesday
11 -- Discuss documentation in general; possible code reviews.
12 -- Press Release # 2 due.
13 -- First Draft of User's Manual due (Monday 4/11):
14 – Overview of project presentation and last minute details. Presentations (4/20/2011)
FINAL VERSION OF User's Manual & code due 4/20/2011
15- Discussion of presentations: Wrap-up
Course Evaluation: Grading Scale:
Attendance 30* A 94-100% C 73-76
Presentation 30 A- 90-93 C- 70-72
Project 240 B+ 87-89 D+ 67-69
Tests(2) 200 B 83-86 D 63-66
B- 80-82 D- 60-62
Total 500 pts C+ 77-79 F 0 -59
Attendance: Attendance is strongly encouraged ( you are expected to attend at least 85% of all classes). Tests missed due to an excused absence (usually meaning prior approval of instructor) can be made up. This equates to “miss five classes (an excused absence is still an absence - excused allows you to make up the missed activity) and you automatically fail the course.” *Otherwise, attendance is graded as 30 – 3X, where X is the number of absences.
Academic honesty: All assignments must represent the student’s own efforts. Copying written assignments or portions of another’s work in any manner from any source, without the explicit direction/permission of the instructor is a form of plagiarism and will cause the student to receive a zero for the assignment and possible failure of the course; and the student may be subject to other punitive actions by the college.
Disability accommodations: Contact (email@example.com)
Software Documents: Deliverables for this course will include:
Each of these documents must be peer-reviewed, reviewed by the course instructor, and approved by the customer before it is base-lined. Thus, the document must be produced early enough in the software development process to enable meaningful review and modification.
NOTE: CS 492W Software Engineering is a “W” course.
Writing-intensive courses at the University of Mount Union are required so students get some exposure to the ways in which writing works in at least three different disciplines. The way you need to write depends on a number of factors, including the discipline in question, the context and purpose for writing, and your intended audience. It's important for you to learn how writing needs to take into account these factors, as there are not only different kinds of writing in different disciplines, but different kinds of writing within each discipline. Courses that carry the “W” designation do not necessarily require more writing, but they do require you to pay attention to how writing works in three academic disciplines, and discussions about writing will be embedded into their course structures. In “W” courses, you will be asked to work on developing your writing and your understanding of writing in a particular discipline.
Writing Resources:There are numerous resources on campus to help you succeed in a writing-intensive course. Make use of your professor's office hours to review concepts and drafts at multiple stages. Make and keep appointments at the Writing Center—tutors can help you brainstorm writing ideas and they can provide feedback on specific aspects of your writing if you take your assignment sheet with you and don't wait until the last minute. In addition, you can draw on the knowledge you have gained about writing from your college writing course. You should form a writing group with other members of your class to discuss writing assignments, brainstorm ideas, read drafts, and provide feedback. Writing does not take place in a vacuum; it is a social event that is shaped by and shapes those around you. Mount Union's liberal arts curriculum can help you learn to write well in a variety of settings for a variety of purposes, if you take advantage of the instruction and resources available; they will serve you well at UMU and beyond.
As part of the Senior Culminating Experience for both the CS major and the IS major, one of the desired outcomes of the course is to allow students to participate in a software development activity/project that simulates current practice in the non-academic world and to experience the professional work environment in the disciplines. As such, it is expected that every student will act in a professional manner during class sessions and outside-of-class meetings. This includes:
• participating in class discussions and exhibiting attentive engagement in lecture presentations
• submitting work completed in a professionally-acceptable manner on time
• respecting other members of the class
• exhibiting professional demeanor and making eye contact when meeting with outside clients
• and/or technical advisors
• attending EVERY scheduled class event (lecture sessions, team meetings) it is recognized that absences may be necessary in special circumstances; in such a rare case, the leader of the meeting, be it the instructor, team leader, customer contact, etc., MUST be informed of the problem IN ADVANCE, as a courtesy.