Information Technology Projects


Professor: Arthur Goldberg
Email: email:
Course home page:
Meeting time: Thursday, 5-7
Place: Room 9-172 MEC (the Stern School)
Course number: G22.3812.001
Email beacon:
Credits: 3
Office: Information Systems Department, Stern School of Business, Management Education Center, Room 9-75, 44 West 4th St.
Home page:
Office hour: By appointment.
Secretary: Yuet Lo, 998-0839,


The Information Technology (IT) Projects Seminar will give students real-world experience understanding and solving IT software and systems problems. This course will involve a set of projects at local corporations and other institutions. We will organize students in teams of about four. Each team will undertake one IT project that lasts the semester.

Proposed Projects


To work productively in our projects students must possess sufficient technical and/or managerial skills. These skills can be obtained by academic training and/or experience. In particular, for CS students, the Software Engineering course is a pre- or co-requisite.

As the set of skills cannot be precisely specified, interested students should contact Prof. Arthur Goldberg (artg@cs) for permission to register. Email a resume or short bio, with the word ``Projects'' in the ``Subject'' line.

In addition, we will limit the number of students who can enroll to no more than 30.

Prof. Goldberg will email admitted students a 4-digit access code. Register for the course as ``Advanced Laboratory in Information Systems'' (G22.3812.001). CS students can register by calling TorchTone and providing the access code. Unfortunately, students enrolled in Stern must appear in person at Stern registration.

Course Resources

Whenever possible, clients will provide computing resources. In addition, the CS department will provide.


Team Composition

At the first class meeting each student will rank each project's desirability between 1 and 10. Prof. Goldberg will assign students to teams by the second class. He will try to maximize the total satisfaction achieved, assign students to projects for which they're skilled, and allocate some CS and some MS in IS students to each team.

Students will work in teams composed of CS and MS in IS students. Each expertise and talent will support the other, so CS students with weak management and/or language skills can feel comfortable, as should MS in IS students with weak technical skills.

We encourage clients to break projects to 1 and 2 person tasks so team members can work independently.

General Schedule

Class Meeting Schedule

Revised 2/29/96.
  1. Jan-25 Information Technology Projects: Introduction and Logistics
  2. Feb-1 Professor Lecture: Web Publishing and Java Fundamentals; How to Give a Technical Lecture
  3. Feb-8 No Meeting
  4. Feb-15 Professor Lecture: Java Fundamentals
  5. Feb-22 Student Technical Lectures
  6. Feb-29 Student Technical Lectures
  7. Mar-7 No Meeting
  8. Mar-21 No Meeting
  9. Mar-28 Class visit to Andersen Consulting Financial Ideas Exchange
  10. Apr-4 Student Progress Presentations
  11. Apr-11 Student Progress Presentations
  12. Apr-18 Professor Lecture: Topic to be determined
  13. Apr-25 Student Final Presentation Rehearsals
  14. May-2 Student Final Presentation Rehearsals
  15. May-3 Student Final Presentations at Conference and Luncheon with All Clients


Technical presentation

Scheduling and Students Employed Full-time

Some students who work full-time want to take the projects course. They may do so. Class meets most, but not all, weeks. Attendance is mandatory, as class meetings include technical and operational lectures by both students and Prof. Goldberg.

Typically each team meets weekly with the client. However, work for a couple of the proposed projects would be conducted primarily at NYU. Students unable to work at client sites should apply for these projects, and Prof. Goldberg will try to assign them accordingly. If no such projects are staffed, then these students should take the course another time. Resources for running special individual projects are not available.

Students should know that the Projects course, like all graduate CS courses at NYU, demand significant effort. Doing a good job will require an average of 6 - 12 hours of work a week, and students who want to excel will need to devote that level of effort.


All students and client supervisors must read and respond to Internet email daily. All students should join the class mailing list. Send an email to with
subscribe g22_3812_001_spring96
in the message body. Hopefully, the message history can be made available on our Web site. Prof. Goldberg will use it to multicast email to the class. Each project will form its own mailing list.

Each team needs a team liaison responsible for organizing interaction with the client. The liaison's job includes

If you want to be your team's liaison, volunteer.

Each student must send Prof. Goldberg a weekly email progress report on Thursday before class. While this sounds bureaucratic and impersonal, but it's the only way I can efficiently track all the students in the course. Spend 5-15 minutes composing the progress report (so if you work 8 hours/week on the class the report takes at most 3% of class time - not too bad). Writing the report will help you evaluate how you're doing. The report contains:

Please email the report with a subject line of:
Projects; "client";  "week number";
so my software can parse and organize reports.


This document and associated materials were authored or compiled by Arthur Goldberg. This compilation and supporting electronic teaching materials may be freely used for non-commercial use provided any electronic or print version includes this notice. All rights reserved. Copyright Arthur P. Goldberg, 1996.