1 Basic Course Information

1.1 Catalog Description

Laboratory work required. Students write professional and non-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 demonstrate the prototype to a formal panel along with delivering the formal product specifications and a draft formal grant proposal. This is a writing intensive course.

1.2 Overall 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.

1.3 Prerequisites

Students must have earned a grade of C or better in one (i.e., any) of the following

• ENGL 211C
• ENGL 221C
• ENGL 231C

and a grade of C or better in all three of the following

• CS 330
• CS 350
• CS 410

1.3.1 General Programming Knowledge

Students should be familiar with certain basic programming techniques that are largely independent of any specific programming language:

• using editors, compilers and other basic software development tools.
• basic software design (i.e., stepwise refinement and top-down design)
• software testing, including the use of scaffolding code (stubs and drivers), selection of test cases for black-box testing, and head to head testing.
• debugging, including the use of debugging output, the use of automatic debuggers to set breakpoints and trace program execution, and the general process of reasoning backwards from failure locations to the faulty code responsible for the failure.

1.3.2 C++ & Java Knowledge

I will assume that you are familiar with the basics of C++ or Java. This includes:

• the various C++ statements and control-flow constructs,
• the built-in data types,
• the use of arrays, pointers, pointers to arrays, and linked lists,
• the use and writing of functions, and
• the basic use of structs and/or classes for implementing abstract data types.

1.3.3 Python 3 & Rust Knowledge

1.3.4 Unix/Linux

All students in the course will receive accounts on the CS Dept. network, and knowledge of how to work with the Linux servers is part of the course prerequisites. This course does not require familiarity with shell scripting. All other topics in CS 252 are required.

Some assignments will require the use of software available only on the Linux servers. Others may require (or, at least, be simplified by) use of the X windowing system.

1.3.5 General Computer Literacy

You will be studying techniques in this course for preparing professional-quality software documentation. The key embedded word in “software documentation” is “document”. Students taking this course should be able to use word processors and other common tools to produce good quality documents, including mixing text and graphics in a natural and professional manner.

1.4 When and Where

Scheduled Recitation Meetings will be held via Zoom. Meeting information can be found in Canvas under Course Collaboration Tool. Recordings of these meetings will be available under Media Gallery.

1.5 Instructor

Important: All email related to this course should have the phrase CS 411 somewhere in the subject line. This flags your message in my mailbox for faster attention.

I try to respond to all (properly marked) messages

• before I leave campus each day (Monday through Friday)
• within 48 on weekends & holidays.

Any delays in replying to email will be noted in a Canvas Announcement.

1.5.1 Office Hours

2 Required Materials

2.1 Textbooks

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

2.2 Supplemental Materials

All supplemental resources and materials will be available in Canvas.

2.3 Technology Requirements

2.3.1 Computer Accounts

Students will need an account on the CS Dept. Unix network to participate in this class. This account is unrelated to any University-wide account you may have from the ODU’s Information Technology Services (ITS).

3 Course Objectives

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

1. Recognize the value of collaboration in the field of computer science.
2. Plan and execute the development of a major software project.
3. Identify the order in which tasks should be completed either in parallel or in sequence in completing large projects.
4. Establish communication strategies to stay on task, complete team-based deliverables, and conduct effective team meetings asynchronously.
5. Establish effective asynchronous and synchronous communications with faculty and industry mentors.
6. Prepare collaborative outlines of the required written Assignments.
7. Prepare quality written papers based upon the collaborative outlines.
8. Document individual progress, challenges, concerns, and successes.
9. Recognize the need for the four types of professional writing addressed in the course as professionals and academics.
10. Utilize the assignments to develop high quality group projects.
11. Recognize the value of prototyping in the development of software projects.

4 Course Schedule

5.1 Presentations and Discussion Activities

Throughout the semester… discussion activities will be announced. These activities will include required discussion board activities. Details will be discussed during recitation and through Canvas Announcements. Discussion activities will be used to evaluate each team’s project as a whole and each student’s understanding of and contribution to the project. Discussion performance will be used to adjust individual grades for each presentation.

6 Course Policies

6.1 Attendance

Recitation attendance is not required. It is your responsibility to

1. watch the recording of any recitation that you are unable to attend
2. follow up with your team regarding any team feedback provided during recitation
3. contribute meaningfully to development of presentation, written, and prototype materials

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

6.2 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.

Extensions to due dates will not be granted simply to allow “porting” from one system to another. “But I had it working on my home PC!” is not an acceptable excuse.

