Spring 2016 Syllabus: Sections 1-4
- Instructors & Laboratories
|Director||Ms. Margaret Heil (2292 Engineering Building II)|
heil AT ncsu.edu
Office Hrs: by Appt.
|Associated Faculty/Technical Advisors||Dr. Lina Battestilli|
lbattestilli AT ncsu.edu
Office Hrs.: by Appt.
| ||Mr. Ignacio X. Domínguez|
ixdoming AT ncsu.edu
Office Hrs. by Appt.
| ||Dr. Sarah S. Heckman (2297 Engineering Building II)|
sarah_heckman AT ncsu.edu
Office Hrs.: by Appt.
| ||Dr. David B. Sturgill (2294 Engineering Building II)|
dbsturgi AT ncsu.edu
Office Hrs: by Appt.
|Teaching Assistants||Mr. Zachary Cleghern|
zbcleghe AT ncsu.edu
| ||Ms. Christa Cody|
cncody AT ncsu.edu
| ||Mr. Nick Freeman|
ndfreema AT ncsu.edu
|Website Support||Mr. Ben Tilley|
jbtilley AT ncsu.edu
|Senior Design Center Labs||EB2-1203A (Classroom: EB2-1025)|
- Course Prerequisites
CSC 492: CSC 326, Senior Status
- Student Learning Objectives & Outcomes
The primary objective of this course is to provide seniors in computer science an opportunity to relate classroom topics to the working environment of a computer science professional; they will demonstrate the ability to participate in professional practices related to software engineering.
The outcomes associated with this objective are that, upon completion of CSC 492, students should be able to:
- Negotiate, clarify, and document customer requirements
- Apply knowledge of fundamental algorithms, programming language concepts, and design patterns to determine an overall design for a software system
- Implement a fully specified system
- Test a fully specified system
- Plan and monitor the progress of software projects to ensure on time delivery of a high-quality system
Another objective is that students will be able to communicate effectively about computer science-related topics.
The outcomes associated with this objective are that, upon completion of CSC 492, CSC students should be able to:
- Deliver an audience-sensitive oral technical presentation
- Write an audience-sensitive technical document
The final objective of this course is to provide students with experience in teamwork, by creating an environment in which it is necessary to cooperate with each other to achieve a technical goal.
The outcome associated with this objective is that, upon completion of CSC 492, CSC students should be able to:
- Contribute to software-based system development teams
- Required Text
Spring 2016 Course Pack (to be posted online).
- Course Organization & Scope
- Lecture Topics
- Team Formation & Development
- Software Engineering Process From a Team Perspective
- Project Management
- Team Task Planning
- Sponsor & Team Meetings
- Writing & Speaking
- Operating Rules/Expectations
All projects in CSC 492 are based on formation of teams and appropriate teamwork throughout the semester. Teams are expected to:
- Develop ground rules, assign roles, & function as a unit
- Participate in project activity & observe deadlines:
- Project development via a defined software engineering process
- Documentation & presentation preparation
- Posters & Pies: 4/26/16 (Note: This is a Reading Day.)
- Final project delivery & final presentation to sponsor
- Meet with faculty and/or industrial sponsor approximately every two weeks to review progress
- Provide instructors/team members/sponsors with team meeting agendas & minutes
- Keep lab space orderly & garbage free. Teams will be subject to penalties for unkempt team spaces
As an individual member of a team, you are expected to:
- Join a project team & fully participate. This means that there must be evidence that each team member has contributed to design, coding, or testing
- Attend all team meetings & all class meetings
- Maintain project documents -- rotate responsibility
- Give progress presentations to entire 492 class at regularly scheduled class meetings -- rotate responsibility (help each other with presentation content and preparation)
- Keep an Individual Project Log (i.e., a personal journal of individual project activity - see web site) and summarize monthly individual contribution using the personal contribution section of the peer eval. Project Logs will be collected four times during the semester per the calendar.
- Check email on a daily basis and keep boxes under quota so instructors' email is not blocked. Since the instructors' main vehicle for communication with students is via email, this is extremely important
Noncontributing individuals- Evaluation of an individual's contribution comes from three sources: instructors, sponsors, and peers. During the course of the semester, if any two of these three elements judge an individual's contribution as negligible or belligerent, that individual will be "fired" from the team. Such a determination will not be made lightly, will imply that numerous attempts at reconciliation have failed, and will have serious consequences on the grade of the individual. In particular, his/her grade for the course will become zero and the individual will be immediately removed from any responsibility for the assigned team or project. Alternatives for a subsequent course of action are:
- A late drop recommendation will be made to the Dean
- An individual project may be negotiated between the instructors and the student for which the maximum grade will be 'C' if all project goals are met by semester's end
- Projected Schedule of Reading Assignments
- Schedule of Assignments
- Course Grading
The grading scheme for CSC 492 will be based on the degree to which course objectives are met and mutual accountability of individual team members.
- Grade Calculation
Your grade in CSC 492 is based on an individual grade and a team grade.
Your Individual Grade (I), worth 50%, is a weighted sum of grades for:
- Your Personal Activities (30%)
- Oral Progress Report (15%) = IO
- Personal Tasks (15%) (based on your logs & Statements of Personal Contribution) = IT
- Your Personal Contribution To The Team Effort (20%)
- Peer Evaluations (10%) = IP
- Instructors' Observations (10%) (your project leadership & professional demeanor) = II
Your Team Grade (T), worth 50%, is a weighted sum of grades for:
- Project Progress (40%) = TR
Based on quality, content and timeliness of completed code or activity and written progress reports, as follows:
- Interim Project Report (Total, 10%)
- Final Report (30%) (For report format and content, see course pack).
- Team Cohesiveness (10%) = TC
Based on instructors' evaluation of teamwork as evidenced by team planning, team participation in progress reports (both oral and written), and team participation in final delivery of project product (includes Posters & Pies deliverables: Presentation, Poster & Demo).
Finally, your Course Grade = I + T = (IO + IT + IP + II) + (TR + TC)
- Other Grading Information
- Team documents returned as unsatisfactory will be counted as non-existing
- All deadlines must be met (or revised -- with justification). If a document is given to the instructors after established deadline, a 10% penalty/day will be imposed
- Peer evaluation -- Each team member will rate the performance of fellow team members four times during the semester. See calendar for due dates and access forms via web site. If an individual does not submit a timely peer evaluation for other members of his/her team, that individual's peer evaluation score will be 0%
- Oral Progress Reports - One graded Oral Progress Report per student (15%) - lowest grade will be dropped
- In some cases sponsor evaluations may be counted
- Attendance - Your attendance during class time (lecture, oral progress reports, and Team Work Days) is mandatory. You will be allowed a total of two excused absences from class. Excused absences from class require written permission in advance. Judgment of instructors is final. For each unexcused absence, there will be a 3-point deduction from your total semester numeric grade (see A above). Tardiness is unacceptable as it disrupts the class or team meetings, and it displays disrespect toward our learning community. Two "tardies" during class time will count as one unexcused absence. On Team Work Days (see calendar), you are required to work in your assigned lab space. Attendance will also be monitored on Team Work Days. If you will not be in the lab on a particular Team Work Day because of a sponsor meeting, please notify Ms. Heil before that class period.
Friday Sessions: Check the calendar carefully. Attendance at course events pre-scheduled for Fridays is mandatory [1/8/16, 1/15/16, 1/22/16, 2/5/16, 3/18/16 (see calendar for specifics); 4/1/16 (for P&P presenters only), 4/8/16 (For P&P presenters only]. If sponsor schedules require Friday meetings, then Friday attendance is mandatory. If instructor or faculty mentor schedules require Friday meetings, then Friday attendance is mandatory. Otherwise, attendance at Friday sessions is optional.
- Grading Scale
- 98% <= calculated grade <= 1XX% -> A+
- 92% <= calculated grade <= 97% -> A
- 90% <= calculated grade <= 91% -> A-
- 88% <= calculated grade <= 89% -> B+
- 82% <= calculated grade <= 87% -> B
- 80% <= calculated grade <= 81% -> B-
- 78% <= calculated grade <= 79% -> C+
- 72% <= calculated grade <= 77% -> C
- 70% <= calculated grade <= 71% -> C-
- 68% <= calculated grade <= 69% -> D+
- 62% <= calculated grade <= 67% -> D
- 60% <= calculated grade <= 61% -> D-
- calculated grade <= 59% -> F
Extra Credit Opportunities
Various extra credit opportunities are available in CSC 492. Points will be added to your Instructors' Observation grade (amount to be determined by activity and announced during semester). They include (but are not limited to):
- Fidelity Investments Lecture Series (1/26, 2/25, 3/22)
- Workshop: Building Bridges – Strengthening Leadership for Diverse Communities (Date TBD)
- Poster Session for SDC Sponsors (2/19)
Policies On Incomplete Grades & Late Assignments
See Number 8, Course Grading.
See Number 8, Course Grading.
All students are expected to maintain traditional standards of academic integrity. You should be aware of the University policy on academic integrity found in the Code of Student Conduct, which can be found at http://policies.ncsu.edu/policy/pol-11-35-01.
Reasonable accommodations will be made for students with verifiable disabilities. In order to take advantage of available accommodations, students must register with Disability Services for Students at 1900 Student Health Center, Campus Box 7509, 515-7653. http://www.ncsu.edu/dso/. For more information on NC State's policy on accommodating students with disabilities, please see http://policies.ncsu.edu/regulation/reg-02-20-01
Risk Assumption on Field Trips
In some cases, field trips to sponsor sites may be necessary. Students are at their own risk during travel.
In some cases, field trips to sponsor sites may be necessary. Student travel to local sponsor sites is not reimbursable.
In some cases, field trips to sponsor sites may be necessary. Students are expected to provide their own transportation to local sponsor sites.
Online Class Evaluations
Schedule: Online class evaluations will be available for students to complete from 8 a.m. April 13 through 8 a.m. April 27. Students will receive an email message directing them to a website where they can login using their Unity ID and complete evaluations. All evaluations are confidential; instructors will not know how any one student responded to any question, and students will not know the ratings for any instructors.
Evaluation website: http://oirp.ncsu.edu/eval/clev/students-info
Student help desk: email@example.com
More information about ClassEval: http://upa.ncsu.edu/eval/clev
University Honors Program (UHP)
A student who intends to use anything related to his or her CSC senior design project to fulfill the requirements for the UHP Capstone MUST declare an intent to do so by Friday, January 15, 2016; to declare your intent, send an email to Ms. Heil and the associated technical advisor in charge of your section. Furthermore, a written proposal for the Honors Capstone project MUST be submitted by Friday, February 5, 2016 to Ms. Heil and the associated technical advisor in charge of your section. Please be advised that an Honors Capstone project MUST go above and beyond the deliverables required to successfully complete your CSC senior design project.
Supporting Fellow Students in Distress
As members of the NC State Wolfpack community, we each share a personal responsibility to express concern for one another and to ensure that this classroom and the campus as a whole remains a healthy and safe environment for learning. Occasionally, you may come across a fellow classmate whose personal behavior concerns or worries you, either for the classmate’s well-being or yours. When this is the case, I would encourage you to report this behavior to the NC State’s Students of Concern website: http://go.ncsu.edu/NCSUcares. Although you can report anonymously, it is preferred that you share your contact information so they can follow-up with you personally.