Skip to content

About

Course overview, policies




  • Instructors:

  • Instructor emails:







  • Writing-in-the-Disciplines (WID) TA: Sukshma Vedere
    (vedere @)

  • Time/place:
    • Meeting time #1: Tuesdays 2.15-5.00, T205
    • Meeting time #2: Wednesdays 6.10-8.40, T205
  • Office Hours:
    • Prof. Frank-Bolton: TBA
    • Prof. Simha: 5:00 - 6:00, Tuesdays, SEH 4560
  • Prerequisites: See undergraduate curriculum.

  • Official catalog description:
    Planning, design, and construction of the senior design project .
    Economic analysis of the project.
    Application of software engineering principles, including
    software requirements, specification, requirements engineering,
    reuse, documentation, verification/validation, testing,
    configuration management. Report writing and presentations.

  • Informal description:
    You will learn a great deal, pick up important job/interview
    skills, and develop pride in
    completing a challenging project.

  • Specific learning outcomes:
    • Learn key elements in the development of a significant
      year-long computer science project: planning, specification,
      design, economic analysis, and implementation.

    • Understand and apply concepts from software engineering
      to the project: requirements, specification, requirements
      engineering, reuse, documentation, verification and
      validation, testing, configuration management

    • Learn to write about and make presentations about
      important aspects of the project: the case for launching
      the project, status reports, design, and implementation plan.

    • Demonstrate a working project.
    • Demonstrate an understanding of how knowledge and skill
      in computer science courses played a role in the project.

    • Demonstrate an understanding of how continuing education
      can contribute to career development.

  • Textbook: There is no official textbook. Readings
    will be recommended where appropriate.

  • Programming load:
    The course will be fairly programming-intensive, and just
    intensive in general. If you are taking TWO OTHER programming-intensive
    courses, you could be in for a rough semester. Stop by and discuss
    the issue with the instructor.

  • Coursework and grading:
    See the logistics page

  • Assignment submission and late work policy:
    • All reports, presentations and such will be
      submitted via your project website.

    • Points will be taken off for late submission,
      approximately one letter-grade for each 24-hour period after
      the due-date. These points will not not be pro-rated
      hourly. Thus, if something is due 5pm Oct 19th, a
      submission at 5.05pm Oct 19th drops a letter grade.

    • The submission time will be determined by the
      upload time on the project website.

    • If you're seeking an extension because you've been ill and have
      a letter from a doctor, come by and see us about it.
  • Academic Integrity policy:
    • In this course, you will be expected to work on all assigned
      coursework by yourself, unless otherwise specified by instructions on
      this site. If you have any questions whatsoever regarding these
      policies, see us during office hours.

    • You may not, without permission from the instructor,
      exchange course-related code with anyone (including
      anyone not registered in the course), or download code for use
      in your coursework, or use material from books other than the textbook.
      Likewise, you may not look
      at anyone else's code or show your code to anyone else. Protect
      your work: for example, be careful not to leave your printouts around.

    • If you use material in your assignments that are from
      outside the course material, then you should be prepared
      to explain that material. The instructors and TAs reserve
      the right to question you on your use of extraneous material.
      Failure to answer such questions might be viewed as
      grounds for an integrity violation.

    • The
      Academic Integrity Code
      will apply to this course. Please read
      through the code carefully.

    • Penalties for violating the code or the policies described here
      include failing this course, and are elaborated in the Academic Integrity Code.

  • Late policy: As such, the standard university
    late policy will apply to most deliverables. That is, if you
    have a valid reason, such as a medical issue, then a late
    submission is acceptable if discussed with the instructor.
    However, in this course, there are some deliverables that
    occur at fixed dates, such as the presentations.
    For the presentations, you absolutely need to be there
    for the final presentation and the SD Final Day.
    For presentations 1-4, we will take the best three scores
    and count those towards the final grade.

  • If you have a disability that may
    effect your participation in this course and wish to discuss academic acommodations,
    please contact us as soon as possible.