6.3 Group Membership (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:

• It has been more than one semester since you completed CS 410.
• You are retaking CS 411W.
• You are completing this course (i.e., CS 411W) during the summer.

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.4 Contribution

You will recognize some prose CS 350. Much of this section is based on the CS 350 syllabus.

You will work as part of a team for most of the semester (i.e., from week 2 onward).

Your grade will include (and be based on)…

1. Active participation within your team
2. Active contribution to your team
3. Active engagement with your team

Procrastination and just-before-the-deadline submissions are detrimental to any team dynamic, and will result in lowered grades.

6.5 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 Civility Among Team Members

You will recgnize some prose CS 350. Much of this section is based on the CS 350 syllabus.

You will be working with your team for many weeks, and there will be a lot of communication expected among team members.

6.7 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.8 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 or student may 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 will 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.

6.9 Academic Honesty

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 his evaluation of the student’s understanding of the assignment and of the submitted solution as evidence of cheating. Violations will be reported to the Office of Student Conduct & Academic Integrity for consideration for possible punitive action.

Students who contribute to violations by sharing their code/designs with others may be subject to the same penalties.

• Students are expected to use standard Unix protection mechanisms (chmod) to keep their assignments from being read by their classmates. Failure to do so will result in grade penalties, at the very least.

This policy is not intended to prevent students from providing legitimate assistance to one another. Students are encouraged to seek/provide one another aid in learning to use the operating system, in issues pertaining to the programming language, or to general issues relating to the course subject matter.

Students should avoid, however, explicit discussion of approaches to solving a particular programming assignment, and under no circumstances should students show one another their code for an ongoing assignment, nor discuss such code in detail.

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:

• Just as when writing a paper, if you use someone else’s ideas, you must cite your sources appropriately. Within code, such citations appear in comments.

  Example:

  ⋮
  double x = 23.0;
  double xsqrt = sqrt(x);
  // Search algorithm based upon code by S Zeil at
  // https://www.cs.odu.edu/~zeil/cs361/latest/Public/functionAnalysis/index.html#orderedsequentialsearch
  int loc = 0;
  while (loc < arraySize && numbers[loc] < xsqrt)
  ⋮
  

• Just as when writing a paper, if you use someone else’s words (code), you must cite your sources appropriately and mark the quoted text. Within code, such citations appear in comments.

  Example:

  ⋮
  double x = 23.0;
  double xsqrt = sqrt(x);
  
  // Begin quoted code from  S Zeil at
  // https://www.cs.odu.edu/~zeil/cs361/latest/Public/functionAnalysis/index.html#orderedsequentialsearch
  int loc = 0;
  while (loc < listLength && list[loc] < searchItem)
  {
      ++loc;
  }
  // End quoted code
  
  ⋮
  

• Failure to appropriately cite any such “found code” will be taken as evidence of plagiarism.

• The overall principle stated in the first sentence of this section remains in effect. “Everything turned in for grading in this course must be your own work.” If the bulk of your assignment, code, paper, etc., are copied, even with appropriate citation, to the degree that, in the judgment of the instructor, you have not demonstrated your own knowledge of the course material, you will receive a zero for that exercise.

7 University Policies

7.1 Code of Student Conduct and Academic Integrity

7.2 Honor Pledge

By attending Old Dominion University, you have accepted the responsibility to abide by the Honor Pledge:

I pledge to support the Honor System of Old Dominion University. I will refrain from any form of academic dishonesty or deception, such as cheating or plagiarism. I am aware that as a member of the academic community it is my responsibility to turn in all suspected violations of the Honor Code. I will report to a hearing if summoned.

7.3 University Email Policy

7.3.1 Student Email

7.3.2 Email Account Activation

It is the responsibility of every eligible student to activate MIDAS, the Monarch Identification and Authorization System, in order to obtain email access.

7.3.3 Expectations Regarding Use of Email

7.3.4 Educational Uses of Email

University offices and instructors cannot validate that a communication coming by email is from an ODU student unless it comes from a valid ODU email address. If students send mail from non-ODU email accounts (e.g., Hotmail or Yahoo), faculty and staff are not obligated to respond and may request that official e-mail accounts be used.

7.4 Withdrawal

7.5 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.

• If you experience a disability which will impact your ability to access any aspect of my class, please present me with an accommodation letter from OEA so that we can work together to ensure that appropriate accommodations are available to you.

• If you feel that you will experience barriers to your ability to learn and/or testing in my class but do not have an accommodation letter, please consider scheduling an appointment with OEA to determine if academic accommodations are necessary.