Personal tools

Sections

Skip to content. | Skip to navigation

You are here: Home → Academics → Syllabi → Spring 2008 Syllabi → M&IS 44048 Spring 2008 Steinberg & Weinroth

Navigation

M&IS 44048 Spring 2008 Steinberg & Weinroth

SYLLABUS

Spring 2008

M&IS 44048 Software Integration

Dr. Geoffrey Steinberg / gsteinbe@kent.edu / A418

Dr. Jay Weinroth/ gweinrot@bsa3.kent.edu / A427

Objective

This course has two objectives:

To develop excellent writing and communication skills.
To learn to work cooperatively on a team while producing professional quality results. Specifically you will be developing a real information system prototype. Thus the course will draw on your analytical, communication and technical skills. You will be working with real clients who have real needs.

Professionalism is expected throughout in comportment and outcome.

This course fulfills the University's writing intensive course requirement. Among various expectations is that you wll be provided at least one opportunity for guided revision of written work.

Class Organization

Students will be assigned to a project team. Each team works on a specific project throughout the semester. Class time will be available for team work rather than for conventional lecture and discussion. Each team will meet with

Thursday with Dr. Steinberg
With Dr. Weinroth to be announced.

There are no regular class meetings on Tuesday except as announced by Dr. Weinroth.
> The emphasis of this course is on writing and communication. This is not a class in which you will be taught new technologies by lecture. The emphasis is not on technologies used to accomplish information system development. As you design your system and develop your prototype you should use technologies that you are already familiar with. The instructor will help with use of technology (programming, database, etc.) as appropriate.
> Each student takes on the roles of analyst and developer. Roles will change as the project demands.

Grading

Your group receives a grade for each phase of the project and all members of the group receive the same grade for each project phase.
Your individual grade will be derived from a review of your work by your peers (see below).
The Kent State grading scale is used:

A	>=90
B	80-89
C	70-79
D	60-69
E	<60

Grades will not be rounded and will not be curved.
No exceptions.
No incompletes will be granted because this is a group effort and if you do not do your part the whole team suffers.
Your grade is composed of individual and group contributions. See the schedule on Orion for details.

Important Note About Your Individual Work

· You are part of a team effort and you and you peers will evaluate each other.

· 50% of your grade is based on your peers' evaluation of your contribution to the team effort.

· Check handouts for an explanation of how peer reviews are conducted.

Etc.

Textbook: None. You have taken the needed courses already. Here you put it all together. Supplement what you need with any other references (management, techinical, etc.) that you need.
> Lateness: Not allowed. No exceptions. Lateness as a professional is not acceptable and it is not acceptable in this class either.
> Attendance: Expected. The standard KSU allowances for absence are permitted with proper documentation. If you frequently miss group or class meetings then it is likely that your peers will give you low grades - they should.
> Computer virus: It is not nice to send a virus to a server. If you do then you may render all group projects useless. So be careful!
> Students with Disability: In accordance with University policy, if you have a documented disability and require accomodations to obtain equal access in this course, please contact the instructor at the beginning of the semester or when given an assignment for which accomodation is required. Students with disabilities must verify their eligibility through the Office of Student Disability Services (SDS) in the Michael Schwartz Services Center (672-2972).
> Backup Your Work: Expected. Your team will be provided space on a server. The server is not backed up. It is your responsibility to maintain backup copies of everything that you develop.