CIS 4339.001 - Project in Computer Science

Fall 2007
Class meets Wednesday 2:40 - 4:30 (TL 1A)
Labs 2:40 - 4:30 Monday & Friday (CC104)

Paul Wolfgang
1041 Wachman
(215) 204-5155

Email: wolfgang@temple.edu

Office hours: Monday, Wednesday, Friday 1:30 - 2:30
Or by appointment

It is best to meet by appointment.  Each team must meet with the instructor at least once per week.  Each meeting will last approximately 30 minutes.

Course Objectives:

• Implementation of a software engineering project with a client

• Utilize standard project management techniques for managing tasks and reporting

• Develop and practice effective presentation styles and skills

• Utilize the Team Software Process

• Participate in lectures and instruction provided by guest lecturers

Course Format:

Students will be assigned projects with clients in the local business community or the university.  They are expected to utilize the skills introduced during the first semester in CIS4298 (W338).

Groups will be introduced to a client with a real business problem.  After meeting with the client, they will engage in data gathering and the development of a Functional Specification and Design Document. 

Groups will present their solutions to the class and the client.  After approval from the client and the instructor, the team will proceed to implement their solution.

Attendance:

ATTENDANCE IS MANDATORY FOR TEAM PRESENTATIONS AND SCHEDULED LECTURES. 

Evaluation:

Grading will be based upon individual performance.  The group will submit the project deliverables, but a review of the weekly task list will be used to assess individual contributions. 

Preparation: teams are expected to be on time for meetings with the instructor.  Teams must submit an updated project task list at each meeting.

Grading:

All deliverables should be submitted earlier than the announced due date.  Groups that submit material before the due date will receive a preliminary assessment of the work product.  They will then have an opportunity to perform any necessary rework prior to grading.  Remember that clients expect "A" quality work from every team.  Therefore, it will be necessary to correct any submissions that the instructor deems unacceptable before submission or presentation to a client.

Schedule:

Texts:

            Facts and Fallacies of Software Engineering
            Robert L. Glass
            Addison-Wesley
            Boston, MA
            ISBN 0-321-11742-5

Recommended Reading

            Introduction to the Team Software Process
           The SEI Series in Software Engineering
           Watts S. Humphrey
           Addison Wesley 1999

Groups:

Each group should have 4 - 5 participants (any other number will require special approval from the instructor.)

One person must be chosen as the group leader.  This person will be the primary instructor contact.

A project plan must be completed by the third week of class.  These documents should be discussed with the instructor before class project presentations.  The project plan must contain:

1. Task list (completed and outstanding tasks)

2. Person or persons responsible for each task

3. Estimated time to completion, completion date, required delivery date

4. Task dependencies

5. Resource requirements

Groups are expected to meet with the instructor at least once a week (approximately 10 meetings); however, more meetings may be scheduled when necessary. 

Basic class policies: 

• Refer to the Temple University Student Code of Conduct for details.

· Plagiarism: Don’t do it.  Cite references and sources.  The reader must not confuse your work with the work of others.

· Cheating: Don’t do it.   The class requirement is that original work be completed for this class.  If there is any doubt about what is acceptable, please ask the instructor.  If you are expanding upon other assignments completed for another class, you must receive permission from the instructor.

Syllabus:

The syllabus lists discussion topics for the first few classes.  Additional topics will be presented as time permits.  Like project requirements, the syllabus is subject to change without notice.

Course prerequisites and co-requisites:

Prerequisite:            CIS4298 (W338) - Software Engineering and senior status.

For details visit:

http://www.temple.edu/bulletin/ugradbulletin/ucd/ucdtoc.html

Disability disclosure:

Any student who has a need for accommodation based on the impact of a disability should contact me privately to discuss the specific situation as soon as possible.  Contact Disability Resources and Services at 215-204-1280 in 100 Ritter Annex to coordinate reasonable accommodations for students with documented disabilities. (Temple University Policy and Procedures Manual)

Academic freedom:

Freedom to teach and freedom to learn are inseparable facets of academic freedom. The University has a policy on Student and Faculty and Academic Rights and Responsibilities (Policy #03.70.02) which can be accessed through the following link: http://policies.temple.edu/getdoc.asp?policy_no=03.70.02.

Last Note:

I would like to suggest that there are some universal project rules that make the lives of project participants and project managers bearable:

Rule 1:  No surprises.  Keep your group leader and instructor informed.

Rule 2:  It is never the responsibility of the project leader to track people down to get status reports.

Some final notes from the Dean's office:

First class: Monday August 27.

Thanksgiving Holiday: November 22 & 23.  Note on Wed. November 21, follow your Friday schedule.

Last day to drop (tuition refund available): Monday, September 10.

Last day to withdraw (no refund): Monday, October 29. Students who have previously withdrawn from the same course, or who have already withdrawn from 5 courses since September 2003 may not withdraw.

Last Class: Wednesday, December 5.

Students who miss the final and do not make alternative arrangements with me will be graded F.