[an error occurred while processing this directive]

<div id="Path">
  <a href="http://www.cs.brown.edu/">Brown CS</a> //
  <a href="/courses/cs190/index.shtml" title="CS190 Home">CS190 Home</a> //
  <a href="/courses/cs190/2007/syllabus.shtml" title="Syllabus">Syllabus</a>
</div>

<div id="Content">
  <h1>Syllabus</h1>

  <!-- Page content goes here -->

  <table>
    <tr>
      <td class="SyllabusCell">
        Professor: David Laidlaw<br />
        Office: CIT 449<br />
        Office Hours: By Appointment<br />
        Phone: x37647<br />
        Email: dhl [at] cs.brown.edu
      </td>
      <td class="SpacerCell"></td>
      <td class="SyllabusCell">
        Graduate TA: Kiran Pamnany<br />
        Office: CIT 361<br />
        Office Hours: by appointment<br />
        Phone: x36193<br />
        Email: kiran [at] cs.brown.edu
      </td>
    </tr>
    <tr>
      <td class="SpacerCell" colspan="3"></td>
    </tr>
    <tr>
      <td class="SyllabusCell">
        Head TA: Amy Simpson<br />
        Email: asimpson [at] cs.brown.edu
      </td>
      <td class="SpacerCell"></td>
      <td></td>
    </tr>
    <tr>
      <td class="SpacerCell" colspan="3"></td>
    </tr>
    <tr>
      <td class="SyllabusCell">
        Undergraduate TA: Greg Howard<br />
        Email: ghoward [at] cs.brown.edu
      </td>
      <td class="SpacerCell"></td>
      <td class="SyllabusCell">
        Undergraduate TA: Tara Olson<br />
        Email: tolson [at] cs.brown.edu
      </td>
    </tr>
  </table>

  <h2>Course Description</h2>
  <p>
    CS 190 is a course in which students working in teams of about 10 implement significant software applications.
    Students learn and practice techniques of project management, specification, presentation, analysis, design, coding,
    documentation, testing, and maintenance. This class is one of the last in the undergraduate curriculum and it can tie
    together many of the earlier classes very practically. In addition to the focus on a group programming project, we
    will discuss, debate, and think about the group software development process. Groups introduce a non-determinism that
    can be refreshing but can also make a project more challenging than you might first imagine.
  </p>

  <h2>Aims</h2>
  <p>
    I have three aims for people taking CS190. First, learn enough of the issues about creating software in groups to
    successfully implement future software systems. Second, become one of the team members on future projects to whom
    others turn for advice on software engineering and development. Third, learn to think clearly about the issues,
    articulate your conclusions, and adapt to changes.
  </p>

  <h2>Objectives</h2>
  <p>
    When you finish the course, you will have implemented a moderately large software system as a group. That is the
    primary objective of the course. Along the way, you will need to determine requirements and specifications for a
    project and present it to the class. In a larger group, you'll design the overall project, design the pieces,
    implement the pieces, integrate them, and demo the result. Throughout, we'll discuss the problems that crop up and
    see what we can learn from them. We'll also try out a few in-class and homework programming experiments to evaluate
    some different software engineering strategies.
  </p>

  <h2>Assessment</h2>
  <ul>
    <li>
      Project success and demo: base for class grade. This will be a group grade.
    </li>
    <li>
      Each group leader and the TA's will evaluate each group member at the end of the term. An evaluation can affect 
      an individual's grade by 1/2 letter.
    </li>
    <li>
      Each handin and presentation: can alter your grade by up to 1/2 letter. A late handin will cost 5% of a letter
      grade off the final course grade for each calendar day it is late. Each student gets three free late days before
      penalties accrue.
    </li>
    <li>
      Class participation: up to 1/2 letter grade increase.
    </li>
  </ul>

  <h2>Course Content Overview</h2>
  <p>
    Classes will be divided between lectures, student presentations, discussions, and group meetings. See the project
    handout and the course schedule for more details.
  </p>

  <h2>Textbooks</h2>
  <p>The required texts are:</p>
  <ol>
    <li>
      The Mythical Man-Month: Essays on Software Engineering, by Fredrick P. Brooks, Jr. (Addison-Wesley, 1995).
    </li>
    <li>
      Debugging the Development Process: Practical Strategies for Staying Focused, Hitting Ship Dates, and Building
      Solid Teams, by Steve Maguire (Microsoft Press, 1994).
    </li>
    <li>
      Large Scale C++ Software Design, by John S. Lakos (Addison-Wesley 1996).
    </li>
    <li>
      Writing Solid Code, by Steve Maguire (Microsoft Press, 1993).
    </li>
  </ol>
  <p>We'll also read a few pages from A Practical Introduction to Software Design with C++ by Steve Reiss (from CS 32).</p>

  <!-- Page content ends here -->

</div>

[an error occurred while processing this directive]