CS 411W Professional Workforce Development II (Summer 2021)


1 Course Description

The Professional Workforce Development course sequence (CS 410 and CS 411W) expands upon the experimental and design approach of typical computer science curricula by addressing the creativity and productivity required for business and industrial applications. Students in this course sequence engage in projects that investigate each stage of transforming a creative idea into an innovative product.

Writing can comprise as much as 60% of a computer scientist’s professional activities. The evolution of software engineering into a team-centric process (possibly across geographic distances) requires the sharing of a wide variety of documentation with attention to version control and version management.

This course is the writing intensive (W) course for the major, which requires 51% or more of the computed grade be based upon writing assignments. You must demonstrate the ability to write clearly and accurately for a technically oriented audience. You will complete graded and ungraded writing exercises.

You will write professional and technical documents, and continue the development of the project defined in CS 410. Written work is reviewed and returned for corrective rewriting.

Students will design and develop a project prototype, and formally demonstrate the prototype.

2 Instructor Information

Instructor Office Phone # Email Home Page & Office Hours
Janet Brunelle E&CS 3210 757.683.7714 brunelle@cs.odu.edu http://www.cs.odu.edu/~brunelle/
Jim Brunelle     jabrunel@odu.edu https://www.cs.odu.edu/~jamesbr
Ajay Gupta ajay@cs.odu.edu
Thomas J. Kennedy Dragas 1100D 757.683.7725 tkennedy@cs.odu.edu http://www.cs.odu.edu/~tkennedy

3 Readings

There is no required textbook. All readings will be provided through the course site.

4 Objectives

At the end of this course, students will be able to:

5 Grading

Graded Element Description Weight Individual/Group
Writing Exercises Discussion Activities 5% (Individual)
Writing - Lab I Descriptive/Persuasive Paper 15% (Individual)
Writing - Lab II Prototype Product Specification 15% (Individual/Group)
Writing - Lab III Prototype Test Plan/Procedures 15% (Individual/Group)
Writing - Lab IV Product/Prototype User’s Manuals 15% (Individual/Group)
Prototype Demo Product Laboratory Prototype 30% (Individual/Group)
Website Product and Course Documents 5% (Group)

6 Course Policies

6.1 Due Dates and Late Submissions

Late papers, assignments, prototype contributions, and presentations/demonstrations will not normally be permitted.

Exceptions will be made only in situations of unusual and unforeseeable circumstances beyond the student’s control, and such arrangements must be made prior to the due date in any situations where the conflict is foreseeable.

I’ve fallen behind and can’t catch up”, “I’m having a busier semester than I expected”, or “I registered for too many classes this semester” are not grounds for an extension.

6.2 Academic Honesty

This section is borrowed the CS 330 and CS 350 syllabi as written by Steven J. Zeil.

Everything turned in for grading in this course must be your own work. If an assignment is explicitly described as a team assignment, it must be the work of the team members only.

The instructor reserves the right to question a student orally or in writing and to use this evaluation of the student’s understanding of the assignment and of the submitted solution as evidence of cheating. Violations will be reported to the Honor Council for consideration for punitive action. By CS Dept. policy, students found to be in violation of this rule will, at the very least, receive a failing grade in the course and may be subject to stiffer penalties.

Use of Online Resources

You may not post details of course assignments, projects, or tests at online Forums, Bulletin Boards, Homework sites, etc., soliciting help.

You may use information that you have not solicited but have located, subject to the following restrictions:

6.3 Attendance

Recitation attendance is not required, but you are responsible for all material covered and announcements made in class (e.g., assignments given or modified, due dates established or modified, and handouts). If you are going to miss recitation, be sure to get notes, handouts, etc., from a groupmate or classmate.

Students must meet all course deadlines and be present for Prototype Demonstrations.

6.4 Team Assignment (From CS 410 to CS 411W)

In CS 410 you were assigned to a team. Your team developed an idea and designed a Prototype. Barring specific conditions, you will remain with your team from CS 410.

You will be assigned to a new team if:

You may be assigned to a new team, at the instructor’s discretion, if you are unable to work with your CS 410 team. Note the use of may.

6.5 Weekly Progress & Deliverables

After Lab 1 (i.e., the first paper), there will be at least one informal presentation per week. The expected deliverables (e.g., presentation content, group website) will be discussed during class meetings (lecture and/or recitation).

The instructor will ask each group to provide a brief summary of both progress and identified issues. All group members should be prepared to provide a summary.

6.6 Professionalism & Contribution

Old Dominion University supports a comprehensive evaluation of a student’s achievement in a course as a vital part of the educational process. In support of this university policy, successful completion of this course includes satisfactory performance in the development of formal documentation (including presentations) and the Prototype (Software Solution).

Any student who fails to collaborate with his/her group in a satisfactory manner may possibly not pass the course, regardless of overall point total. Each student will be evaluated based upon demonstrated professionalism and contribution. Any student who receives poor marks from the instructor and/or their group members may not pass the class.

6.6.1 Prototype Contribution

The Prototype (Software Solution) is a core deliverable of CS 411W. All students must contribute to development by

  1. contributing code continuously throughout the semester.
  2. contributing meaningful code.
  3. communicating with their group throughout the semester.

Any student who fails to effectively contribute to the Prototype will not pass the course.

6.6.2 Unsatisfactory Performance

If a student fails to contribute meaningfully within his/her group, or a student feels he/she cannot contribute meaningfully within his/her group, the instructor will arrange a meeting. The meeting may be conducted face-to-face, via network conferencing, or via email. The instructor may consult other CS 410/411W instructors or ask other CS 410/411W instructors to attend the meeting.

During the meeting the instructor and student will discuss the student’s current contributions and expected contributions moving forward. The instructor and student arrange a follow-up meeting. If by the follow-up meeting, the student has not made the expected (i.e., agreed upon) contributions he/she may not pass the course.

7 Educational Accessibility

Old Dominion University is committed to ensuring equal access to all qualified students with disabilities in accordance with the Americans with Disabilities Act. The Office of Educational Accessibility (OEA) is the campus office that works with students who have disabilities to provide and/or arrange reasonable accommodations.

The Office of Educational Accessibility is located at 1021 Student Success Center and their phone number is (757) 683-4655. Additional information is available at the OEA website http://www.odu.edu/educationalaccessibility/